Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!e260-3c!laba-1ei
From: laba-1ei@e260-3c.berkeley.edu (Joseph Chung)
Newsgroups: comp.sys.amiga
Subject: Re: Multitasking is slower
Keywords: games, multitasking
Message-ID: <1990Jun5.082227.29350@agate.berkeley.edu>
Date: 5 Jun 90 08:22:27 GMT
References: <279@smosjc.UUCP> <4039@darkstar.ucsc.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: laba-1ei@e260-3c (Joseph Chung)
Organization: University of California, Berkeley
Lines: 25

In article <4039@darkstar.ucsc.edu> davids@ucscb.UCSC.EDU (Dave Schreiber) writes:
>>NO!  For a program to allow multitasking, it has to be "nice".  It must own
>>and disown the system resources (esp. blitter) using OS calls, and do so
>>often enough to allow other tasks a chance to use them.  Depending on the 
>
>Are you reading all of the original message?  If the machine is in a state
>so that the game is going "without anything else running", then there won't
>be "other tasks" that demand system resources like the blitter.  This
>seems fairly self-evident.

Hold on a minute.  If I want to multitask,  I must nicely ASK for resources
to be given, therefore incurring an extra overhead.  However, if I take over
the machine, I TAKE whatever resources I want, bypassng the boss.

I have a question here: Does WB count as a process/task?  Cuz if it does,
then exec must time-slice in order to share it with a running game. No
matter how small that slice of time is, it is still taken; otherwise, how
will WB know to respond when a mouse is clicked in its domain?

-jc

--
Joseph Chung
== You can always find what you're not looking for! ==
laba-1ei@web.berkeley.edu