Vista hard drive error check destroys a FAT 16 drive? Help!

  • Thread starter Thread starter Jon
  • Start date Start date
J

Jon

I used a WD 120GB Fat32 external UBS drive to move old files from a MS ME
desktop computer to my Vista ultimate notebook. It worked great. But I
decided to use the Vista system to scandisk this WD FAT 32 drive to check
for ay bad sectors.There were none. [Drive G - properties - tools - this
option will check the fVolume for errors].

Now my MS ME desktop can't read this Fat 32 WD drive after the Vista drive
error check. It says this drive is not formatted. Sometime it says the drive
is corrupted. In desktop MS ME, all the files on the drive show up like they
ae supposed to, but if I click on one and open it, it says this file is not
there, do I want to create it?
It looks like Vista just destroyed a good harddrive, which contained 120 GB
of my MS ME backup files.

Unrelated to this problem is my Seagate FreeAgent NTSF exterior drive for my
Vista notebook - which works great there - cannot be read by my MS ME
desktop.
Thanks for any help, Jon
 
Jon said:
I used a WD 120GB Fat32 external UBS drive to move old files from a MS
ME desktop computer to my Vista ultimate notebook. It worked great. But
I decided to use the Vista system to scandisk this WD FAT 32 drive to
check for ay bad sectors.There were none. [Drive G - properties - tools
- this option will check the fVolume for errors].

Now my MS ME desktop can't read this Fat 32 WD drive after the Vista
drive error check. It says this drive is not formatted. Sometime it says
the drive is corrupted. In desktop MS ME, all the files on the drive
show up like they ae supposed to, but if I click on one and open it, it
says this file is not there, do I want to create it?
It looks like Vista just destroyed a good harddrive, which contained 120
GB of my MS ME backup files.

Unrelated to this problem is my Seagate FreeAgent NTSF exterior drive
for my Vista notebook - which works great there - cannot be read by my
MS ME desktop.
Thanks for any help, Jon
Click to expand...

May be there was a switch between FAT16 and FAT32?

Roy
 
Back
Top