Path: utzoo!mnetor!uunet!husc6!think!ames!ptsfa!well!ewhac
From: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Newsgroups: comp.sys.amiga
Subject: Re: Semicoherent flame about Amigados.
Message-ID: <5249@well.UUCP>
Date: 15 Feb 88 21:40:00 GMT
References: <2539@crash.cts.com>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: Shhh!!  We're not supposed to be on the Net!
Lines: 30

In article <2539@crash.cts.com> haitex@pnet01.cts.com (Wade Bickel) writes:
> [ ... ]  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.
>
	This is the case with the 1000.  The LEDs reflect the true status of
drive activity.  However, when it came time to create the 2000, something
got lost in the translation.

	Apparently, there is a flip-flop in the drives or drive controllers
which controls the state of the drive LED in the 1000.  When it's on, the
drive is in use.  When it's off, it's *off*.

	Evidently, some engineer at Braunschweig couldn't figure out what
this flip-flop was for, decided it served no useful purpose, and diked it
out of the 2000 design.

	And so now some users are having problems with corrupted disks
because they're removing them from the drives too soon, or killing power too
soon.

	This story is my interpretation of a story related to me by a former
C-A engineer, so it may be mutated from the actual truth.

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	ihnp4!ptsfa -\
 \_ -_		Recumbent Bikes:	      dual ---> !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor