Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!rutgers!labrea!rocky!ali
From: ali@rocky.STANFORD.EDU (Ali Ozer)
Newsgroups: comp.sys.amiga
Subject: Re: Resource manager needed.
Message-ID: <460@rocky.STANFORD.EDU>
Date: Fri, 31-Jul-87 02:59:11 EDT
Article-I.D.: rocky.460
Posted: Fri Jul 31 02:59:11 1987
Date-Received: Sat, 1-Aug-87 15:53:12 EDT
References: <1012@vu-vlsi.UUCP>
Reply-To: ali@rocky.UUCP (Ali Ozer)
Distribution: na
Organization: Stanford University Computer Science Department
Lines: 18

In article <1012@vu-vlsi.UUCP> cheung@vu-vlsi.UUCP (Wilson Cheung) writes:
>my program hung up FORTH probably a stupid endless loop.  The Multi-Forth
>now eats up huge CPU time causing my mouse pointer to become jerky and 
>sluggish.
>Now do I pop up another FORTH evironment and put up with a much slowed down
>68000 or do I reboot, lose my file transfer, and the work in setting up my
>applications the way I wanted.  

A solution that works well is to set the priority of the runaway or
otherwise hung task to some low value --- Minus hundred works well.
There are several programs to do this, I believe. I use one named "cpri."
I think it appeared on a Fish disk, but browsing through a full index
didn't reveal it. (I either remember wrong about "cpri" being from Fish
disks or maybe I renamed it...) In any case, with a priority of -100, the 
task will not interfere with any other tasks (unless it is truly runaway 
and eating memory)... 

Ali Ozer, ali@rocky.stanford.edu