Why in the world would you ned a boot CD to execute a chkdsk /R? It's a
piece of cake. What am I missing.
Basic clue:
1) ChkDsk /R implies suspected failing HD
2) HD-booted Windows ALWAYS writes to the HD
3) Most systems store all HD data in one doomed NTFS C:
It appears as if the original poster is aware of these issues, and
therefore wants to exclude HD errors BEFORE allowing Windows to
scribble all over the at-risk disk (think AutoChk, SR, etc.).
But ChkDsk /R is not a suitable tool for the job, because:
- it may test file system before checking disk surface
- it tries to "fix" things, without prompting you first
So you have a tool that tries to write file structure logic changes to
a disk that has not yet been tested to see if it is safe to write to.
It's better to test first the hardware, and only once you know that is
OK, the file system. If NTFS or > 137G, you're chained to ChkDsk for
the latter, but you can use HD Tune (free from
www.hdtune.com) to
check the HD at the hardware level (ignoring file systems, and without
trying to "fix" things).
There's still the risk that the HD's firmware will try to "fix", but
you can check SMART details to assess whether this is already
happening before you do the "slow" surface test.
HD Tune needs admin rights to operate, which is a problem when run
from the Vista DVD's mOS mode. But it will work perfectly from a Bart
bootable CDR, so you could beg an XP user to build one of those.
---------- ----- ---- --- -- - - - -
On the 'net, *everyone* can hear you scream