i installed a western digital caviar 33200 (taken out of another computer) in an external enclosure (ngear 2U3488). the computer recognized a new device but said i must restart for it to work properly. upon restart, nada. i replaced it with a wd caviar 21200 and it worked right away. i then slaved the 33200 inside a computer and it was recognized. i reinstalled it into the external enclosure and tried many different jumper settings (including no jumper). when i turn on the enclosure the light (it has a blue led) shines bright and i hear the beloved "dong-ding" a few seconds later the light goes dim (still on) and i hear "ding-dong". i hooked it up to the old computer (externally) and it was recognized and i formatted it. i hooked it up to the new computer and it isn't recognized. when i hook it up to the new computer it briefly displays the "found new hardware" message but then either says there was a problem and the new hardware might not work or it just "ding-dong"s out. and the little led on the enclosure goes dim. i have a seagate 7200.9 in an identical enclosure and it works great. i also installed a maxtor d740x-6l in the enclosure and it is recognized for a while and then "unplugs" itself. i installed the maxtor as an internal hd and it works great. any ideas?
i can understand that but what i can't understand is why that western digital (caviar 33200) hd in the enclosure is recognized and works with no problem on a piece of crap computer that i found (pentium 2). i'll test it out on other computers but if it were a faulty enclosure i'd expect it to be faulty for all computers, no?
There could be some issue between the controller chip on the Maxtor hard drive and the chip in the hard drive box. You'd have to do some searching, but I wonder if there isn't some sort of issue with that pairing, or even with the USB controller on the system that it acts up on.
Just look at your event viewer, what it says about this problem. Control Panel > Administrative Tools > Event Viewer Can you see anything in there relating to your hard drive? Post that error here