CHKDSK Problem

Peter Jason wrote:
On Mon, 25 Jul 2011 19:38:23 -0400, "Don Phillipson"
wrote:

"Peter Jason" wrote in message
...

My other (XP) machine will not run chkdsk on the C: drive because it
shows the message "Can't open volume for direct access".
This can usually avoided by starting CHKDSK via
/Control Panel / Admin Tools / Computer Management / Disk Management
Select C: in the upper right panel and right click for menu
Select / Tools / Error Checking
This runs CHKDSK

All attempts to reload XP, or the repair disk gives the message
"The software you have is younger than this".
This is normal if your Repair CD finds you have installed
a Service Pack later than that buillt into the CD.

Thanks, I found the Computer Management and right-clicked on the C: in
the right-hand top panel. I found 'Properties', then 'Tools' and
then 'Check Now'.
I rebooted, but the same problem occurred. Incidentally, the
computer seems stuck on chkdsk because it tries after every reboot.

If you have a WinXP installer CD, you can boot to the recovery
console. It gives an MSDOS prompt. CHKDSK will run from there,
but you'd need to check a Microsoft web page to see how the
parameters may differ. (CHKDSK command differs, depending
on where it is run from.)

The recovery console can also be installed on a PC, such that
when WinXP starts, you see two entries, one for the regular
boot system, the other for the recovery console. If an installation
is so equipped, you can enter recovery console that way.

The advantage of the recovery console, is the C: drive isn't
busy, and so CHKDSK can run without being scheduled.

If you Google, you'll find there are plenty of reports
of CHKDSK looping, where you can't escape. CHKDSK runs
at startup, because of a particular registry entry, which
has scheduled it. CHKDSK can also be enabled, by keeping
the registry entry in a more "normal" state, but having
the "dirty" bit set on the partition, and then CHKDSK
runs because it sees the dirty bit. The dirty bit can
be set, but cannot be cleared, which appears to be
its design intent. (At least, I haven't seen a recipe
for turning it back off again.)

(Using FSUTIL to force CHKDSK... Only an option if you
really need it, as normally CHKDSK is only too willing to run.)

http://www.microsoft.com/resources/d....mspx?mfr=true

I have this page bookmarked, for various trivial on CHKDSK
and CHKNTFS.

http://technet.microsoft.com/en-us/l.../bb457122.aspx

A way of disabling chkdsk at startup, but you still need
some kind of environment to do it.

http://www.raymond.cc/blog/archives/...ndows-startup/

Paul