I once spent a while trying to find out why my HDD in my new build wasn't working.
The IDE cable was plugged in at the HDD end and the motherboard end.
Except that it wasn't. There was an IDE cable plugged into the HDD and there was an IDE cable plugged into the motherboard. Two different cables. I had a bunch of spare cables and stuff, as you do.
Incorrectly setting the jumpers on a board for a K6-2, overclocking it from 300 to 550. The chip survived, though.
Not bothering to put the outer section back on an old tower case that had a framework and a removable outer section that covered the entire case. So I had a very open case. I was going to get around to putting the outer back on, but I wanted to play with my new toy right away! Then I knocked a pint of fizzy lemonade over it, while it was on. I recall the CPU socket fizzing and bubbling with lemonade when I took the CPU out. I washed everything in water, dried it off and reassembled it. It worked. That was the same CPU as above. Tough kit, that was.
The IDE cable was plugged in at the HDD end and the motherboard end.
Except that it wasn't. There was an IDE cable plugged into the HDD and there was an IDE cable plugged into the motherboard. Two different cables. I had a bunch of spare cables and stuff, as you do.
Incorrectly setting the jumpers on a board for a K6-2, overclocking it from 300 to 550. The chip survived, though.
Not bothering to put the outer section back on an old tower case that had a framework and a removable outer section that covered the entire case. So I had a very open case. I was going to get around to putting the outer back on, but I wanted to play with my new toy right away! Then I knocked a pint of fizzy lemonade over it, while it was on. I recall the CPU socket fizzing and bubbling with lemonade when I took the CPU out. I washed everything in water, dried it off and reassembled it. It worked. That was the same CPU as above. Tough kit, that was.



.

