Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utcsri!utegc!utai!garfield!john13 From: john13@garfield.UUCP Newsgroups: comp.sys.amiga Subject: Re: Weird Bug under 1.2 (Shell 204m Disk Trash'g) Message-ID: <3382@garfield.UUCP> Date: Thu, 25-Dec-86 01:00:14 EST Article-I.D.: garfield.3382 Posted: Thu Dec 25 01:00:14 1986 Date-Received: Thu, 25-Dec-86 02:11:06 EST References: <6977@decwrl.DEC.COM> <743@watmum.UUCP> Reply-To: john13@garfield.UUCP (John Russell) Organization: Memorial University of Nfld, St. John's Lines: 19 In article <743@watmum.UUCP> rmariani@watmum.UUCP (Rico Mariani) writes: >I'm glad I'm not the only one who had this problem. I thought I was >losing my marbles or something. So far I've been "lucky", all the hits >have been on my root block which (thanks to DiskSalv or DiskDoctor) >are 100% harmless (pheww!). Track 40, surface 0, perchance? The distinction between programs is an important one, since DiskDoctor will reformat the root block if it decides it's munged. DiskSalv I remember as making a *lot* of grinding noises, but maybe it is better at recovering files...DiskDoctor always loses >= 1/2 of them, since the root block (and 1 other, usually 36 or 43) is what always goes on my disks (drive mechanism, no doubt). Or maybe the changes in file placement under 1.2 lead to more failures with marginal drives? Either way, it would be nice to one day see a read/write error message that was non-fatal... Can't wait to see that clown! John