G
Guest
A friend of mine just got a new x64 system and it would not recognize the
files on his old hard drive, which has XP Pro service pack 2 on it. I
connected the hard drive to my system, which also has XP Pro service pack 2,
and set it up as a slave. The drive was recognized with no problem. I
copied the contents of the drive to a briefcase on my hard drive, and then
attempted to reformat the slave drive so I could put the files back on it,
minus the OS. There was a FAT32 system on the slave drive, which Windows
would not allow me to format or delete. My system froze, so I rebooted it,
and windows would no longer load, instead I got the BSOD. I attempted to do
a repair of Windows, using my installation cd, but was prompted that there
are files missing and that setup would be shutting down, which it did. I
have no idea why this would have happened, and anyone who might be able to
suggest a fix would be my new hero...
files on his old hard drive, which has XP Pro service pack 2 on it. I
connected the hard drive to my system, which also has XP Pro service pack 2,
and set it up as a slave. The drive was recognized with no problem. I
copied the contents of the drive to a briefcase on my hard drive, and then
attempted to reformat the slave drive so I could put the files back on it,
minus the OS. There was a FAT32 system on the slave drive, which Windows
would not allow me to format or delete. My system froze, so I rebooted it,
and windows would no longer load, instead I got the BSOD. I attempted to do
a repair of Windows, using my installation cd, but was prompted that there
are files missing and that setup would be shutting down, which it did. I
have no idea why this would have happened, and anyone who might be able to
suggest a fix would be my new hero...