Well, my little brother's hard drive has done it again.
I spent all this morning trying to fix his comp, because his hard drive occasionally is not properly recognized. (For example, when it should come up SAMSUNG xxxxx... on the POST screen, I instead get QAESUNE xxxxx... , the size is wrong and the drive is unusable in any OS.) At the same time, I was trying to finagle the Windows XP into recognizing this drive as it originally was (D
when it got changed to G: after previous hard drive installations that have since been taken out.
Well, I got the hard drive letter issue resolved, and I also figured out that the hard drive cable was faulty. Even though another hard drive had no problems, there must've been some touching or disconnected wires in the part that connected to his drive.
AND NOW...the drive doesn't work in Windows XP!!!! >.<
When I boot it with Hiren's BootCD v6.0, the drive works just fine. It's got one FAT32 partition. The usable size is about 38GB. Though the drive works fine in a standard command prompt, PartitionMagic 8.2 for DOS reports that its FAT copies don't match, then bombs out with an error. (In Windows XP PartitionMagic 7.0, the drive reports an error #1806.) PartitionMagic for DOS or XP gets the drive size correct and the filetype correct but all other things (used space, free space, label) are horribly wrong. There is no option to fix the FAT. Scandisk for DOS reports that the FAT is 'just fine.' Scandisk for Windows doesn't even work.
So, I'm led to believe that DOS relies on an undamaged FAT while Windows XP uses a bogus one that must've been created when the computer booted and the cable was faulty. (I've since replaced the cable and it never misreports the drive presence now.)
WHAT DO I DO NOW?
For now, I'll check out other utilities on this nice Hiren's BootCD, but I'm hesitant to overwrite FATs unless I can be certain I'm replacing the bad one and not the good one!!
I spent all this morning trying to fix his comp, because his hard drive occasionally is not properly recognized. (For example, when it should come up SAMSUNG xxxxx... on the POST screen, I instead get QAESUNE xxxxx... , the size is wrong and the drive is unusable in any OS.) At the same time, I was trying to finagle the Windows XP into recognizing this drive as it originally was (D
Well, I got the hard drive letter issue resolved, and I also figured out that the hard drive cable was faulty. Even though another hard drive had no problems, there must've been some touching or disconnected wires in the part that connected to his drive.
AND NOW...the drive doesn't work in Windows XP!!!! >.<
When I boot it with Hiren's BootCD v6.0, the drive works just fine. It's got one FAT32 partition. The usable size is about 38GB. Though the drive works fine in a standard command prompt, PartitionMagic 8.2 for DOS reports that its FAT copies don't match, then bombs out with an error. (In Windows XP PartitionMagic 7.0, the drive reports an error #1806.) PartitionMagic for DOS or XP gets the drive size correct and the filetype correct but all other things (used space, free space, label) are horribly wrong. There is no option to fix the FAT. Scandisk for DOS reports that the FAT is 'just fine.' Scandisk for Windows doesn't even work.
So, I'm led to believe that DOS relies on an undamaged FAT while Windows XP uses a bogus one that must've been created when the computer booted and the cable was faulty. (I've since replaced the cable and it never misreports the drive presence now.)
WHAT DO I DO NOW?
For now, I'll check out other utilities on this nice Hiren's BootCD, but I'm hesitant to overwrite FATs unless I can be certain I'm replacing the bad one and not the good one!!