Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.games
Subject: Re: Review of Star Control From Accolade
Message-ID: <16747@cbmvax.commodore.com>
Date: 22 Dec 90 02:45:47 GMT
References: <10745@ur-cc.UUCP> <1803@robbie.tegra.COM>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 18

In article <1803@robbie.tegra.COM> nad@robbie.UUCP (Nancy Durgin) writes:
>I found a little bug that only seems to show up under 2.0 on my 3000. 
>Try pitting the Quan Dreadnought against the Alliance's kami-kaze ship,
>and have a computer-player run both sides.  Everything goes into
>slow-motion.  I'd appreciate if someone else running 2.0 (KS 2.02, actually)
>could confirm this...  Under 1.3.2, it worked fine.

	I'll bet those are bus timeouts on invalid-address accesses (the
bad-access timeouts in the A3000 hardware are something like ~1/8sec - in
any case, very long).  Running enforcer with a terminal/machine hooked to the
serial port will probably show illegal memory accesses.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)