Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!uwvax!speedy!derek
From: derek@speedy.WISC.EDU (Derek Zahn)
Newsgroups: comp.sys.amiga
Subject: Re: Taking Over
Message-ID: <3799@spool.WISC.EDU>
Date: Fri, 3-Jul-87 09:42:09 EDT
Article-I.D.: spool.3799
Posted: Fri Jul  3 09:42:09 1987
Date-Received: Sat, 4-Jul-87 13:12:50 EDT
References: <3788@spool.WISC.EDU> <2450@husc6.UUCP>
Sender: news@spool.WISC.EDU
Distribution: comp
Lines: 21

> What kind of resources do you want to be "guaranteed"?
> You realize the Amiga has a resource arbitration scheme so if another
> task is using a resource you cannot have access to it?  In that case your
> program should simply wait for the resource or die.  I really don't see
> much use in taking over the machine unless you are a VERY processor-
> intensive game program or something that needs all the sprites, etc.

That's it exactly.  A very processor-intensive game program.  I would like to
allow the user to just slip the disk in a drive (while booted in workbench),
play, then exit back to that workbench.  It has always bugged me that graphics
games (Marble Madness, Sinbad, etc) require rebooting.  This make sense?
Does it bother anyone else that you have to reboot if you want to play
Marble Madness for a while?

I hadn't thought of just using a Forbid()/Permit() pair in effect for the
whole duration of the game, and am still not sure that this is sufficient
(I am assuming that resource arbitration will not be a problem -- if some
resource is tied up, the user could easily be asked to kill the offending
program; a similar situation for memory needs).

p, ) t