Re: Checkdisk - Boot Execute key for autocheck on Win2k

Yeah, I got it on my own. I just had the strings in the
wrong order. It is ultra important to have the specific
autocheck string (autocheck autochk /p \??\C before the
general autocheck string. Otherwise, it puts itself into
an endless checkdisk loop.

-C

>-----Original Message-----
>Chris Caran wrote in news:03be01c33c1d$74cac5f0
$(E-Mail Removed):
>
>> I'm trying to programatically start Checkdisk when the
>> user reboots. The registry key I used correctly sets
it
>> off, but it doesn't appear to clear itself out of the
>> Boot Execute key until I manually cancel the
checkdisk.
>> Does anyone know why this is? Am I missing something?
>>
>> The key is:
>>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Sessio
>> n Manager\BootExecute
>>
>> The original value is (without quotes) "autocheck
autochk
>> *"
>> It is a REG_MULTI_SZ - I added the following string to
>> the end of it:
>> "autocheck autochk /r \??\C:" which enables checkdisk
to
>> run on the C drive. I just don't know why it won't
STOP
>> running.
>
>Okay. I must have misunderstood. Is it that you want
chkdsk to run
>after a reboot (even if not "dirty")? 1) set the
drive's "dirty bit".
>I'd have to hunt that down as I can't recall the
details. 2) when you
>manually schedule a chkdsk this is done:
>
>The valuename you mentioned is modified but you said "I
added the
>following string to the end of it:" As a multi-string
value both the
>line-ender (CR LF) and the order of the entries is
important. The
>manually scheduled chkdsk is added as the first line (in
front of) the
>standard line and looks like
> autocheck autochk /p \??\C:
> autocheck autochk *
>
>If you shedule yet another volume then it to is
added "at the top":
> autocheck autochk /p \??\D:
> autocheck autochk /p \??\C:
> autocheck autochk *
>
>Is that it? (won't reboot here just to test it now)
>
>
>
>
>
>
>.
>