2 replies
by jaqui
firstly, is the pin setting for the jumper set on master, slave or cable select?
is the drive in correct place on the ribbon cable for the pin settings?
[ pin settings = jumper beside ide connection on back of hard drive ]
second, did he try to save anything when rebuilding after crash? if yes, could be what is causing conflict with it now re errors
third, are all drives set to autodetect, with correct pins for where they are on the cables?
[ best setting is cable select {cs}, as this avoids locking drives into wrong settings ]
by dbucyk
If Windows XP has this type of glitch where once out of 50 times the computer does detect the slave drive, then the problem is two-fold.
First, you will have to go to Microsoft and check the Hardware Compatibility List with the Slave Hard drive manufacturer which is listed on the hard drive.
Get this information and then take it to the HCL list. If it is not on the list, then you'll have to find a drive that is.
If it is, then go to the hard drive manufacturer web site and you will probably have to update the firmware on the hard drive or possibly get the controller drive from the motherboard manufacturer.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending