Xref: utzoo comp.sys.ibm.pc.programmer:1769 alt.msdos.programmer:1708
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!jarthur!petunia!unmvax!sci.ccny.cuny.edu!cucard!dasys1!cooper!phri!cmcl2!yale!think!samsung!uunet!matrix!venkat
From: venkat@matrix.UUCP (D Venkatrangan)
Newsgroups: comp.sys.ibm.pc.programmer,alt.msdos.programmer
Subject: Removing int 2f TSR
Keywords: int 2f
Message-ID: <138@matrix.UUCP>
Date: 3 Jun 90 09:46:30 GMT
Distribution: na
Organization: Matrix Computer Systems, Nashua, NH
Lines: 19



I plan on using the INT 2f multiplex interrupt for installing and accessing
my TSR.  It seems easy enough to do the install and chain to the old int 2f
ISR (if the request is not ours).  But what is the best way to remove?  As
long as no other TSR that comes in later changes the int 2f, I can reset it
to the old value that was saved when we installed, and of course, free our
TSR's memory block.  What should be done if this is not the case?

I have heard of the Mark/Release TSR management utilities, but I want
a programmable interface.

It seems like if all int 2f TSRs were required to supply a standard
function code that returns the location (both segment and offset) where it
has saved the old int 2f ISR address, we can save our saved int 2f ISR
address at that location (thus replacing our ISR address with the one we
saved - the next one in the chain) and remove ourselves from the chain.

Is there such a convention?