--- "a12795" wrote:
> Is it possible to use Ranish to resize an NTFS partition?

Doc Chiron: here lazybones - learn to use the search function, and NO
I'm not rude - you are! Who has my PMS medicine?

http://groups.yahoo.com/group/partman/messagesearch?query=resize%
20NTFS%20partition

>  Is it possible to use Ranish to resize an NTFS partition?

I guess yes if you make it bigger, but I am not sure the OS will make any
profit of this...

If you mean to make it smaller, answer is certainly no: RPM knows nothing
about NTFS as it should be clear from the screens, so is unable to operate
on its structure. And a keypoint of NTFS is that the mirror copy of the
inode list (MFT) lies precisely... at the end of the partition. So to be
able to shrink it, you should before move this copy in another place...


Antoine

At 18:19 11/01/2005, somebody wrote:

>Is it possible to use Ranish to resize an NTFS partition?

No problemo.
Backup.
Delete the partition.
Create partition the size you want.
Restore everything from backup.
Takes about a week.
There's the rub.

Alternatives
1: XP has built in tool for resizing a partition larger if there is
adjoining free space.
2: Partition Magic will resize it up or down or hither or thither. Get the
right version.
3. You could try going part way through a SuSe Linux 9.1 or greater (IIRC)
install and bail out after resizing the NTFS partition to make way for
Linux. Reboot and use RPM to delete your newly created Linux partitions.
Better still - go all the way with Linux then delete your NTFS partition.

Dermot

At 18:19 11/01/2005, somebody wrote:


>Is it possible to use Ranish to resize an NTFS partition?

Alternative 4:

Download ASPLinux.

For info see
http://www.linuxmafia.com/pipermail/conspire/2002-October/000037.html

Again delete any unwanted partitions after the install.

Try one of the following for the download:

<ftp://ftp-linux.cc.gatech.edu/pub/Linux/distributions/asplinux/i386/7.3/>ftp://\
ftp-linux.cc.gatech.edu/pub/Linux/distributions/asplinux/i386/7.3/
ftp://fddisunsite.oit.unc.edu/pub/Linux/distributions/asplinux
<ftp://ftp.oit.unc.edu/pub/Linux/distributions/asplinux>ftp://ftp.oit.unc.edu/pu\
b/Linux/distributions/asplinux
http://east.dl.sourceforge.net/mirrors/metalab/Linux/distributions/asplinux/
<ftp://ftp.metalab.unc.edu/pub/Linux/distributions/asplinux>ftp://ftp.metalab.un\
c.edu/pub/Linux/distributions/asplinux
http://rpmfind.net/linux/ASPLinux/i386/7.3/
<rsync://download.asplinux.ru::ASPLinux/i386/current/>rsync://download.asplinux.\
ru::ASPLinux/i386/current/
ftp://fr.rpmfind.net/linux/ASPLinux/i386/7.3/
<ftp://ftp.ese-metz.fr/pub/Linux/distributions/asp-linux/i386/current/>ftp://ftp\
.ese-metz.fr/pub/Linux/distributions/asp-linux/i386/current/
http://fr.rpmfind.net/linux/ASPLinux/i386/7.3/
<ftp://ftp.informatik.rwth-aachen.de/pub/comp/Linux/sunsite.unc.edu/distribution\
s/asplinux/>ftp://ftp.informatik.rwth-aachen.de/pub/comp/Linux/sunsite.unc.edu/d\
istributions/asplinux/
http://sunsite.informatik.rwth-aachen.de/cgi-bin/ftp/ftpshow/pub/Linux/sunsite.u\
nc.edu/distributions/asplinux
<ftp://ftp.duth.gr/pub/ASPLinux/>ftp://ftp.duth.gr/pub/ASPLinux/
ftp://ftp.ntua.gr/pub/linux/asplinux/i386/7.3/
<ftp://ftp.fsn.hu/pub/CDROM-Images/asplinux/i386/7.3/>ftp://ftp.fsn.hu/pub/CDROM\
-Images/asplinux/i386/7.3/
ftp://ftp.kddlabs.co.jp/Linux/distributions/ASPLinux/i386/7.3/
<ftp://ftp.kr.psi.net/pub/mirrors/asp-linux/>ftp://ftp.kr.psi.net/pub/mirrors/as\
p-linux/
ftp://ftp.surfnet.nl/pub/os/Linux/distr/asplinux/i386/7.3/
<ftp://ftp.nluug.nl/pub/os/Linux/distr/asplinux/i386/7.3/>ftp://ftp.nluug.nl/pub\
/os/Linux/distr/asplinux/i386/7.3/
ftp://ftp.clear.net.nz/mirror/ftp.asp-linux.com/i386/7.1/
<ftp://ftp.man.poznan.pl/vols/vol1/sunsite/distributions/asplinux>ftp://ftp.man.\
poznan.pl/vols/vol1/sunsite/distributions/asplinux
ftp://ftp.gamma.ru/pub/asplinux/i386/7.3/
<ftp://linux4u.jinr.ru/pub/ASPlinux/i386/7.3/>ftp://linux4u.jinr.ru/pub/ASPlinux\
/i386/7.3/
http://download.asplinux.ru/install/ftp/i386/7.3/



[Non-text portions of this message have been removed]

--- In partman@yahoogroups.com, Dermot Moynihan <der_moyn@o...> wrote:
> Alternatives
> 1: XP has built in tool for resizing a partition larger if there is


Are you talking about the Disk Management tool under the Computer
Management snap-in?

At 22:27 12/01/2005, somebody wrote:


>--- In partman@yahoogroups.com, Dermot Moynihan <der_moyn@o...> wrote:
> > Alternatives
> > 1: XP has built in tool for resizing a partition larger if there is
>
>
>Are you talking about the Disk Management tool under the Computer
>Management snap-in?

I'm referring to the DISKPART command line tool.
Do some research. No doubt Google will tell you all about it.

I still can't figure out how to get more than 4 primary partitions.
I am using XOSL with 2.38 but I have other versions available.  I can
easily enter primary partitions 1 through 4, but when I enter the
next primary partition I cannot enter a number.  Then after a save,
the unnumbered partition is gone.  I'm usually pretty good, but I
think I need the Dummy's guide to this one!

Hi,

When you joined the group you might have recevied a message from group
redaring must read/visit sites. Please review them before asking a question.
That will solve this problem.

Regards,
Rahul.
----- Original Message -----
From: "tonym1" <tonym1@...>
To: <partman@yahoogroups.com>
Sent: Friday, 14 January, 2005 7:18 AM
Subject: [partman] more than 4!





I still can't figure out how to get more than 4 primary partitions.
I am using XOSL with 2.38 but I have other versions available.  I can
easily enter primary partitions 1 through 4, but when I enter the
next primary partition I cannot enter a number.  Then after a save,
the unnumbered partition is gone.  I'm usually pretty good, but I
think I need the Dummy's guide to this one!








--
To unsubscribe, please, email to: partman-unsubscribe@yahoogroups.com

Yahoo! Groups Links

Doc Chiron here: Been busy, but I just couldn't let this THREAD go
uncorrected. Some readers might believe it! My input will be
interspersed to challenge mistakes or misconceptions as I see them
needed.
----------------------------------------------

MSG-3985 From: keithmj1026 <keithmj1026@y...>
Date: Sun Nov 21, 2004 9:27am
Subject: I like it, but a couple of questions


Keith: Hi I just downloaded version 2.40 because it was the stable
version. I used it successfully, but have a couple of questions.

1) Other than being able to have more that 4 primary partitions, what
is different in the latest version 2.44? It sais [says] beta, but
that was a year ago, is 2.44 stable by now?


=========================DOC: =========================
As it is obvious that many folk either have never known or forgotten
the history of version changes, I include here a reminder. Now don't
you'all start crying "homework agin, but it's Friday"

[These extracts are from Mikhail or Muthu's Release notes available
in PART244.ZIP]

Ranish Partition Manager      Version 2.40.00       February 08, 2001
---------------------------------------------------------------------
...First of all, I suggest this version only to the EXPERIENCED users.

Version (2.40) is the same as version 2.38 beta 1.91.
I simply had renamed the program since it was working without any
problems or bugs for almost a year and appears to be very stable.

This version is the latest version of Partition Manager.
There is no other "full" version in exsistance (I wish there was).
This version is a fully functional shareware...

This version supports disks of any size and up to 4 primary
partitions. Unfortunately, it does not support 30 primary partitions
as it was in the previous version. You can download 16-bit version
2.37 from my web site, but it works only on the first 8GB of your
disk. I am planning to add support for more than 4 primary partitions
in the 32-bit version, but it is taking longer than I hoped.


------- Readme for Version 2.42 (Beta by Muthu)  March 09, 2002 -----

Please read this file completely before trying out anything.
This is a long one but it contains some important information that
you need to be aware of.

(As usual, this version is for EXPERIENCED USERS ONLY!
-If you are new to RPM, I suggest you read the URL
-http://www.trombettworks.com/multi-boot.htm   *completely* )

While I have *tested* my changes many times except 2TiB disk limit,
and found them *working* as expected, standard disclaimers still
apply.

Beta v2.42 includes the following new features/changes:

1. A maximum of 31 primary partitions

2. Can restore RPM's MBR in case it was overwritten by some other
    program (e.g.: fdisk /mbr) or after a new OS installation (thereby
    establishing the link to the "lost" RPM partition table).

3. Check for clash/overlap of a *new* partition (found in MBR/EMBR)
    before importing the newer partition into RPM partition table
    (the table used by RPM internally to store all the partition
    information).

4. [Greater than] 128 GiB disk support but only upto 1.99 TiB
     -UNTESTED. (GiB & TiB refer to the SI notation of "binary
    Gigabytes" & "binary Terabytes" respectively. 1 binary Gigabyte
    (GiB) is same as 1 x 1024 x 1024 x 1024 bytes whereas 1 Gigabyte
    is 1,000,000,000 bytes.
    Please see http://physics.nist.gov/cuu/Units/binary.html)

5. "MBR row numbering" related changes in Partition Manager

6. Boot Manager [TEXT80x25] can now support up to 32 primary
    partitions.
    [Actually, that's 32 entries in the RANISH Partition TABLE.]

[Details of the above info are in the README244.TXT file in
PART244.ZIP]


------ Readme for Version 2.43 (Beta by Muthu)  April 12, 2002 ------

Beta v2.43 fixes a bug that prevented some OSes (FreeBSD to name one)
from booting when /boot partitions was located above 8G.

The fix will let you boot Linux or FreeBSD from partitions above 8G,
however it will not make magic and boot DOS from the end of 60G disk.

------ Readme for Version 2.44 Beta / CMD Line  June 09, 2002 ------

Beta version 2.44 combines Partition Manager GUI and command line.
It also have increased buffer size to investigate reported crashes
on some systems (laptops?) when users enter cylinder [values] >
max_cyl_value.  ...Mikhail
==============================================================end Doc:

Keith:
2) I had 1 primary partition of 2 gigs and an extended partition with
an 8 gig (100%) logical drive.

it looked like this:

1 Primary 2gig NTFS
2 Extended
3 logical 8gig Unallocated

That is what I expected to see.

=====================================DOC:
Yes, but do you know what those three lines represent?

1 and 2 make reference to 2 "partition descriptors" in the Master
Partition Table in the MBR.

3 makes reference to a "partition descriptor" in an Extended
Partition Table existing in the first sector of the EXTENDED
partition described in Primary partition descriptor #2.

What appears to be 3 partitions in that list are actually just two.
The second one has the entire remainder of the disk assigned to it.
Although Keith has identified it as LOGICAL, the fact that he
says "8GB unallocated" indicates that in fact NO LOGICAL partitions
have been created yet and the Extended Partition Table is in fact
either empty OR contains an entry indicating that ALL of the
extended partition (minus 1 track of usually 63 sectors).
====================================end doc:

Keith:
I wanted to break the 8 gig unallocated space into 2-4 gig logical
drives in the extended partition.
I created the first logical drive and set the size to 4 gig and then
the structure looked like this:

1 Primary 2gig NTFS
2 Extended
3 Logical 4 gig Fat32
4 Extended
5 Logical 4 gig unallocated

According to that structure, it looks like it created another
extended drive. "I don't want 2 extended drives, I want 2 logical
drives in one extended. How do I control that? Thanks!"

===doc: Answered later.
---------------------------------------------------------------------
MSG-3986 From: Rahul Gupta <rahul.gupta@g...>
Date: Mon Nov 22, 2004 6:44pm
Subject: Re: I like it, but a couple of questions
...
Seems that your question 1 can be only answered by Mr. Ranish...
There is one known bug in it (Which I reported and was confirmed by
Mr. Ranish).

Question 2: I felt nothing was wrong in it, IF it was displayed like
this:

Extended
|_Logical
|_Extedned
|_Logical

But if it is displayed like below then definately something went
wrong:

Extended
|_Logical
Extended
|_Logical

Regards, Rahul.
--------------------------------------------------

MSG-3988 From: keithmj1026 <keithmj1026@y...>
Date: Tue Nov 23, 2004 5:11am
Subject: Re: I like it, but a couple of questions

Hey thanks Rahul! I downloaded version 2.44 and read the readme file.
It looks like 2.44 added some command line switches, but it still
pretty much the same as 2.40.

=====DOC: Then you didn't read enough! Big changes in 2.42.

Keith: It showed my disk organized like:

Primary
Extended
--Logical
--Extended
--Logical

It's not a big deal, but why is that second extended listed if I only
have one extended? For every logical drive I create, will it list it
with an extended before it, eventhough there really isn't and
extended partition there?

=====================================DOC:
This writeup demonstrates the linking character of the extended
partition boot descriptor chain. Read it.
http://www.goodells.net/multiboot/ptedit.htm

Remember:
--1. The PRIMARY EXTENDED DOS partition descriptor entry in the
Master Partition Table describes the entire SIZE and starting sector
of the EXTENDED partition itself, but provides NO information about
ANY LOGICAL partitions contained within.

--2. Every LOGICAL partition has its first track (usu. 63 sectors)
reserved for an EXTENDED PARTITION BOOT RECORD that usually contains
only a 2 entry partition table:

---a. The first descriptor entry is for defining the FileSystem (aka
partition type byte), starting sector and "unofficially"* the size.

---b. The second entry exists in each Extended Partition Boot Record
(except the one whose first entry uses up the remaining sectors of
the EXTENDED PARTITION because its purpose is only) to point to the
remaining unused space and indicate its size.

--3. Although the EMBR only uses the first sector of the first track
of the partition, by convention, the rest of the track remains unused
so that the PARTITION BOOT SECTOR can be found at the first sector of
a track, just like happens to the PRIMARY partition following the MBR.

Here is what the "Sector Usage List" SHOULD look like with EVERY
sector of the drive accounted for:

:start of HDD
MBR (1 sector) containing:
--1.boot code
--2.disk signature bytes for NT-based OSes
--3.Master partition table (all descriptors here are PRIMARY)
----a.slot 1 descriptor: Primary OS partition (reserving 2GB space)
----b.slot 2 descriptor: Primary Extended partition (reserving 8GB)
----c.slot 3 descriptor: unused
----d.slot 4 descriptor: unused

62 UNUSED SECTORS of first cylinder track = 31KB

OS Partition (2GB) including:
--Partition Boot Sector including
----boot code
----BIOS Parameter Table
--Directory & allocation structures
--System & Data area

EXTENDED DOS partition (8GB = remainder of disk) containing:
--1. 1st Extended Partition Boot Record (1 sector) containing:
----a. NO boot code (usually)
----b. Extended Partition Table
------  i. slot 1 descriptor: Logical Data partition
           (bootable OSes here are non-standard)
------ ii. slot 2 descriptor: Link to sectors not allocated here
------iii. slot 3 descriptor: never used
------ iv. slot 4 descriptor: never used

--2. 62 UNUSED SECTORS of first cylinder track = 31KB

--3. LOGICAL DATA partition (4GB) containing:
------ Partition Boot Sector (1 sector) containing:
--------- No boot code (usually)
--------- BIOS Parameter Block Data
------ Directory & Allocation Structures
------ Data area

--4. 2nd Extended Partition Boot Record (1 sector) containing:
----a. NO boot code (usually)
----b. Extended Partition Table
------  i. slot 1 descriptor: Logical Data partition
            (bootable OSes here are non-standard)
------ ii. slot 2 descriptor: unused due to no remaining sectors
------iii. slot 3 descriptor: never used
------ iv. slot 4 descriptor: never used

--5. 62 UNUSED SECTORS of first cylinder track = 31KB

--6. LOGICAL DATA partition (4GB) containing:
------ Partition Boot Sector (1 sector) containing:
--------- No boot code (usually)
--------- BIOS Parameter Block Data
------ Directory & Allocation Structures
------ Data area

ANY remaining sectors in a Partial LAST cylinder.
:end of HDD
===============================================end DOC:

MSG-3990 From: Rahul Gupta <rahul.gupta@g...>
Date: Tue Nov 23, 2004 7:51am
Subject: Re: Re: I like it, but a couple of questions

It's because of a fact that the logical partitions are not
distinguishable without reading the complete structure of the disk.
this is made such that to quickly identify the data and the adjacent
logical partition. And in reality an extended partition [boot record]
exists there to store the information of the following partition
which is logical. "Note the size". you will notice some bytes are
left out. it is occupied by this partition. Regards, Rahul.

====Doc: Correct, but more simply put, the existence of the extended
partition boot records forms a linkage to access the remaining
partitions while providing a "familiar face" to the OS in terms of
obtaining partition details. ==end doc:


MSG-3991 From: keithmj1026 <keithmj1026@y...>
Date: Tue Nov 23, 2004 9:41am
Subject: Re: I like it, but a couple of questions

So for every logical partition there is, in reality, an extended
partition to contain the logical partition.

====DOC: Rather than say you are wrong, let's just change that to
read "for every logical partition, there is an extended sub-partition
or SEGMENT to contain the logical partition and its link to the
BEYOND. ===end doc:

Keith:
So, I use FDISK to create an Extended partition [by defining reserved
space in the MBR's Master Partition Table]. In that extended
partition I create the first LOGICAL partition... [in a portion
of that Extended partition, starting with its associated EPBR track].

When I create the second logical partition, it really creates an
[other sub-portion of the] extended partition inside the original
Extended partition [with its EMBR track as well including the] new
logical partition inside [the original] extended partition?

In that case, if I take the extended partition and divide that into 2
logical partitions, the second logical partition will actually be a
few bytes smaller than the first? That being because the second
logical partition is actually contained in another extended partition.

============Doc:
Since we now know that is not true (ie the partitions are NOT nested
within each other, but rather chained together).
If the original Primary EXTENDED DOS partition was created with an
EVEN number of cylinders.
That is hard to do in fdisk. You must calculate the number of bytes
in a cylinder (512x63x255) and size the partition as an EVEN multiple
of that size). Then you need to use half that amount when specifying
the size of the first LOGICAL partition. The reamaining size should
match when the EMBR tracks are accounted for.
In Ranish you simply make sure the # of cylinders in the Primary
EXTENDED partition descriptor is EVEN.
=========end DOC:

Keith: That's interesting, I didn't know that. Thanks!

*Note: For those who may be confused about the linkage of logical
partitions based on some things you may have read elsewhere, be aware
that there is some differing usage of the value of the "LBA sector
size" field in the 1st Extended Partition Table entry.

[The Primary EXTENDED partition descriptor always contains the
COMPLETE size of the extended partition in its "LBA sector size"
field.]

In each Extended Partition Table descriptor, Ranish always sets
the "LBA sector size" (and psuedo CHS ending sector field entry) to
the size of the sectors used by that LOGICAL partition.

I have read some descriptions of Extended Partion tables that have
that entry set to the same value as in the PRIMARY EXTENDED DOS
partition descriptor. That could be the source of some confusion
concerning the NESTING of partitions. The extant information about
this entry concludes that THAT field data is NEVER used as part of
any calculations by any program. I believe that Ranish's usage is
helpful in both understanding the relationship of the LOGICAL
partitions to each other, as well as being a help in recoving data if
the second entry in that table is damaged. That entry is used to
determine the size of the LOGICAL partition that EMBR is preceding
(or within, depending on your point of view). DOC

Sic 'em Rahul! That's tellin' them!
Shalom,
Doc

Those who use Solaris x86 together with Linux know very well that
its partition ID 0x82 is the same as Linux swap. In the most recent
Solaris 10 (still as beta aka Solaris Express), starting with build
72, Sun introduced a new partition ID 0xbf known as Solaris2, in
order to avoid the problem.

My question is when we could expect Ranish PM to be aware of that
new ID?

http://groups.yahoo.com/group/solarisx86/message/15064

MZ

First off, I am a newbee to the world of drive partitoning, but
otherwise an experinced user.

I have a Maxtor one touch 250GB hard drive. Using with Windows 98SE.
Is RPM a good tool to use to partition this type of drive. Just want
to use the external drive for 1)back up of selected files and 2)to
store audio and media files. If RPM would be appropriate to use, could
someone point me to some step by step guide to do.

Yes, RPM is a good tool (AFAIK), since it relies on Int13x BIOS support, and
this one (assuming your BIOS is up to date) will provide the necessary
services. About the step by step guide, follow the existing documentation,
seen from RPM there is NOTHING special about such a drive (the limit is at
2TB, when the count the sectors will overflow in 32-bit; perhaps at 1TB that
is 1000GB we could have sign problems but I doubt it).

However, perhaps Win98SE is NOT a good OS for such a large drive. I hear
this OS does not natively handle 48-bit LBA (a.k.a. ATA-6)...

Now, if you are aware of the latter and you have some idea of awkward
partitioning (taking into accounts the limits), RPM is probably even more a
good tool to do so! Just go ahead and explain your ideas.


Antoine


-----Original Message-----
I have a Maxtor one touch 250GB hard drive. Using with Windows 98SE.
Is RPM a good tool to use to partition this type of drive. Just want
to use the external drive for 1)back up of selected files and 2)to
store audio and media files. If RPM would be appropriate to use, could
someone point me to some step by step guide to do.

Sorry if I miss your point.

There are a lot of ID that do not show up in the UI of RPM as shipped. I
guess the reason is to keep the list manageable. As an example, I do not see
OpenBSD or NetBSD, yet I believe there are a fair number of them out there;
I grant you few of their admins use RPM; but I am not sure many Solaris 10's
admins use RPM either...

My guess is that the current list is the choice of the last builder; so if
you insist, perhaps the next builder will add it to the list; but then the
question becomes, when will we see a next build?  ;-)


http://groups.yahoo.com/group/solarisx86/message/15064

is 404 for me.


Antoine

-----Original Message-----
Those who use Solaris x86 together with Linux know very well that
its partition ID 0x82 is the same as Linux swap. In the most recent
Solaris 10 (still as beta aka Solaris Express), starting with build
72, Sun introduced a new partition ID 0xbf known as Solaris2, in
order to avoid the problem.
My question is when we could expect Ranish PM to be aware of that
new ID?

Antoine Leca wrote:
> There are a lot of ID that do not show up in the UI of RPM as shipped.


But Ranish PM is known as a fdisk tool that supports Solaris partition
ID.

> I grant you few of their admins use RPM; but I am not sure many Solaris 10's
> admins use RPM either...

Believe or not but Ranish PM is quite popular among Solaris users
(I'd say admins, as real admins don't install more than one OS into
their servers) due to the fact I mentioned above.

> My guess is that the current list is the choice of the last builder; so if
> you insist, perhaps the next builder will add it to the list; but then the
> question becomes, when will we see a next build?  ;-)

It's not that I insist, but it would be appreciated by those users.


--
Mariusz Zynel         University of Bialystok, Institute of Mathematics
                                   Akademicka 2, 15-267 Bialystok, Poland
-----------------------------------------------------------------------
mailto:mariusz@...                office: +48 (85) 745 7552
http://math.uwb.edu.pl/~mariusz               mobile: +48 (604) 777 588

--- "eckerpw" wrote:
> ...newbee to ...drive partitoning,
> but otherwise an experinced user.

> ...Maxtor "one touch" [external USB?} 250GB hard drive.
> Using with Windows 98SE.
> Is RPM a good tool to use to partition this type of drive.
> Just want to use the external drive for:
> 1)back up of selected files and
> 2)to store audio and media files.
> If RPM would be appropriate to use,
> could someone point me to some step by step guide to do.

Doc Chiron here:
That depends -
Since RPM works through the BIOS for drive support, you need to know
what USB support is provided to access the drive from DOS. That could
take the form of direct BIOS support if the BIOS "sees" the USB
device as a drive and enters it into the DISK PARAMETER TABLE during
startup, AND if the motherboard BIOS (I don't think an add-in card's
BIOS would help with a USB drive) supports LBA48 for drives over
128GiB.

Hopefully, you have not yet committed valuable data to the drive such
that you may experiment. If so, I suggest you try using RPM (no
installation required) by running it off a bootable floppy. If
you're using a notebook w/o a floppy, find someone to make you a
bootable DOS (A:) CD with Ranish (and other tools while you are at
it).
Have the drive connected & powered when you power-up your PC and boot
the CD (or floppy).
Run PART243.exe or PART244.exe.
The display comes up in CHS addressing mode looking at HDD 1 (your
internal drive).
Press [F5] to see if RPM sees the EXTERNAL drive. If so, the
indication will switch to DRIVE 2 and the display contents should
change. You want to see if the largest number (often a 512byte sector
count) corresponds to the actual drive capacity. If so you may be in
luck.

A quick test would be to manually create a small FAT32 partition
(1000 or less cylinders):

Force creation of that partition at the top of the drive by:

Highlight the UNUSED list entry.

Press INSERT.

Cursor to the Windows FAT32 entry.

Press Enter.

Highlight the "starting cylinder" field, and change it to a value
1000 (or your chosen value) less than the maximum shown in the ENDING
CYLINDER field. The idea here is to force access to the drive above
the 128GiB point.

Set the STARTING HEAD & SECTOR fields to 0 and 1 respectively (if not
already set).

The ending CHS values should already be set at CYLmax,HEADmax,SECmax
(often = CYLmax,255,63).

With the highlight anywhere on that row, press F to format and choose
the QUICK version for the test.

When done, the bottom-right window will show a partial BIOS PARAMETER
BLOCK (of the new VOLUME's Partition Boot Sector) including it
default name, FAT type, FAT size, and storage values. Also look for
the designated drive number (probably 129 or close higher value).
If you can do all that, you are probably okay. I'd test access to the
partition from Win98 (using the supplied Maxtor driver(s), as win98se
does not natively support 48bit LBA).

If all seems well go back to RPM and set the partitions up however
you like. And don't forget to do the required reading.
Especially: http://www.goodells.net/multiboot/
DOC

Doc Chiron here:
For ANY partition systemID (i.e. filesystem) type that RPM does not
directly support there is a reasonable work-around:

Use RPM to create a FAT32 partition of the size and in the location
you want, but don't bother to format it. Do go ahead and save the MPT
or EPT to disk by pressing [F2].

Then use either PTEDIT run from DOS (or a bootable DOS diskette), or
PTEDIT32 from Windows95B, (or higher) to change the systemID.

Owners of Partition Magic (many versions) by PowerQuest or Symantec
have them on their installation CDs.
Everyone else can find them at: ftp://ftp.symantec.com/public/

Warning: There are many, many languages supported there so let there
be no pushing or shoving to get your copy. (I bearly spreek Engrish,
so I have no experience with the other language versions.)

PTEDIT (both versions are GUI) is a GREAT (and handsome)
partition "TABLE" editor. It doesn't support/recognize Solaris
systemIDs but wait, you can add them yourself. PTEDIT comes with a
TXT file of partition types, so you can edit it to include any
systemID you like (and you get to name it too).

Actually, on a NEW drive, you can use it instead of RPM to create
partitions, but FORMATTING is NOT supported at all.

Although not apparent at first, there is support for EXTENDED BOOT
RECORDS via the EMBR button below the table that is NOT grayed-out
when a Primary Extended DOS partition exists. You'll note how closely
the EMBRs resemble the MBR with only max2 entries: the first of 2 is
always a LOGICAL partition descriptor (unless it has been deleted)
followed by an EXTENDED PARTITION BOOT RECORD LINK to the next EMBR.

There is a useable help file, and is very user friendly, but there
are no protections (i think) to prevent you doing grievous harm to
you existing partitions - be careful.

While at the ftp: site, poke around and get some of the other tools
there as well. There's a little head ZIP thing that contains 2 useful
programs:

[Excerpts from the HEAD.ZIP readme]

1) MBRUtil.exe (Windows Version)  2) MBRUtilD.exe (DOS Version)
3) WipeTrk.exe (Windows Version)  4) WipeTrkD.exe (DOS Version)

MBRUtil.exe (and MBRUtilD.exe)
This utility will save the Master Boot Record (the first sector on
the first hard drive) to a file. It will also restore the contents of
a file to the MBR. It can be used to save the first head (sectors 1
through 62 on most drives) to a file. It will also restore the
contents of a file to the first head.

WipeTrk.exe (and WipeTrkD.exe)
This utility will clear the contents of the first track (a.k.a. head)
on the first hard drive with the exception of the MBR (the first
sector). If the drive has 63 sectors per track, this utility will
clear out (e.g. set all bytes to zero) sectors 2 through 63. It has
an optional parameter (a file name) that can be used to save the
contents of the first track to a file prior to clearing.
======end cite:

DOC enough for now.

P.S. The following is excepted (w/o permission) from:
http://www.goodells.net/multiboot/tools.htm

** Warning: older versions of ptedit.exe cannot edit the boot record
of hidden NTFS partitions. There are several versions of ptedit.exe
that identify themselves as "Version 1.0", so check the file date.
Versions prior to the 10/22/1999 version (filesize 494,922 bytes)
reportedly have this bug. If you are using an older version (and note
PowerQuest has not updated their ftp site as of this writing), the
solution to editing hidden NTFS boot records is simple: use
ptedit.exe to change the partition type from "17" (hidden NTFS)
to "07" (regular NTFS), then edit the boot record, then change the
partition type back to "17".

That is MUCH too complex for such an easy task.

If you want to create a partition with some ID that is not
prelisted, after pressing INS a first time and observing
that indeed BF is not in the list, just press INS a second
time (hint: "Custom code"), you'll have a window asking you
to type in two hexa digits. Done.

This way you can even create Solaris10 partitions that are
then hidden from normal Windows (on 2.37, or 2.42+)  ;-)


Antoine

-----Original Message-----
Doc Chiron here:
For ANY partition systemID (i.e. filesystem) type that RPM does not
directly support there is a reasonable work-around:

Use RPM to create a FAT32 partition of the size and in the location
you want, but don't bother to format it. Do go ahead and save the MPT
or EPT to disk by pressing [F2].

Then use either PTEDIT run from DOS (or a bootable DOS diskette), or
PTEDIT32 from Windows95B, (or higher) to change the systemID.

Antoine Leca wrote:
> If you want to create a partition with some ID that is not
> prelisted, after pressing INS a first time and observing
> that indeed BF is not in the list, just press INS a second
> time (hint: "Custom code"), you'll have a window asking you
> to type in two hexa digits. Done.
>
> This way you can even create Solaris10 partitions that are
> then hidden from normal Windows (on 2.37, or 2.42+)  ;-)


I like it. But:
1. I'm using RPM for a long time but didn't know that functionality,
     so how a casual user could?
2. it would be much better to have Solaris partition recognized
     and listed as such by RPM. Not many fdisk tools is able to do
     that.

Any way, thanks for the tip!



--
Mariusz Zynel         University of Bialystok, Institute of Mathematics
                                   Akademicka 2, 15-267 Bialystok, Poland
-----------------------------------------------------------------------
mailto:mariusz@...                office: +48 (85) 745 7552
http://math.uwb.edu.pl/~mariusz               mobile: +48 (604) 777 588

I'm a newbie to partition manipulation and multibooting but an
experienced user otherwise. I've read all the recommended readme and
FAQ files in the files section of this group but I can't seem to find
the answer to my question (or else I missed it..). Although RPM can
manipulate partitions on two drives, everything I have read seems to
deal with multibooting on a single drive. What I want to do is have
one or more operating systems in appropriate partitions on the IDE
master hard drive and have one or more different operating systems on
the IDE slave and be able to boot to an operating system on either
drive at system startup time. Is this possible with RPM? If not, how
about other partition managers?

Sincere thanks,
Bill Moon

Użytkownik billmoon1944 napisał:
> I'm a newbie to partition manipulation and multibooting but an
> experienced user otherwise. I've read all the recommended readme and
> FAQ files in the files section of this group but I can't seem to find
> the answer to my question (or else I missed it..). Although RPM can
> manipulate partitions on two drives, everything I have read seems to
> deal with multibooting on a single drive. What I want to do is have
> one or more operating systems in appropriate partitions on the IDE
> master hard drive and have one or more different operating systems on
> the IDE slave and be able to boot to an operating system on either
> drive at system startup time. Is this possible with RPM? If not, how
> about other partition managers?

Yes, definitely. You need to install RPM into both drives. Use
TAB key to switch between drives.

MZ

--- In partman@yahoogroups.com, Antoine Leca <aleca@a...> wrote:
> Hi,
>
> Sorry to have missed your post earlier.
>

[snip]

Hi Antoine;

Sorry for taking so long to get back to you on this, but I'm self
employed and had to work on the paying projects. Anyway, I found some
time this evening to follow your suggestions.

Works like a champ! Thank you!!!!!

For those interested, here are my step-by-step instructions:

1) Booted box from DOS floppy and used RPM to copy XP (NTFS)
partition.
2) Used F4 key in RPM to note starting sector for copied XP partition
(not really needed).
3) Re-booted box into 1st XP partition (remember I have DOS v6.2, XP,
and 2nd copy of XP).
4) Used XP disk manager to assign drive F: to 2nd XP partition.
5) Labled drive C: as "C: Main".
6) Labled drive F: as "F: Backup".
7) Changed background color of the desktop on 1st XP partition to
another color so I can easily see which copy of XP is booted.
8) Clicked <START>, <RUN>, and ran REGEDT32.
9) Loaded hive from 2nd XP partition as per Antione's instructions
as "ccs_f".
10) Modifed the C: drive's key in the just loaded partition to match
the F: drive's key in the existing hive.
11) Unloaded hive "ccs_f".
12) Re-booted box to DOS and used RPM to hide 1st XP partition.
13) Re-booted box and am able to boot the 2nd XP partition (no need
to change boot.ini if 1st partition is hidden).

Hope this helps someone else.

Charles...

Mariusz Zynel wrote:
> 1. I'm using RPM for a long time but didn't know that functionality,
>     so how a casual user could?

Remember: RPM is for experienced users only. No casual users in sight ;-)

I do not know if anyone have access to the web site; this hint could be
helful to hide in some point of the FAQ...

> Any way, thanks for the tip!

You are welcome.


Antoine

> Works like a champ! Thank you!!!!!

You are welcome. I am happy you solve your problem.


Antoine

Antoine Leca wrote:
> Mariusz Zynel wrote:
>
>>1. I'm using RPM for a long time but didn't know that functionality,
>>    so how a casual user could?
>
>
> Remember: RPM is for experienced users only. No casual users in sight ;-)

Yes and no. Solaris (haven't tested latest b74l3 build yet) uses
a bit different CHS geometry/logic. In result a partition created
with Solaris fdisk is not aligned on cylinder boundary from view
of other fdisk tools. BTW RPM has no problem with that, but most
like Partition Magic gets confused and refuses to run.
So the main use of RPM, by most casual users I've been thinking of,
is to create Solaris partition prior installation of the OS if
it's going to be a multiboot environment.

BTW try to google "solaris ranish". You'll find many references
even from Sun websites.

--
Mariusz Zynel         University of Bialystok, Institute of Mathematics
                                   Akademicka 2, 15-267 Bialystok, Poland
-----------------------------------------------------------------------
mailto:mariusz@...                office: +48 (85) 745 7552
http://math.uwb.edu.pl/~mariusz               mobile: +48 (604) 777 588

Hello I've just d/l'd and used RPM for the first time.  I created the
boot floppy.  But I don't seem to understand the output it's giving me

                              c      s      h      c      s      h
0 MBR    Master Boot Record  0      0      1      0      0      1
1 PRI    Unused              0      0      2      0      0     63
2 >PRI 1 Unknown (0x44)      0      1      1  10336    239     63 (??)

About 2,  I can boot up this disk ok.  It has Fat32 on it.  But I have
several partions which it does not see.  I have a seperate partition
for C - H.

Partition magic see's these partitions and it says they're type 0x0b,
and the extended partition is 0x0F.  Here is what pm see's

================================================================================\
===========================
Partition Information for Disk 1:    76,316.1 Megabytes
Volume         PartType    Status    Size MB    PartSect  #
StartSect  TotalSects
================================================================================\
===========================
C:WINDOWS      FAT32       Pri,Boot  4,230.3           0  0
63   8,663,697
                ExtendedX   Pri      72,085.8           0  1
8,663,760 147,631,680
                EPBR        Log      10,402.4        None --
8,663,760  21,304,080
D:APPS         FAT32       Log      10,402.4   8,663,760  0
8,663,823  21,304,017
                EPBR        Log      10,247.3   8,663,760  1
29,967,840  20,986,560
E:WINARCHIVE   FAT32       Log      10,247.3  29,967,840  0
29,967,903  20,986,497
                EPBR        Log       5,123.7  29,967,840  1
50,954,400  10,493,280
F:PICS         FAT32       Log       5,123.6  50,954,400  0
50,954,463  10,493,217
                EPBR        Log         760.4  50,954,400  1
61,447,680   1,557,360
G:SECURITY     FAT32       Log         760.4  61,447,680  0
61,447,743   1,557,297
                EPBR        Log      10,247.3  61,447,680  1
63,005,040  20,986,560
H:ARCHIVE      FAT32       Log      10,247.3  63,005,040  0
63,005,103  20,986,497
                Unallocated Log      35,304.6        None --
83,991,600  72,303,840

--- "kj6loh" wrote:
> Hello I've just d/l'd and used RPM for the first time. I created
the boot floppy.  But I don't seem to understand the output it's
giving me
>                              c      s      h      c      s      h
> 0 MBR    Master Boot Record  0      0      1      0      0      1
> 1 PRI    Unused              0      0      2      0      0     63
> 2 >PRI 1 Unknown (0x44)      0      1      1  10336    239     63
(??)

Doc Chiron here:
First: You transposed your SECTOR and HEAD headings in the table.
Second: You made NO or a feeble attempt to search the internet
to answer your question, so after doing so for you, I found these to
read:

Partition types, Andries Brouwer, aeb@..., 2004-12-12
http://www.win.tue.nl/~aeb/partitions/partition_types.html#toc1
the meat is here:
http://www.win.tue.nl/~aeb/partitions/partition_types-1.html

http://startup.iamnotageek.com/srch-GoBack.html
http://www.sysinfo.org/startuplist.php?
letter=&filter=&count=50&offset=1850
http://www.mysuperpc.com/pc_assembly/computer_sisoft_sandra_benchmarks
.shtml

You failed to mention that you are running GoBack, and you obviously
didn't read the fine manual. During the GoBack startup there is an
opportunity to boot from a floppy, use it to boot the Ranish Floppy!
Then things will look better! Booting from the floppy alone bypasses
the structure that GoBack has created for your BOOT Volume!

Much like the dreaded DDO (Disk Manager) that is installed to ADD
BIOS enhancements, GoBack needs to do the same thing for a different
reason; it needs to load its journaling code before your OS boots
from the HDD.

If you are running as DOS/Windows OS (Win95b thru WinME), you can run
PART24x.exe from an MS-DOS window within Windows. As long as you
operate as if you were in a read-only mode (i.e. MAKE NO CHANGES).
You should see the same RPM info as when run from the GoBack floppy
boot point. (I hope you read that stuff above.)

I stopped using GoBack when I forgot to turn it OFF (you lose all
history data when you do that) prior to running DEFRAG and my volume
got trashed (You ARE WARNED!). Goback makes a valiant attempt to
track all of the data movement, but probably runs out of storage
space before finishing. PLUS the GoBack storage space itself is being
moved during the defrag. (I think of it as trying to wash the windows
on a 747 while in-flight!)

Hope this helps. Doc Chiron

That should have read:
...I think of it as trying to wash the windows on a 747 while in-
flight, from the outside!
Doc

I might have been better off if the GoBack storage was on a DIFFERENT
VOLUME.

First: oops my bad
Second:  Actually I did do some investigation and all I could find was
that it was a chain loader.
I had GoBack installed but disabled.  not uninstalled.  So it never
occurred to me that it was still on the machine.  But when I went to
Add/Remove Programs sure enough it was there.
So thanks for figuring out that GoBack was still on my machine.  BTW I
was just using RPM to look at my partitions, I'm not going to change
anything (yet...).
--- In partman@yahoogroups.com, "doc_chiron" <doc_chiron@c...> wrote:
>
> --- "kj6loh" wrote:
> > Hello I've just d/l'd and used RPM for the first time. I created
> the boot floppy.  But I don't seem to understand the output it's
> giving me
> >                              c      s      h      c      s      h
> > 0 MBR    Master Boot Record  0      0      1      0      0      1
> > 1 PRI    Unused              0      0      2      0      0     63
> > 2 >PRI 1 Unknown (0x44)      0      1      1  10336    239     63
> (??)
>
> Doc Chiron here:
> First: You transposed your SECTOR and HEAD headings in the table.
> Second: You made NO or a feeble attempt to search the internet
> to answer your question, so after doing so for you, I found these to
> read:
>

Hi guys, first post & I already bring-up very serious problem that I am facing
right now.
Hopefully you guys can help me out...........

My computer setup:
Pentium II 350 Mhz with 32 + 64 MB memory
HD 1: Maxtor 40 Gb
partition 1: primary NTFS Windows 2000 (my system) = 6Gb
partition 2: primary Fat32 Windows 98 SE (my wife)= 4Gb
partition 3: primary Fat 32 Windows 98SE (my Son)= 4Gb
partition 4: logical, containing:
     500mb  fat32:swap file
     100mb  XOSL
     1Gb      fat32:photo files
     1Gb      fat32:data files
     8 Gb     fat32:downloaded stuff
     rest      empty
HD 2: Quantum 3.2 Gb
empty space
logical partition

First problem:
While booting to "my wife", system hang (& I heard loud strange Movement of HD)
& upon restart HD 2 is gone - also from "my system" & "myson" (even bios only
saw one hd). I first thought  the aging HD 2 broke ...(but I later on found out
that HD 2 is still working perfectly. I disconnected HD 1 & made HD 2 as
primary, BIOS immediatelly recognized on boot & I can also install win 2k on
empty space. But also this system could not recoqnize my logical partition on HD
1 - that I put as slave now)
Second problem:
all 3 systems crashed (completely failed to boot). I can only get to "my son" in
dos.
What is worst, suddenly logical partition got converted to unknown partition
(Ranish reported as one unknown type partition whereas partition magic reported
as one EB type partition)

My big concern: HOw to get  all my data (photo, data files, & downloaded stuff
back)?
Please help anyone !! I really desperate

Another question if I delete that EB partition using partition magic floppy,
will it destroy all data on it or it just delete the partition so that I can
make the logical partition & try to recreate those partitions? Using Ranish I
can not delete the partition but It offered to erase instead. Same question,
will it erase all data on it?? Reading Trombettot, It said Ranish did not
actually delete the partition, it only erased from MBR, but what about
erase?????????

Prior to this problem I had different setup with Similar problem:
HD1:
primary 1 : Win 98 my system
primary 2:  Win 98 my wife
primary 3:  empty
Logical:
1: XOSL
2: Linux swap
3: Linux
4: Photo file
5: Data file
6: downloaded stuff

HD 2:
at first : empty space + one logical
then it became:
1: primary Win 98 game (my son)
2: logical old stuff

Using XOSL I hide both partition of HD 2 from "my system" and "my wife"
I also hide all partitions of HD 1 when on "my son"
No problem with this setup.

Probably due to virus infection, "my son" crashed. I deleted it s0 HD 2 is back
to original setup, i.e.:
1: empty
2: logical = old stuff
Here comes odd problem:
If I unhide logical old stuff both "my system" & "my wife" did not boot (just
hang). However Linux has no problem whatsoever reading old stuff.

I then ghosted "my system" to empty primary 3 for my son. Strange enough, the
new my son had no problem with logical old stuff but instead It cannot read any
partition on HD 1 logical partition (Photo, data, & downloaded stuff).
I had partition magic installed on "my system" & it read all partitions with no
problem but the same partition magic ghosted to "my son" read logical partition
on HD 1 as EB partition.

2 months ago I decided to reformat & created the above system.............
Please anyone help me rescuing those valuable data back.

Thanks.




---------------------------------
Do you Yahoo!?
  Yahoo! Search presents - Jib Jab's 'Second Term'

[Non-text portions of this message have been removed]