Raven
10-11-2002, 09:50 AM
Error message: Fixed Disk Error (80) Controler cable not connected
I'm in the process of building a new system, I have an Epox 8KHA+ motherboard, with an AMD 1800 processor.
Anywho, I place the board (with the static bag under it) on my bench. I installed the processor and HSF, using good ol'Arctic Silver 3. Everything went flawlessly. I continued with the installation, I installed my video card and my hdd. I decided with the basics in it would be time to boot it up.
Well it boot up flawlessly, it detected my hard drive, and even identified it properly. THen I get the error listed above, with the standard press F1 to continue. I hit F1 and get the following error message: No OS found.
WTF??? I flip the cable around thinking it might be a Pin 1, issue. Nogo, so I flip it on the mobo... still no go, both this time and the last, the bios didn't recognize my drive, so I know it was in properly before.
I thought it might be a faulty cable, so I swapped it out, but get the same error.
I checked the "Slave/Master" jumper and it's all good.
I then tried the drive in my other system and it boots up fine with an OS.
Anyone have anythoughts on this? Anything I might have forgotten?
I'm in the process of building a new system, I have an Epox 8KHA+ motherboard, with an AMD 1800 processor.
Anywho, I place the board (with the static bag under it) on my bench. I installed the processor and HSF, using good ol'Arctic Silver 3. Everything went flawlessly. I continued with the installation, I installed my video card and my hdd. I decided with the basics in it would be time to boot it up.
Well it boot up flawlessly, it detected my hard drive, and even identified it properly. THen I get the error listed above, with the standard press F1 to continue. I hit F1 and get the following error message: No OS found.
WTF??? I flip the cable around thinking it might be a Pin 1, issue. Nogo, so I flip it on the mobo... still no go, both this time and the last, the bios didn't recognize my drive, so I know it was in properly before.
I thought it might be a faulty cable, so I swapped it out, but get the same error.
I checked the "Slave/Master" jumper and it's all good.
I then tried the drive in my other system and it boots up fine with an OS.
Anyone have anythoughts on this? Anything I might have forgotten?