
	      WINDOWS NT 3.5 DRIVER INSTALLATION INSTRUCTIONS
			    Version v1.57

The \WINNT directory contains the following files:

README.TXT   - This file.

The \WINNT subdirectory contains the following subdirectories:

\ALPHA       - Driver and installation files for Windows NT running
	       on Alpha systems.
\INTEL       - Driver and installation files for Windows NT running
	       on Intel systems.
\MIPS        - Driver and installation files for Windows NT running
	       on MIPS systems.  (NOT SUPPORTED IN WINDOWS NT 3.5)
\POWERPC     - Driver and installation files for Windows NT running
	       on PowerPC systems.  (NOT SUPPORTED IN WINDOWS NT 3.5)


			***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 and Intel platforms are 
supported.  The Windows NT device drivers support the final release
(Build 807) of Windows NT 3.5 Workstation and Windows NT 3.5 Server.
Windows NT 3.51 (Build 1057) includes the DEC FDDIcontroller/EISA and 
DEC FDDIcontroller/PCI drivers with the operating system.

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, the final
release (Build 807) of Windows NT 3.5 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.

"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.

"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     Registry configuration data could not be opened for this adapter.
	 The Registry is possibly corrupted.

0x02     Could not allocate 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" keyword
	 if increased from default.

0x03     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.  Also verify
	 that PCI bus number and card instance are correct.  DEFPA.SYS
	 driver only.

0x04     Too many DEC FDDIcontrollers installed.  DEFEA.SYS driver supports
	 up to four (4) DEC FDDIcontroller/EISA controllers per system.
	 DEFPA.SYS driver supports up to eight (8) DEC FDDIcontroller/PCI 
	 controllers per system.

0x05     Could not read factory MAC address (MLA) from adapter.

0x06     Receive buffer count (RcvBuffCnt) keyword missing or incorrect 
	 in Registry.

0x07     Transmit buffer count (XmtBuffCnt) keyword missing or incorrect 
	 in Registry.

0x08     Burst size (BurstSize) keyword missing or incorrect in Registry.

0x09     FDDI Full Duplex (FullDuplexEnable) keyword missing or incorrect 
	 in Registry.

0x0A     Requested Target Token Rotation Time (RequestedTTRT) keyword 
	 missing or incorrect in Registry.

0x0B     EISA slot (SlotNumber) keyword missing or incorrect in Registry.  
	 DEFEA.SYS driver only.

0x0C     Unsupported 0K host memory option selected during EISA configuration
	 of adapter.  DEFEA.SYS driver supports only 1K or larger memory
	 options.

0x0D     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.

0x0E     PCI adapter not installed in Bus Master slot or Bus Mastering not
	 enabled.  DEFPA.SYS driver only.

0x0F     Memory 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.

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     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.

0x12     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.

0x13     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.

0x14     The adapter transitioned to the HALT state.  Run diagnostics 
	 on adapter.  If the diagnostics fail or if error occurs regularly, 
	 have the adapter replaced.

0x15     The receive FMC had a descriptor or other kind of error.  If error
	 occurs regularly, have the adapter replaced.

0x16     The adapter had a miscellaneous descriptor error.  If error
	 occurs regularly, have the adapter replaced.

0x17     The transmit packet flush operation could not be completed.  If
	 error occurs regularly, have the adapter replaced.

0x18     The adapter could not be reset.  The adapter may have a hardware 
	 fault.

0x19     The adapter node address override could not be set.  

0x1A     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" keyword if increased from default.

0x1B     Could not allocate normal (regular) system memory.  Verify that
	 system has enough memory to run Windows NT.

0x1C     Could not register adapter memory mapped space with operating
	 system.  If DEFEA.SYS driver, verify that an exclusive (not shared)
	 area of host memory was configured for this adapter during EISA
	 configuration.  A 1K memory block is recommended for this adapter.

	 If DEFPA.SYS driver, memory address is normally set by system
	 PCI BIOS and is not configurable.  However, it's possible that
	 the same PCI FDDI adapter is being registered twice.  Verify
	 that the set of PCI bus number and card instance values are
	 unique for each FDDI adapter.

0x1D     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.  However, it's possible that
	 the same PCI FDDI adapter is being registered twice.  Verify
	 that the set of PCI bus number and card instance values are
	 unique for each adapter.

0x1E     Driver attempted to change adapter state, but failed.  This may 
	 indicate a reset failure or hardware problem.  Run diagnostics on 
	 adapter.  If the diagnostics fail or if error occurs regularly, 
	 have the adapter replaced.

0x1F     Maximum frame size (MaxFrameSize) keyword is incorrect in Registry.

0x20     Static transmit buffer count (StaticXmtBuffCnt) keyword is
	 incorrect in Registry.

0x21     Bus number (BusNumber) keyword is missing or incorrect in Registry.

0x22     PCI card instance (CardInstance) keyword is missing or incorrect
	 in Registry.  DEFPA.SYS driver only.

