Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!nrl-cmf!mailrus!tut.cis.ohio-state.edu!ut-sally!utah-cs!utah-gr!uplherc!sp7040!wsccs!bill
From: bill@wsccs.UUCP (Bill Housley)
Newsgroups: comp.sys.ibm.pc
Subject: Re: How do ya when your FATs corrupt?
Message-ID: <315@wsccs.UUCP>
Date: 13 Mar 88 04:14:20 GMT
References: <9765@shemp.CS.UCLA.EDU>
Lines: 31

In article <9765@shemp.CS.UCLA.EDU>, todd@SEAS.UCLA.EDU writes:
> I use the Norton utilities to save a copy of my FAT table, but how do I
> know if the FAT was good to start with?


I have had Norton tell me (sometimes, even if there is nothing really
wrong with it).  Once I did the famous DBaseIII-editor-file to big-fry
your fat-#@$^&*#$  mistake and spent 4 hours finding a disk utility that
would help me re-construct it.  ALL and I repeat ALL utilities I tried
puked all over me and it (the gore was revolting) including all of old
Norton (didn't have new Norton then, so I don't know about it).  Except
of course Norton Format (or something like that) which made the disk
more readable for the others.  The point is that the FAT format is awful
picky and it's rather obvious when it's bad, because nobody wants to
talk to it.  CHKDSK and Norton DT will at least handle it with some
grace (tell you it's bad and exit normally), others just tell you it's
the wrong format or just give you the old:

    (some kind of generic device error message): abort, retry, or ignore.
......................................................................



Kirk: But this planet is destroying it's self around us!!!

Kruge: Invigerating, isn't it!!

---------------------------------------------------------------------
UUCP !ihup!utah-cs!utah-gr!uplherc!sp7040!obie!wsccs!bill  {WSC Utah}
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Disclaimer: These opinions are my own, not those of my wife who neither
selects, sensurs, understands, nor cares about what I write here.-