NWSERVER.TXT Driver File Contents (Ne10100.zip)

***********************************************************
NE10/100 ISA 32-bit NetWare Server Driver Information

Updated February 1997
***********************************************************

Driver Installation
=======================

The NetWare server driver file name is NE100I.LAN and the server
driver installation file name for the NetWare INSTALL.NLM program
is NE100I.LDI.

We recommend that you install the NE100I.LAN Server Driver using
Novell's INSTALL NLM (NetWare Loadable Module (described below). Make
sure the current NLMs are available for the operating system version
you are loading the driver on.

If your system is not Plug and Play compatible, you must run the 
CONFIG program before starting operating system setup of 
the adapter. For more information, type GENERAL.TXT in \GENERAL
or view the Plug and Play Notes section of README - General
Introduction. CONFIG must be run under DOS.

Using NetWare's INSTALL.NLM to Install the Driver
------------------------------------------------------

On a NetWare server that is already installed and operational, use 
the INSTALL.NLM (NetWare Loadable Module) to install new server LAN 
local area network) drivers.  The NetWare INSTALL program copies the
NE100I.LAN driver file from the NE10/100 ISA disk to the
server's SYSTEM directory and updates the server's AUTOEXEC.NCF
file with the necessary driver LOAD and BIND commands to make the
driver operational.

The procedure is listed below:

1. At the NetWare system console prompt, type LOAD INSTALL and press 
the <Enter> key.

2. Follow the INSTALL program's instructions to install and load new
LAN (network) drivers.

3. When presented with a list of drivers that can be installed,
press the <Insert> key to install an unlisted driver.

4. Insert the NE10/100 ISA disk into a floppy disk drive and provide
the path NWSERVER.

5. When prompted by the NetWare INSTALL program, select the driver
parameters and protocols. See the final paragraph of this document
for information about accessing keyword information.

6. Save the parameters and load the driver.

Installing the NE10/100 ISA Driver During NetWare Installation
------------------------------------------------------------------

If you have not yet installed the NetWare Server software on this PC,
you can install the NE10/100 ISA driver during the NetWare Server
installation. The procedures are the same as those above for
installing the NE10/100 driver using NetWare INSTALL, except Step 1 
is omitted (since the NetWare INSTALL program is integrated into 
NetWare installation).

The procedures are:

1. Follow the NetWare installation program's instructions to install
the Server software.

2. At the appropriate point in the installation (according to the
NetWare installation instructions), select the option to install a new
LAN driver.

3. When asked to do so, insert the NE10/100 ISA disk
into a Disk drive. Enter the correct drive letter and path (NWSERVER).

4. When prompted by the NetWare installation program, select driver
parameters. See the final paragraph of this document
for information about accessing keyword information.

Installing the NE10/100 ISA Driver Manually
------------------------------------------------

NOTE:  This procedure requires you to access the server from your
client PC. This means that another adapter must already be set up.
  
1. Copy the driver file (NE100I.LAN) from the NWSERVER directory on
the NE10/100 disk to the server's SYSTEM directory.  For example,
at the DOS prompt on a DOS client workstation, enter

    copy a:\nwserver\ne100i.lan f:\system

2. Edit the server's AUTOEXEC.NCF file (or other server command file
that you are using) to LOAD the driver and BIND one or more protocol
stacks to it. If you add the LOAD and BIND commands to the
AUTOEXEC.NCF file, the NetWare server OS will normally load the driver
each time that the server OS is loaded.  If you add the LOAD and BIND
commands to another command file, you can either execute this other
command file by calling it from the AUTOEXEC.NCF file or by typing its
file name at the NetWare server's system console prompt.


Example 1
---------

load ne100i.lan frame=ethernet_802.2 name=NE100I0_8022
bind ipx to NE100I0_8022 net=70e28022

The example loads the NE100I server driver for the only NE10/100
ISA adapter found in the PC, using Ethernet 802.2 frames.

The NAME string defines an arbitrary but unique tag that is used in
the BIND command line that follows. Also, the NET number (hexadecimal) in
the BIND command is a unique and arbitrary number.

To load all four (4) possible frame types, 4 LOAD commands and
4 BIND commands must be used.

Example 2
---------

load NE100I.lan frame=ethernet_802.3 name=NE100If_8023   serial=044721
bind ipx to NE100If_8023 net=70e38023

Example 2 loads the NE100I server driver for the NE10/100  adapter
that has serial number 044721 (hex), using Ethernet 802.3 frames.
The serial number is required for multiple NE10/100 ISA adapters.
The NAME string defines an arbitrary but unique tag that is used in
the BIND command line that follows. Also, the NET number (hexadecimal)
in the BIND command is a unique and arbitrary number.

Example 3
---------

load NE100I.lan frame=ethernet_802.2 name=NE100I0_8022
bind ipx to NE100I0_8022 net=70e28022
load NE100I.lan frame=ethernet_802.3 name=NE100If_8023
bind ipx to NE100If_8023 net=70e38023
load NE100I.lan frame=ethernet_ii name=NE100If_ii
bind ipx to NE100If_ii net=70e11111
load NE100I.lan frame=ethernet_snap name=NE100I0_snap
bind ipx to NE100I0_snap net=70e555aa

Example 3 loads the NE100I driver four times, using all four
possible different NetWare frame types.  Each frame type is then
bound to the IPX protocol stack.

Using the NE100I.LAN Driver with NetWare 3.1x
=====================================================

The NE100I.LAN driver is a NetWare 4.0 or NetWare 4.10 driver. To use
the driver on a NetWare 3.1x server, you must follow the guidelines in
this section.

Use the LOAD command to load the following programs on the NetWare
server (the first three programs enable the use of new LAN drivers
with NetWare 3.1x).

load LSLENH (for NetWare 3.11 only; not used for NetWare 3.12)
load MSM31X (version 2.50 or higher, dated Nov. 23, 1994, or later)
load ETHERTSM (version 2.55 or higher, dated April 18, 1995, or later)
load NE100I.LAN

You can enter these LOAD commands at the system console, in the 
AUTOEXEC.NCF file, or in another .NCF file.

Important: The MSM31X and ETHERTSM NLMs must be loaded before the
NE100I server driver is loaded; otherwise the wrong versions of MSM
and ETHERTSM may be loaded automatically by NetWare.

Server Driver Custom Statistics
===================================

The NE100I server driver maintains the following custom statistics,
which can be viewed by loading the NetWare MONITOR program and
pressing <PageDown> on the keyboard several times.

    Current Line Speed (Mbps):                 10 or 100
    Duplex Mode (0 = Half, 1 = Full):          0 or 1
    Link State (0=Down, 1=Up, 2=Unknown):      0, 1, or 2
    Receive Symbol Errors (100 Mbps only):     count
    Get RCB Attempts Reject Count:             count
    Early Receive Interrupts Count:            count
    Back-to-back Send Count:                   count
    No Transmit Resources Count:               count

If the driver's MEDIATYPE setting for the NE10/100 ISA adapter is
AUTO , the Current Line Speed, Duplex Mode, and Link State are
updated any time that the driver detects changes in the NE10/100
ISA adapter and its physical network connection.

The custom counter fields are updated once per second by the MONITOR
program.

Receive Symbol Errors apply to 100 Mbps operation only.  They are also
counted in the General Statistics Checksum Errors counter.

If the Get RCB Attempts Reject Count is counting upward quickly, it
probably means that some client station(s) on the network are not
using the correct FRAME type to communicate or that the server does
not have the correct FRAME types bound to the IPX protocol stack.

The Early Receive Interrupts Count gives an indication of how much
early receive packet processing is happening.  This count will remain
at 0 if RXEARLY = OFF (the default). See the Keywords note at the
bottom of this file.

The Back-to-Back Send Count is the number of packets that were queued
to the driver for transmission while the driver was busy.

The No Transmit Resources Count is the number of transmit attempts
that failed because the driver had run out of transmit descriptors.

Driver Message Numbers and Text
===================================

This section lists driver messages by number and text.  It also
explains them and possible remedies.

message   message
number    text
------    -----------------------------------------------------------
50        The adapter cannot be found.

          The NE100I driver has searched the system for an NE10/100
          ISA adapter using Plug and Play methods and
          cannot locate an adapter.  If you have an NE10/100
          ISA adapter installed, it may be defective.

60        Cannot reset the adapter (error = #).

          The adapter has been located but cannot be reset.  The
          reset error code is also displayed.  Call Customer Support.

89        The Node Address override could not be set.

          The driver LOAD command used the NODE=xxxxxxxxxxxx
          parameter, but the NE100I driver could not set the 
          adapter's node address to the new address specified. 
          Call Customer Support.

91       The hardware configuration conflicts.

          The driver located the adapter and tried to register the
          adapter's hardware configuration with the NetWare operating
          system.  However, NetWare indicated that the adapter's
          I/O address range or INT (or IRQ) setting is already in use
          by another device in the system.

          You must reconfigure one or more adapters in the system so
          that there are no system resource conflicts.

100       The configuration option is being ignored.

          This message is displayed if parameter keyword was used and
          its use resulted in a non-fatal error.  Correct the keyword
          entry.

          For example, if you had entered RXEARLY = 4 (or anything 
          other than ON or OFF), this message would be displayed as
          RXEARLY operation affects driver performance but does not
          keep the driver from operating.

101       Terminating due to keyword error(s).

          There were fatal keyword parameter errors that have already
          been displayed on the system console.  Correct all keyword
          errors listed and reload the driver.

110       Multiple adapters found; must specify which one to use.

          The PC has more than one NE10/100 ISA adapter installed
          and you have not specified which adapter to use. If the 
          NE10/100 ISA adapters are in Plug and Play mode in an ISA
          or EISA system (with or without Plug and Play BIOS or
          Configuration Manager), you must use the SERIAL keyword
          to specify the adapter.

111       The adapter initialization failed.

          The driver located the NE10/100 ISA adapter but
          cannot initialize it.  Call Customer Support.

112       Cannot open the adapter.

          The driver cannot make the adapter operational.
          Call Customer Support.

113       Cannot schedule an AES event callback

          The driver cannot obtain a NetWare operating system service
          that it needs to operate.  Call Customer Support.

114       Cannot schedule an Interrupt event callback

          The driver cannot obtain a NetWare operating system service
          that it needs to operate.  Call Customer Support.

115       Link Detected: 10 Mb

          A 10 Mbps active link has been detected on the adapter
          cable.

116       Link Detected: 100 Mb

          A 100 Mbps active link has been detected on the adapter
          cable.

117       Link Detected: 10 Mb Full Duplex

          A 10 Mbps active full duplex link has been detected on the
          adapter cable.

118       Link Detected: 100 Mb Full Duplex

          A 100 Mbps active full duplex link has been detected on the
          adapter cable.

119       Warning! Cable appears to be disconnected

          The adapter cable is disconnected.  Connect the cable and
          the driver will begin operation.

151       Invalid SERIAL parameter

          The SERIAL keyword value is not a hexadecimal number.
          Correct its value and reload the driver.

158       Invalid RXEARLY parameter

          The RXEARLY keyword's value was something besides OFF/ON.
          Correct its value and reload the driver.

159       Error setting the Media Type on the adapter.

          The driver encountered an error when it attempted to change
          the media type being used by the adapter.  If the media
          type is invalid for the adapter, change the MEDIATYPE
          keyword's value. If the media type is valid for the
          adapter, check the adapter's media connections for failure.
          Lastly, you may need to replace the adapter.

160       Invalid MEDIATYPE parameter

          The MEDIATYPE specified is not valid for the adapter.

171       The located adapter address (#) does not match the
          specified PORT address (#).

          An NE10/100 ISA adapter was located but its PORT
          address does not match the PORT address specified in the
          LOAD command.  You do not need to specify the PORT address
          of the adapter in the LOAD command, because the driver can
          locate the adapter(s) automatically.  However, to select
          one adapter when you have multiple adapters installed, you
          must use the SERIAL keyword.

172       The located adapter interrupt (#) does not match the
          specified INT configuration (#).

          An NE10/100 ISA adapter was located but its interrupt
          setting does not match the INT setting specified in
          the LOAD command.  You do not need to specify the INT
          setting of the adapter in the LOAD command.  The driver can
          determine this setting automatically.

(none)    Adapter not assigned necessary resources.

          The adapter does not have any I/O ports assigned or an
          interrupt (IRQ) assigned.  Use the NE10/100 CONFIG
          program to configure the adapter.

(none)    Adapter failed self test.

          The adapter's self-test routines failed.  The adapter may
          be defective.

(none)    No adapter of appropriate type located.

          An NE10/100 ISA adapter could not be located.
          Install the adapter in your PC and use the NE10/100
          CONFIG program to configure the adapter.  If you have
          already installed the NE10/100 ISA adapter, it may be
          defective.  Call Customer Support.

(none)    Adapter placed in an 8-bit slot.

          The adapter is in an 8-bit ISA slot.  It only operates in a
          16-bit ISA or EISA slot.  Move it to a 16-bit slot.

(none)    Media selected not supported on physical layer.

          The MEDIATYPE that has been specified is not supported by
          the adapter.  Specify the correct MEDIATYPE (see the note
          on keywords at the end of thisis file) or do not specify
          MEDIATYPE and let the driver automatically use the connected
          media type.

(none)    Interrupt level specified does not match hardware settings.

          The INTERRUPT setting specified does not match the
          adapter's interrupt setting.  You do not need to specify
          the setting because the driver can automatically
          determine and use the correct interrupt.


(none)    Port=h  Int=h  Slot=d  Node=hhhhhhhhhhhh

          The driver displays this adapter configuration message upon
          successful driver loading and initialization. 'd'
          represents a decimal number.  'h' represents one or more
          hexadecimal numerals.


Note: To view the available keywords supported by the Microdyne
NE10/100 ISA Adapter, go back to the main menu of README and select
Keywords or type the KEYWORDS.TXT file in the GENERAL directory.
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.51