Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!sdd.hp.com!usc!julius.cs.uiuc.edu!psuvax1!psuvm!auvm!giampal
From: GIAMPAL@auvm.auvm.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <90316.091455GIAMPAL@auvm.auvm.edu>
Date: 12 Nov 90 14:14:55 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu> <15756@cbmvax.commodore.com>
Organization: The American University - University Computing Center
Lines: 18


In article <15756@cbmvax.commodore.com>, peter@cbmvax.commodore.com (Peter
Cherna) says:
>In article <90312.082534GIAMPAL@auvm.auvm.edu> GIAMPAL@auvm.auvm.edu writes:
>>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?

Well unless "enforcer" is run in the startup-sequence by default, this isn't
the case.  The machine had basically been just pulled out of the box and
set up.  There is definitely something different going on, but I'm not
quite sure what (time to buy ReSource '030 and figure out what you guys are
doing in there :-)

--dominic