Xref: utzoo comp.sys.ibm.pc.misc:5779 comp.lang.c:35440 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!samsung!usc!elroy.jpl.nasa.gov!decwrl!mcnc!uvaarpa!murdoch!fermi.clas.Virginia.EDU!jvb7u From: jvb7u@fermi.clas.Virginia.EDU (Jon Brinkmann) Newsgroups: comp.sys.ibm.pc.misc,comp.lang.c Subject: Re: interrupt far functions in Microsoft 5.1 Message-ID: <1991Jan23.221144.3809@murdoch.acc.Virginia.EDU> Date: 23 Jan 91 22:11:44 GMT References: <801@gsg.UUCP> Sender: news@murdoch.acc.Virginia.EDU Organization: Department of Astronomy, University of Virginia Lines: 22 In article martino@logitek.co.uk (Martin O'Nions) writes: #lorvig@gsg.UUCP (Don Lorvig) writes: #> have been using void far interrupt routines for some time now. The #>addresses of this routines are passed to a TSR which executes them. #>Recently I began attempting to make this functions more complex. (They #>merely set flags before). When I attempt function calls from within #>these interrupt routines, strange behavior results. I've encountered similar problems. Many of the MSC routines will not work when used in a ISR or TSR. A good addition to your MSC manuals is an article on writing TSRs in MSC: Christian, Kaare, "Using MicroSoft C Version 5.1 to Write Terminate-and-Stay-Resident Programs", MicroSoft Systems Journal, September 1988, Volume 3, Number 5, pages 47 - 57. Jon -- Jon Brinkmann Astronomy Department Internet: jvb7u@Virginia.EDU University of Virginia UUCP: ...!uunet!virginia!jvb7u P.O. Box 3818 SPAN/HEPnet: 6654::jvb7u Charlottesville, VA 22903-0818