Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!rutgers!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <15924@cbmvax.commodore.com>
Date: 17 Nov 90 06:14:51 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu> <15756@cbmvax.commodore.com> <90316.091455GIAMPAL@auvm.auvm.edu> <1834c248.ARN04024@adspdk.UUCP> <15887@cbmvax.commodore.com> <2455@wn1.sci.kun.nl>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 14

In article <2455@wn1.sci.kun.nl> rhialto@cs.kun.nl (Olaf Seibert) writes:
>>these errors.  (Each hardware bus error imposes a 1/4 sec pause).
>
>Why does it take so long? You must execute an awful lot of code
>to take 1/4 second.

	No, that's the hardware Bus Error timeout.  It's waiting for an
acknowlege of a bus xfer (DSACK/etc).

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
Thus spake the Master Ninjei: "If your application does not run correctly,
do not blame the operating system."  (From "The Zen of Programming")  ;-)