I had the same problem and when I researched it, it came down to Windows and therefore
Windows programs read the partition table in a different order than Linux. The error
I got was #120. It is because Linux programs chain logical partitions together in the
order they were created and Windows and OS2 require them to be chained together in
ascending order. Which ones better I don't know, I got that from the Partition Magic
book. I know this doesn't fix anything, but it is why I allways use Partition Magic
to do my stuff. Linux isn't picky, but windows is.
---------- Original Message ----------------------------------
From: bascule <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Thu, 01 Jun 2000 03:47:20 +0100
>i second that, diskdrake really messed up my disk after i decided to let
>it do the job instead of pm, went back to pm and had no problems
>
>bascule
>
>Ron Peake wrote:
>>
>> Hi Dick
>>
>> I have experienced the same problem and in my case it resulted from letting
>> Mandrake's Diskdrake 'fiddle' with the partitions created by Partition Magic.
>> The only solution that I found was to let Nortons DiskDoctor fix the partition
>> tables, then resize the partitions again using Partition Magic 4,01.
>>
>> Mandrake Sofware suggested in January or February of this year to use a later
>> version of their Diskdrake program instead of the one which was in release 7,0.
>> But in my PC, there was no improvement.
>> So from my experience, Mandrake's program is still unable to
>> alter vfat or even linux partitions safely, in a way which allows other
>> operating systems such as DOS/Windows to also use them.
>>
>> Ron
>
>
