COMPEX ENET32-VL Ethernet Adapter (940128) Checked by Alwyn Song Jan 28, 1994 January 29 1994 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � � � DIRECTORY STRUCTURE � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 1) INTRODUCTION This floppy diskette contains network drivers and a configuration utility. The files are arranged in the following directories. a) \WFW31 Contains: - Files for installing a DOS NDIS driver in Windows For Workgroups. b) \DOS Contains: - NetWare ODI workstation driver. - NET.CFG, a sample configuration file for your quick reference. - ENET32.INS, a driver installation information file used by the DOS Requester INSTALL program. c) \OS2ODI Contains NetWare OS2 Requester. d) \NETWARE.4X Contains NetWare ODI server driver and its installation file. f) \MSLANMAN.DOS Contains files for installing DOS NDIS driver in a Microsoft LAN Manager network. Refer to the section "LAN MANAGER" in this document for more details. e) \MSLANMAN.OS2 Contains the driver for installation of OS/2 workstation or OS/2 server. Refer to the section "LAN MANAGER" in this document for more details. f) \UTILITY Contains a configuration utility for you to change the settings of the board. g) \PKT Contains a Packet Driver for the network adapter. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � � � NOVELL NETWARE � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 1) INTRODUCTION The floppy diskette contains drivers and utilities which enable the ENET32-VL to operate in the following NetWare Operating system: a) NetWare Lite v1.x b) NetWare v3.1x c) NetWare v4.x The main features and functions of the drivers are listed below. a) NetWare DOS Workstation Driver (EN32VL.COM) This ODI driver is for DOS workstations when using Novell ODI driver stack. b) NetWare OS2 Requester (EN32VL.SYS) This ODI driver is for OS2 workstations when using Novell ODI driver stack. c) NetWare Server Driver (EN32VL.LAN) This Ethernet driver is for NetWare v3.x or v4.x file Servers and complies with Novell ODI (Open Data-link Interface) Specifications. The functions of the utilities are listed below. a) NET.CFG - sample configuration file for DOS ODI driver. b) EN32VL.INS - driver installation information file used by the DOS Requester INSTALL program. c) EN32VL.LDI - driver installation information file used by the NetWare 4.x server INSTALL program. 2) Installing the NetWare DOS ODI Client Driver The DOS ODI driver may be installed using the Novell client INSTALL program (available in NetWare v3.12 and above). Please refer to the Novell user manuals for specific instructions to load additional drivers from an external floppy diskette. The driver may also be loaded manually through the DOS command line or automatically through a batch file such as AUTOEXEC.BAT. The driver is located in the DOS subdirectory on the driver diskette. To install the ENET32-VL driver, follow the instructions given below: i) Insert the Driver diskette into the system's floppy drive. ii) Create a subdirectory in your client's main boot drive with the following files: LSL.COM - Link Support Layer EN32VL.COM - The ENET32-VL DOS ODI Driver IPXODI.COM - The IPX protocol stack file NETX.EXE - NetWare Shell (Used with conventional memory workstations) NET.CFG - Optional; for configuring options different from the default settings VLM.EXE - Use this instead of NETX.EXE to utilize NetWare Directory Service (NDS) for Netware 4.x and above NETX.EXE, LSL.COM, VLM.EXE and IPXODI.COM can be obtained from the Workstation Driver Diskette in the Novell Client Software Package. Copy the client files EN32VL.COM from the DOS directory of the Driver Diskette to the subdirectory. Please note, when loading the VLM, the CONFIG.SYS must have the following line to operate correctly. LASTDRIVE=Z iii) To load these files manually, execute the following commnads at the DOS prompt: LSL EN32VL IPXODI NETX (Use VLM instead for NetWare 4.x) iv) To automatically load these files, use a DOS text editor to create and/or modify the AUTOEXEC.BAT file, then save it to the disk. The AUTOEXEC.BAT file should look similar to the following: \\LSL \\EN32VL \\IPXODI \\NETX (Use VLM instead for NetWare 4.x) Reboot the workstation so the above commands are executed. v) After NETX (or VLM) is executed, and if a server is present, it will attach to the server and display the server name on the monitor. You can now login to the network. Keyword Examples: To change any default settings when the driver is loaded, the NET.CFG file must exist in the workstation. A sample NET.CFG section of EN32VL.COM driver is in the DOS directory of the driver diskette. You can append the contents of this sample to your existing NET.CFG file and edit it according to your needs. 3) Installing the Netware OS/2 Client Driver To install the OS/2 ODI driver, the Novell OS/2 Requester should be used. Load Netware OS/2 ODI driver from the OS/2 CONFIG.SYS file in the sequence below. For more information on installing the OS/2 ODI driver, refer to the NetWare Requester for OS/2 installation documentation. i) Insert the driver diskette into the system's floppy drive. ii) Using the Netware OS/2 disks provided by Novell, install the Netware OS/2 requester files on the target hard disk and the file server. Follow the instructions on screen to configure the Netware OS/2 requester for a Netware-supported LAN adapter board. Select any LAN adapter (e.g., NE2000). iii) Copy the OS/2 ODI driver, EN32VL.SYS, from the Driver Diskette to the C:\NETWARE directory of the boot drive through path: A:\OS2ODI iv) Edit the CONFIG.SYS file and replace the Netware-supported LAN adapter driver with the name of the OS/2 ODI driver, EN32VL.SYS. For example: DEVICE=C:\NETWARE\EN32VL.SYS The following is an example of NetWare 3.x of the CONFIG.SYS load sequence for OS/2 ODI driver support for the IPX protocol stack. REM ---Netware Requester Statements Begin --- DEVICE=C:\NETWARE\LSL.SYS RUN=C:\NETWARE\DDAEMON.EXE DEVICE=C:\NETWARE\EN32VL.SYS (Located in OS2ODI directory on Driver Diskette) DEVICE=C:\NETWARE\IPX.SYS DEVICE=C:\NETWARE\NWREQ.SYS IFS=DEVICE=C:\NETWARE\NWIFS.IFS RUN=DEVICE=C:\NETWARE\NWDAEMON.EXE REM ---Netware Requester Statements End --- The default settings may be modified when the driver loads by using the file NET.CFG. Also, the OS/2 ODI driver may also be installed to support multiple protocol stacks and Ethernet frame types. For more information, refer to the Netware Requester for OS/2 installation documentation. Keyword Examples: To change any default settings when the driver is loaded, the NET.CFG file must exist in the workstation. A sample NET.CFG section of EN32VL.SYS driver is in the DOS directory of the driver diskette. You can append the contents of this sample to your existing NET.CFG file and edit it according to your needs. 4) Installing NetWare Server 4.x Driver The NetWare server driver EN32VL.LAN is located in the NETWARE.4X subdirectory of the driver diskette. The INSTALL utility of NetWare 4.x can be used for automatic installation of the driver. Follow the guidelines in the Novell NetWare documentation for more details to install the ENET32-VL driver from the driver diskette. To manually load the drivers through the Server command console, use the LOAD and BIND commands as described below. For more information on these commands, refer to the NetWare LAN driver installation documentation. To load the server driver, either use the server command line prompted by ":" or edit AUTOEXEC.NCF. If you use the server command line, you will need to load the driver each time the system is booted. If you edit AUTOEXEC.NCF, it will automatically load the driver each time your system is booted. To install the NetWare Server, follow the instructions given below: i) Copy the ODI server driver, EN32VL.LAN, from the Driver Diskette to the hard disk directory where the NetWare system files are located. The path on the Diskette should be: A:\NETWARE.4X ii) Boot NetWare by executing SERVER.EXE. Refer to NetWare documentation on loading disk drivers and mounting volumes. iii) To load the driver manually, simply follow the instructions given below: type the following command at the file server console: LOAD EN32VL (You will need to specify DOS path if the driver is located in a DOS partition). No keywords need to be specified for interrupt channel and I/O address. Make sure that MSM and ETHERTSM files are present in the same directory as EN32VL. The EN32VL driver will autoload these files. These files are provided with Novell NetWare. Then, bind the driver to the IPX protocol stack by typing: BIND IPX TO EN32VL NET=xxxx (Bind to ipx or any other protocol stack). iv) To load the driver using AUTOEXEC.NCF, you must edit AUTOEXEC.NCF and add the above LOAD and BIND command lines to the file. You should use the Novell server utility INSTALL to edit the AUTOEXEC.NCF file. Keyword Examples: The FRAME keyword should be used with the LOAD command to designate the desired frame type. In addition, the BOARD keyword must be used in conjunction with the FRAME keyword if no IO Address is specified to support multiple FRAME types. The available frame values are: Ethernet_802.2 Ethernet_802.3 Ethernet_SNAP Ethernet_II Please refer to the Novell NetWare documentation for details regarding each frame type. The BOARD keyword value is designated by the user. The range available for BOARD is 0 - 99999999. For example, to load multiple frame types for one physical ENET32-VL board, the following should be entered: LOAD EN32VL FRAME=Ethernet_802.2 BOARD=1 LOAD EN32VL FRAME=Ethernet_802.3 BOARD=1 LOAD EN32VL FRAME=Ethernet_II BOARD=1 LOAD EN32VL FRAME=Ethernet_SNAP BOARD=1 Finally, the driver must be binded to the IPX protocol for each frame type according to the procedure provided in the Novell documentation. Please note that if memory is too low to support multiple frames, the buffer size must be increased in the STARTUP.NCF in NetWare. For example, the "ReservedBuffersbelow16Meg" should be set to below 32 from the default setting of below 16. The correct syntax is as follow: Set ReservedBuffersbelow16Meg=32 Single FRAME type support The FRAME keyword should be used with the LOAD command to designate the desired frame type. For single FRAME support, no BOARD keyword is needed to designate one frame type. The available values and description to load FRAME types is explained above in the Multiple FRAME type support section. Loading Multiple Boards The driver must be loaded again for each new adapter board installed in the system. For example, to load two boards in the system for the NetWare environment, the following must be entered. For first adapter board: LOAD EN32VL For second adapter board: LOAD EN32VL Loading Multiple Boards With Multiple Frames The following example can be used: For first adapter board: LOAD EN32VL FRAME=Ethernet_802.2 BOARD=1 LOAD EN32VL FRAME=Ethernet_802.3 BOARD=1 For second adapter board: LOAD EN32VL FRAME=Ethernet_802.2 BOARD=2 LOAD EN32VL FRAME=Ethernet_802.3 BOARD=2 5) Installing NetWare Server 3.1x Driver For NetWare 3.1x server, the ENET32-VL server driver is same as the one used on NetWare 4.x server. The driver (EN32VL.LAN) is located under the NETWARE.4X subdirectory in the Driver Disk. NetWare 3.1x INSTALL utility cannot be used to install the server driver onto the server. You have to use the LOAD and BIND commands to load the NetWare server driver as described below. For more information on these commands, refer to the NetWare 3.1x LAN driver installation documentation. To install the NetWare Server 3.1x, follow the instructions given below: i) Copy the server driver EN32VL.LAN from NETWARE.4X directory of the driver diskette to the hard disk directory where NetWare 3.1x system files are located. ii) Boot NetWare by executing SERVER.EXE. Refer to the NetWare documentation on loading disk drivers and mounting volumes. iii) To load the driver manually, follow the instructions given below. For NetWare 3.11, type the following command at the file server console: LOAD LSLENH.NLM LOAD MSM31X.NLM LOAD ETHERTSM.NLM LOAD EN32VL Note: The LSLENH.NLM, MSM31X.NLM and ETHERTSM.NLM are updates for NetWare 3.11 and are not found on the original NetWare 3.11 diskettes. These updates are available from Novell. The original MONITOR.NLM also cannot be used since it has a bug and will crash the system. A new version of MONITOR.NLM is needed. For NetWare 3.12, type the following command at the file server console: LOAD EN32VL (You will need to specify DOS path if the driver is located in a DOS partition). Then, bind the driver to the IPX protocol stack by typing: BIND IPX TO EN32VL NET=xxxx (Bind to ipx or any other protocol stack). iv) To load the driver using AUTOEXEC.NCF, edit the AUTOEXEC.NCF. Use the "INSTALL" utility to add the above command lines. Keyword Examples: See Keyword Examples under Installing NetWare 4.x Server driver. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � � � MICROSOFT LAN MANAGER AND WINDOWS FOR WORKGROUP � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 1) INTRODUCTION The ENET32-VL has two NDIS drivers which comply with Microsoft NDI Specifications v2.0.1. The ENET32-VL NDIS 2.0.1 drivers (EN32VL.DOS and EN32VL.OS2) are located in the MSLANMAN.DOS and MSLANMAN.OS2 directories. The directory structure provided on the driver diskette has been setup for automatic OEM installation. Follow the guidelines in the Microsoft LAN Manager Installation Guide for more details to install the ENET32-VL driver from the driver diskette. The three files necessary for proper driver installation are: a) EN32VL.NIF A Network Information file. It contains information needed by the LAN MANAGER SETUP program to install the NDIS driver. b) PROTOCOL.INI A sample initialization file. It holds the hardware settings of the network adapter and the necessary information for the driver to configure itself to work in different environments. c) EN32VL.DOS (or EN32VL.OS2) NDIS driver. 2) LAN MANAGER INSTALLATION Use the installation procedure described here as general guidelines. Your exact installation requirements may vary slightly. LAN Manager has a SETUP program that functions to import and configure drivers. The SETUP utility for LAN Manager will install the ENET32-VL NDIS driver that is provided in the Driver Diskette. To install the NDIS driver, follow the instructions given below: i) Insert the driver diskette into the floppy drive. ii) From the LAN Manager subdirectory on your hard disk, run SETUP to begin installation. iii) Use the ALT key on your keyboard and the highlighted letter to pull down the Configuration menu (ALT + C). iv) From the Network Adapter Drivers dialog box, select the Compex ENET32-VL driver from the menu, if shown. Otherwise, select Other Driver to import the ENET32-VL driver from the driver disk. v) Enter the disk drive letter for the driver diskette. No path is required because the driver diskette is structured for the Microsoft LAN Manager OEM setup. vi) Select the ENET32-VL Ethernet adapter and choose OK. vii) Select the desired protocol from the Network Protocol dialog box and choose OK. viii)In the Workstation Configuration dialog box, select the ENET32-VL Ethernet adapter and choose OK. ix) Follow the remaining instructions from LAN Manager to complete installation. 3) Windows for Workgroups 3.1 Driver Installation The installation for the NDIS 2.0.1 driver is menu driven through the Windows interface. The driver and other relevant files are located in the root directory. The directory structure provided on the driver diskette has been setup for automatic OEM installation. Follow the guidelines in the Microsoft Windows for Workgroups User's Guide for more details to install the driver from the driver diskette. To install the NDIS 2.0.1 driver, follow the instructions below: i) Insert the driver diskette in the system's floppy drive. ii) From the Main group in Windows, choose the Control Panel icon. iii) In the Network Settings dialog box, choose the Adapters button and the Network Adapters dialog box should appear. iv) Choose the Add button to install the driver from the diskette. v) In the list of network adapters, select the "Unlisted or Updated Network Adapter" option. vi) Enter the drive letter and the WFW31 path to load the NDIS driver. For example, A:\WFW31. vii) Select the ENET32-VL Driver and choose OK. viii)If the network adapter driver requires additional settings, a setup dialog box appears displaying the default settings. Modify the settings if necessary. ix) In the Network Adapters dialog box, choose the Close button. Then choose the OK button in the Network Settings dialog box. x) Follow the remaining Window instructions, to restart the computer and have the driver take effect. 4) NDIS driver keyword The following are the supported keywords for the NDIS driver. IOADDRESS - IO address of the board. Supported values are 0x220, 0x240, 0x280, 0x2A0, 0x300, 0x320, 0x340 and 0x380. Use this keyword if you have more than one board on the system and you want to choose a particular board to run the driver. INTERRUPT - Interrupt no of the board. Supported values are 10, 5, 3 and 15. TXBUFFERS - Transmit buffer size. A valid value is a number which is a power of 2. Default value is 4. RXBUFFERS - Receive buffer size. A valid value is a number which is a power of 2. Default value is 4. 5) Special Notes on ENET32-VL Rev.C board. Due to a minor bug in the EEPROM contents, the NDIS driver will detect the interrupt channel of the board as 0 which is incorrect. You should use the the VLSET.EXE program to reprogram the EEPROM. To correct the bug, run the VLSET.EXE program, change the default settings to what you need or just load the default settings again, and then reprogram the board. 6) Other installations To install the NDIS driver for use with non-LAN MANAGER based products, follow the directions supplied with that product. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � � � PACKET DRIVER � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 1) INTRODUCTION The Packet driver EN32VLPK.COM for DOS conforms to the Packet Driver Specification v1.09" developed by FTP Software Inc. 2) INSTALLATION To install the driver, copy the Packet Driver EN32VLPK.COM from the PKT directory in the Driver Diskette to your desired directory. The packet driver can be loaded from the DOS prompt or from the AUTOEXEC.BAT file. The command line format for Packet Driver is: EN32VLPK [-n] [-d] [-w] [IOADDR=io_addr] The keyword is the software interrupt used to communicate with the packet driver and must be included in the command line. The valid range is from 0x60 to 0x80. The most commonly used number if 0x60. For example: EN32VLPK INT=0x60 Other optional options are explained below. [-n] - The [-n] option converts Ethernet type 8137 and Novell PSO-like packets. This is required if you use a standard boot ROM and use the Packet Driver and IPX included in the Packet Driver package, as the drivers loaded from the boot image file. [-d] - The -d option delays initialization. The -d option will keep the initialization code after loading. This is required for making the PROM boot work. [-w] - The -w switch is used for Windows. Install the Packet Driver before running MS-Windows. This switch does not prevent Windows from swapping the network application out of memory, it simply detects when that has happened, and drops the packet. IOADDR - Used to specify the IO address of the board. This option is usually not necessary as the driver will search for the installed board if this option is not specified. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � � � UTILITY � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� The configuration utility, VLSET.EXE, allows you to view the current setttings of the ENET32-VL board and to change the settings. Settings that can change include the IO address, Interrupt channel, Cable type, Boot ROM address and Burst Mode. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � � � HISTORY OF DRIVERS AND UTILITIES � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� 1) INTRODUCTION This section records the modifications made on the device drivers and utilities. 1.1) ODI Workstation Driver A) EN32VL.COM v1.00 a) First release. 1.2) OS2 Requester A) EN32VL.SYS v1.00 a) First release. 1.3) ODI Server Driver for NetWare 4.x and 3.x A) EN32VL.LAN v1.00 a) First release. 1.4) DOS NDIS Driver A) EN32VL.DOS v1.00 a) First release. 1.5) OS/2 NDIS Driver A) EN32VL.OS2 v1.00 a) First release. 1.6) Packet Driver A) EN32VLPK.COM v1.00 a) First release. 1.7) Configuration Utility A) VLSET.EXE v1.00 a) First release. Provided by: COMPEX Inc 4055, La Palma Unit C, Anaheim CA 92807, USA