Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!sri-spam!parcvax!hplabs!hp-sdd!ncr-sd!ncrcae!ncsu!uvacs!edison!dca
From: dca@edison.UUCP (David Albrecht)
Newsgroups: net.micro.atari16
Subject: Re: Query
Message-ID: <839@edison.UUCP>
Date: Thu, 14-Aug-86 08:41:04 EDT
Article-I.D.: edison.839
Posted: Thu Aug 14 08:41:04 1986
Date-Received: Sun, 17-Aug-86 05:48:59 EDT
References: <503@elmgate.UUCP> <8608061704.AA23758@ames-nas.ARPA>
Organization: General Electric Company, Charlottesville, VA
Lines: 19
Summary: Amiga crashes

In article <8608061704.AA23758@ames-nas.ARPA>, fouts@AMES-NAS.ARPA writes:
>      You claim that the Amiga's system software is at LEAST an order of
> magnitude more robust that the ST's.  Thinking of the blind men and the
> elephant, I would like to comment that in four hours of playing with
> a friend's AMIGA, I got about a dozen crashs.  My ST crashes about once
> a month, unless I have to reboot because the software I'm debugging has
> gone into an infinite loop.

If you decide to 'play around' with an Amiga let me give you a word to the
wise.  The system tasks and the disk driver are separate in the Amiga and
the communication is not real tight.  What this means is that the task may
prompt you to swap disks while the disk driver is still writing to it.
If you don't sit and stare at the disk light you will take the disk out
while the Amiga is writing to it.  I had quite a number of crashes that
I blame on this. Once I 'trained' myself to not pull the disk until the
light is out no matter what the screen says crashes have been extremely
infrequent.

David Albrecht