Article View: comp.os.msdos.programmer
Article #2618Re: Turbo C Interrupt Question
From: Edward John Kalenda
Date: Wed, 10 Oct 1990 19:04
Date: Wed, 10 Oct 1990 19:04
9 lines
901 bytes
901 bytes
I may be wrong, but the way I do it is to look at the return address on the stack. By examining the instruction it points to (actually the instruction before) to see if it is an INT will tell me if it is hardware or software. A better method is to have the interrupt handler call a second routine with a flag parameter to indicate the hardware/software nature of the caller. When you call from software, call the second routine instead of the handler. Ed ekalenda@cup.portal.com
Technical Details
Message-ID:
<34729@cup.portal.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!olivea!apple!portal!cup.portal.com!ekalendaReferences:
<32923@nigel.ee.udel.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!olivea!apple!portal!cup.portal.com!ekalenda From: ekalenda@cup.portal.com (Edward John Kalenda) Newsgroups: comp.os.msdos.programmer Subject: Re: Turbo C Interrupt Question Message-ID: <34729@cup.portal.com> Date: 10 Oct 90 19:04:40 GMT References: <32923@nigel.ee.udel.edu> Organization: The Portal System (TM) Lines: 9