From: muta...@gmail.com   
      
   On Saturday, July 3, 2021 at 10:42:25 AM UTC+10, Rod Pemberton wrote:   
      
   > Look, I'm not entirely sure of the mechanism, but I think LINE is a   
   > user space app, i.e., it wouldn't have the necessary privilege to   
   > intercept INT 80H. Hence, I thought it might be worth a look at their   
   > technique. Maybe, Windows has some function that is being used.   
      
   Ok, good point. If Windows is willing to (at its whim) allow   
   an app to set INT 80H, then that would indeed work.   
      
   PDOS/386 also allows apps to trash interrupt vectors.   
      
   But ideally, an executable should not be relying on the grace   
   of the calling environment to give it access to an interrupt   
   (and there may be conflicts with interrupt numbers too).   
      
   It is better if the executable just quietly executes callbacks,   
   in one form or another, so that no-one with any authority   
   has any idea whatsoever what is happening.   
      
   THAT is my definition of a "clean executable", and Win32   
   console mode programs, at least the ones I produce, fit   
   that description, even though they are not *necessarily*   
   my preferred design.   
      
   Rumor has it that Linux supports the same thing via the   
   parameter after envp, which is great, and *possibly* even   
   superior to Win32, so I'll put that on my "to do" list for   
   changes to PDPCLIB to remove the INT 80H in the Linux target.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)