Path: utzoo!attcan!uunet!husc6!think!ames!pasteur!ucbvax!decwrl!decvax!tektronix!tekgen!tekigm2!phils
From: phils@tekigm2.TEK.COM (Philip E Staub)
Newsgroups: comp.sys.amiga
Subject: Re: HELP! Corrupted Disks
Keywords: This seems to be a common problem, no ?
Message-ID: <3052@tekigm2.TEK.COM>
Date: 12 Jun 88 04:44:51 GMT
References: <1544@edison.GE.COM> <4005@cbmvax.UUCP>
Reply-To: phils@tekigm2.UUCP (Philip E Staub)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 46

In article <4005@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
<In article <1544@edison.GE.COM> mfs@edison.GE.COM (mfs @ Somewhere in the Mountains) writes:
<> 
<> I have a new (4 month old) Amiga 500 that has started giving me all
<> kinds of trouble with the disks.  It seems everytime I turn around, I get
<> the infamous 'Volume xxxx has a read/write error' requester.  Sometimes
<> I can edit or download for hours before this happens and sometimes it
<> just takes a few minutes.
<> 
<> I have tried all kinds of disks: Sony, BASF, Memorex and Generics.
<> They all seem to eventually go bad.  The funny thing is, when I run
<> diskdoctor on them, they all (with rare exceptions) have hard errors
<> on track 40.  Also, after diskdoctor finishes, I get a requester
<> that says: Insert volume Lazarus.  I have never had a disk named this!
<> What exactly is going on here ?! 
<
<Sounds for sure like some kind of drive alignment problem or other
<drive related defect...
<
<-- 
<George Robbins - now working for,	uucp: {uunet|ihnp4|rutgers}!cbmvax!grr
<but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
<Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)

Sounds more to me like the infamous Delay(0) bug. By any chance are you
using an older version of Steve Drew's shell? (like about 2.4, I think).
There was one of those versions which I had regular problems similar to what
you describe. The shell had a certain configuration in which it could call
Delay() with a parameter of '0' and somehow (I've never bothered to
investigate either the source in the Shell or the cause of the problem in 
Delay, but I seem to remember Neil Katin posting something a while back
indicating that the bug is indeed in Delay and would be fixed... sooner or
later)

To check this: don't use the shell. To fix: get a newer version.

Also, Lazarus is the name which DiskDoctor gives any disk which it has
"resurrected".


Phil
-- 
------------------------------------------------------------------------------
Phil Staub        
Tektronix, Inc., Vancouver, Washington 98668
phils@tekigm2.MEN.TEK.COM