The thought crossed my mind, but as you said, it's a brand new board- no reason to settle for a faulty one.Originally Posted by Geezer57
I'm in unfamiliar waters with SATA, but I think I tried all my options- feel free to tell me otherwise:When you were attempting to install WinXP on the new SATA hard drive, did it prompt you for a SATA driver? Or is the mobo's BIOS so advanced it contains the code already?
First off, Windows setup detected the drive and partitioned/formatted it without incident. My understanding is that if it sees the drive, it doesn't need a special driver. However, later I tried to load a driver with the F6 option during setup using a floppy that I created from the MoBos driver CD. On the SP2 slipstreamed XP install, it made no difference whatsoever- still bluescreened on the first reboot after copying files. Using an XP SP1 CD, I got it to install completely once- but during reboots it constantly gave me errors about the registry claiming it had restored a corrupted file, then when I applied SP2, it rebooted to the all too familiar BSOD. Oddly, when I tried another SP1 install later is gave the BSOD on reboot after copying files. Sometimes I would get the same STOP errors, but sometimes it would be different- I guess depending on what I tried.
Sound like a bad onboard SATA controller to you? Also, my understanding was that most SATA drives would detect in Windows as an IDE drive. Is this the case? Regardless, I would've thought the fact that Windows setup detected the drive without needing a special driver would suggest I was in good shape.![]()
Bookmarks