I'm pretty ticked off right now. I recently bought a
WD Elements Desktop external harddrive on the recommendation of a Fry's employee (all it says on the package is "WD Elements" but I assume the whole family is basically one product). My computer refuses to recognize it as existing. Since there's a pretty limited list of things to mess with here, I figured I'd go ahead and start asking for help now.
I have a hunch that it's a driver problem, but actually finding the driver in question is proving frustrating. Western Digital does not provide drivers with the drive
or on their website because they insist all relevant drivers are included in the Windows XP installation (and other versions). However, ever since I reformatted my computer early this year (and kinda botched it up), it bitches at me while windows is starting that it needs to install some harddrive driver that it can never identify or find. Since the internal drive works, I always assumed it was just being stupid, and wrote it off as a non-issue. But since the Automatic Updater doesn't seem to know what it's looking for, I sure as Hell don't either. It's also possible that my version of XP simply doesn't have the drivers Western Digital insists it would, since the external drive is NFTS, and I'm pretty sure the included one from 2003 or whenever this clunker was built is not.
Googling for answers is totally fruitless, because I'd have to wade through dozens of pages of related but useless troubleshooting guides, and I haven't found anything like a relevant driver-download. Everywhere seems to assume the use of the system factory-restore disc, which A) would be for a different version of XP than what I have installed now, B) didn't work before, and C) I don't know where it is, and it seems ridiculous that I can't find a way to download the relevant drivers regardless. I'm going to look around in the BIOS next, but since it's a USB drive, I don't know what I'm looking for. If anyone knows of a good one-stop-shop for drivers, I'd love that, but I don't even know if that's the problem. At least it might shut up the Updater finally.