README.TXT Driver File Contents (dfo64.exe)

  Readme for Adaptec DuraLAN NIC LAN and Failover Drivers
  Netware 4.xx
  Last Updated 09/03/98
  =====================================================================

  For the latest drivers, see 
  http://www.adaptec.com/support/overview/networking.html
  
  Required Support Packs
  ======================

      -   For Netware 4.11 servers, install Support Pack 5 before
          installing the Adaptec drivers.  The Support Pack can be 
          found on Novell's Web Site http://support.novell.com.

      -   Install the patch required for ODI 3.31 specification support
          (ODI 3.31 patch is included in Support Pack 5 for
          Netware 4.11).

  NetWare O/S Support
  =================
      -   NetWare 3.x and NetWare SFT-III are not
          supported.

  NetWare Client32 Support
  ====================
      -   NetWare Client32 driver does not support Client32 for
          Windows 3.1x, Windows 95 and Windows NT.

      -   NetWare Client32 for DOS is supported, include "iomap=1"
          on the LOAD line, otherwise a Page Fault may result when the
          driver is loaded. Also you will need to install the patch 
          required for ODI 3.31 specification support.

      -   To ensure that connections remain active it is recommended 
          that the NT registry be updated.  The RETRY COUNT should be 
          changed from 16 (default) to 255.

      -   The driver used to support Client32 for Dos is located on the
          NetWare diskette; A:\NWSERVER\ADPTSF.LAN.

  Hotplug Support
  ===============

      -   The Duralink 4.1 driver does not support Hotplug 
          functionality. 

  64-bit Compatibility & Support
  ==============================

      -   Due to the limited availability of 64-bit servers the DuraLAN
          network adapters and Novell drivers have not been tested on
          all 64-bit systems. As other OEM vendors release new 64-bit
          server platforms, Adaptec will test the DuraLAN &
          Duralink products.  These driver updates will be released via
          our Adaptec Web site.

  Duralink Failover Support
  =========================

      -   During installation of multiple DuraLAN adapters in a NetWare
          Server, you must configure each port for each Failover pair
          you have installed. If you exit the Duralink Failover
          configuration utility "FOSETSF" without configuring each pair
          of ports, you will need to re-enter protocol information
          regarding those Failover pairs.

  Configuration Issues
  ====================

       -   Connection types

           When fixed connection type is used, and there is a mismatch
           between the speed on the switch/hub port and NIC port,
           there is a problem in link detection even after the
           mismatch is corrected. This results in the Link Status
           for the mismatched port to be marked active even if the
           switch indicates the link is down. In addition, link state
           changes are ignored (e.g. removing a mismatched speed port's
           cable will not cause the port to failover to a backup port).

           To avoid this problem, use AutoDetect connection
           type or correctly configure the port and switch/hub speeds
           and reboot the system with the NIC(s).

  Server Compatibility Issues
  ===========================

      -   Acer Power P6-200: Because of the motherboard in the system
          not supporting INT B, the 2nd port of a ANA-62022 does not
          work properly.  None of the interrupts asserted by the 2nd
          port (which uses INT B) are propagated to the operating 
          system. As a result, 2nd port will not work in a standalone 
          mode and functionality will not work with 2nd port as a 
          backup port.  There is no work around for the motherboard 
          bug on this system.

      -   Intel 450GX PCI Host Bridge Chip Incompatibility with
          ANA-6x022/6x044:

          ANA-6x022/6x044 boards will cause a system hang under heavy
          network traffic with Pentium-Pro SMP systems using the Intel
          450GX PCI Host Bridge chip (PCI Device ID 0x84C4). This is
          due to an incompatibility issue between the Intel bridge and
          the DEC bridge on the multiport cards. Single port cards,
          ANA-6x011, work fine. Contact Adaptec technical support for
          details.

          Systems that have been identified by Adaptec internal testing 
          with the 450GX (Please refer to Intel's errata list for 
          details).

          * Intel "Alder"
          * Dell 6100
          * IBM NetFinity 7000
          * Compaq Proliant 6000
          * Compaq 5000
          * HP Netserver LXe
          * Compaq Proliant 6500

      -   Compaq Proliant 2500:  When an ANA-62022 is installed on 
          bus 1 the server can display the message:
           "Break at F109C482 because of -- Non-maskable interrupt
            (NMI)..."

          Also booting up the system with a ANA-62022 in bus 1 gets a
          POST warning message.  The ANA-62022 works fine in bus 0 on
          this system.

      -   Dell Precision Workstation 410MT:  When an ANA-62022 is
          installed in bus 0 or bus 1 the driver can be loaded without
          any error messages being displayed.  However, a NT client or
          DOS client cannot connect or ping the server.  The ANA-62022
          is not compatible with this system and there is no workaround.

      -   Dell Poweredge XL:  This system is incompatible with the
          ANA-62011 board but is compatible with the ANA-62022 or
          ANA-62044 boards.

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web1, load: 1.69