I want to log the results of chkdsk, because XP doesn't leave it up on the
screen long enough for me to read it. The parameters that I can pass, however
(I usually use /F, /V, and /R) don't include a log file for when I check disk

How can I set up a chkdsk log? I tried Google and this forum, no luck.

Running XP Home Edition, SP2, full updates.

Thanks in advance.

Moxieman

Moxieman wrote:
> I want to log the results of chkdsk, because XP doesn't leave it up on the
> screen long enough for me to read it. The parameters that I can pass, however
> (I usually use /F, /V, and /R) don't include a log file for when I check disk
>
> How can I set up a chkdsk log? I tried Google and this forum, no luck.
>
> Running XP Home Edition, SP2, full updates.
>
> Thanks in advance.
>
> Moxieman

If you run chkdsk without any of the switches that require the volume to
be locked or unmounted, you can just pipe the output to a text file:

chkdsk > C:\checkdisklog.txt

Because you won't see any output, you'll need to wait (in a Command
Prompt window) until you see the command prompt reappear.

If you run chkdsk with the /f or /r switches, the volume must be locked.
Because the system is using the volume (assuming that you're checking
the partition on which Windows is installed), it can't be locked, so
chkdsk offers to run at the next reboot. If you OK this, what happens
is that a module named autochk.exe is scheduled to run at the next
restart. See http://support.microsoft.com/kb/314835/en-us which
includes the following:

<quote>
However, if CHKDSK is scheduled to run when the computer restarts, the
binary module that contains the verification code is Autochk.exe, a
native Windows program. Because Autochk.exe runs early in the computer's
startup sequence, Autochk.exe does not have the benefit of virtual
memory or of other Win32 services.

Autochk.exe generates the same kind of text output that the Chkdsk.exe
utility DLLs generate. Autochk.exe displays this text output during the
startup process and also logs an event in the application event log. The
logged event information includes as much of the text output as can fit
into the event log's data buffer.
</quote>

So, look in Event Viewer Application log for the first event after the
reboot. The "source" will be "Winlogon" and have Event No. 1001.

This KB article, although written for Win2K, may also be of interest:
http://support.microsoft.com/kb/218461

--
Lem -- MS-MVP - Networking

To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm

Perfect! Thank you very much. Went to Event viewer and there it was.

Moxieman

"Lem" wrote:

> Moxieman wrote:
> > I want to log the results of chkdsk, because XP doesn't leave it up on the
> > screen long enough for me to read it. The parameters that I can pass, however
> > (I usually use /F, /V, and /R) don't include a log file for when I check disk
> >
> > How can I set up a chkdsk log? I tried Google and this forum, no luck.
> >
> > Running XP Home Edition, SP2, full updates.
> >
> > Thanks in advance.
> >
> > Moxieman
>
> If you run chkdsk without any of the switches that require the volume to
> be locked or unmounted, you can just pipe the output to a text file:
>
> chkdsk > C:\checkdisklog.txt
>
> Because you won't see any output, you'll need to wait (in a Command
> Prompt window) until you see the command prompt reappear.
>
> If you run chkdsk with the /f or /r switches, the volume must be locked.
> Because the system is using the volume (assuming that you're checking
> the partition on which Windows is installed), it can't be locked, so
> chkdsk offers to run at the next reboot. If you OK this, what happens
> is that a module named autochk.exe is scheduled to run at the next
> restart. See http://support.microsoft.com/kb/314835/en-us which
> includes the following:
>
> <quote>
> However, if CHKDSK is scheduled to run when the computer restarts, the
> binary module that contains the verification code is Autochk.exe, a
> native Windows program. Because Autochk.exe runs early in the computer's
> startup sequence, Autochk.exe does not have the benefit of virtual
> memory or of other Win32 services.
>
> Autochk.exe generates the same kind of text output that the Chkdsk.exe
> utility DLLs generate. Autochk.exe displays this text output during the
> startup process and also logs an event in the application event log. The
> logged event information includes as much of the text output as can fit
> into the event log's data buffer.
> </quote>
>
> So, look in Event Viewer Application log for the first event after the
> reboot. The "source" will be "Winlogon" and have Event No. 1001.
>
> This KB article, although written for Win2K, may also be of interest:
> http://support.microsoft.com/kb/218461
>
> --
> Lem -- MS-MVP - Networking
>
> To the moon and back with 2K words of RAM and 36K words of ROM.
> http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
> http://history.nasa.gov/afj/compessay.htm
>