Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!agate!darkstar!ucscb.UCSC.EDU!davids From: davids@ucscb.UCSC.EDU (Dave Schreiber) Newsgroups: comp.sys.amiga Subject: Re: Multitasking is slower Keywords: games, multitasking Message-ID: <4039@darkstar.ucsc.edu> Date: 3 Jun 90 23:23:08 GMT References: <279@smosjc.UUCP> Sender: usenet@darkstar.ucsc.edu Organization: UCSC Open Access Lines: 25 In article <279@smosjc.UUCP> brett@smosjc.UUCP (Brett Coon) writes: >>From: Tim Friest - Programmer/Analyst >>The point the people are making about games needing to multi-task is simply, >>if I run the game without anything else running, it is exactly the same as >>if the game took over the machine and didn't let me run anything else.... > >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. [...] -- Dave Schreiber The blue leprechaun at davids@slugmail.ucsc.edu (prefered but flakey) or (not both) davids@ucscb.ucsc.edu "Coffee, Darling?"