Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,637 of 4,675    |
|    R.Wieser to All    |
|    Re: Indirect INT calling    |
|    30 Oct 18 08:36:23    |
      From: address@nospicedham.not.available              Rod,              > Then, I'd probably recommend Rick's interrupt redirect using       > INT 0x03, i.e., trap-flag interrupt.              I've never tried to use/work with that particular INT. I'll have to look       into it. Thanks for the suggestion.              > Obviously, you can modify this to read and store one interrupt,       > such as for your packetdriver, in olddosint, and have another       > new interrupt installed elsewhere via newdosint              The problem with that is that the new INT has to be fixed (or go in a nice       circle back to the origional problem :-) ). If it than in any way clashes       with any other program (having the same idea or maybe even the same program       run a second time) it would be in trouble, with no way to remedy it.              On the other hand, I seem to have a vague rememberance of a method to chain       multiple programs onto a single INT, even mentioning a default INT for it.       Drawback: slow(ish) (needs to go down the chain), and fully dependant on       other programs chaining and, more importantly, un-chaining themselves       properly.              Regards,       Rudy Wieser              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca