Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!mintaka!geech.ai.mit.edu!rjc From: rjc@geech.ai.mit.edu (Ray Cromwell) Newsgroups: comp.sys.amiga.advocacy Subject: Re: Y.A.A.G. (Yet Another Amiga Gripe) Message-ID: <1991Feb12.212208.2873@mintaka.lcs.mit.edu> Date: 12 Feb 91 21:22:08 GMT References: <58782@eerie.acsu.Buffalo.EDU> Sender: daemon@mintaka.lcs.mit.edu (Lucifer Maleficius) Organization: None Lines: 23 In article cpc@czaeap.UUCP (Chris Cebelenski) writes: >In article fstuart@eng.auburn.edu (Frank Stuart) writes: >>In article <58782@eerie.acsu.Buffalo.EDU> skwood@acsu.buffalo.edu (Scott K Wood) writes: >>> >>> All in all, the Amiga is a wonderful machine and I probably wouldn't >>>choose another computer. However, there are always little things >>>with any system that are utterly annoying. The Amiga is no exception. >>> In 1.0-1.3 versions of Workbench (don't know about 2.0), if you wrote >>>to a disk with an error, a Read/Write error requester popped up asking you >>>to Cancel or Retry. Here's the gripe : EVEN IF YOU PRESS CANCEL, Why does >>>the OS insist on continuing the operation, nearly always resulting in >>>ANOTHER Read/Write error requester. I have tried to copy files from a bad >>>disk only to spend 5 minutes pressing Cancel on the Read/Write error >>>requesters before FINALLY the system got the hint and stopped the copying >>>process. Why does the system do this? Also, is this problem fixed in >>>the current beta-versions of 2.0? If not, is it going to be fixed? >>> >>> >>> Scott There is a PD program availible that fixes this called 'Tracksalve' It patches all the quirks/bugs in the trackdisk.device, and even enhances it. If you get an error, it will try to recover that sector.