D
David Dickinson
On many of our machines, chkdsk fails to execute upon restarting Windows XP
Home or Professional using the NTFS file system.
We have machines with single and multiple drives. On the single drive
machines, it's hit-or-miss whether or not chkdsk will execute upon restart
regardless of whether it's called from the command line or through the
Explorer\My Computer interface (right-click a drive, Properties, Tools,
Check Disk, etc.) Most often (by far) it does not execute.
On machines with multiple drives, some of the drives /may/ be checked but
others /will not/ be checked, whether using the Explorer interface or
command line calls such as:
chkdsk c: /F
chkdsk d: /F
chkdsk e: /F
with the apropriate "Y" responses to the prompt to perform the check on
restart. However, upon a subsequent (second) restart, chkdsk /may/ execute.
I'll be grateful for any hints as to why this is happening and what I can do
about it.
David Dickinson
eis at softhome dot net
Home or Professional using the NTFS file system.
We have machines with single and multiple drives. On the single drive
machines, it's hit-or-miss whether or not chkdsk will execute upon restart
regardless of whether it's called from the command line or through the
Explorer\My Computer interface (right-click a drive, Properties, Tools,
Check Disk, etc.) Most often (by far) it does not execute.
On machines with multiple drives, some of the drives /may/ be checked but
others /will not/ be checked, whether using the Explorer interface or
command line calls such as:
chkdsk c: /F
chkdsk d: /F
chkdsk e: /F
with the apropriate "Y" responses to the prompt to perform the check on
restart. However, upon a subsequent (second) restart, chkdsk /may/ execute.
I'll be grateful for any hints as to why this is happening and what I can do
about it.
David Dickinson
eis at softhome dot net