IDE problems

  • Thread starter Thread starter Catani
  • Start date Start date
C

Catani

Dear all!
For some reason my IDE ports won’t see my hard-drives. I installed a
IDE Rocket raid 404 in a PCI slot and tried to boot Windows through
it. Now the hard-drives are identified, but when Windows starts to
load, the screen soon flashes and the computer reboots. After a few
tries now the computer won’t even start to load Windows through the
raid. Now and then I can successfully load Windows though one of the
motherboard IDE ports. Then upon next boot-up no hard-drive is found.
So everything points to either the IDE cable or the hard-drive, but
I’ve tried different cables and different hard-drives with the same
result. What is going on? And why the reboot when loading through the
raid? Thank you for your attention.
 
Catani said:
For some reason my IDE ports won’t see my hard-drives. I installed a
IDE Rocket raid 404 in a PCI slot and tried to boot Windows through
it. Now the hard-drives are identified, but when Windows starts to
load, the screen soon flashes and the computer reboots. After a few
tries now the computer won’t even start to load Windows through the
raid. Now and then I can successfully load Windows though one of the
motherboard IDE ports. Then upon next boot-up no hard-drive is found.
So everything points to either the IDE cable or the hard-drive, but
I’ve tried different cables and different hard-drives with the same
result. What is going on?
Click to expand...

I got weird results like that due to an intermittent short to case.

Running the motherboard loose on the desktop fixed the problem
and proved that it was due to an intermittent short to case.

Very rare, but it does happen and if you really did test the
cables and drives properly, it could be something rare like that.

It would be worth resetting the cmos too, Win can get
seriously confused at times with hardware changes.
And why the reboot when loading through the raid?
Click to expand...

Thats likely just the usual NT/2K/XP reboot on serious errors.
You can turn that behaviour off and it should have something
in the error logs about it too.
 
Back
Top