Usually when I run chkdsk and it finds an error I use chkdsk /f and restart
the computer to fix it. Today I tried doing the same and it skips doing the
chkdsk. I did a search for chkdsk.exe and found the following:

c:\WINNT\$NtServicePack1Uninstall$
c:\WINNT\$NtUpdateRollupPackUninstall$
c:\WINNT\Service PackFiles\i386
c:\WINNT\system32
c:\WINNT\system32\dllcache

I ran the "chkdsk.exe" in "\system32" and the one in "\system32\dllcache"
and they both run so the problem seems to be in the handling of the "/f"
parameter. Either how it gets set, may not be working properly or how it
gets recognized on start-up may not be working. Anyone know which files
handle these tasks? I have a cloned backup disk from a few weeks ago that I
could use to replace suspect files on the problem disk.

Thanks for any info you might have,
Marv

You didn't mention what happens when you try but if you get an error
something to the effect "cannot open volume for direct
access" There is some system/boot start device that is reading/writing to
the drive before chkdsk can get a lock on the drive. Some anti-virus
applications do this.

After backup you can also run;
chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %windir% or %systemroot%


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Marv Raybin" wrote:
| Usually when I run chkdsk and it finds an error I use chkdsk /f and
restart
| the computer to fix it. Today I tried doing the same and it skips doing
the
| chkdsk. I did a search for chkdsk.exe and found the following:
|
| c:\WINNT\$NtServicePack1Uninstall$
| c:\WINNT\$NtUpdateRollupPackUninstall$
| c:\WINNT\Service PackFiles\i386
| c:\WINNT\system32
| c:\WINNT\system32\dllcache
|
| I ran the "chkdsk.exe" in "\system32" and the one in "\system32\dllcache"
| and they both run so the problem seems to be in the handling of the "/f"
| parameter. Either how it gets set, may not be working properly or how it
| gets recognized on start-up may not be working. Anyone know which files
| handle these tasks? I have a cloned backup disk from a few weeks ago that
I
| could use to replace suspect files on the problem disk.
|
| Thanks for any info you might have,
| Marv
|
|