Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!mips!apple!oliveb!amdahl!rtech!llama!fredb
From: fredb@llama.rtech.UUCP (Fred Buechler)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Stumpers
Message-ID: <4403@rtech.rtech.com>
Date: 5 Jan 90 15:48:58 GMT
References: <1236@srhqla.SR.COM>
Sender: news@rtech.rtech.com
Reply-To: fredb@llama.UUCP (Fred Buechler)
Organization: Relational Technology, Inc. Alameda, CA
Lines: 31

In article <1236@srhqla.SR.COM> tcm@srhqla.SR.COM (Tim Meighan) writes:
>In article <21990002@hpvcfs1.HP.COM> rexw@hpvcfs1.HP.COM
>(Rex Wickenkamp) writes:
>
>>2)  I have always wondered why CHKDSK, when used with the /F parameter,
>>    creates FILE0000.CHK files in the root directory.  Can anyone give me
>>    a good explanation of this?
>

> {Deleted}

>
>Note that CHKDSK could just as easily have automatically returned
>any lost chains back to the disk free pool.  However, the lost clusters
>are purposely converted to files instead, to give you a chance to 
>examine them just in case they contain something you need.
>
>CHKDSK will always tell you when there are lost clusters in the FAT.
>However, it won't actually convert the clusters to files unless you
>specifically tell it to with the /F (fix) switch as a command argument. 
>If you don't convert the clusters to files, they remain lost, and you
>will never be able to use them for anything.
>

Actually, CHKDSK will just return the lost clusters to the free space pool
IF you answer "NO" to the "Convert lost chains to files?" question AND you
have specified the /F (fix) flag. The *.CHK files are only created to give
you a chance to manually re-attach the chains where they belong. A tedious
task, even with Norton Utilities, et al.

Fred.