home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / protocol / tcpip / ibmpc / 4474 < prev    next >
Encoding:
Internet Message Format  |  1992-07-28  |  1.1 KB
  1. Xref: sparky comp.protocols.tcp-ip.ibmpc:4474 comp.sys.novell:6118
  2. Path: sparky!uunet!stanford.edu!rutgers!hsdndev!burrhus!ddl
  3. From: ddl@burrhus.harvard.edu (Dan Lanciani)
  4. Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.novell
  5. Subject: Re: Help with Novell's ODI drivers
  6. Message-ID: <1992Jul28.221043.6726@burrhus.harvard.edu>
  7. Date: 28 Jul 92 22:10:43 GMT
  8. References: <1992Jul25.045135.21123@CS.ORST.EDU><14t5nkINN5r7@matt.ksu.ksu.edu> <92209.202057RBYAML@rohvm1.rohmhaas.com>
  9. Followup-To: poster
  10. Organization: Harvard University, Cambridge, MA
  11. Lines: 16
  12.  
  13. In article <92209.202057RBYAML@rohvm1.rohmhaas.com>, RBYAML@rohvm1.rohmhaas.com (Aengus Lawlor) writes:
  14. | I used Manifest (it comes with QEMM) to see what interrupts
  15. | ODIPKT used.
  16.  
  17.     My, the lengths people will go to to avoid reading the
  18. documentation :)
  19.  
  20. | Unfortunately, ODIPKT isn't
  21. | unloadable, and it locks in all the other ODI drivers loaded before it.
  22.  
  23.     ODIPKT unloads with the standard packet driver API function
  24. defined for that purpose.  You can call this function with the "TERMIN"
  25. program.
  26.  
  27.                 Dan Lanciani
  28.                 ddl@harvard.*
  29.