******************************************************************************* ** ** ** Part: SF0005-08 Znyx Corporation ** ** 48501 Warm Springs Blvd. ** ** EPIX Driver Diskette for ZX312 Suite 107 ** ** Release 8 Fremont, California 94539 ** ** USA ** ** ** ** Copyright (c) 1994 510 249 0800 voice ** ** All Rights Reserved 510 656 2460 fax ** ** 510 656 7969 BBS ** ** ftp.znyx.com anonymous ftp ** ** ** ******************************************************************************* ******************************************************************************* ** ** ** Revision History ** ** ** ** Date Rev Changes ** ** ** ** 01/24/94 1 Original Release ** ** 02/17/94 2 Added NetWare 4.01 driver ** ** 03/01/94 3 Added Windows NT NDIS 3.0 driver ** ** 05/03/94 4 New NDIS 3.0 driver for Windows for Workgroups 3.11, ** ** various enhancements and fixes for most other drivers. ** ** 05/18/94 5 New SCO and Interactive Unix drivers, new NetWare 3.1X ** ** driver solution, enhanced DOS ODI driver. ** ** 05/24/94 6 Added support for Windows/NT Advanced Server, modified ** ** SCO to pass current ANT certification tests. ** ** 08/02/94 7 New Univel UnixWare DLPI driver, updated Windows NT ** ** driver covering v3.5, Full Duplex and Latency register ** ** support in most drivers and automatic media detection, ** ** 12/06/94 8 New Packet Driver, Certified Novell HSM, updated DOS ODI, ** ** NDIS 2.01, SCO/ISC/UnixWare Unix drivers, Diagnostics ** ** ** ******************************************************************************* This release includes software to support the following LAN environments: Driver Directory Used By -------------- ------------- -------------------------------------- DIAG312.EXE \ Diagnostic from the DOS environment DOS ODI \DOSODI Novell NetWare ODI workstation NetWare 3 \3.1X Novell NetWare 3.11, 3.12 NetWare 4 \4.XX NetWare 4.01 OS/2 ODI \OS2 NetWare Requester for OS/2 DOS NDIS 2.01 \MSLANMAN.DOS Microsoft LAN MANAGER, WFW \IBM\DOS IBM LAN Server (LAPS) OS/2 NDIS 2.01 \MSLANMAN.OS2 Microsoft LAN MANAGER \IBM\OS2 IBM LAN Server (LAPS) VxD NDIS 3.0 \WFW WFW 3.11 (Install script in root dir) NT NDIS 3.0 \ Windows/NT Streams LLI/LLC \ SCO Unix, Interactive Unix Streams DLPI \ Univel UnixWare Packet Driver \PKTDRV Various protocol stacks and tools The following sections give specific release notes on each driver. In addition, there are sections that cover PCI related issues. DIAG312.EXE ----------- The DIAG312.EXE program will seek and run a confidence check on any ZX312 board it finds in the system. It does NOT test the analog output stages of the board, so it is possible for DIAG312.EXE to pass a board which does not work with one or more of the media types supported. To list all PCI devices in the system, enter the command DIAG312 LIST. A ZX312 does not need to be installed to run this option. DOS ODI ------- This driver includes the following enhancements: 1. Automatic media detection. This is the new default choice for the MEDIA parameter. 2. Full duplex support. Use 'MEDIA TPFD' as the media specifier to run full duplex ethernet over 10 Base-T. 3. Driver defaults to PCI burst mode enabled. NetWare 3 --------- The monolithic NetWare 3.1X driver has been moved to the subdirectory \3.1X\MONOLITH. The default case for Netware 3.1X is the modular LAN driver configuration using the Hardware Support Module (HSM), as explicitly recommended by Novell. Version 2.24 of the ZX312 HSM fully supports operation under NetWare 3.11 and NetWare 3.12. Installation for NetWare 3.11: - Load PATCHMAN.NLM and LSLENH.NLM. These modules are required to update NetWare 3.11 LAN driver interface functionality to the NetWare 3.12 level. - Replace the MONITOR.NLM found on your NetWare 3.11 server with the one found on the driver disk. The NetWare 3.11 MONITOR.NLM will not function properly with the new HSM statistics tables and will ABEND the server. - Load MSM31X.NLM. Make sure you load version 2.20 of the Media Support Module or later. The server software will inform you of that the module name is in fact MSM.NLM. This is normal. - Load ETHERTSM.NLM. Make sure you load version 2.20 of the Ethernet Topology Support Module or later. - Load the ZX312.LAN HSM. Installation for NetWare 3.12: - Load MSM31X.NLM. Make sure you load version 2.20 of the Media Support Module or later. The server software will inform you of that the module name is in fact MSM.NLM. This is normal. - Load ETHERTSM.NLM. Make sure you load version 2.20 of the Ethernet Topology Support Module or later. - Load the ZX312.LAN HSM. NetWare 4 --------- Version 2.22 of the ZX312 HSM has been certified by Novell, Inc. This driver can be found in the \4.XX\V2_22 directory on the diskette. Version 2.24 of the ZX312 HSM incorporates changes to enhance compatibility with newer PCI systems. Certification of this driver version is pending. The files were re-arranged to eliminate installation conflicts when the driver is installed under Windows/NT. To install the driver on Windows/NT, copy the contents of the \4.XX directory on the diskette to an empty directory on the hard disk. When installing the driver from the installation dialog box, specify the hard disk directory. Shared interrupts are fully supported in this version of the driver and have been tested with various SCSI adapters, including NCR and Adaptec. IMPORTANT NOTE: When using this driver with Windows NT (NetWare Requester) and the system is shut down, the user MUST engage a hard reset to shut down the adapter. The current version of the NetWare Requester does not inform the HSM (driver) that the system is being shut down, which leaves the hardware active after a warm boot. Failure to provide a hard reset will result in a crash or data corruption of the system after it is re-started. OS/2 ODI -------- The OS/2 ODI driver has not changed from the prior release. The current version of OS/2 does not recognize that PCI devices are capable of sharing interrupts. Znyx is working with IBM to resolve this problem. DOS and OS/2 NDIS 2.01 ---------------------- The following enhancments are in this release. 1. Automatic media detection. This is the new default choice for the MEDIA parameter. 2. Full duplex support. Use 'MEDIA TPFD' as the media specifier to run full duplex ethernet over 10 Base-T. 3. Driver defaults to PCI burst mode enabled. VxD NDIS 3.0 ------------ This driver supports Windows for Workgroups (WFW) 3.11. The following enhancments are in this release. 1. Automatic media detection. This is the new default choice for the MEDIA parameter. 2. Full duplex support. 3. Driver defaults to PCI burst mode enabled. IMPORTANT NOTE: When halting a WFW 3.11 system, a hard reset must be performed. Failure to do so will leave the adapter(s) active, causing data corruption and crashes on future operations. A CTRL-ALT-DEL sequence will NOT deactivate the ZX312. EXTREMELY IMPORTANT: When re-configuring an Adapter, the WFW dialog box will provide an option to "RE-BOOT System." Clicking this button will NOT deactivate the ZX312 adapter and when the system re-boots, data corruption and/or crashes can occur. The reset button must be pressed during a warm boot. Error messages under WFW and Windows/NT --------------------------------------- Error messages generated by the NDIS3 driver can be retrieved in the following ways: - For Windows NT, launch the 'Event Viewer' application found in the 'Administrative Tools' program group. Events generated by the ZX312 are marked as such. Double-clicking an event line will pop-up a more detailed description of the event. In the case of a ZNYX network adapter, click on the 'Words' button in the Data portion of the Event Detail window. The last word in the data window is the ZNYX-specific error code, which is required by ZNYX personnel for problem diagnosis. - For Windows-for-Workgroups, use the Notepad editor to peruse the NDIS error log file NDISLOG.TXT found in the Windows directory (e.g. C:\WINDOWS) Errors are logged into this file, one line at a time. In the case of a ZNYX network adapter, the number at the very end of a line is the ZNYX- specific error code, which should be noted before contacting ZNYX Technical Support. The NDISLOG.TXT file is erased every time Windows starts or restarts, so be sure to retain a copy for later study. Packet Driver ------------- The ZX312 packet driver is loaded using the following parameters: ZX312 [-ndw] [U] [bus=X] [dev=X] [media=] The optional switch parameters preceded by a dash effect the following: -n: Novell IPX frames are slightly changed to maintain compatibility with some drivers in Netware 2.X file servers. -d: Delayed driver initialization on the first bind request. -w: Windows compatibility, used if software using the packet driver is run in a DOS-box under Windows 3.X. The parameter is the only required parameter and represents the software interrupt to be used for packet driver-to-protocol communication. Permissible values are 0x60 through 0x6F. The 'bus=' and 'dev=' parameters are required in installations with more than one ZX312 and select a specific adapter board to be used. The optional 'media=' parameter selects a specific media type to be used. The driver defaults to automatic media detection. Valid media types are BNC, TP, TPFD, AUI, or AUTO. TPFD will select full duplex operation in connection with a full duplex twisted pair Ethernet hub. Specifying the parameter followed by the option 'U' will attempt to unload the packet driver. Successful unloading is not possible under all circumstances. Unix Drivers and the MAKEDISK program ------------------------------------- In order to install the Unix drivers, you will need to prepare a floppy disk with the driver and support files in the format appropriate for your OS. Under DOS, run the MAKEDISK utility provided on the driver disk. Follow the directions given by the MAKEDISK utility to generate the Unix driver disk. Before booting the Unix system to install the driver, boot DOS and run DIAG312 to examine your system configuration. Make a note of the PCI bus and device numbers as well as the interrupt configured for the adapter. With most PCI systems, the interrupt assignment is configurable in the ROM BIOS setup. When configuring the Unix driver under either OS, select PCI bus 0, device 0 for automatic board detection. Automatic detection works for more than one adapter, but is only recommended when using a single adapter. Streams Buffer Configuration under System V Release 3: ------------------------------------------------------ For frame reception, the drivers use 512 byte Streams buffers. Increasing the number of Streams buffers of that size (NBLK512) might help increase your system performance. Most systems are adequately configured for a single bus master network adapter. If you are using more than one adapter, increase the present NBLK512 parameter by 80 times the total number of network adapters in your system. See the individual Unix brand sections below on how to configure Streams parameters for SVR 3. SCO Unix Driver --------------- Tested with SCO Unix 3.2.4 and SCO ODT 2.0, and 3.0. Use the 'custom' command to install the driver. The 'mkdev' and 'netconfig' configuration methods are both supported. Use the 'configure' command located in /etc/conf/cf.d to configure Streams buffer allocation. Sunsoft Interactive Unix Driver ------------------------------- Tested with Interactive Unix versions 2.2, 3.0, and 4.0. Use the 'sysadm' command to install the driver. If you are running version 3.0 or newer of Interactive Unix, the driver will become part of the network device driver subset. When configuring TCP/IP, select picking a driver from the subset rather than specifying '3rd party driver'. Use the 'kconfig' command to configure Streams buffer allocation. Univel UnixWare Driver ---------------------- Installation of the Univel UnixWare Driver is fully menu-driven. From the UnixWare desktop, open the System_Setup folder. Launch the Application Install utility ('Appl-n_Setup') and select 'Uninstalled Applications' from the 'View' pulldown menu. Choose the floppy disk drive you are installing from. You will be prompted for the PCI bus and device numbers, the interrupt configuration, and the desired media type. Note that UnixWare is based on SVR4 and does not require configuration of individual Streams buffer counts. PCI Configuration ----------------- Many questions have arisen during installation of the ZX312 relating to the system BIOS, which is responsible for implementing and reporting the configuration of PCI devices. The intent of the PCI BIOS is to insulate driver software from variances in PCI hardware implementations. The PCI SIG has issued guidelines for the implementation of the system BIOS for both real-mode and protected mode operations. Although most BIOS' implement real-mode operations sufficiently, ZNYX has discovered (through the PCI Compatibility Workshop and in the lab) that many BIOS implementations do not work under protected mode. This means that the ZX312 drivers for protected mode operating systems cannot rely on the system BIOS to discover the existence and configuration of ZX312 card(s). In some cases, an attempt by the driver to access the BIOS while in protected mode will result in a system crash. The current ZNYX drivers for Novell NetWare, OS/2 NDIS, and Windows/NT NDIS access the PCI system board hardware directly to detect the configuration of the system. Release 4 and earlier ZX312 drivers are able to work with system boards that use PCI Configuration Method #2 as defined by the PCI Version 2.0 specification. Systems that implement PCI Configuration Method #1 will be supported starting with Release 5 of the ZX312 driver set. The DOS based ZX312 drivers, NDIS and ODI, use the system BIOS for PCI configuration and will work regardless of which Configuration Method is used. The DIAG312 program will indicate which method the system's motherboard utilizes. PCI Underrun/Overrun Conditions ------------------------------- In some PCI systems the possibility of underrun and overrun exists. This is caused by some devices on the PCI bus violating the PCI latency rules. If this occurs while the ZX312 is receiving or transmitting large data packets, the transmission or reception will be aborted for that packet. The higer level protocols will have to re-transmit the packet when a time-out occurs. To ensure data corruption will not occur during underruns and overruns, the PCI drivers in this release automatically detect the condition and take over the responsibility of calculating CRCs on packet transmissions. If no underrun or overrun conditions occur on the PCI system, this section of the drivers will operate normally. ******************************** * End of RELEASE.TXT SF0005-08 * ********************************