linux fdisk hidden fat32 (1b) --> fat32 (0b) = dos fdisk fat16 ???

linux fdisk hidden fat32 (1b) --> fat32 (0b) = dos fdisk fat16 ???

Post by bill » Mon, 03 Mar 2003 15:10:44



  Well, well.

  I decided to give Partition Manager's
boot manager a test drive today (QBOOT or
whatever the hell it's called).

  This was on Win98SE.

  I fired it up and got a menu asking me if I wanted to boot
drive J:, which is where I have win2000 installed.

  "Aha,", I thought, "here's a way to boot from Win98SE
right into Win2000. Neat!"

  Not.

  What it did was

  (1) hide my Windows boot partition and set it to Inactive

  (2) set my Windows2000 partition to active, and

then it rebooted the machine.

  Unfortunately, my Windows2000 partition is not bootable.

  Now I can't boot Win98SE to use P.M to unhide my C: drive and I can't
get into Win2k.

  What do I now?

  My first thought was to use Linux fdisk to reverse the process:

  (1) unhide my Windows boot partition, by changing its ID from 1b
(hidden fat32) to 0b (fat32) and make it active,

  (2) make my Win2000 partition inactive

   So, that's what I did, which gave me this:

Disk /dev/hde: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Boot    Start       End    Blocks   Id  System
/dev/hde1    *        1       261   2096451    b  Win95 FAT32
/dev/hde2           262      1536  10241437+   f  Win95 Ext'd (LBA)
/dev/hde3          1537      3066  12289725    7  HPFS/NTFS
/dev/hde5           262       516   2048256    b  Win95 FAT32
/dev/hde6           517       771   2048256    b  Win95 FAT32
/dev/hde7           772      1026   2048256    b  Win95 FAT32
/dev/hde8          1027      1536   4096543+   b  Win95 FAT32

   Next, I booted my Win98 restart disk and ran Windows FDISK
to check the partition info.

   Guess what?

   Windows FDISK now thinks my C: drive/partition is FAT16 -- and the
file names all look like this:

!.#*
!.#*
).+*
).+*
. *
. *
:0398.:03b4*
:0398.:03b4*
:0398.:03b4*
:0398.:03b4*
:03982.:03b42*
:0398:207f.:03b4:207f*
:0398:2219.:03b4:2219*
:0398:221a.:03b4:221a*
:0398:2229.:03b4:2229*
:0398:2248.:03b4:2248*
:0398:2261.:03b4:2261*
:0398:2264.:03b4:2264*

  Anyone seen anything like this before?

  Drives E,F,G, and H seem ok.

  And my Win2000 partition seems ok afaict after booting from the win2k
cdrom and opening the repair console.

  What should I do next?

  How can I unhide my boot partition so Windows FDISK sees it as FAT32?

  Can I boot from the win2k cdrom and then boot Win2000 from the repair
comsole "dos" prompt?

  What should I do next?

--

 
 
 

linux fdisk hidden fat32 (1b) --> fat32 (0b) = dos fdisk fat16 ???

Post by Joe » Tue, 04 Mar 2003 04:23:10


Hey Bill,
    I have worked with multiboots a great deal, but never run across
anything like what you have.  I have had Windows 98 and 2K installed using
NTLDR, but then Win98 had to be reinstalled on top of itself to get it to
work.  That deleted the NTLDR to load 2K.  I then started the install for 2K
again, but when it rebooted the first time I removed the cd.  It seem that
it writes the NTLDR first as to know where to start.  Then just edit the
Boot.dos file on the C drive to delete the Install portion of the loader.
All back to normal...  Don't know if tring the NTLDR trick would work or
not?
later Joe


Quote:

>   Well, well.

>   I decided to give Partition Manager's
> boot manager a test drive today (QBOOT or
> whatever the hell it's called).

>   This was on Win98SE.

>   I fired it up and got a menu asking me if I wanted to boot
> drive J:, which is where I have win2000 installed.

>   "Aha,", I thought, "here's a way to boot from Win98SE
> right into Win2000. Neat!"

>   Not.

>   What it did was

>   (1) hide my Windows boot partition and set it to Inactive

>   (2) set my Windows2000 partition to active, and

> then it rebooted the machine.

>   Unfortunately, my Windows2000 partition is not bootable.

>   Now I can't boot Win98SE to use P.M to unhide my C: drive and I can't
> get into Win2k.

>   What do I now?

>   My first thought was to use Linux fdisk to reverse the process:

>   (1) unhide my Windows boot partition, by changing its ID from 1b
> (hidden fat32) to 0b (fat32) and make it active,

>   (2) make my Win2000 partition inactive

>    So, that's what I did, which gave me this:

> Disk /dev/hde: 255 heads, 63 sectors, 4865 cylinders
> Units = cylinders of 16065 * 512 bytes

>     Device Boot    Start       End    Blocks   Id  System
> /dev/hde1    *        1       261   2096451    b  Win95 FAT32
> /dev/hde2           262      1536  10241437+   f  Win95 Ext'd (LBA)
> /dev/hde3          1537      3066  12289725    7  HPFS/NTFS
> /dev/hde5           262       516   2048256    b  Win95 FAT32
> /dev/hde6           517       771   2048256    b  Win95 FAT32
> /dev/hde7           772      1026   2048256    b  Win95 FAT32
> /dev/hde8          1027      1536   4096543+   b  Win95 FAT32

>    Next, I booted my Win98 restart disk and ran Windows FDISK
> to check the partition info.

>    Guess what?

>    Windows FDISK now thinks my C: drive/partition is FAT16 -- and the
> file names all look like this:

> !.#*
> !.#*
> ).+*
> ).+*
> . *
> . *
> :0398.:03b4*
> :0398.:03b4*
> :0398.:03b4*
> :0398.:03b4*
> :03982.:03b42*
> :0398:207f.:03b4:207f*
> :0398:2219.:03b4:2219*
> :0398:221a.:03b4:221a*
> :0398:2229.:03b4:2229*
> :0398:2248.:03b4:2248*
> :0398:2261.:03b4:2261*
> :0398:2264.:03b4:2264*

>   Anyone seen anything like this before?

>   Drives E,F,G, and H seem ok.

>   And my Win2000 partition seems ok afaict after booting from the win2k
> cdrom and opening the repair console.

>   What should I do next?

>   How can I unhide my boot partition so Windows FDISK sees it as FAT32?

>   Can I boot from the win2k cdrom and then boot Win2000 from the repair
> comsole "dos" prompt?

>   What should I do next?

> --