Workstation: NetWare OS/2 requester v1.00 NetWare* OS/2* ODI client driver installation notes for Intel's EtherExpress(TM) PRO/100B adapter =============================================================== Location of driver: \OS2\E100BODI.SYS Sample configuration files ========================== CONFIG.SYS DEVICE=C:\NETWARE\E100BODI.SYS NET.CFG LINK DRIVER E100BODI 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/100B 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, 2.1 or Warp, 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 E100BODI.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 Configuration and Drivers 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 E100BODI.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 E100BODI.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 or cable disconnect. NET.CFG optional parameters --------------------------- FORCEDUPLEX: Specifies the duplex mode the driver uses. Syntax: FORCEDUPLEX n Where n=0 (auto-negotiate) 1 (half duplex) 2 (full duplex) NOTE: If adapter is set to half or full duplex, the SPEED parameter must be set to either 10 or 100. (see SPEED below) Duplex modes: Auto-negotiate _ the adapter negotiates with the hub how to send/receive packets, either full or half duplex. Full duplex _ the adapter sends and receives packets at the same time. This improves the performance of your adapter. Set duplex mode to full duplex ONLY if you have a full duplex hub that doesn't do auto-negotiation (a non-NWay* hub). Half duplex _ the adapter performs one operation at a time. It either sends or receives. Default: FORCEDUPLEX = Auto-Negotiate A regular adapter can perform only one operation at a time (half- duplexing). The PRO/100B adapter has the ability to send and receive packets at the same time (full-duplexing). In order to reap the benefits of full duplexing, you MUST have a full duplex hub. The PRO/100 adapter has the added ability to "talk" to the hub and determine at which mode to communicate (either full or half duplex). This is called auto-negotiation. You must have a auto- negotiating hub (an NWay hub) to get full duplex support with the FORCEDUPLEX parameter set to 0 (auto-negotiation). If you don't have an auto-negotiating hub, set FORCEDUPLEX to 2 (full duplex) and then set the SPEED parameter to either 100 Mbps or 10 Mbps. If you don't know what kind of hub you're attached to, contact your LAN Administrator 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,...15). SPEED: Specifies the speed the driver uses. If you don't use this parameter, the driver automatically detects the network speed. If no cable is attached, the driver defaults to 100 Mbps. If you don't have a auto-negotiating hub and are configuring the adapter for full-duplex support, you must specify the speed using this parameter. If you use this parameter, the driver operates at the specified speed instead of automatically detecting network speed. Syntax: SPEED n (n = 10 or 100) Default: none, the adapter automatically senses speed THRESHOLD: Represents the threshold for transmits from extender SRAM FIFO. Syntax: THRESHOLD n (n = number of 8 bytes) For example, 16 represents 16x8 (or 128 bytes). In this case, the LAN controller transmits after copying 128 bytes from the host memory. Default: 16 The maximum number that you can specify is 200 (200x8=1600 bytes). NODE ADDRESS: Specifies a local node address unique to each adapter. The first two digits of the address indicate who assigned the address when the driver loads. Syntax: NODE ADDRESS 02aa12345678 02aa => Locally administered address 00aa => Typical Intel address (default) 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 ipx e0 Ethernet_802.2 Values: e0=Ethernet_802.2 0=Ethernet_802.3 8137=Ethernet_II 8137=Ethernet_SNAP Detailed example ---------------- LINK DRIVER E100BODI SLOT 1 SPEED 100 THRESHOLD 16 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.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.