From: address@nospicedham.not.available   
      
   Terje,   
      
   > Adding 10-100 patch locations in order to save a single word of stack   
   > space?   
   >   
   > "You gotta be kidding!"   
   > :-)   
      
   I think you misunderstood.  I was expressing my preference for a single   
   procedure (with a singe to-be-patched byte) which gets called instead of any   
   INT 0x60.   
      
   But now you mention it, creating a patching framework just to save a single   
   stack save does sound a bit exessive, doesn't it ?   
      
   On the other hand, I *did* ask for possible other solutions, and that it   
   certainly is. :-)   
      
   > Before calling a driver which switches to a private stack anyway?   
      
   :-)  That is for thr SIS900 packet driver. I cannot say anything about   
   others.  They might, but they also might not.   
      
   Hmmm...  I'm rather sure that with some stack shennigans I could change the   
   stackframe of a simple near call of a procedure into a push-and-far-return,   
   needing only the far jump to the INT procedure ...   
      
   I'm not sure I would actually want to use it though ... (too hackish) :-)   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)