Path: utzoo!censor!geac!maccs!cs4g6ag
From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Stumpers
Message-ID: <25A51804.9795@maccs.dcss.mcmaster.ca>
Date: 5 Jan 90 21:56:20 GMT
References: <21990002@hpvcfs1.HP.COM>
Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Organization: McMaster University, Hamilton, Ontario
Lines: 21

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?

   Well, to put it bluntly, because that's what it's supposed to do!

   These files are created when CHKDSK/F finds lost clusters (a cluster is
a group of an integral power of two sectors, and is the smallest unit of
disk space that can be allocated; a lost cluster is a cluster which is not
part of a file and which is also not part of the free space on the disk ...
in other words, it's in limbo).  Each time it finds a chain of lost clusters,
it creates another file out of it.  When you delete these files, the formerly
lost space once again becomes available.

   Hope this helps!
-- 
Stephen M. Dunn                               cs4g6ag@maccs.dcss.mcmaster.ca
          <std_disclaimer.h> = "\nI'm only an undergraduate!!!\n";
****************************************************************************
    If it's true that love is only a game//Well, then I can play pretend