home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!crdgw1!newsun!db!mcollins
- From: mcollins@db (Marty Collins)
- Newsgroups: comp.sys.novell
- Subject: Re: NDIS<-->ODI
- Message-ID: <1993Jan7.212120.8652@novell.com>
- Date: 7 Jan 93 21:21:20 GMT
- References: <93007.204133P85025@BARILVM.BITNET>
- Sender: news@novell.com (The Netnews Manager)
- Organization: Novell, Inc.
- Lines: 43
- Nntp-Posting-Host: db.sjf.novell.com
- X-Newsreader: Tin 1.1 PL4
-
- P85025@BARILVM.BITNET (Doron Shikmoni) writes:
- : This might be a FAQ:
- :
- : What *exactly* is required to run NDIS and ODI alongside?
- :
- : 1. When ODI owns the NIC, I understand you need something called
- : ODINSUP (or something). Where can this thing be had, and how
- : do you use it?
-
- This can be had from Netwire via the DOSUP6.ZIP file found
- in library (I am not sure try them all).
- All that really needs to be done is update the protocol.ini
- file with the correct NDIS specification for your ODI
- Driver. THere are examples to help you along. Also updates
- to Config.sys, Autoexec.bat and Net.cfg will be required
- but this is painless.
-
- :
- : 2. Is there a way to do the opposite? I mean, let NDIS MAC drive the
- : NIC, and let ODI be on top (as an NDIS protocol). Is there an NDIS
- : protocol driver that presents an ODI driver interface upwards?
-
- I really can't say if there is such a beast, but I know
- that Novell does not have such a thing.
-
-
- :
- : (I understand some of (2) above can be achieved if I put DIS_PKT
- : in the NDIS stack and then run IPXPD from BYU; but then I get only
- : IPX, not real ODI - say, for Lan Workplace).
- :
- : Thanks
- : Doron
-
- --
- A woman needs a man like a fish needs a bicycle.
-
- Marty Collins U2
- Product Support Tryin to throw your
- NOVELL, INC. San Jose, CA. arms around the world.
- mcollins@novell.com or
- Marty_Collins@SJF.Novell.COM
- 1-800-NETWARE
-