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,644 of 4,675   
   Mateusz Viste to All   
   Re: Indirect INT calling   
   01 Nov 18 07:56:29   
   
   From: mateusz@nospicedham.wont.tell   
      
   On Wed, 31 Oct 2018 14:12:36 -0700, sdn45478 wrote:   
   > Just as a observation, drivers are usually transparent and don't need   
   > any INT location at setup. It seems like a good driver will figure   
   > things out on it's own so that it will work with any normal DOS   
   > application, maybe with a drive or directory which represents the remote   
   > location.   
      
   The INT interface is a necessity, by design. And the INT can be anywhere   
   within the range 60h..80h (by design, too), hence the need to detect its   
   location before calling it. There may be many packet drivers loaded at   
   the same time, because the computer may have many network interfaces.   
   Then it should be up to the user to select which INT the client program   
   should use.   
      
   Mateusz   
      
   --- 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