Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!genrad!decvax!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Interrupt serving?
Message-ID: <8710042026.AA07079@cory.Berkeley.EDU>
Date: Sun, 4-Oct-87 16:26:24 EDT
Article-I.D.: cory.8710042026.AA07079
Posted: Sun Oct  4 16:26:24 1987
Date-Received: Wed, 7-Oct-87 06:38:32 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 15

>	I have been trying to do some display hacking based on a vertical
>retrace interrupt server.  I have Dan Silva's example from the IFF disk, which,
>although invaluable, does not address my specific needs.  If I put in really
>innocuous code, like assignment statements, it runs.  As soon as I try to fool
>with the display inside the server routine, it croaks.  I have tried using
>ScreenToFront(), SetRast(), and DrawGList() but none of them work.

	From an interrupt service routine?  Oi-Vay!  Since an interrupt
service routine is NOT a task, you cannot do *any* operation that might
possibly execute a Wait().  All the routines you've mentioned above can do
Wait()s.  This is not the only restriction.  In general, the only thing you
should use interrupt service routines for is to service actual hardware, and
then possibly Signal() a task to handle other things.

					-Matt