If you're having trouble with defrag, run Error Checking (chkdsk.exe).
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.]]
You have to reboot for Error-checking to run.
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.
Bootex.log can be acessed with recovery software such as Restoration.
Chkdsk
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_tol_pwfd.asp
Chkdsk
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx
Describes how to use the chkdsk command at the command line.
http://www.microsoft.com/windowsxp/...WINDOWSXP/home/using/productdoc/en/chkdsk.asp
An Explanation of the New /C and /I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/default.aspx?scid=kb;en-us;314835
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
