Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!uunet!unsvax!uns-helios!alfter
From: alfter@uns-helios.nevada.edu (SCOTT ALFTER)
Newsgroups: comp.sys.apple2
Subject: Re: High level language "fools"  (was:Re: Stellar 7 re-release)
Message-ID: <2496@unsvax.NEVADA.EDU>
Date: 15 Dec 90 21:22:43 GMT
References: <930@redford.UUCP> <10621@ucrmath.ucr.edu> <10136@darkstar.ucsc.edu>
Sender: news@unsvax.NEVADA.EDU
Organization: University of Nevada System Computing Services
Lines: 28

In article <10136@darkstar.ucsc.edu> unknown@ucscb.UCSC.EDU (The Unknown User) writes:
>	It's in 8088 on PCs... One thing I will say about the PCs was
>that doing interrupt stuff sure is damn easy! You just do a little BIOS
>call and change an address to your new routine... (I would HOPE it's
>that easy on the GS, but you have to go through the toolbox, don't you??
>Someone please inform me)..

To get an interrupt daemon up and running, just issue an
ALLOC_INTERRUPT call to the MLI, along with the address where your
daemon resides; ProDOS will then add the daemon to the routines it'll
check when the system is interrupted.  All that remains after that is
to stick a CLI in your source code to enable interrupts.

Only four interrupt drivers are supported, though; when you no longer
need a particular daemon, DEALLOC_INTERRUPT will get rid of it for
you.

More comprehensive information is in _Beneath_Apple_ProDOS_.

BTW, note that this example is for 8-bit IIs as well as the GS; I
figure this information would be of more interest than GS-specific
info.  Besides, I don't have a GS and couldn't help you with interrupt
questions on that machine.

Scott Alfter-----------------------------_/_----------------------------
                                        / v \ Apple II:
Internet: alfter@uns-helios.nevada.edu (    ( the power to be your best!
   GEnie: S.ALFTER                      \_^_/