3 NDIS 2.x Driver Notes (OS/2, LAN Manager, others) v1.01 General NDIS 2.x Driver Notes for Intel's EtherExpress(TM) PRO/10 PCI LAN Adapter ========================================================================= Location of Driver: \NDIS\E10P.DOS \NDIS\E10P.OS2 Support files: \NDIS\E10PEDOS.NIF \NDIS\E10PEOS2.NIF \NDIS\OEMSETUP.INF \NDIS\MSLANMAN.BAT \NDIS\PROTOCOL.INI \NDIS\STNDNIF\E10PDOS.NIF \NDIS\STNDNIF\E10POS2.NIF Sample Configuration Files -------------------------- CONFIG.SYS (for DOS will contain) DEVICE=C:\path\PROTMAN.DOS /I:C:\path DEVICE=C:\path\E10P.DOS CONFIG.SYS (for OS/2* will contain) DEVICE=C:\path\PROTMAN.OS2 /I:C:\path DEVICE=C:\path\E10P.OS2 PROTOCOL.INI (may contain) [PROTMAN] DriverName = PROTMAN$ [NETBEUI_XIF] Drivername = netbeui$ Sessions = 6 NCBS = 12 Bindings = "E10P_NIF" LANABASE = 0 [E10P_NIF] Drivername = E10P$ General Notes -------------- Several network operating systems use a standard 2.0.1 version NDIS driver to talk to the network adapter. The EtherExpress PRO/10 PCI adapter's NDIS driver conforms to the Microsoft NDIS 2.0.1 specification. The NDIS subdirectory on the EtherExpress PRO/10 PCI adapter disk contains the files needed to use the adapter card with one of these operating systems. The files and their purpose are listed below. E10P.DOS: NDIS driver for DOS workstations. E10P.OS2: NDIS driver for servers & OS/2* workstations. E10PDOS.NIF: The standard DOS NIF file used with Microsoft LAN Manager* installations. Other network operating systems may use these during their installation. If so, copy the E10P.DOS and this NIF file into the same directory and reference that directory. E10POS2.NIF: The standard OS/2 NIF file used with Microsoft LAN Manager* installations. Other network operating systems may use these during their installation. If so, copy the E10P.OS2 and this NIF file into the same directory and reference that directory. E10PEDOS.NIF: The Extended Network Information file (NIF) that IBM LAN Support uses during its installation process. Specify the \NDIS directory when installing so the installation procedure will find the correct NIF file. E10PEOS2.NIF: The Extended Network Information file (NIF) that IBM OS/2 uses during its installation process. Specify the \NDIS directory when installing so the installation procedure will find the correct NIF file. PROTOCOL.INI: A fragment of the general PROTOCOL.INI file. This fragment contains information specific to the EtherExpress PRO/10+ PCI adapter. Be sure your file contains this fragment. Some installation procedures create this file for you. This file is provided as an example of what the EtherExpress PRO/10+ PCI adapter section could look like. OEMSETUP.INF: The version located in the \NDIS subdirectory on the driver disk is used by IBM's LAN requester for DOS version 4.0. MSLANMAN.BAT: Executing this file creates the directory structure required for a Microsoft LAN Manager installation. Other NDIS installations may also look for this structure: \MSLANMAN.DOS\DRIVERS\ETHERNET\E10P\E10P.DOS (DOS) or \MSLANMAN.OS2\DRIVERS\ETHERNET\E10P\E10P.OS2 (OS/2) Hints and Tips -------------- 1. Parameters for the PROTOCOL.INI file are listed below. DRIVERNAME: (required) If you have a single adapter, use the syntax in the Sample Configuration file section. If you are installing multiple adapters, each adapter must have a unique driver name. Additional instances of the driver would be referenced by DRIVERNAME=E10Px$, where "x" would be a unique number 2 through 9. SLOT: (required for multiple adapters) This parameter is optional if only one adapter is present. If it is specified but is incorrect, a message indicates that the value doesn't match the configuration but the driver will find the adapter and load anyway. This parameter becomes required if more than one adapter is present in either one bus or multiple PCI buses of a system. The value of this parameter makes it possible for the driver to uniquely identify which of the adapters is to be controlled by this driver. The SLOT number is the encoded value of the PCI adapter's device location. To determine the slot number, load the driver with only the DRIVERNAME parameter specified. The driver will report all the slots which have PCI adapter(s) installed. You can determine which card is in which slot by using SETUP.EXE and matching the Ethernet addresses of the adapter to the device number specified in View Configuration. [Example: SLOT=0x1C] NODE: (optional) This value sets the adapter's Individual Address, overriding the value read from the adapter EEprom. The address must consist of 12 hexadecimal digits, enclosed in double quotes. The value can not be all zeros. The value can not have the Multicast bit set. So, use only the hexadecimal digits 2, 6, A, or E as the second digit of the twelve required in the NODE ADDRESS parameter. Use any other numbers you prefer in all other positions.[Example: NODE = "02AA00123456"] * Third-party trademarks are the property of their respective owners.