I'm new here and have dug around a bit but can't find anything that helps with my problem.
First the HW details:
PC is 5-6 years old
It was built by a local, well known computer shop that's been around for years
MOBO is an Asus K8VSE Deluxe
BIOS is AMI version 08.00.09, Build date 09/08/05, ID A0058002
Next a little back story:
The PC was running WinXP Pro until one day it wouldn't boot, saying that a critical file was missing. I played around with it and *thought* the HDD had failed. So I parked the PC for a while and just used my laptop, until this week, when I decided to get this pig working again.
While troubleshooting the issue (months ago) I noticed that my one and only SATA HD was not plugged into the standard SATA port on the Mobo, but on the SATA port on the on-board RAID controller. Why this was done is beyond me, but it was done when this machine was built.
Now the current situation:
I decided to go with a new WD Caviar Black, 1.0TB drive, and Windows 7 Pro. Plugged everything in, set the BIOS to boot to the Windows CD, and fired it up.
First thing is that the BIOS does not see a HDD, hit F1 to continue. So I did.
Windows 7 started loading files, and I thought I was in good shape. But alas, 7 could also not see the HDD but asked if I wanted to load drivers
Now I am confused; drivers should not help if the BIOS can't even see the HDD, right?
So I futzed around with the BIOS, and can't see a whole lot of anything mentioning SATA. I thought that if you set the IDE type to auto detect, the BIOS would figure out there was a SATA drive, but apparently not in my case.
All cables are from HDD to mobo are plugged in firmly, the drive spins up. I even tried a new SATA cable and got the same result.
I reset the BIOS to factory defaults and got the same result.
I disabled and re-enabled the on-board Promise controller and got the same result.
At this point, I think it's either something so simple that I am overlooking it, or the MOBO is fried. But remember, when this all started all was fine save for a missing file that would not allow Win XP to boot, so . . . . .
Thanks in advance for any and all responses.