NW312.TXT Driver File Contents (dec_nic1.zip)

   Driver Installation - for NetWare Server 3.12
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


   (1) Introduction:
   ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

   This document describes the procedure to install the NetWare v3.12
   server driver for 10/100 Base-TX PCI Bus Ethernet Adapter.


   (2) Location of Driver:
   ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
                                \NWSERVER\4.X\DC21X4.LAN


   (3) Installation Procedure:
   ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

      Before you start with the installation process, make sure that
      the Novell NetWare 386 v3.12 server is properly installed.
      Similarly, your adapter should also be properly installed in your
      server.

      1. Insert the Driver Diskette into drive A and check the
         contents of subdirectory  \NWSERVER\3.1X, It should contain the
         following files :

         LSWAP.EXE    ÄÄÄ  the file to update the loader segment in
                           the SERVER.EXE file
         LOADER.EXE   ÄÄÄ  the loader file
         NBI31X.NLM   ÄÄÄ  Novell NBI needed to run the ODI server driver
                           with NetWare 3.1x
         MSM31X.NLM   ÄÄÄ  Novell MSM needed to run the ODI server driver
                           with NetWare 3.1x
         ETHERTSM.NLM ÄÄÄ  Novell TSM needed to run the ODI server driver

         And the ODI server driver file is placed under the
         \NWSERVER\4.X directory :

         DC21X4.LAN   ÄÄÄ  Novell NetWare 3.1x ODI server driver

      2. If you are first time to install the driver, please proceeds
         as below. Otherwise, go to step 3, please.

         Assume the C:\SERVER.312 directory is the server directory
         where the SERVER.EXE file was installed.

         Copy the following files to the C:\SERVER.312 directory.
         These files must be provided by the driver diskette.

         LSWAP.EXE
         LOADER.EXE

         And run the LSWAP.EXE file to update the loader segment in
         the SERVER.EXE file as below :

         LSWAP.EXE C:\SERVER.312\LOADER.EXE C:\SERVER.312\SERVER.EXE

      3. Copy the following files to the SYS:\SYSTEM directory on
         the NetWare server. These files must be provided by the
         driver diskette.

         NBI31X.NLM
         MSM31X.NLM
         ETHERTSM.NLM

      4. If you can log into the server as a supervisor , copy DC21X4.LAN
         relative files from the Driver Diskette subdirectory
         A:\NWSERVER\4.X into the NetWare 386 subdirectory SYSTEM of your
         server. (If some files exists, rename the existing files in the
         SYSTEM subdirectory).

      5. When the NetWare 386 prompt appears (indicated by a colon),
         load these following modules before load the server driver:

         : LOAD NBI31X    <Enter>
         : LOAD MSM31X    <Enter>
         : LOAD ETHERTSM  <Enter>

      6. And load the server driver, simply type:

         : LOAD DC21X4 <Enter>

         or, you can directly load file from the driver diskette:

         : LOAD A:\NWSERVER\3.1X\DC21X4 <Enter>

      7. Bind IPX to the adapter driver. At the NetWare server prompt
         ,type:

         :BIND IPX TO DC21X4 <Enter>

      8. After pressing <Enter> the computer prompts you for the Network
         Number. For details on how to assign this number, please consult
         your NetWare 386 Installation Manual.

      9. Add the load and bind statements you require to the server's
         AUTOEXEC.NCF file so that the LAN driver will load automatically
         each time the server starts up.


   (4) Notes:
   ÄÄÄÄÄÄÄÄÄÄ
      1. If the adapter not work fine after installation, try to adjust
         TransmitThreshold and ReceiveBuffers.

      2. Installing One LAN adapter with Multiple Frame Types:
         When  binding multiple frame types to one adapter, enter a LOAD
         and BIND statement for each frame type. Each LOAD statement will
         use a different network number is required on the bind statement.
         You need  to supply  a name on each load line in order to avoid
         being  prompted  for which  board to bind IPX to. If you do not
         have the name option in the AUTOEXEC.NCF , it will not  execute
         completely without user intervention.  Example:

           LOAD DC21X4 FRAME=ETHERNET_802.3 NAME=IEE8023
           BIND IPX TO IEE8023 NET=11111
           LOAD DC21X4 FRAME=ETHERNET_802.2 NAME=IEE8022
           BIND IPX TO LAN8022 NET=22222

     If problems occur during the binding process, your  screen will prompt
     you with error  messages.  Please refer to your NetWare 386 manual for
     details on these messages.


   (5). Parameters:
   ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

      The following parameters belong on the server's command line, or in
      the load line inside the AUTOEXEC.NCF. The general way of using these
      parameters is:

            LOAD <driver name> <PARAMETER NAME>... <PARAMETER NAME[=VALUE]>

         Example:

            LOAD <driver name> TURBO SLOT=16 FRAME=Ethernet_802.2

         Driver specific parameters list  (as for NetWare standard parameters,
         please see the NetWare user's manual):

                SLOT            slot number that corresponds to the physical
                                expansion slot where the board or other
                                device is installed.

           (**) AUTOSENSE       auto-sense the line speed 10Mbps or 100Mbps

           (*)  AUTODETECT      enable auto-detection of media type when
                                driver is loading. Note that this ONLY!
                                works at initialization time, i.e. when
                                the driver first loads for a specific
                                network card.

                TP              selects TP  port

                BNC             selects BNC port

                AUI             selects AUI port

                T4              selects 100 Base-T4 interface
                                (in conjunction with Line_Speed 100)

                TP_NO_LINK_TEST selects twisted pair connection, but disables
                                the LINK test for specific HUBs that do not
                                support LINK.

                TP_FULL_DUPLEX  selects twisted pair connection to work in
                                full duplex mode.
             
                NT              run under NT requester

                OS2             run in NetWare for OS/2

                UnixWare        run in UnixWare

                Client32Win     run in Client32 environment for windows

                Client32Win95   run in Client32 environment for Windows 95

                Client32DOS     run in Client32 environment for DOS

                TURBO           Fixes the problem of multiple transmit
                                underflows and receive overflows (i.e. lose of
                                packets) in systems that use certain PCI
                                chipsets.

           (**) SNOOZE          Change Chip's Power Management to
                                Power-Saving mode

           (**) LINE_SPEED      selects line speed between 10MPBs and 100MBPs
                                on network cards based on DC21140.

                                Format: LINE_SPEED=<value>

                                Allowed values are: 10,100

           (**) GENERAL_PURPOSE_CONTROL user override of the control value in
                                        the GENERAL_PURPOSE register in DC21140
                                        Normally, this value should not be
                                        changed.

                        Format: GENERAL_PURPOSE_CONTROL=<Hexadecimal Value>

                        Allowed values: in the range 1FF-0 hex.

           (**) GENERAL_PURPOSE_DATA    user override of the data value in the
                                        GENERAL_PURPOSE register in DC21140
                                        Normally, this value should not be
                                        changed.

                        Format: GENERAL_PURPOSE_DATA=<Hexadecimal Value>

                        Allowed values: in the range 1FF-0 hex.

                RX_BUFFERS  Allows the user to select the amount of receive
                            buffers to work with.
                            More buffers means larger driver resident in
                            memory but with higher performance.

                            Format: RX_BUFFERS=<hex value>
                            Allowed values: 2-F hex

                TX_THRESHOLD Setup the threshold value of transmit FIFO.

                            Format: TX_THRESHOLD=<decimal value>
                            Allowed values:
                                0 - 72 bytes
                                1 - 96 bytes
                                2 - 128 bytes
                                3 - 160 bytes
                                4 - 160 bytes in Tulip and Full packet in
                                    FasterNet 100Mbps.

         Notes :
           (*)   Those keywords affect ONLY DC21040/DC21041 based network
                   interface cards.

           (**)  Those keywords affect ONLY DC21140 based network
                   interface cards.


      (6). Driver Error Messages:
      ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

      Some messages also have a numerical code printed with them. The codes
      are given here to the left of the message (when applicable).

         50  - No PCI board found in machine!
               Driver could not detect a supported NIC.
         53  - Board is disabled for no apparent reason!
               EISA board is not enabled. Normally BIOS & ECU should enable
               the board.
         73  - Unable to allocate memory
               Driver failed to allocate needed memory from the OS
               (receive/transmit descriptors or needed transmit buffers).
         200 - Timeout when initializing DecChip 21X4 with setup packet!
               This happens mainly when the PCI slot does not support DMA
               accordingly.
               Make sure the BIOS setup or motherboard switches are set to
               enable DMA or Bus Master operation of this slot.
         209 - Do not support DC21041 in DC21040 mode
               The DC21041 MODE_SELECT pin is connected to VSS making it work
               in MODE_0, i.e. as a virtual DC21040 in all respects. The
               driver does NOT support this mode.
         210 - Driver failed to locate PCI bus!
               The machine is not identified as PCI (to support PCI NICs).
         211 - Failed to locate DecChip 21X4 on board
               Failed to identify a DecChip 21x4 signature in an EISA board.
         212 - Unsupported DC21140 chip version
               The DC21X4 drivers do not support DC21140 rev 1.0 chip.
               If you receive this message, please make sure you have an
               updated rev of your NIC.
         213 - Unexpected OS behavior. Driver supports 3.11 and later
               This identifies a fail of assumption regarding the OS behavior.
         214 - Read bad mask value from EISA configuration
               An assumption regarding data read from EISA ECU (for EISA based
               NICs) failed. This might happen because of incorrect ECU file
               for that NIC.
         215 - Read bad port size value from EISA configuration
               An assumption regarding data read from EISA ECU (for EISA based
               NICs) failed. This might happen because of incorrect ECU file
               for that NIC.
         216 - Failed to read EISA configuration
               An assumption regarding data read from EISA ECU (for EISA based
               NICs) failed. This might happen because of incorrect ECU file
               for that NIC.
         217 - Failed to find PCI BIOS
               The machine is not identified as PCI (to support PCI NICs).
               This error is generated when driver is directed to load PCI NIC
               (using the 'slot=xx' keyword, and slot value is a PCI number).
               If the driver is loaded without specifying slot number, the
               driver checks for PCI support, and in this case will
               generate another error message (please refer to error number
               210 - Driver failed to locate either PCI bus).
         218 - Bad PCI BIOS status
               PCI BIOS returned a fail status in one of the calls. Please
               check the BIOS version and BIOS correctness using an external
               utility.
         219 - Bad PCI BIOS Register err
               PCI BIOS returned a fail status in one of the calls. Please
               check the BIOS version and BIOS correctness using an external
               utility.
         220 - PCI BIOS failed to initialize DecChip 21040 CBIO reg!
               PCI BIOS has initialized a DWORD register in the NIC's
               configuration space (at offset 10Hex) with illegal value.
               Please check the BIOS version and BIOS correctness using
               an external utility. Also verify that your BIOS setup
               enables I/O and initialize correctly the device in this
               PCI slot.
         221 - PCI board disappeared...
               PCI BIOS is not consistent with returned values per this NIC.
         222 - Unsupported TSM version (need x.yz and above)!
               This driver supports EtherTSM.NLM of version as specified and
               higher.
         223 - DC21X4 Tx babbles on slot x. Driver halted this slot's NIC.
               This is a watchdog put in the driver to make sure the transmit
               does not babble on the cable.
         224 - DC21X4 detected PCI bus error on slot x (bus error bits = xh).
               Driver halted this slot NIC due to that identified error.
         225 - PCI BIOS assigned DecChip 21040 an illegal interrupt number
               PCI BIOS has initialized a byte register in the NIC's
               configuration space (at offset 3CHex) with illegal value. Please
               check the BIOS version and BIOS correctness using an external
               utility. Also verify that your BIOS setup enables interrupt,
               assigns a reasonable interrupt value and initialize correctly
               the device in this PCI slot.
         226 - Could not handle Turbo switch successfully
               Failed to operate the 'Turbo' mechanism from one of the
               following reasons:
                  - Unknown chipset on the motherboard
                  - PCI BIOS returned a fail status in one of the calls
                          involved with operating this mechanism.
         227 - Internal CRC table corrupted
               Driver found an error in internal CRC table.
         228 - Could not handle chipset bug workaround successfully
               Failed to operate chipset bug workaround because PCI BIOS
               returned a fail status in one of the calls involved with
               operating this mechanism.
         229 - This machine Host to PCI bridge has a known bug. Driver limits
               DC21X4 bursts as a workaround.
         230 - This machine Host to PCI bridge has a known bug when
               using cache in WB mode which may cause data corruption or
               system hang. Please change the cache mode to WT (Write Through)
               as a workaround.

               This machine Host to PCI bridge has a known bug that might
               violate system integrity. Driver cannot be responsible for
               outcome, therefor it will not load in this case. Putting the
               machine in write-through mode (cache) makes the system safe
               to work with. Driver will load in that case.
         240 - Unable to locate or read the Ethernet ROM address on board!
               This might happen due to bad data stored in the IEEE serial
               ROM, an error when reading it, or a wrong data structure
               burnt into the ROM.
         244 - Serial ROM - Read failed
               Driver failed to read the IEEE serial flash ROM due to hardware
               handshake failure. Make sure the IEEE flash ROM on your NIC
               is operational using external utility.
         245 - The selected media is unsupported
               The selected media is unsupported by the device.
         246 - Cannot initialize the network card (CreateNIC failed)
               The CreateNIC routine failed, and we cannot initialize the nic
         247 - This is an internal warning that warns against the use of
               WriteCSR6 before CreateNIC was called for the first time
         248 - The OPTI chipset might cause excessive tx underflow and
               cause network nodes to perform poorly or disconnect from
               the server. The driver switchs to STORE and FORWARD mode
               to overcome this at the cost of performance.

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: ftp, load: 1.27