Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!ucsd!hub.ucsb.edu!dougp
From: dougp@voodoo.ucsb.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: Flopy disk error handling
Message-ID: <5115@hub.ucsb.edu>
Date: 6 May 90 06:38:43 GMT
Sender: news@hub.ucsb.edu
Organization: UC, Santa Barbara. Physics Computer Services
Lines: 24

-Message-Text-Follows-
In article <1410046@hpcvca.CV.HP.COM>, charles@hpcvca.CV.HP.COM (Charles Brown) writes...
>> Handle floppies the way it is done now, untill you get an error. If
>> you find an error on reading (the only time you can detect an error)
>> go back and retry, but do the retry syncronous to index.
> 
>But by then you have already lost data.  My intention is that you
>should never loose data.

But a read is done immediatly after a write (otherwise you could never
detect an error while writing), this is commonly known as verifing. Come
to think of it, I don't know if the Amiga verifies the write or not.
It should at liest be an option for those willing to take a performance
hit.

If an error was detected on a verify read, the track could be rewritten
in index syncronous mode, if it failed again, the block could be mapped
out.

>> 	Douglas Peale
>	Charles Brown	charles@cv.hp.com or charles%hpcvca@hplabs.hp.com
>			or hplabs!hpcvca!charles or "Hey you!"

Douglas Peale