NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: ODINSUP - ODI/NDIS Connectivity DOCUMENT ID: TID014812 DOCUMENT REVISION: A DATE: 28JAN94 ALERT STATUS: White INFORMATION TYPE: Issue README FOR: NA NOVELL PRODUCT and VERSION: PERSONAL NetWare 1.0 ABSTRACT: This document gives a brief explanation of ODINSUP and basic installation instructions but does not indicate if or when ODINSUP is needed. If you have been directed to use ODINSUP to maintain connectivity with NDIS while communicating with ODI, please continue. To get more detailed information and the latest ODINSUP driver, download DOSUPx.EXE (where x is the version indicator). The ODINSUP.DOC file in DOSUPx.EXE gives complete instructions and specific examples for various NDIS based networks. ------------------------------------------------------------------ DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ------------------------------------------------------------------ ISSUE ODINSUP SHIM EXPLANATION ODINSUP is the shim (program code) that allows an NDIS stack to be supported by Novell's ODI stack. This level of connectivity is at a lower layer than the network shell or requester being used. A network that supports ODI (such as NetWare Lite or PERSONAL NetWare) can be made to coexist with and communicate through the same network interface card as a network that supports NDIS (such as Windows for Workgroups 3.1) by enabling this ODI/NDIS connectivity. (Note: Windows for Workgroups 3.11 can also support NDIS but will function directly from the ODI stack.) The following is an example of how the drivers for the two protocol stacks are layered: --------------------------------------------- LAN WorkPlace NetWare NDIS STACK | | | TCP/IP IPXODI ODINSUP | | | +-------------+----------+ | \|/ Link Support Layer (LSL) | \|/ MLID driver (such as, NE2000) | \|/ Network Interface Card (such as, Eagle NE2000) ------------------------------------------------ SETTING UP ODINSUP SUPPORT To provide this dual connectivity, you must do the following: 1. If the ODI network is not installed, do so. This will provide the ODI drivers. If you are installing NetWare Lite or PERSONAL NetWare, a STARTNET.BAT file is created during product installation that will load your ODI drivers, the SERVER.EXE file (if you selected to make this machine a server or to share its resources), and the client software (CLIENT.EXE or VLM.EXE files). The following is an example of part of a STARTNET.BAT file. LSL <--Link Support Layer driver -+ NE2000 <--MLID (Hardware) driver +-- ODI drivers IPXODI <--IPX protocol driver -+ SERVER <--driver for sharing resources VLM <--driver for using shared resources Test and verify that the NetWare Lite or PERSONAL NetWare network is functioning correctly. If it is not functioning, contact your normal lines of technical support for this NetWare product to receive assistance. 2. Now, reboot without loading the NetWare network drivers. When NetWare Lite or PERSONAL NetWare was installed, a line was added to the AUTOEXEC.BAT file to run the STARTNET.BAT file. You should insert a remark at the beginning of this line before you reboot. 3. Install the NDIS network. If the NDIS network was already installed, verify that all the drivers are set up to load properly; then load them. Run the NDIS network and verify that it is functioning correctly. If it is not functioning correctly, contact your normal lines of technical support for this NDIS product to receive assistance. 4. The ODI and NDIS hardware drivers cannot share the network interface card. ODI will take control of the hardware and pass the NDIS packets up to the NDIS stack. Insert a remark on the NDIS MAC driver line. This line is probably in your CONFIG.SYS file. For details on what this driver is called, consult the documentation supplied with the NDIS network. 5. Verify that the PROTMAN driver is loading in the CONFIG.SYS file. Also verify that the PROTOCOL.INI file is in the path specified on the PROTMAN load line. (For example, if the load line reads DEVICE=PROTMAN.DOS /I:C:\BOB, then the PROTOCOL.INI file should be in the C:\BOB directory.) 6. Modify the PROTOCOL.INI file. Disable the Bindings statements for the NDIS MAC driver line by putting a semi-colon at the beginning of the line, and add a Bindings statement for the ODI MLID driver. The following is an example of part of a PROTOCOL.INI file: [PROTOCOL_MANAGER] DriverName = PROTMAN$ [ETHERAND] DriverName = DXME0$ Bindings = NE2000 ; Bindings = x3C523 ; Bindings = ne22 7. Edit the STARTNET.BAT file and add a line to load ODINSUP. The ODINSUP driver should be loaded after the MLID driver and before the IPX protocol driver. The following is an example of part of a STARTNET.BAT file. LSL NE2000 ODINSUP IPXODI SERVER VLM 8. ODINSUP requires that all possible FRAME types be installed with the driver. To do this, edit the NET.CFG file located in your NWLITE or NWCLIENT directory. If you are using a Token-Ring driver, you need to load both of the following frame types: TOKEN-RING TOKEN-RING_SNAP If you are using Ethernet, you need to load the following frame types: Ethernet_802.2 Ethernet_802.3 (not needed, but recommended for compatibility) Ethernet_snap Ethernet_ii These frame types are added by adding FRAME lines under the LINK DRIVER (MLID) section. Unless you have a bind statement in the LINK DRIVER section, make sure that the frame type being used by your ODI based network is the first frame type listed. To instruct ODINSUP what driver it is going to bind to, a protocol section must also be added. The following is an example of part of a NET.CFG file: PROTOCOL ODINSUP BIND NE2000 LINK DRIVER NE2000 INT 5 PORT 340 FRAME Ethernet_802.2 FRAME Ethernet_802.3 FRAME Ethernet_snap FRAME Ethernet_ii 9. To allow STARTNET to run again when the computer is rebooted, edit the AUTOEXEC.BAT file to remove the remark in front of the STARTNET line. Also, make sure that the NETBIND and other NDIS network commands are executed after STARTNET has loaded. 10. Double check the setups specified in the previous steps to verify that everything is set up properly, then reboot the machine. When your machine comes up, you should be able to connect and use both the ODI-based and NDIS-based network. TROUBLESHOOTING GUIDE If the ODINSUP driver doesn't load, check the NET.CFG file for syntax errors or missing information. If the NET BIND fails, check the PROTOCOL.INI file for syntax errors or incorrect "Bindings=" lines. If the ODINSUP shim does not function properly and you have double checked all the set up specified in the previous steps, contact your normal lines of NetWare technical support for assistance.