Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!rutgers!rochester!rit!cci632!ccicpg!paulm
From: paulm@ccicpg.UUCP (tmp Paul Moreau usenet acct)
Newsgroups: comp.sys.atari.st
Subject: Re: Is there a (reliable) CHKDSK for the ST?
Summary: fsck not so hot
Message-ID: <56875@ccicpg.UUCP>
Date: 6 Feb 90 17:40:06 GMT
References: hard disk, FAT integrity <1990Jan31.032956.28008@gpu.utcs.utoronto.ca> <1255@lzsc.ATT.COM>
Organization: ICL North America (Business Systems), Irvine, CA.
Lines: 52

In article <1255@lzsc.ATT.COM>, hcj@lzsc.ATT.COM (HC Johnson) writes:
> In article <1990Jan31.032956.28008@gpu.utcs.utoronto.ca>, romwa@gpu.utcs.utoronto.ca (Royal Ontario Museum) writes:
> > Sorry if this has come up before, but I am really in need of info
> > regarding a reliable way to verify the integrity of the FAT.
> > Hopefully, the program should also go ahead and fix lost clusters,
> > etc. as automatically as possible.
> > 
> fsck.prg was previously posted.  It works well up the 16 meg partitions.
> 
> Since TOS 1.4 supports up to 32 Meg partitions, I have modified fsck.prg.
> I will send it to anyone who writes.
> 
> Howard C. Johnson
> ATT Bell Labs
> =====NEW address====
> att!lzsc!hcj
> hcj@lzsc.att.com

  Last night while attempting to extract files using unlzh12.prg the system
  sat for a while blinking the drive light then crashed with 2 bombs.
  After rebooting the system I attempted to extract the files again using
  unlzh11.prg.   It then came up with an error saying that there was
  insufficient space on Drive E to extract the files!   Using the desktop
  show info it said that drive E had around 4 megs used with 0 bytes free.
  My E partition is a 16 meg partition!   I then used fsck which quickly
  exited saying that all was fine!   Around 1 year ago I wrote a program
  called dskana which bypassed all DOS calls, read the boot and  partition
  blocks and with a built in driver read the FATs , directories and checked
  the blocks used by each file to make sure  that they didn't use any more
  or less sectors than they should and also check to make sure they didn't
  use any blocks previously used while building a memory image of the FAT
  while tracing.  At the end it compared it's FAT with the one on the DISK
  and showed a whole Sh*t load of blocks that were marked in use but not
  assigned to any particular file!  Fortunatly I had the partition backed
  up so I had to use a SUPRA utility to 'clear' the partition which also
  cleared the directories and FAT entries.  Just deleting all the files
  still left all those entries in the FAT since they weren't assigned to
  any files for directories.
  My point is that FSCK didn't do the job for a standard 16 meg partition!
  Now I'm working on dskana to not only find errors but to correct them.
  I'll also make it more general purpose and if I get it working I'll post
  it to whomever may want it.
---
  .==========================================================.
  | ### ####### ###     |    N O R T H    | /==============\ |
  | ### ###     ###     |  A M E R I C A  |< An STC Company >|
  | ### ####### ####### |    (was CCI)    | \==============/ |
  |----------------------------------------------------------|
  | UUCP:  ...ccicpg!dl2!paulm   |      Paul L. Moreau       |
  |   or   ...ccicpg!dl1!paulm   | Diagnostics Software Eng. |
  |   or   ...ccicpg!paulm       |    Irvine, California     |
  `=========================================================='