Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!ukma!ukecc!agollum
From: agollum@engr.uky.edu (David Herron aka Admiral Gollum)
Newsgroups: comp.sys.ibm.pc
Subject: Re: AT disk or controller problems?
Message-ID: <1545@ukecc.engr.uky.edu>
Date: Thu, 27-Aug-87 01:21:11 EDT
Article-I.D.: ukecc.1545
Posted: Thu Aug 27 01:21:11 1987
Date-Received: Sat, 29-Aug-87 11:56:23 EDT
References: <444@parcvax.Xerox.COM>
Reply-To: agollum@ukecc.UUCP (David Herron aka Admiral Gollum)
Distribution: na
Organization: Univ. of KY Engineering Computing Center
Lines: 17
Keywords: General Failure reading drive C: but it's OK later

Our AT developed this once.  After running several hours it would 
get errors on certain sectors.  One of the boot sectors had this problem,
so rebooting was a bit of a crapshoot.  Finally we took it back to the
dealer, who ran it for several hours, then ran mace when it started 
showing symptoms.  Mace locked out several clusters and everything 
was fine.
Except occasionally I'd still have problems booting.  I finally used
Mace again to rewrite the boot track and the problem went away for good.

If your system develops problems after running a while, boot off a floppy
if you have to, but run your disk-checker *when the disk gives you
problems*, not after letting it rest/cool down.  Mace always reported
the disk fine when it had been allowed to cool down; the bad sectors
only appeared after prolonged use.  And don't be afraid to mark off
60 or 80k worth of space, if it's no good it's no good.

Kenneth Herron