Hi Shelomo,
You are not supposed to run CHKDSK if
you are shelled out of another program. This is the
only way you can have open files. If you do run it
from a shell the results may not be valid. Also if
you run it with the "/f" switch it may screw up some
of your files if they are open.
Eric
Shelomo wrote:
>by'"`--
>
>It appears that many are not aware that when a program has opened a
>file for writing and written to it, until it is closed, the CHKDSK
>utility will incorrectly report lost clusters, which are just those
>that have been asigned to the file that is being written; if one uses
>chkdsk/f to "fix" the problem, one is just adding another problem.
>
>The newer SCANDISK utility does not seem to have this problem (nor
>does SCANDISK's big brother NDD), as it seems to be able to ignore
>files in the process of writing.
>
>In short, do not run CHKDSK unless you know that all files opened for
>writing have been closed. I am not sure how this is related to
>reported ARACHNE problems, but it should be more widely known. In the
>case of my installation, when I go to the DOS prompt from within my
>editor, there are often several files opened for writing, and
>everything is normal on the disk despite the lies CHKDSK tells me
>about lost clusters.
>
>
>shalom,
>
>Shelomo
>
>
>
--
__________
| Ayrx |__\_ Eric S. Emerson
| E-male:~_: ! [EMAIL PROTECTED]
`~(*)~~~~(*)~' `````````````````````````
