It's only in event viewer if it runs at boot.
--
------------------------------------------------------------------------ --
------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
================================================= "Wesley Vogel"
It doesn't matter how you run chkdsk.exe, you still get the log in
Event Viewer.
For a peek at the chkdsk log.
Open the Event Viewer...
Start | Run | Type: eventvwr | 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.
Bootex.log can be acessed with recovery software such as Restoration.
But there is no reason to do this, unless you just want to compare what
is in the Bootex.log and what you see in the Event Viewer.
-----
Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the drive you want
to check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:
Automatically fix file system errors
Runs Chkdsk by using the /f parameter.
[[Specifies whether Windows repairs file-system errors found during
disk checking. All files must be closed for this program to run. If
the drive is currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is not available to run other tasks while the disk is being
checked.]]
Scan for and attempt recovery of bad sectors
Runs Chkdsk by using the /r parameter.
[[Specifies whether Windows repairs file-system errors found during
disk checking, locates bad sectors, and recovers readable information.
All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule the disk
checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked. If
you select this option, you do not need to select Automatically fix
file system errors. Windows fixes any errors on the disk.]]
-----
The following will create an actual, separate chkdsk log in Notepad.
Assuming the drive is C:...
Paste this into a command prompt...
CHKDSK C: /F > C:\CHKDISKLOG.TXT
Hit your Enter key.
Click YES on the popup to reboot.
After CHKDSK has run paste this in Start | Run...
C:\CHKDISKLOG.TXT
Click OK.
From:
Doug Knox <
[email protected]>
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In jll <
[email protected]> hunted and pecked:
I've been doing it my old way, i.e. highlight the drive> properties>
tools> error checking. When I do that I don't get the summary. I'll
try the suggested way. As for the second question, I'm using NTFS and
as you say it won't work.
Thanks,
jll wrote:
Thanks, that was fast. Now for a followup. How can I extract
scandisk. exe from the Win 98 CD and will it work in XP?
Thanks,
I asked the same question here recently and was told no.
--
Kenny Cargill
Hi,
Is there a way to make the XP disk error checker generate a short
summary report the way scandisk does in Win 98?
Thanks,
jll
addy is fake
will it work in XP?
NO!