Now you know. ChkDsk can fix all sorts of crap. If you haven't ever ran the option "Scan for and attempt recovery of bad sectors" you may want to let it run on each of your hard disk(s) when you aren't going to be using your computer for a couple of hours, the time it takes depends upon your hard disk(s) speed and size. Like I already stated in a previous post or two I run "Scan for and attempt recovery of bad sectors" once every 1 to 3 months, and I always run it on a new system I get.
That was what I wanted clarified, I didn't really think you'd be running all the options every day.Now you know. ChkDsk can fix all sorts of crap. If you haven't ever ran the option "Scan for and attempt recovery of bad sectors" you may want to let it run on each of your hard disk(s) when you aren't going to be using your computer for a couple of hours, the time it takes depends upon your hard disk(s) speed and size. Like I already stated in a previous post or two I run "Scan for and attempt recovery of bad sectors" once every 1 to 3 months, and I always run it on a new system I get.
I posted that question about HDCleaner on MajorGeeks, where I got the program. I got a response from one of the old hands there, he checked it out with Process Explorer. Chkdsk.exe wasn't flagged as a running process, he said, it seems like it is separate. He didn't offer a clear opinion on whether it's as good, just said that "if it is separate, it looks capable enough." I think it looks good, too, but it's kinda hard to judge performance from that.
I posted that question about HDCleaner on MajorGeeks, where I got the program. I got a response from one of the old hands there, he checked it out with Process Explorer. Chkdsk.exe wasn't flagged as a running process, he said, it seems like it is separate. He didn't offer a clear opinion on whether it's as good, just said that "if it is separate, it looks capable enough." I think it looks good, too, but it's kinda hard to judge performance from that.
Well I suppose chkdsk.exe wouldn't be hard to combine/embed into an app if Microsoft gave permission since it's only 11.5 KB (11,776 bytes), so who knows how HDCleaner is scanning the disk for errors, it could even be calling it another way that doesn't show up in Process Explorer such as a hidden external Command Window.
From what I could tell it was giving similiar information as chkdsk.exe does when using it in a Command Prompt (which is what I use) because that's the only way it will report any errors such as volume bitmap errors, or minor inconsistencies. The GUI version via right clicking a drive in My Computer doesn't state squat about what's wrong.
However it's being done, you've got to like the way it's executed. The GUI is lots better than what Windows Chkdsk has, and you shouldn't have to run it from Command Prompt in order to get any information from it.
MS should adopt something similar, a lot more users would run Chkdsk regularly if they made it that easy.
Nothing is faster an easier than what I do, which is:
1. Dump a batch file such as "Check Disk.bat" into C:\Windows
2. Input the command line chkdsk parameters you want to use, mine are:
CHKDSK.EXE /X /V /F D:
CHKDSK.EXE /V C:
3. Create a shortcut on the Desktop that points to C:\Windows\Check Disk.bat and all I have to do is double click it to have my disks scanned for errors.
I only have it clean indexes on C: which will report any errors because the fix command won't work for my C: drive for some reason. Instead to fix errors on C: I run: FSUTIL.exe DIRTY SET C:
and then reboot.
Nothing is faster an easier than what I do, which is:1. Dump a batch file such as "Check Disk.bat" into C:\Windows
2. Input the command line chkdsk parameters you want to use, mine are:
CHKDSK.EXE /X /V /F D:
CHKDSK.EXE /V C:
3. Create a shortcut on the Desktop that points to C:\Windows\Check Disk.bat and all I have to do is double click it to have my disks scanned for errors.
I only have it clean indexes on C: which will report any errors because the fix command won't work for my C: drive for some reason. Instead to fix errors on C: I run: FSUTIL.exe DIRTY SET C:
and then reboot.
That's fast and easy when you know how to do that stuff, but the average Joe Blow wouldn't have a clue how to create a batch file, and if he saw the Command Prompt window he'd be scared to death.