5 Workstation: NetWare OS/2 requester v1.02 NetWare OS/2 ODI client driver installation notes for Intel's EtherExpress(TM) PRO/10 PCI LAN adapters ============================================================= Location of driver: \OS2\E10PODI.SYS Sample configuration files ========================== CONFIG.SYS DEVICE=C:\NETWARE\E10PODI.SYS NET.CFG LINK DRIVER E10PODI SLOT n FRAME ETHERNET_802.3 FRAME ETHERNET_802.2 Introduction ============ To connect an OS/2 workstation to a NetWare* server, you must have the latest version of the Novell* NetWare Requester for OS/2 and the EtherExpress(TM) PRO/10 PCI LAN adapter OS/2 ODI driver. These installation instructions assume you're using the INSTALL program that ships with Novell's OS/2 requester. For more information about OS/2 workstations, see the Novell manual, "NetWare Requester for OS/2." NOTE: If you're running IBM OS/2 2.0 or 2.1, you must have the OS/2 Requester version 2.01 or later. General instructions ==================== 1 Run Novell's INSTALL utility on the OS/2 requester disk and follow its instructions. If asked for the name of the network interface driver, enter E10PODI.SYS. 2 Choose the session support you need. This is based on your configuration. See the NetWare Requester manual if you need help. 3 Save the configuration. 4 When asked for the path and filename for the driver, insert the Intel EtherExpress PRO/10 PCI disk in drive A and press enter. 5 After completing the installation section, choose CONFIGURATION from the main menu. Then choose THIS WORKSTATION. This allows you to modify the NET.CFG file. (NET.CFG must reside in the root directory.) Note: The default frame type for E10PODI.SYS is 802.2. If you're using the 802.3 frame type, you have to include a FRAME statement in the NET.CFG file. The start of this document lists a NET.CFG file to use with 802.3 and 802.2 frame types. Hints and tips ============== Verify driver loaded properly ----------------------------- In the CONFIG.SYS file, add a "fake" device=xxx statement after the E10PODI.SYS line. The screen stops and you can check for error messages. Error message "not getting a connection ID" ------------------------------------------- This OS/2 error message often appears when there is a frame type mismatch. NET.CFG optional parameters --------------------------- SLOT: Specifies the slot number. This is optional for single adapter installations but required for multiple adapter installations. For PCI adapters, SLOT is derived from DEVICE LOCATION and doesn't map to the physical location of the adapter. Currently, the PCI specification doesn't tell you how to determine which adapter corresponds to a device number. One way to do this is to load the driver from the command line. You'll be prompted with valid device numbers for the adapter. Select one of them. Syntax: SLOT=n (n = 1,2,3,4,...). NODE ADDRESS: Specifies a local administered address (LAA) unique to each adapter. Use this option to provide your own unique node address for the adapter. Setting this parameter overrides the default factory setting. The node address is a 12-digit hexadecimal number; the second digit must be one of the following digits: 2, 6, A, E. Syntax: NODE ADDRESS 02aa12345678 Default: value read from EEprom FRAME: Indicates one of four valid frame types the system is transmitting and receiving. Syntax: FRAME n n = Ethernet_802.2 Ethernet_802.3 Ethernet_II Ethernet_SNAP Default: Ethernet_802.2 PROTOCOL: Indicates the standard protocol in use. Syntax: Protocol e0 Ethernet_802.2 Values: e0=Ethernet_802.2 0=Ethernet_802.3 8137=Ethernet_II 8137=Ethernet_SNAP Detailed example ---------------- LINK DRIVER E10PODI SLOT 1 NODE ADDRESS 00aa00xxxxxx <--Last six digits are unique for each adapter) FRAME ETHERNET_802.2 PROTOCOL IPX E0 ETHERNET_802.2 * Third-party trademarks are the property of their respective owners