Hello,

Just wanted to give a positive feedback on the latest release.
I managed to get things working again, which could not be done with
the one-click tools.

Just two suggestions for future improvements:
1. Before I found an old version of your program on my harddisk, I
was searching the webb for tools like yours.  I found a lot of
programs, which were not very useful, but somehow I did not find
links to your page.  Maybe you should add some more keywords to your
pages, to help people finding them.

2.  You have short explantaion about logical drives in your primer.
maybe it would be helpful to add a couple of more words to it.  Esp.
about the difference between Extended-LBA and Extended, and why there
is no extended partiton around the first logical drive.  I got my
things working, but still I did not realy understand the details of
what I was doing.

Once again, many thanks to the author for writing this excelent
utility.

martin

Just a note to say I just used Partman for the first time to resize
the primary partion on a laptop, create new partition in unallocated
space.  Now I have a functioning dual boot W98/W2K system.  Thanks
Michail!!!!!!!  I'm stoked, what a great program.
Thanks a million!

Hi!

I have just tried to install WIN98, WINNT 4 Server and W2K Server on
separate partitions.

First, the installation went smoothly except that during the install,
the process still show the other partitions, even though in the RPM,
it has been toggle to the hidden mode. Also, after install (in NT and
W2K), the other (supposedly hidden)partitions continue to be visible
in Disk Management(NT/W2K). Is the behaviour normal?

I am confused after read the Trombett Multi-boot article on the usage
of the Boot Manager within RPM, is it absolutely necessary? Why
allocate as partition 4???

For the above 3 O/S, I hv specific problems with NT. In RPM, whether
I have chosen as NTFS partition or first FAT-16 and afterwards
convert to NTFS, I get Blue Screen during booting up. The problem
does not appeared if I remain as FAT-16 partition.

I have no problems with W2K on NTFS partition, has anyone got a
similar encounter?

Thanks in advance.


Regards
Chee Seng

1. Create a partition thru RPM for the OS you are going to install

2. Make it the first partition in MBR (it is easy to remember if all
your OSes are assigned the first partition in MBR - before booting
them). While it is possible to assign it another number (<=4), it is
better it is assigned 1 for the abovementioned reason.
(You can make it active also).

3. Boot the system and install the OS into this new parition.

4. When you reboot, you will see the newer partition automatically
added in the boot manager menu (if you have installed "Text" boot
manager).

     Note that there may be a glitch in "Text" boot manager that it has
problems booting OSes above 8GB except Linux. It is documented near
the end of the README (using LILO to boot FreeBSD above 8GB). So you
might have to try using LILO to boot these other OSes (I know it is
not an elegant solution but this is one workaround I can think of).

     I will try to fix this problem if I find some time.

Regards,
Muthu
--- In partman@y..., "Infinity" <chaos_infinity@h...> wrote:
> Hi,
> I understand that Partition Manager can create up to 31 primary
partitions on a drive. Could someone please tell me how I would go
about installing operating systems on them? I assume I would need a
utility such as BootMagic to switch between boot partitions - as I do
now - but I seriously doubt that BootMagic would allow booting from a
primary partition with a number in excess of four.
>
>     Stuart,
>     aka Infinity.
>
>
>
> [Non-text portions of this message have been removed]

>     Note that there may be a glitch in "Text" boot manager that it
has
> problems booting OSes above 8GB except Linux. It is documented near
> the end of the README (using LILO to boot FreeBSD above 8GB). So you
> might have to try using LILO to boot these other OSes (I know it is
> not an elegant solution but this is one workaround I can think of).

     Can someone try out whether it is possible to boot other OSes
above 8GB (installation should go thru fine and if the OS supports
booting >8GB) and post it to the list please?

Regards,
Muthu

>     Can someone try out whether it is possible to boot other OSes
> above 8GB (installation should go thru fine and if the OS supports
> booting >8GB) and post it to the list please?

I cannot try this at the moment.
A friend of mine said this: if the bios supports HDs > 8GB you can boot from
above 8GB. If the bios does not support HDs > 8GB you can still see the full
HD once booted, if the OS bypasses the BIOS, however you have to boot from
below 8GB.
Same for HDs > 160 GB.
I don't know if this is correct or not... might be not :-)
Regards

--- In partman@y..., "no_carrier" <no_carrier@l...> wrote:
> >     Can someone try out whether it is possible to boot other OSes
> > above 8GB (installation should go thru fine and if the OS supports
> > booting >8GB) and post it to the list please?
>
> I cannot try this at the moment.
> A friend of mine said this: if the bios supports HDs > 8GB you can
boot from
> above 8GB. If the bios does not support HDs > 8GB you can still see
the full
> HD once booted, if the OS bypasses the BIOS, however you have to
boot from
> below 8GB.
> Same for HDs > 160 GB.
> I don't know if this is correct or not... might be not :-)
> Regards

What your friend told you is correct. But I was referring to booting
the OS through "Text" bootmanager (BM) from above 8GB. As I mentioned
in 2.42 README, I had trouble booting FreeBSD (Win98 too, IIRC) from
above 8GB with Text BM but linux worked. I got a private mail too
which talked about windows having problems like this.

At the same time, if I use compact BM, I can boot the same OS from
above 8GB!!!

I don't have a setup now to test this and hence this request :-). If
anyone is successful, please do post to the list (otherwise also).
In my test setup earlier, I could never get 2.40 working. So I
concluded that the problem may be specific to my test system.

Regards,
Muthu

Hi,
Some days ago, I joined the group with some questions.
Thanks to Ed, Magda and Mark for their replies.

Following their advices, I started to play with partitions and
booters.
I also performed some research in the net.
Now I am happy with my configuration, and I want to share some of my
findings:

Resizing.
I combined the features of Partman and Presizer to get "expandable"
partitions that can grow without copying or reformatting. For a new
partition you can use Partman to define and format it at its maximum
foresaw size, again with Partman shrink it to the initial desired
size using the procedure described in the Partman doc. For an
existing partition, you may use Presizer to expand it, then Partman
to shrink. (Presizer works like a format preserving the data). Once
prepared in this way, if in the future you need to expand the
partition, simply use Partman to change the size (using the same
procedure for shrinking but increasing the numbers). I tested with
Windows 98 and it recognizes the size set at the boot sector, not the
real size, I guess other OS too. Of course, both figures must match
to be safe.

Booting.
I learned in an excellent paper by Andries Brouwer
http://www.win.tue.nl/~aeb/linux/largedisk.html
that with current state of the art it is impossible for a booter
confined to the small boot sector to address more than 8GB. That is
why most OS cannot be booted beyond.
There are special booters, like GRUB http://www.gnu.org/software/grub/
that can do that using a trick. There are two parts: a mini booter in
the boot sector and the real booter in a partition (host or own) in
the low part of the HD. The mini booter loads the real booter, who in
turn uses drives (host OS or built in) to load the OS kernels from
any part of a large disk.
Unfortunately, neither Partman Boot Manager nor XOSL behaves that way
even if you load them in their own partition.
I decided no to rely in such sophistication, but to concentrate all
my bootable partition in the low area. To keep them as small as
possible I will have my user data in separate logical drives in an
extended partition in the high area. It is possible to have just the
kernels in the primary partitions and the add-on software in the
logical drives but I guess 8GB are big enough for all my software
needs.

Copying.
Partman can copy partitions without problems but it copies the FAT
also, so the target partitions must have a compatible FAT size or the
resultant size info will be incompatible. Since my purpose is to have
hidden partitions as backup, I gave my backups the same size.
Interesting is that if I copy a shrunk partition the target is an
expandable partition also. My copies are logical drives in the high
area since I don't need to boot them.

OK, I am set. Thanks again.

Oscar Rojas

Hi,
Some days ago, I joined the group with some questions.
Thanks to Ed, Magda and Mark for their replies.

Following their advices, I started to play with partitions and
booters.
I also performed some research in the net.
Now I am happy with my configuration, and I want to share some of my
findings:

Resizing.
I combined the features of Partman and Presizer to get "expandable"
partitions that can grow without copying or reformatting. For a new
partition you can use Partman to define and format it at its maximum
foresaw size, again with Partman shrink it to the initial desired
size using the procedure described in the Partman doc. For an
existing partition, you may use Presizer to expand it, then Partman
to shrink. (Presizer works like a format preserving the data). Once
prepared in this way, if in the future you need to expand the
partition, simply use Partman to change the size (using the same
procedure for shrinking but increasing the numbers). I tested with
Windows 98 and it recognizes the size set at the boot sector, not the
real size, I guess other OS too. Of course, both figures must match
to be safe.

Booting.
I learned in an excellent paper by Andries Brouwer
http://www.win.tue.nl/~aeb/linux/largedisk.html
that with current state of the art it is impossible for a booter
confined to the small boot sector to address more than 8GB. That is
why most OS cannot be booted beyond.
There are special booters, like GRUB http://www.gnu.org/software/grub/
that can do that using a trick. There are two parts: a mini booter in
the boot sector and the real booter in a partition (host or own) in
the low part of the HD. The mini booter loads the real booter, who in
turn uses drives (host OS or built in) to load the OS kernels from
any part of a large disk.
Unfortunately, neither Partman Boot Manager nor XOSL behaves that way
even if you load them in their own partition.
I decided no to rely in such sophistication, but to concentrate all
my bootable partition in the low area. To keep them as small as
possible I will have my user data in separate logical drives in an
extended partition in the high area. It is possible to have just the
kernels in the primary partitions and the add-on software in the
logical drives but I guess 8GB are big enough for all my software
needs.

Copying.
Partman can copy partitions without problems but it copies the FAT
also, so the target partitions must have a compatible FAT size or the
resultant size info will be incompatible. Since my purpose is to have
hidden partitions as backup, I gave my backups the same size.
Interesting is that if I copy a shrunk partition the target is an
expandable partition also. My copies are logical drives in the high
area since I don't need to boot them.

OK, I am set. Thanks again.

Oscar Rojas

Mark,

Have you already solved your problem? If the answer is yes, tell us
about it, as we may learn something new from your experience.
If not, let us go over it once again.

Every modern hard drive has its own embedded controlers that (among
other things) remember different drive settings. Most of them are
invisible to users, some of them can be set with system BIOS. BIOSes
detect _current_ drive settings, but can be told to change them. I
say BIOSes, because they come from different producers (AMI, Award,
IBM, Phoenix etc.) for different mainboards (...). I do not know,
which is yours, but I assume that it has the standard functionality
of them all. Can you name your BIOS?

> I think I have followed your instruction correctly. I am not sure
about the forcing the drive to change? Does this happen by just
reading a file or do you have to do something else?

It is done by changing BIOS settings. The tip about booting into text
mode/command line/safe mode and reading some files comes from my own
personal experience with some drives that did not want to reset their
mode until I read something from them.

> When I change the parameters in the bios I have only changed the
cyl , head , sec numbers and nothing else. do I have to change the
mode or anything else? or does this happen automatically when the
other numbers are changed.

Yes, you have to change LBA/CHS mode flag. Depending on the BIOS
brand it is either a field named "Mode" with possible
values "Auto/CHS/LBA/None or ---" or a field named "LBA mode" with
possible values "Yes/No" or someting along these lines. Changing only
numbers is not enough and can be misunderstood by the BIOS and system
software.

> My Linux partition can be easily formatted as there is nothing on
it. My windows partition has a bit but can be moved to another
partition on my first drive so I can start from scratch if need be.

Do you have two drives? What is the actual layout of your storage
media?

> But will formatting the whole drive and re partitioning the drive
fix this problem?

I do not think so, as the LBA/CHS mode belongs to lower level drive
management than partitioning and formatting.

Magda

I have some questions regarding LBA. Firstly, what is it? Secondly, I
have a 5GB FAT-32 partition that shows up as Windows FAT-32 in RPM.
But before I partitioned my HD (which is 30GB in total), RPM showed
that the HD was a Windows FAT-32 LBA. Also, I created an 18GB FAT-32
partition and that showed up in RPM as Windows FAT-32 LBA. Now, on
the 5GB, I installed WinME, and it's working fine. Do I need to make
the 5GB partition a Windows FAT-32 LBA partition? Or can I leave it
the way it is? Thanks for the help.
Hiran

I'm getting a message in RPM saying that the boot sector of my VFAT
Extended partition doesn't have enough information (or something like
that). Here are the settings I've set for the partition:
                              Start               End         Size (KB)
                           C    H    S        C    H    S
Pri 3 VFAT Extended LBA  637  150   57     1,338 221   63    5,633,022
Log   Linux ext2fs       637  151   57     1,275  33   63    5,121,021
Ext   Extended          1,275  34   1      1,338 221   63      511,969
Log   Linux swap        1,275  35   1      1,338 221   63      511,938

Again, the problem is that the VFAT Extended LBA partition's boot
sector doesn't have enough information. Why am I getting that? And,
what should I do about it? I don't have Linux installed yet, but
should I go ahead and install Linux? Thanks for the help.
Hiran

that is one of those issues you really don't need to worry about. the reason
they are the way they are is because rpm took care of it all for you. lba
stands for logical block addressing: all you need to know about it is that
it is used to address those partitions whose cylinders are greater than 1023
(1024 and beyond). so the reason your 5gb is not lba is because it is within
the first 1024 cyl. the reason your 18gb is is because it ends past cyl
1023. hope this helps.

--jibben
----- Original Message -----
From: "hiranwatson" <hiranwatson@...>
To: <partman@yahoogroups.com>
Sent: Sunday, April 07, 2002 2:15 PM
Subject: [partman] LBA


> I have some questions regarding LBA. Firstly, what is it? Secondly, I
> have a 5GB FAT-32 partition that shows up as Windows FAT-32 in RPM.
> But before I partitioned my HD (which is 30GB in total), RPM showed
> that the HD was a Windows FAT-32 LBA. Also, I created an 18GB FAT-32
> partition and that showed up in RPM as Windows FAT-32 LBA. Now, on
> the 5GB, I installed WinME, and it's working fine. Do I need to make
> the 5GB partition a Windows FAT-32 LBA partition? Or can I leave it
> the way it is? Thanks for the help.
> Hiran
>
>
>
> --
> To unsubscribe, please, email to: partman-unsubscribe@yahoogroups.com
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

errrr im not positive but i believe that it doesn't like you to end a
partition oddly. meaning, you should go to the last head and sector of that
cyl. and then you should start the next one fresh on a new cyl. hope this
helps.

--jibben

----- Original Message -----
From: "hiranwatson" <hiranwatson@...>
To: <partman@yahoogroups.com>
Sent: Sunday, April 07, 2002 2:25 PM
Subject: [partman] Help with VFAT Extended partition


> I'm getting a message in RPM saying that the boot sector of my VFAT
> Extended partition doesn't have enough information (or something like
> that). Here are the settings I've set for the partition:
>                              Start               End         Size (KB)
>                           C    H    S        C    H    S
> Pri 3 VFAT Extended LBA  637  150   57     1,338 221   63    5,633,022
> Log   Linux ext2fs       637  151   57     1,275  33   63    5,121,021
> Ext   Extended          1,275  34   1      1,338 221   63      511,969
> Log   Linux swap        1,275  35   1      1,338 221   63      511,938
>
> Again, the problem is that the VFAT Extended LBA partition's boot
> sector doesn't have enough information. Why am I getting that? And,
> what should I do about it? I don't have Linux installed yet, but
> should I go ahead and install Linux? Thanks for the help.
> Hiran
>
>
>
> --
> To unsubscribe, please, email to: partman-unsubscribe@yahoogroups.com
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

Unfortunately the answer is No. I haven't fix the problem but have patched it. I
reinstalled Linux and found a tab that said "force Fat32"? unfortunately it was
late at night and I wasn't paying enough attention and thinking back it might
have said "force LBA" which might make more sense. The result is that it boots
Linux on the second partition fine although when I look at the hardware under
Linux the hdd is still wrong, same as the bios.

The answers to you questions are

I have a Amibios with a gigabyte 7IXE4 M/B
http://www.gigabyte.com.tw/products/products.htm    The first thing I did when I
had the problem was update the bios to Rev F9. the only other options when it
auto detects are "precomp"? and "mode" which only has the option on/off I have
only manually changed the cyl, heads, sec and nothing else. should I? I couldn't
see anything regarding changing the mode from CHS to LBA, maybe I just have to
turn the mode off?

Yes I have 2 hdd. a 40gb with 4 partitions, business stuff, music, backup and
small spare. The second drive 15gb with 3 partitions, my home use win98, Linux,
and small Linux swap. (I was told by a mate it was best to give Linux a small
swap partition slightly bigger than the ramm)

The next question is if everything is booting fine (due to software work around)
will it cause any problems if I don't change it back, can it damage the hdd if
its wrong? does it read slower?

thanks again for your help.

Regards,

Mark


   ----- Original Message -----
   From: szezynska
   To: partman@yahoogroups.com
   Sent: Sunday, April 07, 2002 9:11 PM
   Subject: [partman] Re: hdd detection


   Mark,

   Have you already solved your problem? If the answer is yes, tell us
   about it, as we may learn something new from your experience.
   If not, let us go over it once again.

   Every modern hard drive has its own embedded controlers that (among
   other things) remember different drive settings. Most of them are
   invisible to users, some of them can be set with system BIOS. BIOSes
   detect _current_ drive settings, but can be told to change them. I
   say BIOSes, because they come from different producers (AMI, Award,
   IBM, Phoenix etc.) for different mainboards (...). I do not know,
   which is yours, but I assume that it has the standard functionality
   of them all. Can you name your BIOS?

   > I think I have followed your instruction correctly. I am not sure
   about the forcing the drive to change? Does this happen by just
   reading a file or do you have to do something else?

   It is done by changing BIOS settings. The tip about booting into text
   mode/command line/safe mode and reading some files comes from my own
   personal experience with some drives that did not want to reset their
   mode until I read something from them.

   > When I change the parameters in the bios I have only changed the
   cyl , head , sec numbers and nothing else. do I have to change the
   mode or anything else? or does this happen automatically when the
   other numbers are changed.

   Yes, you have to change LBA/CHS mode flag. Depending on the BIOS
   brand it is either a field named "Mode" with possible
   values "Auto/CHS/LBA/None or ---" or a field named "LBA mode" with
   possible values "Yes/No" or someting along these lines. Changing only
   numbers is not enough and can be misunderstood by the BIOS and system
   software.

   > My Linux partition can be easily formatted as there is nothing on
   it. My windows partition has a bit but can be moved to another
   partition on my first drive so I can start from scratch if need be.

   Do you have two drives? What is the actual layout of your storage
   media?

   > But will formatting the whole drive and re partitioning the drive
   fix this problem?

   I do not think so, as the LBA/CHS mode belongs to lower level drive
   management than partitioning and formatting.

   Magda



         Yahoo! Groups Sponsor
               ADVERTISEMENT




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


   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



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

Hi Mr. Muthu,

First of all let me thank you & Mr. Mikhail Ranish for putting
together your effort in creating a great program like RPM. I have
started using RPM 2.42b. While, doing all the R&D I ran into a
serious problem. Now, I really need your help. The problem is like
this:

1.I have got a 4 GB HDD with windows installed in 1GB primary
partition & 3 GB of extended partition for storing data.

2.When I executed RPM from DOS prompt using start up disk, it
couldn't recognise the "Extended" partition as the 2 partitions were
not ending as per cylinders.

3. The "MBR/EMBR partition overlap" error message was displayed. Now
I didn't have the option of creating the RPM partition, but still
then I installed the "Boot Manager" as IPL. The partition rows were
not showing the extended partition neither the partition table. I
saved the MBR & quit RPM.

4.Now, my extended partition is lost. Windows nomore show me that
extended partition. Probably, the reference to EMBR from the MBR is
lost. Is there anyway that I can recover my EMBR?

I am sure your knowledge will help me out from this problem. I badly
need to recover my data.

Regards.

techyshailen

Mark,

> I have a Amibios with a gigabyte 7IXE4 M/B ... the only other
options when it auto detects are "precomp"? and "mode" which only has
the option on/off.

It is interesting. I have checked with my Amibios (it is K7S5A
realease 12/15/2001 S). It is true that with "Auto"-detected drive
one can change only the 32bit mode (on/off), but when the drive is in
the "User" mode (with cyls/heads/secs properly autodetected by the
BIOS - pressing [Enter] when the highlight/cursor points to the drive
line does the trick) one can change all of them: "LBA Mode", "Blk
Mode", "PIO Mode" and "32bit Mode". Don't you have these options in
the BIOS setup utility?

BTW: If your drive stays inside the computer (you do not temporary
remove it nor swap it with another one), there is no need to keep it
in the "Auto" mode, because it takes longer to boot the thing. With
fixed "User" mode settings the BIOS knows them and does not waste any
more time then is really needed.

> Yes I have 2 hdd. a 40gb with 4 partitions, business stuff, music,
backup and small spare. The second drive 15gb with 3 partitions, my
home use win98, Linux, and small Linux swap.

So which one is the first, booting one? Have you swapped them lately
(physically and/or changing the boot order in the BIOS setup). It is
possible that it is where your problems origin from.

But if your computer works now, do not fix it. Forcing LBA in Linux
does not hurt nor slow the drive.

Magda

I am not sure whether you can get back the data. But try using 'Gpart'
http://www.stud.uni-hannover.de/user/76201/gpart/

Unfortuantely this is a linux program.

Also, please try: http://www.datarescue.com/laboratory/partition.htm
(you might have to read these pages fully before using).

Going by what you said, I am not sure whether these steps could have
caused issues unless you have changed the partition table before.

Hope you can get back the data.

Regards,
Muthu

--- In partman@y..., "techyshailen" <techyshailen@y...> wrote:
> Hi Mr. Muthu,
>
> First of all let me thank you & Mr. Mikhail Ranish for putting
> together your effort in creating a great program like RPM. I have
> started using RPM 2.42b. While, doing all the R&D I ran into a
> serious problem. Now, I really need your help. The problem is like
> this:
>
> 1.I have got a 4 GB HDD with windows installed in 1GB primary
> partition & 3 GB of extended partition for storing data.
>
> 2.When I executed RPM from DOS prompt using start up disk, it
> couldn't recognise the "Extended" partition as the 2 partitions were
> not ending as per cylinders.
>
> 3. The "MBR/EMBR partition overlap" error message was displayed. Now
> I didn't have the option of creating the RPM partition, but still
> then I installed the "Boot Manager" as IPL. The partition rows were
> not showing the extended partition neither the partition table. I
> saved the MBR & quit RPM.
>
> 4.Now, my extended partition is lost. Windows nomore show me that
> extended partition. Probably, the reference to EMBR from the MBR is
> lost. Is there anyway that I can recover my EMBR?
>
> I am sure your knowledge will help me out from this problem. I badly
> need to recover my data.
>
> Regards.
>
> techyshailen

Try this windows program (found from google - I have not used it
myself):
http://home.arcor.de/christian_grau/rescue/

Regards,
Muthu
--- In partman@y..., "muthukumar_g_2002" <muthukumar_g_2002@y...>
wrote:
> I am not sure whether you can get back the data. But try using
'Gpart'
> http://www.stud.uni-hannover.de/user/76201/gpart/
>
> Unfortuantely this is a linux program.
>
> Also, please try: http://www.datarescue.com/laboratory/partition.htm
> (you might have to read these pages fully before using).
>
> Going by what you said, I am not sure whether these steps could have
> caused issues unless you have changed the partition table before.
>
> Hope you can get back the data.
>
> Regards,
> Muthu
>
> --- In partman@y..., "techyshailen" <techyshailen@y...> wrote:
> > Hi Mr. Muthu,
> >
> > First of all let me thank you & Mr. Mikhail Ranish for putting
> > together your effort in creating a great program like RPM. I have
> > started using RPM 2.42b. While, doing all the R&D I ran into a
> > serious problem. Now, I really need your help. The problem is like
> > this:
> >
> > 1.I have got a 4 GB HDD with windows installed in 1GB primary
> > partition & 3 GB of extended partition for storing data.
> >
> > 2.When I executed RPM from DOS prompt using start up disk, it
> > couldn't recognise the "Extended" partition as the 2 partitions
were
> > not ending as per cylinders.
> >
> > 3. The "MBR/EMBR partition overlap" error message was displayed.
Now
> > I didn't have the option of creating the RPM partition, but still
> > then I installed the "Boot Manager" as IPL. The partition rows
were
> > not showing the extended partition neither the partition table. I
> > saved the MBR & quit RPM.
> >
> > 4.Now, my extended partition is lost. Windows nomore show me that
> > extended partition. Probably, the reference to EMBR from the MBR
is
> > lost. Is there anyway that I can recover my EMBR?
> >
> > I am sure your knowledge will help me out from this problem. I
badly
> > need to recover my data.
> >
> > Regards.
> >
> > techyshailen

Try this windows program (found from google - I have not used it
myself):
http://home.arcor.de/christian_grau/rescue/

Regards,
Muthu

--- In partman@y..., "muthukumar_g_2002" <muthukumar_g_2002@y...>
wrote:
> I am not sure whether you can get back the data. But try using
'Gpart'
> http://www.stud.uni-hannover.de/user/76201/gpart/
>
> Unfortuantely this is a linux program.
>
> Also, please try: http://www.datarescue.com/laboratory/partition.htm
> (you might have to read these pages fully before using).
>
> Going by what you said, I am not sure whether these steps could have
> caused issues unless you have changed the partition table before.
>
> Hope you can get back the data.
>
> Regards,
> Muthu
>
> --- In partman@y..., "techyshailen" <techyshailen@y...> wrote:
> > Hi Mr. Muthu,
> >
> > First of all let me thank you & Mr. Mikhail Ranish for putting
> > together your effort in creating a great program like RPM. I have
> > started using RPM 2.42b. While, doing all the R&D I ran into a
> > serious problem. Now, I really need your help. The problem is like
> > this:
> >
> > 1.I have got a 4 GB HDD with windows installed in 1GB primary
> > partition & 3 GB of extended partition for storing data.
> >
> > 2.When I executed RPM from DOS prompt using start up disk, it
> > couldn't recognise the "Extended" partition as the 2 partitions
were
> > not ending as per cylinders.
> >
> > 3. The "MBR/EMBR partition overlap" error message was displayed.
Now
> > I didn't have the option of creating the RPM partition, but still
> > then I installed the "Boot Manager" as IPL. The partition rows
were
> > not showing the extended partition neither the partition table. I
> > saved the MBR & quit RPM.
> >
> > 4.Now, my extended partition is lost. Windows nomore show me that
> > extended partition. Probably, the reference to EMBR from the MBR
is
> > lost. Is there anyway that I can recover my EMBR?
> >
> > I am sure your knowledge will help me out from this problem. I
badly
> > need to recover my data.
> >
> > Regards.
> >
> > techyshailen

Hiya all,
Am new to this partitioning malake so if someone could recommend some
reading material before i start would be very grateful.

Cheers

>Am new to this partitioning malake so if someone could recommend some
>reading material before i start would be very grateful.

http://ata-atapi.com/  (HIW series)
http://www.firmware.com/support/
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q69912
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q51978

>   Hi Partman Moderator
First off, moderator means moderator. We here moderate the posts you email.
You are probably looking for partman@yahoogroups.com . Also, please skim and
remove any part of the original message to which you are replying to so that
you only resend what is relevent.

>   I Have A 4.3 IDE Drive with the boot sector damaged.
What do you mean boot sector damaged?
> Is there any way that I can Repair it to use?
What do you mean repair to use?
You can select the MBR, hit enter, and reset it to Standard IPL if that is
what you are looking for...
>    I would appreciate your ad vice.
> Yours Truly lakotajackj
Hope this helps,
Jibben Nee

P.S. See the pattern used to reply to the message? It is clear and easy to
follow. Plus, late joiners of the topic don't need to spend all the time
reading the past messages. Also, I have sent this to the group as well, so
you should be getting two of the same emails. Also, the advertisements
Yahoo! and many other email servers append to the end of emails can be
removed as well... I'm sure no one enjoys seeing five ads at the bottom of
one email. :-) Good luck!

Thank you Muthu and Mikhail for putting together such a great program
like RPM. I've found it a pleasure to use. If I may be so bold, I
would like to make a suggestion for 2 additional features for RPM
which in my view would make it perfect;

1. the text boot menu displays the partition volume name rather than
file system  e.g."Disk 1 \ Win 95" rather than "Disk 1 \ Windows FAT-
32" , and

2. the ability to set the volume name from the RPM interface

Do you think this is possible or worthwhile? Thanks, Bob.

I'm using XOSL and currently I have the following setup:
Pri 1 - XOSL
Pri 2 - VFAT Ext LBA
- Windows FAT-32 LBA
- Linux ext2
- Linux swap
Pri 3 - VFAT Ext LBA
- Windows FAT-32 LBA (at least I'm going to, but I haven't formatted
this logical partition for FAT-32 yet)

My question, can I install Win ME on the FAT-32 under the first VFAT
Ext (Pri 2)? Whenever I try, it doesn't seem to work. I'd really
rather not have to change this setup if possible. But is there
anything I can do to point the WinME setup program to the partition
I've created for it? Thanks for the help.
Hiran

well, im not that clear about xosl but normally, you cant boot into an
extended partition. i have seen my ext. partitions listed in ranish's boot
loader but  i dont think they can boot... windows me can install windows to
a hdd other than c but it must put the boot files on the c.... good luck!
~jibben
----- Original Message -----
From: "hiranwatson" <hiranwatson@...>
To: <partman@yahoogroups.com>
Sent: Saturday, April 13, 2002 3:28 PM
Subject: [partman] Help with Windows ME installation


> I'm using XOSL and currently I have the following setup:
> Pri 1 - XOSL
> Pri 2 - VFAT Ext LBA
> - Windows FAT-32 LBA
> - Linux ext2
> - Linux swap
> Pri 3 - VFAT Ext LBA
> - Windows FAT-32 LBA (at least I'm going to, but I haven't formatted
> this logical partition for FAT-32 yet)
>
> My question, can I install Win ME on the FAT-32 under the first VFAT
> Ext (Pri 2)? Whenever I try, it doesn't seem to work. I'd really
> rather not have to change this setup if possible. But is there
> anything I can do to point the WinME setup program to the partition
> I've created for it? Thanks for the help.
> Hiran
>
>
>
> --
> To unsubscribe, please, email to: partman-unsubscribe@yahoogroups.com
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

Bootitng from a logical partition is a common thing to do with Linux,
but not for Microsoft operating systems. I don't do this (and also don't
use XOSL), but FWIW, a method for getting Win9X/ME to boot from a
logical partition is covered in the XOSL FAQ here:

http://home.wanadoo.nl/geurt/faqhow/faq.html

Note that it says you can't install it to a logical partition, but can
copy it to one afterwards and then boot it from there - not worth the
trouble IMO....

Tom


hiranwatson wrote:
>
> I'm using XOSL and currently I have the following setup:
> Pri 1 - XOSL
> Pri 2 - VFAT Ext LBA
> - Windows FAT-32 LBA
> - Linux ext2
> - Linux swap
> Pri 3 - VFAT Ext LBA
> - Windows FAT-32 LBA (at least I'm going to, but I haven't formatted
> this logical partition for FAT-32 yet)
>
> My question, can I install Win ME on the FAT-32 under the first VFAT
> Ext (Pri 2)? Whenever I try, it doesn't seem to work. I'd really
> rather not have to change this setup if possible. But is there
> anything I can do to point the WinME setup program to the partition
> I've created for it? Thanks for the help.
> Hiran
>
>
> --
> To unsubscribe, please, email to: partman-unsubscribe@yahoogroups.com
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

I have installed  WinME  on C:\ .
Now there are two  ways to install  second OS on  D: drive.
1) Installing  winXP  on  D: drive without  activating  D:\  by Fdisk
program.
2)Installing  winXP  on  D: drive  after  activating  D:\  by Fdisk program.

What is your idea?
- --
Babak
b-memari@...

On 7 Apr 2002 at 18:15, hiranwatson wrote:

> I have some questions regarding LBA. Firstly, what is it?

Hale's HIW - How It Works - Documents
<http://ata-atapi.com/hiw.htm>

(all his HIW-pages for offline reading)
Get the ALLHIW.ZIP file.
<http://ata-atapi.com/allhiw.zip>

Maxtor: Breaking the Barriers
<http://www.maxtor.com/products/DiamondMax/techsupport/Q
&A/30004.html>

Maxtor: IDE Hard Drive Capacity Barriers.
<http://www.maxtor.com/technology/whitepapers/63001.html
>

Partition types by Andries Brouwer:
http://www.win.tue.nl/~aeb/partitions/
(see about Limits)

All the best,
Bjorn Simonsen

Hello,

I have uploaded Partition Manager 2.43 beta
to http://www.ranish.com/part/

This version has a bug fix found by Muthu,
that used to prevent FreeBSD from booting
of the partitions located above 8G.

Now you should have no problem booting FreeBSD on large disks.

Thanks,
Mikhail