a:\ndis2\readme.txt 27-JAN-1997 This README file is for the NDIS2 DOS and NDIS2 OS/2 device drivers for Digital's EtherWORKS TURBO PCI/EISA Network Interface Cards. Supported adapters: DE425, DE434, DE435 Device drivers: DC21X4.DOS and DC21X4.OS2 These device drivers comply with the NDIS 2.0.1 specification. The Digital EtherWORKS adapters and the NDIS2 drivers meet the networking needs of any Network Operation System (NOS) which adheres to the NDIS 2.0.1 specification. This file contains information on the following topics: 1. PROTOCOL.INI parameters 2. PATHWORKS V4.1 installation 3. PATHWORKS V5.0 installation 4. IBM OS/2 2.1 with LAN Server 3.X installation 5. Microsoft LAN Manager 2.X installation (DOS and OS/2) For information on installing the NDIS2 DOS driver with Windows for Workgroups, see the readme.txt in the WFW directory of this diskette. *************************** * PROTOCOL.INI PARAMETERS * *************************** Mandatory Parameters: DRIVERNAME (range = DC21X4$, DC21X42$-DC21X48$; no default) This parameter must be DC21X4$ when only one adapter is installed. DC21X42$ is required for the second adapter, etc. Optional Parameters: SIA_MODE (DE425 - parameter is set with EISA config utility; DE434 range = TP, TP_FULL_DUPLEX; DE434 default = TP; DE425,DE435 range = AUTODETECT,BNC,AUI,TP, TP_FULL_DUPLEX; DE425,DE435 default = AUTODETECT) This parameter defines the cable connection type. AUTOSENSE - executes an algorithm which detects the serial interface connection type at initialization time. AUI - selects AUI mode for the external transceiver connection to the 15-pin D-sub connector. The BNC/AUI jumper must also be set to AUI. BNC - selects the BNC (thinwire) connector for internal transceiver. The BNC/AUI jumper must also be set to BNC. TP - selects the RJ45 connector for the adapter's twisted pair transceiver, for connection to a twisted pair hub. TP_FULL_DUPLEX - specifies Full Duplex operation using the twisted pair transceiver. The adapter should be connected to another Ethernet station capable of Full Duplex operation. TP_LINK_DISABLE - selects the TP transceiver with the Link-Fail test ignored. SLOT (range = 0-26; default = 0) This parameter specifies the bus slot where the Digital DC21x4 adapter is placed. It is not needed if there is only one DC21x4 adapter installed in the system. If there is another DC21x4 controller installed in the system, the SLOT keyword must be used. - If SLOT=0 or SLOT=16, the driver will scan for a DC21x4 controller. The first DC21x4 controller will be selected. - A number from 1 to 15 specifies a slot number on the EISA bus (DE425 only) - A number from 17-26 specifies a DC21x4 controller other than the first. For example, 17 indicates the second DC21x4 controller, 18 indicates the third, etc. NETADDRESS (range = 0-FF; default = n/a) This parameter overrides the address stored in the on-board Ethernet Address ROM. The address is a 12-byte hexadecimal number. The user should make certain that the address is a legal IEEE address. The address should be surrounded by quotes. For example: NetAddress = "08002B3C45FC" NUM_TX_BUFFERS (range = 4..16; default = 8) This parameter specifies the number of transmit buffers the driver should use. If the number of transmit and receive buffers is large, problems may arise. Specifically, in OS/2 environments the driver may be unable to load. NUM_RX_BUFFERS (range = 4..16; default = 12) This parameter specifies the number of receive buffers the driver should use. If the number of transmit and receive buffers is large, problems may arise. Specifically, in OS/2 environments the driver may be unable to load. TURBO (range = enabled, disabled; default = disabled) Does not apply to DE425. Controls whether host-to-PCI posting (HPPE) will be enabled or disabled. This is relevant only if the system's host-to-PCI bridge is Intel's 82424 (CDC) or 82434 (PCMC) bridge. enabled - means that HPPE will be disabled. This may improve network performance. disabled - means that the system configuration will remain as it is with no intervention by the driver. TX_THRESHOLD (range = LW128,LW256,LW512,LW1024,FP; default = FP) Controls the transmit threshold of the adapter. A small threshold may improve performance. However, in some machines it could cause many packets to be lost, and perhaps the connection may fail. FP means the threshold is "full packet", which is maximal. The packet will transmit only after it is all in the FIFO. LW1024 is a threshold of almost one full maximum packet. LW128 is the smallest allowable threshold. ****************************** * PATHWORKS 4.1 INSTALLATION * ****************************** Manual Installation: If PATHWORKS is already installed and configured and you do not wish to use the PATHWORKS installation program, perform the following steps manually to install the NDIS2 driver: 1. Copy the DC21X4.DOS file from the driver installation diskette (A:\NDIS2\DOS\DC21X4.DOS) to the C:\DECNET directory. 2. Add the following line to CONFIG.SYS to load the driver: DEVICE = C:\DECNET\DC21X4.DOS 3. ADD the PROTOCOL.INI stub from the driver installation disk to the end of the existing PROTOCOL.INI file located in the DECNET directory. The stub appears as follows: [DC21X4] DRIVERNAME=DC21X4$ 4. Modify the [DATALINK] and [IPX4MAC] sections in the PROTOCOL.INI file to change the value of the keyword BINDINGS = driverlabel to BINDINGS = DC21X4.DOS Automatic Installation Using the PATHWORKS Client Setup Diskettes: Insert the PATHWORKS Client Setup diskette 1 of 2 in the floppy disk drive. Run NETSETUP from that drive and follow the instructions until you reach the window labeled: Select the network adapter type: o Select "Ethernet" and press ENTER key. Select the Ethernet adapter: o Select "Other NDIS" and press ENTER key. Enter full DRIVE:\PATH\FILENAME for NDIS driver: o Type A:\NDIS2\DOS\DC21X4.DOS and press ENTER. Enter full DRIVE:\PATH\ for the PROTOCOL.INI stub: o Type A:\NDIS2\DOS\ and press ENTER. After you have performed these steps, PATHWORKS will copy the corresponding files from the installation diskette to the directory. Example of CONFIG.SYS and PROTOCOL.INI for PATHWORKS 4.1 ---------------------------------------------------------- ----- CONFIG.SYS ----- DEVICE=C:\WINDOWS\HIMEM.SYS DEVICE=C:\WINDOWS\EMM386.EXE 3072 RAM FRAME=E000 DOS=HIGH,UMB DEVICE=C:\DECNET\laddrv.sys /D:4 DEVICE=C:\DECNET\PROTMAN.SYS /I:C:\DECNET DEVICE=C:\DECNET\DC21X4.DOS FILES=30 Buffers=40 STACKS=9,256 SHELL = C:\COMMAND.com /P /E:1024 lastdrive=z ----- PROTOCOL.INI ----- [protocol manager] DRIVERNAME = PROTMAN$ BINDINGS = DC21X4_NIF [DC21X4_NIF] DriverName = DC21X4$ [DATALINK] DRIVERNAME = DLL$MAC LG_BUFFERS = 16 SM_BUFFERS = 6 OUTSTANDING = 32 HEURISTICS = 0 BINDINGS = DC21X4_NIF ******************************* * PATHWORKS V5.1 INSTALLATION * ******************************* Automatic Installation Using the PATHWORKS Client Setup: Insert the PATHWORKS Client Setup diskette 17 in your floppy drive. Run SETUP from that drive and follow the instructions 1. From "Select Drive" screen Select Alt_N for Network Select Decnet_Transport 2. Select "Other Adapter" Example: "Other Adapter" Screen Adapter Name: [Digital DC21X4] NDIS Driver Path: [a:\ndis2\dos] NDIS Driver File: [DC21X4.dos] NDIS Driver Name: [DC21X4] Other File: [ ] Enter ALT_O 3. Please insert the disk which contains file: A:\NDIS2\DOS\DC21X4.DOS Insert Diskette Re-insert SETUP diskette when prompted 4. Is the adapter a token ring adapter? [NO] 5. "Verify Network Information" Screen Example: Your Node Name:[LAB004] Your Node Address: [4.711] Lan Manager Username:[ADMIN] Lan Manager Username:[********] (enter twice for verification) Server Name:[LAB001] Server Node Address: [4.700] Service:[PWV51] Enter password for service: [ ] ( if none) 6. "Edit Protocol.ini" Screen Enter the correct Medium as displayed. TP, TP_FULLDUPLEX, etc. ALT_S to save. 7. The SETUP utility will auto connect you to your desired PATHWORKS client setup service. Continue with the instructions to complete the installation. ************************************************* * IBM OS/2 2.1 WITH LAN SERVER 3.X INSTALLATION * ************************************************* Installation using IBM LAN Adapter and Protocol Support (LAPS) -------------------------------------------------------------- 1. In OS/2 open the OS/2 System window, the System Setup window and the LAPS window. If you are installing LAN Server for the first time, LAPS is automatically started. 2. Use arrow keys or mouse to select from the main menu. 3. Insert the Driver Distribution Diskette in the drive. Enter for the source directory. 4. LAPS will copy the network drivers onto the system drive and display a message saying . Click on 5. Select from the LAPS main window. 6. Select and . 7. Select Digital EtherWORKS Adapter and add the driver to the current configuration. Select the protocols used on your network. See your network administrator if you do not know what protocols are used. 8. Select when completed. Select Exit at the main LAPS window and at the Update Drives window. Exit LAPS, shut down OS/2 and reboot the machine. Refer to the LAN Server installation guide for additional directions on using LAPS. ********************************************************* * MICROSOFT LAN MANAGER 2.X INSTALLATION (DOS AND OS/2) * ********************************************************* Automatic installation using the LAN Manager setup program ---------------------------------------------------------- (DOS and OS/2) 1. In the \LANMAN directory, start the SETUP program. 2. Select from the main menu. 3. Select from the configuration menu. 4. Remove any old adapter using . 5. Select . 6. Select and follow the directions. Manual installation for DOS LAN Manager --------------------------------------- If LAN Manager is already installed and configured and you do not wish to use the LAN Manager installation program, you must perform the following steps manually: 1. Create DC21X4 driver directory :\LANMAN.DOS\DRIVERS\ETHERNET\DC21X4 2. Copy the files \MSLANMAN.DOS\DRIVERS\ETHERNET\DC21X4\DC21X4.DOS and \MSLANMAN.DOS\DRIVERS\ETHERNET\DC21X4\PROTOCOL.INI to the new directory. 3. Copy the file \MSLANMAN.DOS\DRIVERS\NIF\DC21X4.NIF to the directory :\LANMAN.DOS\DRIVERS\NIF 4. Add the following to CONFIG.SYS to load the driver: DEVICE=:\LANMAN.DOS\DRIVERS\ETHERNET\DC21X4\DC21X4.DOS 5. Modify PROTOCOL.INI by appending the following information: [DC21X4_NIF] DRIVERNAME=DC21X4$ 6. Modify TCPIP_XIF and NETBEUI_XIF modules in PROTOCOL.INI by changing the value of the bindings keyword. from BINDINGS = driverlabel to BINDINGS = DC21X4_NIF Manual installation for OS/2 LAN Manager ---------------------------------------- If LAN Manager is already installed and configured and you do not wish to use the LAN Manager installation program, you must perform the following steps manually: 1. Create DC21X4 driver directory :\LANMAN.OS2\DRIVERS\ETHERNET\DC21X4 2. Copy the files \NDIS2\OS2\DC21X4.OS2 and \NDIS2\OS2\PROTOCOL.INI to the new directory. 3. Add the file DC21X4.NIF to the directory :\LANMAN.OS2\DRIVERS\NIF with the following contents: Model = DEC EtherWORKS Turbo PCI/EISA Path = ETHERNET\DC21X4 DeviceDriver = DC21X4.OS2 DeviceName = DC21X4$ Type = NDIS MediaType = ETHERNET 4. Add the following to CONFIG.SYS to load the driver: DEVICE=:\LANMAN.OS2\DRIVERS\ETHERNET\DC21X4\DC21X4.OS2 5. Modify PROTOCOL.INI by appending the following: [DC21X4_NIF] DRIVERNAME=DC21X4$ 6. Modify TCPIP_XIF and NETBEUI_XIF modules in PROTOCOL.INI by changing the value of the bindings keyword. from BINDINGS = driverlabel to BINDINGS = DC21X4_NIF