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,643 of 4,675   
   sdn45478@nospicedham.gmail.com to R.Wieser   
   Re: Indirect INT calling   
   31 Oct 18 14:12:36   
   
   On Saturday, October 27, 2018 at 5:55:25 AM UTC-7, R.Wieser wrote:   
   > Hello all,   
   >   
   > I'm dealing with a packet driver, which API (ABI?) can be put behind any   
   > available INT (by specifying the number when loading it).   
   >   
   > I would like my program to find the right INT at runtime (which is not hard,   
   > as the packet driver has a certain string at a certain place, just so you   
   > can check if its actually there) and than use that.   
   >   
   > The problem is that no "INT [byte address]" exists.   
   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.   
   So maybe the solution is to junk that driver and find another which   
   is transparent to application programs.   
   Steve   
      
   --- 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