Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!udel!new
From: new@udel.EDU (Darren New)
Newsgroups: comp.sys.amiga
Subject: Re: Bad floppy crashes system and Support FLAME!!
Message-ID: <15583@louie.udel.EDU>
Date: 16 May 89 16:31:36 GMT
References: <0473.AA0473@myhut>
Sender: usenet@udel.EDU
Reply-To: new@udel.EDU (Darren New)
Organization: University of Delaware
Lines: 13

In article <0473.AA0473@myhut> gmd@myhut.UUCP (George MacDonald) writes:
>Anyhow as soon as I pop in the floppy the guru comes right back! Arrgh!!

I have not used it, but the latest version of DiskSalve is documented
as avoiding this problem. Start DiskSalve first, wait for some prompt
or other (sorry, from memory) and then put in the disk. By this time,
the drive has been snatched out from under the filesystem, which will
therefore not check the disk. Diskcopy can be used to copy it by starting
Diskcopy from the CLI and waiting for the "put in the disk" prompt before
inserting any disks. Workbench will show the disks as "DF?:BUSY" which
is your clue that it is safe. (Of course, Diskcopy probably wont fix
your problem, but if the files are important, you may want to do this
until you get DiskSalve.) Anyway, try DiskSalve. -- Darren New