Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!aurora!ames!ptsfa!ihnp4!chinet!ward
From: ward@chinet.UUCP (ward)
Newsgroups: comp.sys.ibm.pc
Subject: Beward: chkdsk /f
Message-ID: <1333@chinet.UUCP>
Date: Fri, 24-Jul-87 23:36:25 EDT
Article-I.D.: chinet.1333
Posted: Fri Jul 24 23:36:25 1987
Date-Received: Sat, 25-Jul-87 18:02:12 EDT
Organization: Chinet, Chicago Ill.
Lines: 19
Keywords: DOS chkdsk PC

Be aware that there is a "characteristic" of CHKDSK /F that you may not want.
  Background: when DOS encounters a 00 byte at the front of a directory entry,
it assumes the rest of the directory is empty.  For example, disk-reorg 
programs will pack all the active files to the front of the directory, then
zero all the remaining entries.  This speeds up disk access.
  CHKDSK ALSO makes this assumption: that if it finds a 00 as the first byte
of a directory entry, it assumes the rest of the directory is empty.
  Situation that can cause problems:  a program goes bonkers, and writes some
garbage into your DIRECTORY.  Among that garbage, is a 00 at the front of
a directory entry.
  Result: CHKDSK /F will find the entries in the file allocation table for
all the files that FOLLOW the 00 byte, but won't find the files in the
directory!  As such, it will create file after file (filennnn.chk) for the
files that "are actually good".
  Always DISKCOPY a diskette before doing chkdsk /f - it could save you
problems.  On a hard disk, run it without the /f and be sure the disk is not
"too trashed" before trying again with /F.  If CHKDSK reports lots of lost
files, be aware it could be because a 00 byte got into a directory
incorrectly.