How do I create a log file for chkdsk activity? I found two files that have
chkdsk information in them, but I don't recall how they got created.

Is there a command line option to write chkdsk output to a text file?

Thank you.

CHKDSK X: > Y:\<path>\<filename.txt>

Where X is the drive being checked, and Y:\<path> is the path to the location you want the log file created in.

For example:

CHKDSK C: > C:\temp\chkdsklog.txt

--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Jim Strenk" <(E-Mail Removed)> wrote in message news:yIWdna9IKPGvtezZRVn-(E-Mail Removed)...
> How do I create a log file for chkdsk activity? I found two files that have
> chkdsk information in them, but I don't recall how they got created.
>
> Is there a command line option to write chkdsk output to a text file?
>
> Thank you.
>
>

In addition to what Doug posted.

For a look at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
is viewed in the Event Viewer, under Application.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:yIWdna9IKPGvtezZRVn-(E-Mail Removed),
Jim Strenk <(E-Mail Removed)> hunted and pecked:
> How do I create a log file for chkdsk activity? I found two files that
> have chkdsk information in them, but I don't recall how they got created.
>
> Is there a command line option to write chkdsk output to a text file?
>
> Thank you.

Thank you Doug, for the quick reply! I had completely forgotten about the
old > sign on the DOS prompt! DOS is not Dead!

"Doug Knox MS-MVP" <(E-Mail Removed)> wrote in message
news:e4$(E-Mail Removed)...
CHKDSK X: > Y:\<path>\<filename.txt>

Where X is the drive being checked, and Y:\<path> is the path to the
location you want the log file created in.

For example:

CHKDSK C: > C:\temp\chkdsklog.txt

--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart
Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Jim Strenk" <(E-Mail Removed)> wrote in message
news:yIWdna9IKPGvtezZRVn-(E-Mail Removed)...
> How do I create a log file for chkdsk activity? I found two files that
have
> chkdsk information in them, but I don't recall how they got created.
>
> Is there a command line option to write chkdsk output to a text file?
>
> Thank you.
>
>

Thank you Wes, for your quick reply! DOS is not Dead!

"Wesley Vogel" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> In addition to what Doug posted.
>
> For a look at the chkdsk log.
>
> Open the Event Viewer...
> Start | Run | Type: eventvwr | Click OK |
> Look in Application | Listed as Information |
> Event ID: 1001
> Source: Winlogon
> [[Description: This includes file system type; drive letter or GUID, and
> volume name or serial number to help determine what volume Chkdsk ran
> against. Also included is whether Chkdsk ran because a user scheduled it
or
> because the dirty bit was set.]]
>
> [[When Autochk runs against a volume at boot time it records its output to
a
> file called Bootex.log in the root of the volume being checked. The
Winlogon
> service then moves the contents of each Bootex.log file to the Application
> Event log.]]
>
> [[This file states whether Chkdsk encountered any errors and, if so,
> whether they were fixed.]]
>
> Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
> is viewed in the Event Viewer, under Application.
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:yIWdna9IKPGvtezZRVn-(E-Mail Removed),
> Jim Strenk <(E-Mail Removed)> hunted and pecked:
> > How do I create a log file for chkdsk activity? I found two files that
> > have chkdsk information in them, but I don't recall how they got
created.
> >
> > Is there a command line option to write chkdsk output to a text file?
> >
> > Thank you.
>

Additionally, if you don't want the log file overwritten, but appended to, use >> instead of >.


--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"Jim Strenk" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Thank you Doug, for the quick reply! I had completely forgotten about the
> old > sign on the DOS prompt! DOS is not Dead!
>
> "Doug Knox MS-MVP" <(E-Mail Removed)> wrote in message
> news:e4$(E-Mail Removed)...
> CHKDSK X: > Y:\<path>\<filename.txt>
>
> Where X is the drive being checked, and Y:\<path> is the path to the
> location you want the log file created in.
>
> For example:
>
> CHKDSK C: > C:\temp\chkdsklog.txt
>
> --
> Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart
> Display\Security
> Win 95/98/Me/XP Tweaks and Fixes
> http://www.dougknox.com
> --------------------------------
> Per user Group Policy Restrictions for XP Home and XP Pro
> http://www.dougknox.com/xp/utils/xp_securityconsole.htm
> --------------------------------
> Please reply only to the newsgroup so all may benefit.
> Unsolicited e-mail is not answered.
>
> "Jim Strenk" <(E-Mail Removed)> wrote in message
> news:yIWdna9IKPGvtezZRVn-(E-Mail Removed)...
>> How do I create a log file for chkdsk activity? I found two files that
> have
>> chkdsk information in them, but I don't recall how they got created.
>>
>> Is there a command line option to write chkdsk output to a text file?
>>
>> Thank you.
>>
>>
>
>

DOS is dead, Jim, but the command line isn't. ;-)

Command-line reference

Start | Run | Copy and paste the following line:

hh ntcmds.chm

Click OK.

Double click on the closed book icon.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In newspudnRyaGt1CaO_ZRVn-(E-Mail Removed),
Jim Strenk <(E-Mail Removed)> hunted and pecked:
> Thank you Wes, for your quick reply! DOS is not Dead!
>
> "Wesley Vogel" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> In addition to what Doug posted.
>>
>> For a look at the chkdsk log.
>>
>> Open the Event Viewer...
>> Start | Run | Type: eventvwr | Click OK |
>> Look in Application | Listed as Information |
>> Event ID: 1001
>> Source: Winlogon
>> [[Description: This includes file system type; drive letter or GUID, and
>> volume name or serial number to help determine what volume Chkdsk ran
>> against. Also included is whether Chkdsk ran because a user scheduled
>> it or because the dirty bit was set.]]
>>
>> [[When Autochk runs against a volume at boot time it records its output
>> to a file called Bootex.log in the root of the volume being checked. The
>> Winlogon service then moves the contents of each Bootex.log file to the
>> Application Event log.]]
>>
>> [[This file states whether Chkdsk encountered any errors and, if so,
>> whether they were fixed.]]
>>
>> Bootex.log is then deleted. The Application Event log is AppEvent.Evt
>> and is viewed in the Event Viewer, under Application.
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:yIWdna9IKPGvtezZRVn-(E-Mail Removed),
>> Jim Strenk <(E-Mail Removed)> hunted and pecked:
>>> How do I create a log file for chkdsk activity? I found two files that
>>> have chkdsk information in them, but I don't recall how they got
>>> created.
>>>
>>> Is there a command line option to write chkdsk output to a text file?
>>>
>>> Thank you.