*** ODI Server Driver for PDI8023 Family *** This ODI Server Driver for the PDI8023 family of adapters is written to Novell's latest specification 3.1. This driver is capable of working in multiple Network Operating Systems, that meet the following requirementsi 32 bit, single hardware bus, Intel 386 and above processors. Features of this driver: - Support for Netware Servers 3.11, 3.12 and 4.0. - Support for WINDOWS NT July Release. - Supports the following network adapters, PDI8023-8, PDI8023-16, PDI8023Plus-16, PDuC8023-16, and PDE8023Plus-32. - Supports both Pure Data and Compatible modes on the PDI8023Plus adapters. - Supports up to eight adapters in on system. - Supports shared interrupts on PDuC8023-16 and PDE8023Plus-32 adapters. - Supports 32K packet RAM above 1 Meg. on PDE8023Plus-32 adapters. - Supports promiscuous mode for operation with Novell LANalyzer product. - Supports multiple 32 bit Intel Operating Systems. - Supports the following frame types, ETHERNET_802.3, EHTERNET_802.2 ETHERNET_SNAP, and ETHERNET_II - In a multiple adapter system, control of which frame type is loaded on a specific LAN can be controlled from the command line or the AUTOEXEC.NCF file. This is controlled by placing the PORT keyword on the command line, or for Micro Channel systems the SLOT keyword can be used instead of PORT if it is more logical. - The full range of Generic, Media specific, and eight custom statistic counters have been implemented. Driver History -------------- Version 1.0 The initial release of the driver fully supported the PDI8023 family. Known problems: There was a problem specifying frame type on the command line. This version of the driver was written to the server driver specification 3.0 which did not support multiple OS. Version 1.1 This release fixes the above problem and adds support for slot numbers on the command line for Micro Channel and EISA systems. This driver was updated to Novell's latest specification (3.1) for server drivers. Known problems: There was a problem is the driver was unload and then re-loaded, the error message that no free adapters were found. The was a minor release of Ver. 1.1a that fix these issues. Version 1.2 This release fixes the above problem and adds support for the PDE8023Plus-32 EISA adapter. Shared interrupts are now available for the PDE8023Plus-32 and PDuC8023-16 adapters. The PDE8023Plus-32 adapter now supports 32K of packet RAM above the 1 Meg boundry. The PDEN40x.LDI file has been modified to allow for EISA slot numbers, the adapter must of course be an PDE8023Plus-32. See section on installation issues below. The OEMSETUP.INF has been updated to support EISA machines, this file is only required for the new PDE8023Plus-32 other wise support is in the release Netware Requestor. (Nov. 4, 1993) Files released: directory \NETWARE.40 PDEN40x.LAN - Netware ODI Server driver Size 7926 bytes PDEN40x.LDI - Netware install file used by INSTALL.NLM directory \NT OEMSETUP.INF - Windows NT install file (use the same driver now, Nov. 4, 1993 release of Netware Requestor) ================== Statistic Counters ================== This driver has implemented the Novell require generic and media specific statistics plus eight custom statistics have been added. A brief description of the custom statistic counters is as follows: TxUnderrunErrorCount The hardware has not supplied the transmitter with data from the packet RAM fast enough. CDHeartbeatErrorCount After a transmit the ethernet controller tests the collision circuitry if this counter indicates a failure of the collision detect circuit. TransmitTimeoutCount Transmit has taken too long, usually due to the Coax cable been disconnected. ReceiverMissedPacketCount Number of packets missed been copied off the wire because the adapter was busy. BackToBackSendCount A transmit was finished and the second transmit buffer was ready to be transmitted from the interrupt service routine call. BackToBackReceiveCount More than one packet was received on one interrupt service routine call. RxTxSameInterrupt A packet was received and one of the transmit buffers was ready to transmit a packet on the same interrupt service routine call. SpuriousInterrupt A interrupt service routine call was made but the adapter did not require service. ============ Netware 3.11 ============ To operate this driver under Netware 386 Ver. 3.11 the following files are needed. The latest files or at least this verision are required, so check the dates and file sizes with those listed here. LSLENH.NLM 11641 11-16-92 8:29a V1.01 PATCHMAN.NLM 9632 2-04-93 10:38a V2.30 MSM31x.NLM renamed to MSM.NLM 13231 7-19-93 4:11p V2.15 ETHERTSM.NLM 8053 7-07-93 5:05p V2.15 Novell supplies the above files. PDEN40x.LAN 7926 9-24-93 12:12p V1.1 First load the LSLENH.NLM module: LOAD LSLENH this auto loads PATCHMAN Then to load the driver: LOAD PDEN40X.LAN The first time this happens the driver will load the MSM.NLM and ETHERTSM.NLM. ============ Netware 3.12 ============ This new release of Netware has all the appropriate files in the SYSTEM directory, so only the driver is require to be loaded. To load the driver: LOAD PDEN40X.LAN MSM and TSM module requirements. What is shipped with Netware 3.12 will work but the current modules are: MSM 15,628 10-4-93 1:03p ETHERTSM 8,841 9-28-93 2:14p ============ Netware 4.0 ============ To load the driver: LOAD PDEN40X.LAN =============================================================== Install Driver on NETWARE Server that uses the PDEN40x.LDI file =============================================================== To place the driver in the Netware SYSTEM directory either it can be copied from the support disk NETWARE.40 directory to the SYSTEM directory or the INSTALL NLM can be used. At the server type: LOAD INSTALL Select the Maintenance option Select the LAN Driver option Press the INS key Press the F3 key Enter driver letter:\netware.40 ... Update the AUTOEXEC.NCF files to load the driver. Important: If multiple frame type or multiple adapters are used either the Port= or the Slot= field in the Driver PDEN40X Parameters must be filled in. Do not fill in both. Check that the AUTOEXEC.NCF only contains one of the above key words, remove the MEM= and INT= settings if present. An editor can be started from the server by: load edit sys:\system\autoexec.ncf ================================= Multiple Ethernet Adapter Support ================================= If multiple adapter are used in a server the first adapter loaded will load the MSM and ETHERTSM and the actual driver PDEN40x.LAN. Then the system will prompt for the slot number or I/O Base address of the LAN adapter. This allows control of which LAN the driver and frame type loaded on. See below for examples of multiple adapter and frame types been loaded. LOAD PDEN40x PORT=280 or LOAD PDEN40x SLOT=3 This will force the driver to use the specified I/O address and not prompt. Continue to bind a protocol to the driver as in Netware 3.11. ===================== AUTOEXEC.NCF EXAMPLES ===================== It is now possible to specify slot number or port address on the command line and even mix them. Slot number only applies to Micro Channel systems. Examples: load b:\pden40x port=280 frame=ethernet_802.3 name=pdi280_802.3 bind ipx to pdi280_802.3 net=5 load b:\pden40x port=240 frame=ethernet_802.2 name=pdi240_802.2 bind ipx to pdi240_802.2 net=6 load b:\pden40x port=280 frame=ethernet_802.2 name=pdi280_802.2 bind ipx to pdi280_802.3 net=7 load b:\pden40x port=240 frame=ethernet_802.3 name=pdi240_802.3 bind ipx to pdi240_802.2 net=8 The above port= could just as easily be slot= for Micro Channel or EISA machines. Note: There is a case where the following error will occur when loading the driver. There must be more than one adapter in the system to cause this error message "The hardware configuration conflicts". This is cause by the following load commands: load PDEN40x load PDEN40x slot=3 But if the frame=etherent_802.3 was added to the second line, the load command would function normally.