Path: utzoo!mnetor!uunet!husc6!bbn!rochester!rutgers!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!kworrell
From: kworrell@ccvaxa.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Interrupt handlers in MSC-V5
Message-ID: <27000007@ccvaxa>
Date: 4 Jan 88 20:48:00 GMT
References: <19793@amdcad.AMD.COM>
Lines: 35
Nf-ID: #R:amdcad.AMD.COM:19793:ccvaxa:27000007:000:1291
Nf-From: ccvaxa.UUCP!kworrell    Jan  4 14:48:00 1988


I had some difficulty with this as well.

For documentation, read through the README file on one of the
disks you got.

Interrupt is indeed a reserved word.  It just
tells the compiler to save all the registers on entry, restore
on exit, and use iret instead of ret.

Be careful using any of the MSC library functions which could in
any way shape or form issue system calls.  I used the list, in one
of the appendixes, which described what things you could/couldn't use
for ROMable code.  Read the warnings in that section closely!

Another thing, be sure to use the stack check pragma or the -Gs
option or any routines you call from inside your handler will give
you an error like 'R6000 Stack Overflow.'

Some of the routines you cited are used for TSR's rather than just
interrupt handling.  You don't necessarily need to write interrupt
handlers as TSR's.


Why don't you post or mail me other responses you recieve.  I'm
always interested what others find out (why reinvent the wheel!).

Kurt.


------------------------------------------------------------------------
Kurt J. Worrell	                 USEnet:  ihnp4!uiucdcs!ccvaxa!kworrell
Gould CSD-Urbana                 ARPAnet: kworrell@gswd-vms.arpa
1101 E. University               BELLnet: (217) 384-8500, x740
Urbana, IL 61801