home bbs files messages ]

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,655 of 4,675   
   R.Wieser to All   
   Re: Indirect INT calling   
   03 Nov 18 08:29:50   
   
   From: address@nospicedham.not.available   
      
   Wolfgang,   
      
   > what's your reason to have only 6 instead of 8 ?   
      
   Guess how many the origional INT uses.   I also mentioned that, if   
   stack-based arguments where used, my code would still allow it to work.   
   And yes, I tend to try to find/create generic drop-in replacements (as in:   
   doing the exact same as the origional).   
      
   FWI: Neither my current program nor the packetdriver it calls could care   
   less about what the stack looks like, as long as the packetdriver can   
   perform its IRET.   Which means that the basic "INT {runtime patched byte   
   value}", "RET" procedure will do perfectly fine.     Why did you think I was   
   looking for other solutions ?   
      
   > but you seem to insist on it, so how about this:   
   > [Snip code]   
      
   Thats a nice one. Thank you.   
   Never even thought about using a pop-to-memory method.   
      
   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