Xref: utzoo comp.sys.amiga:75888 comp.sys.amiga.tech:17505
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bu.edu!rpi!dali.cs.montana.edu!samsung!umich!sharkey!news.iastate.edu!skank
From: skank@iastate.edu (Skank George L)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: HD Errors
Message-ID: <1991Jan6.090105.23186@news.iastate.edu>
Date: 6 Jan 91 09:01:05 GMT
References: <Plenty!> <1991Jan5.235810.25940@nas.nasa.gov>
Sender: news@news.iastate.edu (USENET News System)
Organization: Iowa State University, Ames, IA
Lines: 26

In article <1991Jan5.235810.25940@nas.nasa.gov> ranma@noc.arc.nasa.gov (Robert Michael Gutierrez) writes:
>jesup@cbmvax.commodore.com (Randell Jesup) writes:
>> 	Another point to realize is that most amiga users wouldn't know what
>> to do with an fsck-equivalent.  For non-simple problems, you had better have
>> at least a modicum of knowlege about what a FS is (ditto on Unix - imagine
>> you sterotypical person who uses Unix for word processing trying to deal
>> with a non-simple problem reported by fsck).
>
>Well, then write a good interface to an Amy version of fsck.  Odd that in the
>Messy-DOS world, there's a TON of software to help fix trashed FS's (like
>Norton, PC Tools, etc), and hundreds of thousands of these are sold to
>the public at large.

     Hmmm...  I wonder why that is???   :)  Our ITT (IBM-XT clone) has had a
ton of hard drive errors, all related to bad blocks.  It takes hours to check
the disk for bad blocks using Norton Utilities.  I can check the entire file
system on my A3000 for bad blocks in about five minutes.  I've had programs
crash while writing files, *and* had something on my mother board go bonkers
while writing files, and never had something I couldn't fix just by deleting
the file.  I'm using 2.0.

--

Fast cars,				+		--George
Fast women,				+
Fast computers.  (Not necessarily in that order)