Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site wlbr.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!nsc!voder!wlbr!steve From: steve@wlbr.UUCP (Steve Childress) Newsgroups: net.micro.amiga,net.micro.atari Subject: Re: amiga a non-entry at Seattle Compufair Message-ID: <382@wlbr.UUCP> Date: Mon, 28-Oct-85 18:54:17 EST Article-I.D.: wlbr.382 Posted: Mon Oct 28 18:54:17 1985 Date-Received: Wed, 30-Oct-85 04:55:41 EST References: <401@ssc-bee.UUCP> Distribution: net Organization: Eaton IMS, Westlake Village, CA Lines: 16 Xref: watmath net.micro.amiga:520 net.micro.atari:1519 Summary: Crashes == (bad_hardware !! bad_software !! cockpit trouble) In article <401@ssc-bee.UUCP>, ditzel@ssc-bee.UUCP (Charles L Ditzel) writes: > Are all the Amiga and Atari horror stories just isolated > incidents or is there a trend ??? > > Are we talking about intrinsically bad hardware design or > just loose chips??? In my years of experience, crashes are usually the fault of software, not hardware. The exception is when a VERY immature hardware design is in use. Regards, Steve Childress {trwrb, scgvaxd, ihnp4, voder, vortex} !wlbr!steve or ...wlbr!wlbreng1!steve