- Joined
- Nov 12, 2002
- Location
- Elsewhere
Alright, here's a stumper for everyone: I use two hard drives, a small one (10 GB) that's a few years old, and a newer one (used to be a maxtor 60GB, now it's a WD 80 GB w/ 8MB cache). Anyway, a little while ago the maxtor started acting funny. At the time, my old one was the master and the new one the slave (obvious problem, read on); both are on the same IDE. Basically, whenever I tried to use it at all, my entire computer would bog down. My mouse was jerky, programs acted as though I had no RAM. Since it had been working with this configuration for months, thought it might be a virus of some sort or hardware failure, not an OS thing. I did virus scanning, ended up reformatting the drive, nothing. I tried the maxtor in a friend's comp, it worked fine. I plugged a friend's HD into my system, that worked fine. So I thought it might be some weird thing with the maxtor, so I went out and got a WD drive. When I installed it, I made it the master and my old one the slave, thinking there might be a problem with the controller card. The first one failed in 30 minutes, made a weird clicking noise. I returned it, got another one. This one worked perfectly for a week, but now it's doing the same thing the maxtor was: my entire system bogs down when I use it, and it seems to get progressively worse. note that I have not once reinstalled my OS, I have been trying to avoid doing so. Bottom line: is it heating? has anyone had this problem? Should I just suck it up and rebuild my computer? Thanks!
Also, could it be a problem with bandwidth sharing over the same IDE?
Ok, I just figured out that the dang thing is being reset to PIO mode instead of UDMA or DMA... why this is happening I don't know, it seems to happen after the HD has been in my computer for a while though... Also, I'm on Win2K if that helps.
Also, could it be a problem with bandwidth sharing over the same IDE?
Ok, I just figured out that the dang thing is being reset to PIO mode instead of UDMA or DMA... why this is happening I don't know, it seems to happen after the HD has been in my computer for a while though... Also, I'm on Win2K if that helps.
Last edited: