Just had to replace a failed motherboard. The replacement is the same make, similar, but not identical.
I knew that my HDD (Windows 7) had been created as Native IDE - out of ignorrance really, that was the default setting on the old board when I installed a few years ago and I didn't know any better to change it.
So when I replaced the board I went into the BIOS and set it to NATIVE IDE. But when I tried booting it just said that no bootable disk was found.
I experimented setting it to AHCI, and this time the disk was detected and started to boot into windows but came up with two option, NORMAL or REPAIR. I tried a normal boot but that quickly just rebooted the PC. Didn't want to try REPAIR just yet.
So I did a bit of reading and found posts suggesting setting it to NATIVE IDE which I had already tried and RAID.
Foolishly I tried RAID, and this started up and then asked for driver disks so I aborted, knowing that wasn't right.
But after that, even when the disk was detected in AHCI it didn't prompt for NORMAL or REPAIR any more. It now prompts to enter bootable media - so it can see the disk but doesn't think it is bootable any more.
In NATIVE IDE it still din't even detect the disk at all.
The failure to detect in NATIVE IDE seemed strabge to me so I swapped the SATA ports around and Bingo! the drive was now detected. However, I now get the same prompt to enter bootable media as I do with AHCI.
I fear that had I swapped the ports originally then it would have booted fine in NATIVE SATA., but since trying RAID it has screwed up the boot sector.
Does that sound plausible. Would selecting RAID, trying to boot, but not provide any drivers midify the boot sector.
If so will going into system repair using the windows disk sort that out? Plan to try anyway, just seeing if there is any advice before I do.
Cheers,
Nigel
I knew that my HDD (Windows 7) had been created as Native IDE - out of ignorrance really, that was the default setting on the old board when I installed a few years ago and I didn't know any better to change it.
So when I replaced the board I went into the BIOS and set it to NATIVE IDE. But when I tried booting it just said that no bootable disk was found.
I experimented setting it to AHCI, and this time the disk was detected and started to boot into windows but came up with two option, NORMAL or REPAIR. I tried a normal boot but that quickly just rebooted the PC. Didn't want to try REPAIR just yet.
So I did a bit of reading and found posts suggesting setting it to NATIVE IDE which I had already tried and RAID.
Foolishly I tried RAID, and this started up and then asked for driver disks so I aborted, knowing that wasn't right.
But after that, even when the disk was detected in AHCI it didn't prompt for NORMAL or REPAIR any more. It now prompts to enter bootable media - so it can see the disk but doesn't think it is bootable any more.
In NATIVE IDE it still din't even detect the disk at all.
The failure to detect in NATIVE IDE seemed strabge to me so I swapped the SATA ports around and Bingo! the drive was now detected. However, I now get the same prompt to enter bootable media as I do with AHCI.
I fear that had I swapped the ports originally then it would have booted fine in NATIVE SATA., but since trying RAID it has screwed up the boot sector.
Does that sound plausible. Would selecting RAID, trying to boot, but not provide any drivers midify the boot sector.
If so will going into system repair using the windows disk sort that out? Plan to try anyway, just seeing if there is any advice before I do.
Cheers,
Nigel