WINDOWS NT 3.5/3.51/4.0 DRIVER INSTALLATION INSTRUCTIONS Version v1.82 The \WINNT directory contains the following files: README.TXT - This file. DEFDDI.HL_ - Help file for Digital FDDI EISA and PCI controllers The \WINNT subdirectory contains the following subdirectories: \ALPHA35 - Driver and installation files for Windows NT 3.5 running on Alpha systems. \ALPHA351 - Driver and installation files for Windows NT 3.51 or later, running on Alpha systems. \INTEL35 - Driver and installation files for Windows NT 3.5 running on Intel systems. \INTEL351 - Driver and installation files for Windows NT 3.51 or later, running on Intel systems. \MIPS351 - Driver and installation files for Windows NT 3.51 or later, running on MIPS systems. \PPC351 - Driver and installation files for Windows NT 3.51 or later, running on PowerPC systems. ***TRADEMARKS*** DEC, Digital, and DECpc are trademarks of Digital Equipment Corporation. Intel is a registered trademark of Intel Corporation. Microsoft, MS, and MS-DOS are registered trademarks and Windows and Windows NT are trademarks of Microsoft Corporation. MIPS is a registered trademark of MIPS Computer Systems, Incorporated. PowerPC is a trademark of International Business Machines Corp. KIT CONTENTS: This distribution kit contains the Windows NT device drivers for the DEC FDDIcontroller/PCI adapter. The Alpha, Intel, MIPS, and PowerPC platforms are supported. The Windows NT device drivers support Windows NT 3.5 and above. INSTALLATION: For general installation instructions, refer to the "Windows NT System Guide". The chapter on the "Control Panel" contains a section that describes the installation of network cards in detail. When prompted for the kit location during installation, press RETURN. The A:\OEMSETNT.INF file will automatically determine what platform is being installed and copy over the appropriate driver. UPDATING FROM PREVIOUS VERSIONS: Normally, driver updates are performed using the "Update" button under the Network Settings option in the Control Panel. However, Windows NT only searches for the file "OEMSETUP.INF" during "Update", while selecting "Add Adapter" searches for both "OEMSETUP.INF" and "OEMSETNT.INF" files. Driver updates can be performed by removing the adapter(s), rebooting, then installing the new driver, then rebooting. Since the process of removing and re-adding an adapter requires multiple reboots of the system, the "Update" button is normally preferred to the above Remove/Add procedure. This option can be used by renaming the "OEMSETNT.INF" file. The A:\OEMSETUP.INF file that is included in the DOS Distribution Diskette (Disk 1) is used by Windows for Workgroups 3.11 to install the supported drivers. By first saving this file, then renaming the Windows NT A:\OEMSETNT.INF installation script to "OEMSETUP.INF", the "Update" button can be used. CUSTOMIZATION: For most configurations, no customization of the driver should be necessary. However, a number of parameters are available for users to change by selecting "Configure" after highlighting the desired DEC FDDIcontroller under "Network Settings". "Bus Number" sets the PCI bus number in which the DEC FDDIcontroller/PCI is installed. In most system configurations, the PCI bus number is 0. If your system has multiple PCI buses, or if the PCI adapter is installed in a bus number other than 0, this parameter should be changed. *** Windows NT 3.5 drivers only. *** "Card Instance" sets the instance of the DEC FDDIcontroller/PCI adapter on the specific PCI bus. For single adapter installations, this parameter should always be set to 1. If installing multiple DEC FDDIcontroller/PCI adapters, this parameter should be set to a unique incrementing integer starting at 1. If installing adapters across multiple PCI buses, care should be taken in assigning the card instance and bus number parameters. *** Windows NT 3.5 drivers only. *** "Receive Buffers" affects the maximum number of host receive buffers that can be used by the adapter at a time. Although this number is small, increasing it is not likely to increase performance because the adapter itself provides a large amount of receive buffering (~1MByte). "Transmit Buffers" affects the maximum number of map registers that can be allocated by the adapter. During packet transmission, an NDIS_PACKET may be comprised of several NDIS_BUFFERs where each NDIS_BUFFER requires a map register for physical DMA (Direct Memory Access). The default of 32 is within NDIS 3.0 specification, but the adapter may be able to handle more outstanding transmit packets if this value is increased. However, map registers are a limited system resource and arbitrarily increasing this parameter may make this adapter or other adapters in the system unusable. Arbitrarily lowering this parameter may impact driver performance or cause undesired behavior. CARE SHOULD BE TAKEN BEFORE MODIFYING THIS PARAMETER! "Requested TTRT (ms)" affects the MACTReq SMT MIB object. FDDI selects the target token rotation time during the claim process (eg. when an FDDI node has entered or left the ring). During this time, each FDDI node offers its requested TTRT (MACTReq MIB object) and the lowest bidder wins. Normally this parameter does NOT need to be modified from the default of 8ms. However, some installations may set this value arbitrarily high on end node stations so that the requested TTRT can be more easily managed from an FDDI concentrator or switch. For this reason, the range of 4-165ms. is supported with a default of 8. This parameter should only be modified by experienced FDDI network managers. "Full Duplex Enable" affects the eFDXEnable MIB value. Digital FDDI adapters are in Full-Duplex (FDX) mode when the mode setting is enabled and the adapter is connected point-point with another similarly enabled FDDI adapter or the Digital GIGAswitch FDDI switch. FDX mode takes advantage of the point-point connection by removing the FDDI token and allowing simultaneous receive and transmit of packets. FDX mode will help reduce latency and may increase network throughput if the system is nearing the standard FDDI maximum throughput. INTERPRETING EVENT LOG ENTRIES: Note: During runtime operation, the NDIS wrapper enables a "watchdog" timer which polls the driver on a regular basis to verify that it is operational. Should the driver return status indicating that it is not, the operating system will reset the driver. If the driver reset is successful, it returns to normal operation. Otherwise, the driver is halted. This process is automatic and does not require user intervention. However, should the system performance become sporadic with constant driver event logger entries being added, the user should verify that the driver is not being constantly reset. If it is, shutdown the machine and run diagnostics on the adapter. When the driver detects errors, it may write entries into the event logger. To interpret the error code, examine the entry that was written by the driver and read the last longword that is contained in the entry. Unless otherwise stated, the following error codes apply to both DEC FDDIcontroller/EISA (DEFEA.SYS) and DEC FDDIcontroller/PCI (DEFPA.SYS) drivers. The following table describes the interpretation of the longword: 0x00 There is no specific information detailing the error. 0x01 No DEC FDDIcontroller/PCI controller found in system, or no controller found for this Registry entry. Verify that number of controllers installed matches the number configured. DEFPA.SYS driver only. 0x02 EISA slot (SlotNumber) parameter missing or incorrect in Registry. DEFEA.SYS driver only. 0x10 I/O space not enabled in PCI Configuration Table. This can be caused by not having PCI slot enabled during PCI system configuration. DEFPA.SYS driver only. 0x11 Could not register adapter I/O mapped space with operating system. If DEFEA.SYS driver, I/O port addresses are based on EISA physical slot numbers and normally cannot conflict. If DEFPA.SYS driver, I/O address is normally set by system PCI BIOS and is not configurable. 0x12 Interrupt level (IRQ) not set or invalid in PCI Configuration Table for this adapter. If system allows user-configuration of PCI slots verify that a proper IRQ value has been set. DEFPA.SYS driver only. 0x13 Could not register interrupt. FDDI drivers support shared interrupts, so interrupt registration failure often means that interrupt is already registered to another driver that doesn't support shared interrupts. Try changing IRQ. 0x20 Could not allocate normal (regular) system memory. Verify that system has enough memory to run Windows NT. 0x21 Could not allocate sufficient shared memory. Verify that system has enough memory to run Windows NT. If running Windows NT 3.5, install Service Pack 2 (SP2) or greater. Reduce "Receive Buffers" and "Static Transmit Buffer Count" parameters if increased from default. 0x22 Could not allocate map registers needed for proper transmit packet operation. Verify that system has enough memory to run Windows NT. If running Windows NT 3.5, install Service Pack 2 (SP2) or greater. Reduce "Transmit Buffers" parameter if increased from default. 0x30 Could not uninitialize or reset adapter. Try power-cycling system. If this doesn't help, run DOS-based diagnostics included with adapter. If problem persists, have adapter replaced. 0x31 Could not transition to link (un)available state. 0x32 Could not set adapter burst size. 0x33 Could not set adapter consumer block address. 0x34 Could not set adapter descriptor block address. 0x35 DMA commands failed during adapter initialization. Verify that adapter is installed in Bus Mastering slot. 0x36 Could not set content addressable memory (CAM) block. 0x37 Could not set adapter filters. 0x38 Could not read factory MAC address (MLA) from adapter. 0x40 The adapter indicated a Non-Existent Memory (NXM) error. Run diagnostics on adapter. If the diagnostics fail or if error occurs regularly, have the adapter replaced. 0x41 The adapter indicated a packet memory parity error. Run diagnostics on adapter. If the diagnostics fail or if error occurs regularly, have the adapter replaced. 0x42 The adapter indicated a host bus parity error. Run diagnostics on adapter. If the diagnostics fail or if error occurs regularly, have the adapter replaced. 0x43 The adapter transitioned to the HALT state. Run diagnostics on adapter. If the diagnostics fail or if error occurs regularly, have the adapter replaced. 0x50 Registry configuration data could not be opened for this adapter. The Registry is possibly corrupted. 0x51 PCI slot number (SlotNumber) parameter is missing or incorrect in Registry. DEFPA.SYS Windows NT 3.51 or later driver only. 0x52 PCI card instance (CardInstance) parameter is missing or incorrect in Registry. DEFPA.SYS Windows NT 3.5 driver only. 0x60 Receive buffer count (RcvBuffCnt) parameter missing or incorrect in Registry. 0x61 Transmit buffer count (XmtBuffCnt) parameter missing or incorrect in Registry. 0x62 Burst size (BurstSize) parameter missing or incorrect in Registry. 0x63 FDDI Full Duplex (FullDuplexEnable) parameter missing or incorrect in Registry. 0x64 Requested Target Token Rotation Time (RequestedTTRT) parameter missing or incorrect in Registry. 0x65 Maximum frame size (MaxFrameSize) parameter is incorrect in Registry. 0x66 Static transmit buffer count (StaticXmtBuffCnt) parameter is incorrect in Registry.