Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!bbn!uwmcsd1!marque!gryphon!crash!pnet01!haitex
From: haitex@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga
Subject: Re: Semicoherent flame about Amigados.
Message-ID: <2539@crash.cts.com>
Date: 14 Feb 88 18:16:11 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 31

charles@hpcvca.HP (Charles Brown) writes:
>One thing I liked from some CP/M systems was being able to read a disk
>knowing there were errors.
>   SECTOR READ ERROR.  A=Abort, I=Ignore, R=Retry.
>Most of the files I cared about were text.  Ignoring the error allowed
>me to reconstruct most of the file.  I could then edit out the junk
>introduced by the sector error.  Of course, this may not be ideal for
>an unsophisticated user.  But in a less than perfect world we often
>have to put up with less than perfect solutions.  After all, the
>perfect solution is a disk which does not make errors.
>

        You might try a PD program called DiskX.  I found it on DevWare's
DevDisk 0026.  It is crude but can be used for retrieving text as you
described.

>It also does not pause... and then write to the disk just when you
>were about to reboot.  I have trained myself to wait 5 seconds after
>the LED goes out before I reboot.  The Amiga is the only computer I
>have needed this for.


        Yes, this is a problem.  So far I've had 4 disks go bad on me, two
of them for this very reason.  I too have become very carefull about removing
floppies.  A simple solution would be to leave the LED on until no more 
jobs are queued for the drive.


UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex
ARPA: crash!pnet01!haitex@nosc.mil
INET: haitex@pnet01.CTS.COM