From: "Hrvoje Mesing" 


"Rich Gauszka"  wrote in message
news:41487d0f{at}w3.nls.net...

> http://searchwin2000.techtarget.com/tip/1,289483,sid1_gci990696,00.html?track
=NL-118&ad=486183
> There are a few ways to manually override this. The first is to run CHKDSK
> /F on the drive in question; if it runs successfully, the AUTOCHK.EXE
> command is cleared and the system will no longer be checked at each
> reboot. Another way to do it is to edit the Registry directly and remove
> the AUTOCHK command. To do this, navigate to
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager in the
> Registry and look for a REG_MULTI_SZ value with the name BootExecute. Set
> the value of BootExecute to a null value. This will prevent AUTOCHK from
> running on next reboot.
>
> On the whole, it's safest to first attempt to use CHKDSK /F on the drive
> that is being repeatedly checked at startup. Editing BootExecute should
> only be done if CHKDSK doesn't seem to be working. Running CHKDSK also has
> the added bonus of manually clearing the dirty bit.


-+-

Well, chkdsk /f clears the manually set dirty bit, but not on the primary
partition - system partition.
AutoChk Reg values are correct and not changed by the manually set dirty command.

Also, when i set dirty bit on the primary partition (C:) and also initiate
chkdsk c: /F (schedule for next reboot) i get a strange thing: Chkdsk
starts and runs, then i get a winXP boot logo, then it restarts, then it
performs a chkdsk again - then restarts, then boot cleanly. Maybe its a
bug, or its forcing commands which is a leak of logic because first chkdsk
performed Ok + said that there is no problems - *hah!* :)

Well, Ill manage, tnks! - Also, there is chkntfs /? - check it, is Handy!


-+-
M.

--- BBBS/NT v4.01 Flag-5