Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!marque!gryphon!richard
From: richard@gryphon.CTS.COM (Richard Sexton)
Newsgroups: comp.sys.amiga
Subject: Re: Hard Drive Grumbling
Message-ID: <2137@gryphon.CTS.COM>
Date: 14 Jan 88 07:45:20 GMT
References: <2060@gryphon.CTS.COM> <3128@cbmvax.UUCP>
Reply-To: richard@gryphon.CTS.COM (Richard Sexton)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 41

In article <3128@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
I write:
>> Summary: floppies too
>
>> as long as we're talking about filesystem wierdnesses, heres one:
>
>> I have corrupted floppy. I have been able to DiskSalv the files
>> off it, but if I try to CD to it or even DiskCopy it, the machine
>> Guru's.
>
>
>Not sure what is corrupted, but it's certainly not all that weird.  DiskSalv
>doesn't assume any more than it has to about the state of a disk, and as
>such isn't going to crash on anything I've seen so far in the way of disk
>corruption.  The DOS, however, does make certain assumptions, I'm not all
>that sure just what, but if something is completely out of wack, there's a
>definite possibility of the DOS crashing on it.   I suppose the DOS could
>have been built to avoid such crashes by checking all the important data it
>looks at, but that may have been too damaging to DOS speed to implement.

Say what ? Couldn't we like, make it an option ? Like, -s for secure,
for those people willing to give up 35 milliseconds per disk access 
all so it doesn't guru (which IS annoying on a multi tasking system).

Reminds me of a job I had once:

"Hey boss, look how much faster DiskCopy is"

"What did you do"

"Took out the verify pass"

"Very good Richard. Your last official act here will be to put it back
in. Our customers want RIGHT not FAST."



-- 
      It's too dark in Santa Fe in my ignition, or something like that.
                          richard@gryphon.CTS.COM 
   {ihnp4!scgvaxd!cadovax, philabs!cadovax, codas!ddsw1} gryphon!richard