Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!ames!ucbcad!ucbvax!decvax!decwrl!labrea!rocky!ali
From: ali@rocky.STANFORD.EDU (Ali Ozer)
Newsgroups: comp.graphics
Subject: Re: Amiga World Ray-tracing article...
Message-ID: <255@rocky.STANFORD.EDU>
Date: Sun, 19-Apr-87 23:40:55 EST
Article-I.D.: rocky.255
Posted: Sun Apr 19 23:40:55 1987
Date-Received: Tue, 21-Apr-87 02:57:18 EST
References: <629@puff.WISC.EDU> <2985@sdcsvax.UCSD.EDU> <647@puff.WISC.EDU> <239@rocky.STANFORD.EDU> <4612@utcsri.UUCP> <72@dalcsug.UUCP>
Reply-To: ali@rocky.UUCP (Ali Ozer)
Distribution: comp
Organization: Stanford University Computer Science Department
Lines: 15
Keywords: cost

In article <72@dalcsug.UUCP> philip@dalcsug.UUCP (Peter Philip) writes:
>Not that you would get much done if you were multitasking while ray-tracing
>unless of course you happen to also have a TURBO-Amiga.

You can simply set the priority of the ray tracer to -1 (with the "cpri"
or "changetaskpri" AmigaDOS command). Then you can run Emacs or other
user-interface oriented programs without any loss in performance. (Tasks of
same priority run in round robin fashion while a task of higher priority will
always preempt one of lower priority.) Of course, the ray-tracer will run a
bit slower, but not much, as the Amiga is heavily interrupt driven.

Of course with a Turbo Amiga things would go several zillion times faster. 
Yes indeed...  

Ali Ozer, ali@rocky.stanford.edu