home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!caen!hellgate.utah.edu!cc.usu.edu!jrd
- From: jrd@cc.usu.edu
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: Help with Novell's ODI drivers
- Message-ID: <1992Jul27.211817.57535@cc.usu.edu>
- Date: 27 Jul 92 21:18:17 MDT
- Organization: Utah State University
- Lines: 17
-
- Now if the developers of our favorite free/shareware programs would
- take the time to add ODI support to their programs we could bypass much of
- this hassle. Not all, but much. I published the code to do both Packet Driver
- and ODI in one package, as file MSNPDI.ASM, on NETLAB2.USU.EDU, cd misc,
- and get odiread.me while there. It includes targeting or searching for a PD
- interrupt as well. The current ODI manuals are in the same directory.
- So far MSNPDI.ASM (part of MS-DOS Kermit v3.12) is the first and only
- fully documented applications layer ODI code you can lay your hands upon, and
- I designed it to be a guide for other developers.
- Where we get into tepid water is running an ODI based program in
- Windows. At the moment we lack the Real<->Windows mode shim equivalent
- to WINPKT for Packet Drivers. Here's a nifty item for even Novell to
- contribute, and hopefully in source code form. I hate to mention Novell
- this way because the SJF-LWP group has contributed so many other related
- items, so I'm really suggesting that someone needs to step in and solve this
- obvious problem.
- Joe D.
-