Why did new drive convert from NTFS to FAT16

[freezing]

I just installed a new 200GB Maxtor Ultra ATA in the Primary Slave position on my machine. I set it up as NTFS with 2 partitions at 40GB and 160GB. I know the installation was successful because I was able to install and run a number of applications on the new drive. It also came back up fine after several hard and soft boots. The last thing I did yesterday was download SP2 for XP. I decided to call it a day and shutdown the machine once Windows had completed the install process and was asking me to restart.

This morning I turned the computer back on and discovered that I couldn't access anything on the new drive. Between Windows Device Manager, BIOS, Partition Magic and MaxBlast I have gathered the following information:

-Windows: says drive is installed but only 33.8GB and not formatted.
-BIOS: settings appear correct but only 33.8GB capacity
-MaxBlast: Thinks drive is 33.8GB and partitioned as FAT16
-Partition Magic: Won't load from Windows or by booting from CD. Gives error #87 and mentions something about "Disk Manager"

Other Info:
AMD Athon 64 bit 3500+
Asus A8V Deluxe Socket 939 Motherboard
BIOS current as of 3 months ago
Primary boot drive is older 12GB Maxtor ATA and functioning properly.
Windows XP Pro SP1 with all security patches.
Current and functioning AV, anti-Spyware and Firewall.

Any ideas?

 

[kestrel1]

I think that I read somewhere that there is a bug in SP2 that behaves like this.
I have a feeling that Maxtor has a tool on thier website that sorts this out.
Hold on.......................
I am back.
Have a llok at this:

http://www.maxtor.com/portal/site/M...tware Downloads/ATA Hard Drives&downloadID=11

This may help.

 

[wolluf]

How did you partition the new drive? (best to use disk management - but you mention PM & Maxblast..)

Are you sure you've not changed any jumpers on the drive? (and are you sure it wasn't showing 33GB in the bios originally) You've obviously got a new bios - so the only reason I can think of for the bios showing 33GB is you've got the limiting jumper set. Now, if that's true, and you used Maxblast to partition it, it will probably have installed an overlay to 'overcome' the limitation of the drive capacity. Then SP2 has probably installed a new version of atapi.sys perhaps - something that's different from when Maxblast was used. This is all conjecture of course!