Hola all,
I posted on here a couple months ago regarding a problem getting Windows XP to install to a SATA hard drive. Well, I fixed that problem by disconnecting ALL IDE devices from the motherboard, leaving only the SATA drive connected. Seems that XP tried to install itself first to my secondary IDE hard drive, then to my Zip drive (!) if they were left connected, regardless of what drive I told it to install to.
Anyway, it has been working fine now since March and today it started acting up again. The computer would not boot from the SATA drive when I turned it on today. I disconnected my other IDE devices (one hard drive, two DVD drives, and one Zip drive) and it booted just fine. But re-connecting any of the other IDE drives returns it to an unbootable state. I can't do without the other drives, so what's the deal here? Anyone have any ideas on how to fix this? The SATA drive is set as the first boot device in the BIOS and always has been, so that's not the problem. I tried using fixboot and fixmbr in the recovery console too. No go there. Any help would be greatly appreciated.
Thanks,
Doug
I posted on here a couple months ago regarding a problem getting Windows XP to install to a SATA hard drive. Well, I fixed that problem by disconnecting ALL IDE devices from the motherboard, leaving only the SATA drive connected. Seems that XP tried to install itself first to my secondary IDE hard drive, then to my Zip drive (!) if they were left connected, regardless of what drive I told it to install to.
Anyway, it has been working fine now since March and today it started acting up again. The computer would not boot from the SATA drive when I turned it on today. I disconnected my other IDE devices (one hard drive, two DVD drives, and one Zip drive) and it booted just fine. But re-connecting any of the other IDE drives returns it to an unbootable state. I can't do without the other drives, so what's the deal here? Anyone have any ideas on how to fix this? The SATA drive is set as the first boot device in the BIOS and always has been, so that's not the problem. I tried using fixboot and fixmbr in the recovery console too. No go there. Any help would be greatly appreciated.
Thanks,
Doug