🚀 go-pugleaf

I have a program that takes over several interrupts, including 0x102.
Naturally enough I have to restore all the default vectors before
exiting since this is not a "Terminate and stay resident" program.  My
program has two exits - the normal one and via interrupt 0x102.  When I
exit normally everything works fine, everybody's happy and life goes on
as usual.  However, when I type ^C the machine _seems_ happy until I
start up something else, at which point it locks up and the only thing
to do is power down.  I've checked using db (from MWC) and when calling
Setexc from Supervisor mode the vectors aren't being reset properly.
The same clean-up routine is being called in all cases.

Any suggestions?  Are there problems with using system traps from 
Supervisor mode?

Jeff Voskamp
--
Views expressed are mine and do not necessarily reflect the views of the
Symbolic Computation Group or those of the University.
bang path: ...{!uunet}!watmath!watmum!javoskamp 
domain   : javoskamp@watmum.uwaterloo.ca or javoskamp@watmum.waterloo.cdn