2 Banyan 6.00 NDIS Workstation v1.01 Banyan* NDIS workstation installation notes for Intel's EtherExpress(TM) PRO/10 PCI LAN adapters ======================================================= Location of Driver: \NDIS\E10P.DOS Sample Configuration Files -------------------------- CONFIG.SYS (will contain): DEVICE=C:\BAN\PROTMAN.DOS /I:C:\BAN DEVICE=C:\BAN\E10P.DOS PROTOCOL.INI: [E10P_NIF] Drivername = E10P$ General Installation -------------------- 1 The EtherExpress PRO/10 PCI LAN adapter uses a NDIS 2.0.1 driver to connect to a Banyan server. If you have a NDIS client disk prepared, skip to step #6. 2 To create an NDIS client disk, run PCCOPY (located on the Z drive of the Banyan server). 3 Select PC Configuration Software and/or LAN driver, and then select NDIS Ethernet and PCCONFIG. 4 Choose the appropriate DOS redirector. For example, REDIRALL for all versions of DOS. 5 Specify the directory where you want the client software copied to. The default is A:\. 6 On the client you're setting up, copy the NDIS client software to a directory on the hard drive. 7 Run Banyan's PCCONFIG program. 8 Select Network Card Settings and page down to select the NDIS Ethernet option. 9 Specify E10P_NIF as the PROTOCOL.INI bindings parameter. 10 Select Login Environment Settings, then Select Default Communications Driver. Page down to select the NDIS Ethernet option. 11 Save the settings and exit PCCONFIG. 12 Copy the PROTOCOL.INI and E10P.DOS files that are located in the NDIS subdirectory on the Intel Configuration and Driver disk to the BAN subdirectory or other directory where Banyan client files are located. Modify the PROTOCOL.INI file to make sure the file contains the line [E10P_NIF] above the DRIVERNAME=E10P$ line. 13 Add the lines to your CONFIG.SYS file as shown in the Sample Configuration Files section above. 14 Reboot and run BAN to attach to the Banyan server. Hints and Tips -------------- 1 Error Message with PRO0025E: This type of message will occur when the driver attempts to bind to the protocol manager. It generally indicates that there's a syntax or other error in the PROTOCOL.INI file. Review the file carefully for errors. Also, verify parameters entered in PCCONFIG. For additional information, reference NDISBAN.DOC which is part of the NDIS Banyan client software. 2 Make sure your NDISBAN.COM is dated April 1994 or later. Earlier versions may not work properly. 3 Parameters for the PROTOCOL.INI file: DRIVERNAME: (required) This is the one required parameter. See the Sample Configuration Files section at the top of this document for syntax. 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.This is the one required parameter. See example at the top of this document for syntax. 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 hexadecimal digits in all other positions.[Example: NODE = "02AA00123456"] * Third-party trademarks are the property of their respective owners