Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!rutgers!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <15756@cbmvax.commodore.com>
Date: 9 Nov 90 16:22:26 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore, West Chester, PA
Lines: 25

In article <90312.082534GIAMPAL@auvm.auvm.edu> GIAMPAL@auvm.auvm.edu writes:
>I've got a semi-simple question about the Scheduler and LoadSeg() under
>2.0 of AmigaDOS.
>
>There seems to be a difference in the way the system handles a heavy load
>between 2.0 and 1.3 of the OS.  For example, on an A3000, if you start a ray-
>trace with TurboSilver and pop back to workbench to start up something like
>DeluxePaint, the entire system _seems_ locked, but then suddenly jumps back
>to life in little bursts.

Are you running a utility called "enforcer" when you're under 2.0?
It finds certain program bugs and spits error reports out the serial
port at 9600 baud -- the machine is suspended during that time.  DPaint
has a few such reports upon startup.  That would explain what you're 
seeing.

>trying for good techie content,
>--dominic

     Peter
--
     Peter Cherna, Software Engineer, Commodore-Amiga, Inc.
     {uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"She read him like a book:  she liked to peek at his end."