The drive was connected to the power, the USB cable connected to the hub, Windows emitted a sound and voila - Nothing! GF had to return to debug mode. Could this be the PC or was it the drive?
He disconnected it and connected it to a laptop - Windows emitted it's sound and voila - still nothing. GF restarted the laptop. Nada.
Could it be the cables? He checked they were firmly seated in the sockets and tried again, niet.
Then he noticed that he had picked up the wrong cable and had been attaching his external DVD drive instead of the HDD all along. This could just be the source of the problem! Someone must have laced the local water supply with stupid pills - GF drank deeply!
2 comments:
As someone who recently had to do a system restore on his home Windows laptop and found to his dismay that his most recent C: drive backup image was 20 months old, I am perhaps not the most credible of advisers on computing matters at the moment. Nonetheless the following may be useful.
I have long had the habit of labelling the ends of connecting cables. Standard practice when dealing with bundles of CAT5 cables at work, but also not as overkill as it might seem at home when the cabling under your desk has reached the cat's cradle stage.
You can label the cable ends with the name of the device if you prefer but I find it enough to number them so I can do a quick sanity check that if USB cable No 3 is connected the device then I should be finding the other end of USB cable No 3 plugged into the hub if smooth progress is to be expected. A simple printed or handwritten label sellotaped near either of end of the cable does the trick.
Excellent advice. Something GF has been meaning to do for a long time. This may just be the impetus!
Post a Comment