From: address@nospicedham.not.available   
      
   Steve,   
      
   > Just as a observation, drivers are usually transparent and don't   
   > need any INT location at setup.   
      
   You're talking about a device drivers outward/hardware facing side.   
      
   What I have been talking about is the user-facing API (ABI?) side of a   
   packet driver (for an ethernet card).   And while its API-supplying INT   
   will default to 0x60 you are free to (nowerdays) to put them almost   
   anywhere.   
      
   Think of it as with a file on a drive: you do need to supply the correct   
   drive letter to be able to adress that particular file.   And while drive   
   letters are easy to store centrally in a program (and thus easy to change),   
   that isn't possible for an INT.   
      
   And yes, the packetdriver itself is fully transparent.  That is, as long as   
   I obey its API specs I do not need to know anything about how it works   
   internally.   You do not even need to care if it actually talks to its   
   intended hardware or not (block device drivers talking to serial connections   
   ?  No problem!), as long as it does the expected / defined thing. :-)   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)