🚀 go-pugleaf

In article <0094A83A.9AE8E1A0@MAPLE.CIRCA.UFL.EDU> sorrow@oak.circa.ufl.edu writes:
>I have written a  TSR that takes over the command line input for INT21H, in
>other words an INT21H replacement.
>
>How can it prevent itself from being re-installed?  I know programs such as
>NORTON SI will show you who "owns" an interrupt, and my program comes up 
>as the owner.  If there was a way to see if the owner was NOT DOS (i.e. another
>program, such as a TSR, owned it) and to not install itself in that case, I
>would like to know.
The way I have handled this, when using an interrupt vector which may
already be used by some other utility/tsr/system function is to
grab a few bytes in the CS of the ISR as a "signature", then when installing
my TSR, look at that segment address and the specific offset. If my signature
is there, I know my TSR has been installed, otherwise it's not and I can
install it....



Hope this helps....
Steve

-- 
-------------------------------------------------------------------------------
        resnicks@netcom.com, steve@camphq, IFNA:        1:143/105.0, 
                 co moderator for comp.binaries.os2
 Real life: Steve Resnick. Chief Software Architect, Process Scientific, Inc
 Flames, grammar and spelling errors >/dev/null
 The Asylum OS/2 BBS - (408)263-8017 12/2400,8,1 - Running Maximus CBCS 1.2
-------------------------------------------------------------------------------