Drive access problem

Alright, I can't access my D: drive.

This all started today when I turned on my computer and the hard drive light continued to flash even though all loading was done. When I tried to got to My Computer, it went unresponsive at first, and the D: drive had some how mysteriously renamed itself to Local Disk when it had previously been named something else.

I ran Spy Sweeper and it found something called Trojan_backdoor_zubox_1.

I imeadiately removed the Trojan with Spy Sweeper. However, my computer is running slower than usual, My Computer is a bitch to access and when I try to access D: (after fighting with My Computer to work) it says something like "Cannot access D:. There is an I/O device failure". However, the system says that the hard drive is healthy and functioning properly. I can access E: which is on the same hard drive as D:.

Can anyone help?

(And yes, I'm using Windows XP)

Dunno about your hdd failure, but Zubox is a false positive on the BullGuard antivirus program. It detects ATI catalyst drivers as a trojan.

Could be a corrupted partition table, could be that the area of the drive that your drive D: occupies is damaged and suffering CRC errors (the "I/O device failure" message is one I've come across before when a hard drive is suffering read errors). The prognosis does not look good, IMO. I doubt the discovery of the possible trojan has anything to do with the hard drive failure - it could have been lurking there weeks or months, and it was only the hardware failure that prompted you to run Spy Sweeper.

As for advice, get hold of Spinrite and run a level 4 diagnostic on the offending drive. I'd better dollars to doughnuts it'll report a problem.

To be fair, the ATI catalyst drivers suck about as hard as a trojan would...

>>5
gotta agree with you there

ATI used to be better than nvidia, too... I was a big fan. I gotta say they dropped the ball, though. I remember the first time I installed my 9200, the computer went into an endless reboot loop using the stock XP vga drivers

As a Linux luser I'm used to hearing people bitch about ATI. I wasn't aware they sucked gonads on Windows as well.

I mean, ATI cards, not bad, I don't think.  But a card has to have decent drivers, or it ends up just being ass.  ATI's drivers have gotten progressively worse over the years.

But anyway, back to the disk error, I would try booting into like, a knoppix live CD, and trying testdisk on the thing.  If the partition is damaged, it may be able to find the partition, and repair it.

>>3

Hmm, yes, I suppose that could be it. However, it's not the entire hard drive as I can still access and run things from both E: and F: which are on the same gard drive.

 I think it may be a partition thing as >>8 said.

 I'll have to try the knoppix thing later. (Thank god Linux is free)

IIRC, Knoppix can't do jack shit with the NTFS file system except read it. You're not going to be fixing anything with linux.

>>10
Actually the ntfs project has got to the point where writing is more-or-less safe.

Knoppix Hacks has a whole chapter on repairing Windows. One of these days I might even buy and read it.

With testdisk, it can find the partition, and possibly recover it.  You can't do anything with the files, but, say the problem is just that the MBR is like "no, there's no partition there teehee" (which was a problem I had on an external drive), it'll rewrite it, and off you go.  Most of the shit you need comes in the knoppix-std live cd.

Of course, your problem may be different.