Okay, 700 miles later and my brother's computer still isn't working.
My guess is, I fried the motherboard. Primary IDE connection doesn't recognize any drives attached, and the hard drive light on the case is constantly on. I'm trying to use the Promise controller card, and the Western Digital diagnostics can tell that the drives are attached but can't access them.
Does it matter, on ATA/100 IDE cables, where the master and slave drives are attached? In trying to get the computer to pass the POST screens, I switched the two drives (adjusted jumpers) but didn't switch the cable. My guess is I burned out a controller on the mboard.
The Promise controller card runs my old ATA/33 hd just fine, but won't access the new WD800JD drives, so I have a feeling the card may not be working right either. Running the WD Data Lifeguard, I get a Data Request Timeout error, which means the hard drives aren't communicating. Both are giving the same errors, so I find it hard to believe I got two bad hard drives at the same time.
What do you guys think? Appreciate your input.
Lymponus
"All the great things are simple, and many can be expressed in a single word: freedom; justice; honor; duty; mercy; hope." - Sir Winston Churchill
My guess is, I fried the motherboard. Primary IDE connection doesn't recognize any drives attached, and the hard drive light on the case is constantly on. I'm trying to use the Promise controller card, and the Western Digital diagnostics can tell that the drives are attached but can't access them.
Does it matter, on ATA/100 IDE cables, where the master and slave drives are attached? In trying to get the computer to pass the POST screens, I switched the two drives (adjusted jumpers) but didn't switch the cable. My guess is I burned out a controller on the mboard.
The Promise controller card runs my old ATA/33 hd just fine, but won't access the new WD800JD drives, so I have a feeling the card may not be working right either. Running the WD Data Lifeguard, I get a Data Request Timeout error, which means the hard drives aren't communicating. Both are giving the same errors, so I find it hard to believe I got two bad hard drives at the same time.
What do you guys think? Appreciate your input.
Lymponus
"All the great things are simple, and many can be expressed in a single word: freedom; justice; honor; duty; mercy; hope." - Sir Winston Churchill