perpetual scandisk

[isabeau]

Im using Windows xp pro with partioned hardrive. Drive c (windows) and drive D (backup). My comp scans mt drive d everytime i boot my comp, I want to disable it. I tried searching the net and followed the instruction from microsoft support site. The support site tells me to Change the BootExecute entry from:
autocheck autochk * /r\DosDevice\C: To: autocheck autochk *
using registry editor. When i opened the registry i found out that the entry was " autocheck autochk * " so i have nothin to change. How can i disable it?

 

[stduc]

Basically the drives "dirty bit" is set - the question is - is it set correctly? or in error?

If correctly set, then the drive has problems and you should be looking at fixing them or replacing the drive. If incorrectly set then you need to clear it.

Try following the instructions is this article from Microsoft.

http://support.microsoft.com/kb/831426

Failing that try looking here.

http://support.microsoft.com/kb/316506

 

[linney]

http://support.microsoft.com/support/kb/articles/q317/2/77.asp

The workaround fix (recreating the Paging file) in this might work for Chkdsk? But (big but), that is just a guess.

You can determine whether your file system errors are legitimate. To know if you've got a file system error, you can type the following command at the command prompt:

fsutil dirty query c: (replace c: with your drive letter)

If the response is that the volume is dirty, then a file system error has occurred, and Chkdsk should run automatically at startup to fix the errors, or you can schedule Chkdsk to run if you want.


What third party programs do you have loading at Startup, anything like Norton Protect or Go Back?

Have you tried running ChkDsk /r from the Recovery Console?

How to install and use the Recovery Console in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;307654&FR=1&PA=1&SD=HSCH

Running Disk Cleanup (and Defrag, if it will run) might help.

 

[isabeau]

Thanks. i did it

 

[linney]

What and how? It might help the next visitor to this thread to know that. I'm glad you got it fixed anyway.