MANUAL.TXT Driver File Contents (ne55001.zip)



ABOUT THIS MANUAL.TXT

for the Microdyne NE2500 and NE5500 Series
of Network Interface boards for Ethernet



This document supplements the reference and installation 
instructions provided on the quick installation card you received 
with this product. The subsequent table of contents shows the 
section headings for the information in this Readme file.

If you want to print this file, use a non proportional font (such 
as Courier 12) for the best results.


The information contained in this document is subject to change 
without notice. Microdyne makes no warranty of any kind with 
regard to this material including, but not limited to, the 
implied warranties of merchant ability and fitness for a 
particular purpose. Microdyne shall not be liable for errors 
contained herein or for incidental or consequential damages in 
connection with the furnishing, performance, or use of this 
material.

Copyright 1995 by Microdyne.
All rights reserved.

This document contains information which is protected by 
copyright. All rights reserved. No part of this document may be 
photocopied, reproduced, or translated to another language 
without the prior written consent of Microdyne.




















MICRODYNE








The following are trademarks of Microdyne and may be used to 
identify Microdyne products: NE2500, NE2500T, NE2500plus, 
NE2500plusT, NE5500, and NE5500plus.

AMD, TPEX, PCnet are registered trademarks of AMD, Inc..

Ethernet is a registered trademark of Xerox Corp.

Novell and Netware are registered trademarks of Novell, Inc.

UnixWare is a trademark of UNIX System Laboratories, Inc., a 
wholly-owned subsidiary of Novell, Inc.

PC-NFS and Solaris are trademarks of Sun Microsystems, Inc.

LAN Server and IBM are registered trademarks of International 
Business Machines Corp.

Microsoft, LAN Manager, Windows for Workgroups, and Windows NT 
Windows 95 are registered trademarks of Microsoft.

UNIX is a registered trademark of AT&T Technologies, Inc.

SCO is a registered trademark of Santa Cruz Operation, Inc.

Artisoft and LANtastic are registered trademarks of Artisoft, 
Inc.

Digital and PATHWORKS are registered trademarks of Digital 
Equipment Corporation.

Intel is a registered trademark of Intel Corporation.

Other product names used in this publication are for 
identification purposes only and may be trademarks of their 
respective companies.












=================
Table Of Contents
=================

Product Summary

Installing The Board

Running Jumpstart
	Implementation
	Configuration
		NE2500 Series Adapter Card
		NE5500 Series Adapter Card
		Driver Installation

Installing Novell NetWare ODI Drivers
	Novell NetWare DOS ODI Client
		Driver Installation Using Jumpstart
		Driver Installation From The Command Line Prompt
			Installing NETX
			Installing VLMs
	Novell NetWare OS/2 ODI Client
	Novell NetWare Server 3.1x
	Novell NetWare Server 4.x

Installing The NDIS 2.01 Driver
	Driver Installation Using Jumpstart
	Microsoft LAN Manager 2.x
		Driver Installation Using Microsoft LAN Manager Setup
	Microsoft Windows For Workgroups 3.11
	IBM LAN Server
		Driver Installation for IBM Extended Services 1.0
	Sun PC-NFS
	Artisoft LANtastic

Installing The NDIS 3.0 Driver
	Microsoft Windows NT 3.1, 3.5, 3.51
	Microsoft Windows For Workgroups 3.11
	Microsoft Windows 95

Installing The Packet Driver
	Driver Installation Using Jumpstart
	Driver Installation From The Command Line Prompt


Appendix A	Software Keywords 
			Common Keywords
			Card Specific Keywords
			Novell NetWare Operating System Keywords
			NDIS 2.01 Driver Keywords
			NDIS 3.0 Driver Keywords
			Packet Driver Keywords

Appendix B	DMI Installation
Appendix C	NET.CFG Options For Novell NetWare
Appendix D	LAN Manager File Examples
Appendix E	Installing A ROM 
Appendix F	Help


=================================================================
Product Summary
=================================================================

The NE2500 series and NE5500 series are high performance Ethernet 
adapters suitable for any networking environment. They can be 
used to provide powerful LAN connections for your ISA/EISA or PCI 
workstations, servers, and/or routers. Both use a Jumpstart 
utility for easy installation and the Fast Frame Xchange (TM) 
feature handles quick data transfer for Novell ODI workstation 
drivers. These products also contain a common driver set to 
simplify administrative support.

All these adapters support Plug and Play installation. Thus, your 
board has the built-in intelligence to automatically handle your 
system configuration needs and assign resources for IRQs, I/O 
Addresses, and DMA channels. This replaces the need for DIP 
switches and jumpers by electronically setting and configuring 
your system, including specifying device drivers for controlling 
any hardware configuration.

The NE2500 is a double media ISA bus Ethernet adapter which can 
connect to twisted pair or coax type networks. The NE2500T is a 
single media ISA bus Ethernet adapter which can only connect to 
twisted pair networks. Both boards are based on AMD's PCnet-ISA+ 
architecture.

The NE5500 is a double media PCI bus Ethernet adapter which can 
also connect to twisted pair or coax type networks. It is based 
on AMD's PCnet-PCI architecture.

The NE2500plus and NE5500plus models support full duplex operation.

The NE2500/NE5500 driver disks contain support for the following 
environments:

o  Novell Netware 3.1x, 4.x Server ODI, DOS ODI, OS/2 ODI

o  Microsoft LAN Manager 2.x

o  Microsoft Windows for Workgroups 3.11 (NDIS 2.01/NDIS 3.0)

o  Microsoft NDIS 2.01 compatible networks
	-  DEC PATHWORKS
	-  IBM LAN Server 2.0/3.x, 4.0
	-  Sun PC-NFS 5.x
	-  Artisoft LANtastic 6.0

o  Microsoft Windows NT 3.1, 3.5 and 3.51 (NDIS 3.0)

o  Microsoft Win95

o  Packet Driver (DOS)


Available by request are:

o  Novell UnixWare 1.1, 2.0

o  SCO UNIX 3.2.4 (ODT 3.0)

o  Sun Solaris 2.1

Please call Microdyne Technical Support for downloading
information.

The rest of this manual details how to install and use these 
Microdyne products.

=================================================================
Installing The Board
=================================================================

1) Look at the first graphic in the Quick Installation Guide if
you need to install a Remote Boot PROM. You can enable this 
by following the directions in Appendix E, Installing a ROM.
Then continue the installation process.

2) Turn off the system power before installing any boards.

3) Insert your board into an expansion slot. Only put an NE2500
Series adapter into an ISA- or EISA-board slot. Only put an
NE5500 Series adapter into a PCI-board slot. Make sure the board
is seated properly by pressing it firmly into its slot and
fastening the holding screw.

4) If installing multiple boards, configure each one 
separately, as shown in Appendix F, Help.

=================================================================
Running Jumpstart
=================================================================

Jumpstart provides an easy-to-use user interface to automatically 
configure or view a NE2500/NE5500 Series adapter card and install 
software drivers. Jumpstart automatically scans the system bus 
(ISA or PCI) to identify which adapter card is present. It has 
two main parts: Configuration and Installation.

To get a quick explanation of any of Jumpstart's choices or 
fields, use the F1 function key. For general help, select the 
Help button.

Jumpstart can automatically install the following drivers:

o  Novell NetWare DOS NETX ODI Client driver
o  NDIS 2.01 driver
o  Packet driver

Refer to the appropriate section in the following documentation
for further information on software installation.

Implementation
==================================

Follow the steps listed below:

1) Insert the desired driver disk into the floppy drive. Make 
sure HIMEM.SYS for DOS is loaded in the CONFIG.SYS file.

2) Type at the prompt:

		jmpstart
	Then press <Enter>.

3) Follow the screens to complete the Configuration and 
Installation for your adapter card. You must run the 
Configuration from DOS for all your adapter cards, even if you 
will be using them in non-DOS systems.

Jumpstart supports a mouse, otherwise a Key Map (see below) 
is provided to navigate through the utility. You may press F1 
at any time for help.

			Jumpstart Keyboard Map

Key       Function
ESC       Exit the configuration or help screen
F1        Help
Tab       Move the cursor to the next position
Arrows    Move the cursor
ENTER     Select (Highlight)
Space bar Select (Highlight)
<Alt> E   Exit the configuration utility

4) See the Configuration and Driver Installation sections below 
to continue.


Configuration
==================================

Jumpstart can configure or view NE2500 Series or NE5500 Series 
adapter cards. Depending on the adapter, this utility lets you
view and/or modify the I/O base address, IRQ channel, and DMA
channel. Use Jumpstart's Configuration dialog box to configure
your adapters. See the appropriate section below for more
information.

Notes:
1) All adapter cards must be configured from a DOS-based system.

2) Depending on which adapter card is being configured, Jumpstart
may not allow certain fields to be modified.

3) If multiple adapter cards are present, you can select each 
adapter card in turn and change its configuration settings as 
needed.

NE2500 Series Adapter Cards
----------------------------------
These adapter cards, the NE2500 Series (coax and twisted-pair) and
NE2500T Series (twisted-pair only), can operate in two different
modes:

o  Microsoft Plug and Play (PnP) ISA Enabled
o  Microsoft PnP ISA Disabled

PnP ISA Mode Enabled

Jumpstart will detect the NE2500 Series adapter card in PnP mode, 
then it sets: I/O base address, IRQ channel, DMA channel, and
media type fields for your adapter card. The only fields that may
be modified here are the Enable BNC box (enables the 10Base2
media) for an NE2500 adapter and the full duplex box for the
NE2500plus. 

You must select the Configure button in the Configuration 
dialog box to update/complete the configuration. This will also 
move Jumpstart into the Driver Installation section, as detailed 
later in this manual. 

When you finish using Jumpstart, exit it and load your PnP 
Configuration Manager in the CONFIG.SYS file. Then reboot your 
system so it will be able to recognize the PnP mode.

PnP ISA Mode Disabled 

Jumpstart will detect the NE2500 Series adapter card. Then it 
will gather the IEEE address, I/O base address, IRQ channel, DMA 
channel, and media type (fields) for your adapter.

You may change the settings for the I/O address, IRQ channel, DMA 
channel, or media type. You may also enable the PnP mode.

You must select the Configure button in the Configuration 
dialog box to update/complete the configuration. This will also 
move Jumpstart into the Driver Installation section, as detailed 
later in this manual.

If you have enabled the PnP mode here, exit Jumpstart when you 
finish using it and load your PnP Configuration Manager in the 
CONFIG.SYS file. Then reboot your system so it will be able to 
recognize the PnP mode.

- Remote Boot

See Appendix E, Installing A Universal Boot ROM 

NE5500 Series Adapter Card
----------------------------------
Jumpstart will detect a NE5500 Series adapter card on the PCI 
Local Bus. This utility then identifies and displays the adapter, 
IEEE address, I/O base address, and IRQ channel. The DMA channel 
in the PCI bus has no associated number, since it is slot-
specific.

You may not modify the settings for this adapter card, as the 
settings are assigned by the PCI system BIOS. You should enable
the slot before using this board. Refer to Helpful Hints, in 
Appendix F.

To enable full duplex operation on the NE5500 Series the FDUP
keyword must be manually entered in the appropriate
configuration file. See Appendix A under Common Keywords and
the section dealing with the network operating system you are
installing/modifying.

To install a driver using Jumpstart, select the Configure 
button in the Configuration dialog box. See the Driver 
Installation section below.

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

Jumpstart can automatically install the following list of 
drivers. Use the Jumpstart Driver Installation dialog box.

o  Novell NetWare DOS ODI (Netx) Client driver
o  NDIS 2.01 driver
o  Packet driver

Any other drivers must be installed manually using your Network 
Operating Systems installation guidelines. Use the Supplemental 
disk and see the proper driver installation section in this manual.

Notes:
1) When Jumpstart installs a device driver, it will also create 
sample CONFIG.NET, AUTOEXEC.NET, and PROTOCOL.INI or 
NET.CFG files as appropriate for proper driver installation. 
You may use these files as examples to modify the system's 
CONFIG.SYS and AUTOEXEC.BAT files when all pertinent files 
exist on the system.

2) See Installing The NDIS 2.01 Driver section (Microsoft LAN 
Manger) for more information on the PROTOCOL.INI file. See 
Appendix C for more information on the NET.CFG file.

Driver Name

PCNTNW is the driver name for the following NE adapters: 2500, 
2500T, 2500plus, 2500plusT, 5500, and 5500plus.

=================================================================
Installing Novell NetWare ODI Drivers
=================================================================

ODI (Open Datalink Interface) is a driver specification developed 
by Novell to offer a standard driver interface for Novell 
NetWare. Microdyne provides driver support for the following 
environments:

o  Novell NetWare 3.x
o  Novell NetWare 4.x

The drivers provided include:

o  NetWare DOS ODI Client - Netx and VLMs
o  NetWare OS/2 Client
o  NetWare Server 3.1x
o  NetWare Server 4.x

The installation of each driver is described below.

Novell NetWare DOS ODI Client
====================================

The NetWare DOS ODI client driver may be installed automatically
using Jumpstart or manually from the command line prompt. 

Driver Installation Using Jumpstart
-----------------------------------
Follow the steps listed below:

1) If your adapter is not already configured, refer to the 
Configuration section above. The Configuration process will take 
you to step 3 below.

2) If you have previously configured your card, press the 
Install Driver button in the Jumpstart Main Window. The Driver 
Installation dialog box will appear.

3) Highlight the Novell ODI DOS Client driver for the Device 
Driver. Change the default path if necessary. The default 
directory is: C:\NETWARE.

4) Press the Install button to install the driver. Jumpstart 
will then copy the driver and related Novell files into your 
specified directory, copy the example NET.CFG and sample 
AUTOEXEC.NET file there. These files can be found on the disk in 
the NETWARE directory. Edit the NET.CFG to reflect whether you
will be loading NETX or the VLMs. Use the AUTOEXEC.NET file
as a model for automatically loading the network software on boot.

5) Exit from Jumpstart when the installation has completed and 
reboot your machine.

The installation of the NetWare DOS ODI client driver is now 
complete. 

Note:
The current JMPSTART will not install the VLM software. To
install the VLM software, please refer to the Installing VLMs
Section below.

Driver Installation From The Command Line Prompt
------------------------------------------------
Installing NETX

Follow the steps listed below:

1) Insert the NetWare driver disk into the floppy drive.

2) Create a subdirectory in your client's main boot drive and 
copy the following files from A:\NOVELL into it:
	LSL.COM, PCNTNW.COM,IPXODI.COM, NETX.EXE
	and optionally NET.CFG.	
For a more complete explanation of these files and their 
function, please refer to the READNETX.TXT on the disk.

3) To automatically load these files, refer to the provided
LAN.BAT file provided on disk. Edit AUTOEXEC.BAT to contain the line:
	call %directory%\LAN.BAT <Enter>
where %directory% is the directory where you have placed the 
network files. The command must be placed in AUTOEXEC.BAT before 
programs that may use network resources are loaded (such as 
Windows).

4) Reboot the workstation. After the commands execute, and if a 
server is present, the workstation will attach to the server and 
display the server's name. Then log into the network.

The installation of the NetWare DOS Netx ODI client driver is now 
complete.

Installing VLMs

1) Switch to the directory containing the VLMs by typing
	CD NOVELL

2) Type:
	COPYVLM directory
Where directory is the full path to copy the software. Example:
	COPYVLM C:\NETWARE\
	
3) Follow 3 and 4 in Installing NETX above.

To change any default settings when the driver is loaded, you 
must create a NET.CFG file on the workstation disk. See the 
Novell NetWare Operating System Keywords in Appendix A for more 
information on valid keywords. See Appendix C for a sample 
NET.CFG file using various keywords.

The Novell Netware ODI DOS installation documentation has more 
information on installing the DOS ODI driver and using keywords 
during installation.

Novell NetWare OS/2 ODI Client
====================================

The Novell OS/2 Requester should be used to install the OS/2 ODI 
client driver. Load the NetWare OS/2 ODI client driver from the 
OS/2 CONFIG.SYS file as provided on the disk. See the Novell 
NetWare Requester OS/2 Installation documentation for more 
information.

After installing the OS/2 Requester, follow the steps listed 
below:

1) Using the Netware OS/2 disks provided by Novell, install the 
Netware OS/2 Requester files on the client. Follow the 
instructions displayed to configure the Netware OS/2 Requester 
for a Netware-supported LAN adapter card.

If the Netware-supported LAN adapter card contains the Microdyne 
adapter option, select it, otherwise select other LAN adapter.

2) Insert the NetWare driver disk into the floppy drive.

3) Copy the OS/2 ODI driver (PCNTNW.OS2) from the NetWare 
driver disk to the C:\NETWARE directory of the boot drive using 
the path:
	A:\NOVELL\OS2

4) Edit the CONFIG.SYS file and replace the Netware-supported 
LAN adapter driver with the name of the OS/2 ODI driver 
(PCNTNW.OS2). For example:

	DEVICE=C:\NETWARE\PCNTNW.OS2

If the Novell OS/2 Requester is used to install the driver, the 
Requester will automatically make modifications to the CONFIG.SYS
file. There is an example of the CONFIG.SYS file in the OS2
directory on the disk.

The default settings may be modified when the driver loads by 
creating the file NET.CFG. Refer to Appendix C for sample NET.CFG 
files using the optional keywords. Also, refer to the Novell 
Netware Requester OS/2 Installation documentation for more 
information on configuring the NET.CFG file.

5) Reboot the system.

The installation of the NetWare OS/2 ODI client driver is now 
complete.

Novell NetWare Server 3.1x
====================================

The NetWare Server 3.1x ODI driver for a NetWare 3.1x server is 
included on the NetWare driver disk. Use the LOAD and BIND 
commands to load the NetWare 3.1x ODI server driver as described 
below. For more information on these commands, refer to the 
Novell NetWare 3.1x LAN Driver Installation documentation.

There are two methods for loading the NetWare Server 3.1x driver: 
use the server command line prompt (:) or edit the 
AUTOEXEC.NCF file.

Note:
If you use the server command line, you will need to load the 
driver each time the system is booted. If you edit the 
AUTOEXEC.NCF file, it will automatically load the driver each 
time your system is booted.

Follow the steps listed below:

1) Install NetWare 3.1x on your system. 

2) Copy all the files except MSM.NLM from the NETWARE\4.xx
directory of the driver disk to the server system directory.

3) Boot NetWare by executing SERVER.EXE. Refer to the appropriate
Novell NetWare documentation for more information.

4) Type the following command at the file server console:
		LOAD LSLENH.NLM (version 3.11 only)
		LOAD MSM31X.NLM
		LOAD ETHERTSM.NLM
		LOAD PCNTNW
		BIND IPX TO PCNTNW NET=xxxx
		(Bind to IPX or any other protocol stack; where
		xxxx=your_net_#)

All the files listed above should be copied from the provided 
driver disk to the System directory.

Note:
All of the files listed above are needed. You must only use the 
versions of these files included on the driver disks.
The adapter card configuration information is automatically 
determined by the PCNTNW driver.

		WARNING
For NetWare 3.11, use the Monitor Program included on the NetWare 
driver disk. The original Monitor Program shipped with NetWare 
3.11 will crash the system.

To load the driver using AUTOEXEC, you must first edit the 
AUTOEXEC.NCF file.

1) Type LOAD INSTALL at the server prompt (:) to access 
the Install Utility.

2) Open the SYSTEM OPTIONS menu to access EDIT AUTOEXEC.

3) Then add the following command lines to the AUTOEXEC.NCF file. 
This example is for any adapter card.
		LOAD PCNTNW
		BIND IPX TO PCNTNW NET=xxxx

The installation of the NetWare Server 3.1x driver is now 
complete.

Novell NetWare Server 4.x
====================================

The NetWare Server 4.x ODI driver for a NetWare 4.x server is 
included on the NetWare driver disk. Use the LOAD and BIND 
commands to load the NetWare 4.x ODI server driver as described 
below. For more information on these commands, refer to the 
Novell NetWare 4.x LAN Driver Installation documentation.

There are two methods for loading the NetWare Server 4.x driver: 
use the server command line prompt (:) or edit the 
AUTOEXEC.NCF file.

Note:
If you use the server command line, you will need to load the 
driver each time the system is booted. If you edit the 
AUTOEXEC.NCF file, it will automatically load the driver each 
time your system is booted.

Follow the steps listed below:

1) Install NetWare 4.x on your system. 

2) Copy the ODI Server driver (PCNTNW.LAN) from the driver disk. 

3) Boot NetWare by executing SERVER.EXE. Refer to the appropriate 
Novell NetWare documentation on loading disk drivers and mounting 
volumes for more information.

Make sure the MSM.NLM and ETHERTSM.NLM files are present 
in the same directory as PCNTNW.LAN. These files should be 
copied from the 4.x subdirectory of the driver disk.

Type the following commands at the file server console:

		LOAD PCNTNW
		BIND IPX TO PCNTNW NET=xxxx
		(Bind to IPX or any other protocol stack; where
		xxxx=your_net_#)

To load the driver using AUTOEXEC, you must first edit the 
AUTOEXEC.NCF file.

1) Type LOAD INSTALL at the server prompt (:) to access 
the Install Utility.

2) Open the MAINTENANCE/SELECTIVE INSTALL menu and select 
the NCF File Options from the menu to access EDIT AUTOEXEC.

3) Add the following command lines to the AUTOEXEC.NCF file. 
This example is for any adapter card.

		LOAD PCNTNW
		BIND IPX TO PCNTNW NET=xxxx

The installation of the NetWare Server 4.x driver is now 
complete.


=================================================================
Installing The NDIS 2.01 Driver
=================================================================

NDIS (Network Driver Interface Specification) 2.01 is a driver 
specification developed by Microsoft to offer a standard driver 
interface for adapters. The NDIS 2.01 driver supports the 
following environments:

o  Microsoft LAN Manager 2.x
o  Microsoft Windows for Workgroups 3.11
o  IBM LAN Server 2.0, 3.x, 4.0
o  Sun PC-NFS 5.x
o  Artisoft LANtastic 6.0
  
The NDIS 2.01 driver may be installed automatically using 
Jumpstart or manually from the command line prompt for each 
specific environment. Both methods are described below.

Driver Installation Using Jumpstart
===================================

Follow the steps listed below

1) Run Jumpstart to configure your adapter's I/O base address, 
IRQ channel, and DMA channel.

2) Select the Configure button in the Configuration dialog 
box. The Driver Installation dialog box will appear.

Note:
If IBM LAN Manager, Microsoft Windows for Workgroups, Sun PC-NFS, 
etc. OEM installation procedures are used to install the NDIS 
2.01 driver, do not use Jumpstart to install the NDIS 2.01 
driver.

3) Highlight the NDIS 2.01 driver to install the driver. 
Change the default path if necessary. The default directory is: 
C:\NDIS.

4) Press the Install button to complete the installation. 
Jumpstart will copy the selected driver file into the specified 
directory, create a PROTOCOL.INI file in the specified directory, 
and copy a sample CONFIG.NET file into the specified directory. 

	CONFIG.NET contains the following:
		DEVICE=<install path> PROTMAN.DOS /I:<install path>
		DEVICE=<install path> PCNTND.DOS
Note:
PROTMAN.DOS is distributed by Microsoft, IBM, and other OS 
companies.

5) Exit Jumpstart when the installation has been completed. You 
may need to make modifications to the system files, using the 
sample files as a reference.

The installation of the NDIS 2.01 driver is now complete.

Microsoft LAN Manager 2.x
===================================

Support is provided for the Microsoft LAN Manager (version 2.x) 
environment. The driver should be installed using the Microsoft 
LAN Manager Setup Utility.

Note:
The hardware for the Microsoft LAN Manager environment can be 
configured to run as an OS/2 server, OS/2 workstation, basic MS-
DOS workstation, or an enhanced MS-DOS workstation. Please refer 
to your Microsoft LAN Manager documentation as needed.

Driver Installation Using Microsoft LAN Manager Setup Utility
-------------------------------------------------------------
Follow the steps listed below:

1) Insert the Supplemental Driver Disk into the floppy drive.

Note:
Two information files (pcntnd.nif and protocol.ini) will be 
used for driver installation. These files are located on the
driver disk.

2) Change into the LAN Manager subdirectory on your hard disk 
by typing:
		cd C:\LANMAN

Start the Microsoft LAN Manager Setup Utility by typing:
		setup

3) The following message will be displayed:
		Loading Microsoft LAN Manager configuration ...

4) Hold down the <Alt> key and press C to access the 
Configuration drop down menu.

5) Use the up/down arrow keys to select Network Drivers... 
and then press <Enter>. This will open the Workstation 
Configuration window.

6) If you have an existing (old) Microdyne NE2500/NE5500 Series
driver installed, use the tab key to select <Remove Config> and
then press <Enter>. This removes any existing Microdyne driver.

7) Use the tab key to select <Add New Config> and then press 
<Enter>. This will open the Network Adapter Drivers window.

8) Use the tab key to select <Other Driver>, 

9) Enter the disk drive letter (e.g., A:) where the 
Supplemental Driver Disk is located.

	Use the tab key to select <OK>.

10) Use the up/down arrow keys to select Microdyne NE2500/NE5500
Adapter. Next, use the tab key to select <OK>.

Note:
If you have older Microdyne NE2500/NE5500 drivers installed, you
will be asked if you want to Overwrite?. Use the tab key to
select <Yes>.

11) Use the up/down arrow keys to select the desired protocol, 
press the spacebar to select, and then use the tab key to select 
<OK>. Then press <Enter>. You will then be returned to the 
Workstation Configuration window.

12) Use the tab key to select <Save> and then press <Enter>. 
The following message will be displayed:
		Saving Microsoft LAN Manager Configuration ...

13) Hold down the <Alt> key and press L to access the LAN 
Manager drop down menu.

14) Use the up/down arrow keys to select Exit Setup and then 
press <Enter>. The following message will be displayed:
		LAN Manager Configuration Complete
	<OK> will be highlighted. Press <Enter>.

The installation of the NDIS 2.01 driver for Microsoft LAN 
Manager is now complete.

Microsoft Windows for Workgroups 3.11
=====================================

Support is provided for the Microsoft Windows for Workgroups 
(version 3.11) environment. Microsoft Windows for Workgroups 3.11 
supports both NDIS 2.01 and NDIS 3.0 drivers.

Follow the steps listed below:

1) Insert the appropriate Driver Disk into the floppy drive.

2) In the Windows for Workgroups 3.11 Program Manager, double 
click on the Windows Setup icon.

3) From the Options Menu, select Change Network Settings.

4) From the Network Setup dialog box, select the Drivers... 
button to install the NDIS 2.01 and NDIS 3.0 drivers.

5) In the Network Drivers dialog box, select the Add Adapter button
to install the Microdyne device drivers.

6) In the Add Network Adapter window, choose the Unlisted or 
Updated Network Adapter from the menu and then select OK.

7) The Install Driver dialog box will appear. Enter the drive 
containing the driver Disk and specify the path to install the 
Microdyne drivers. For example, enter:
		A:\WFW311
	Then select OK.

8) Your selection will appear under the Network Adapters list. 
Select OK to continue.


9) In the Network Drivers dialog box, select Setup. In the 
Microdyne NE2500/NE5500 Series dialog box: set interrupt 
(IRQ) to Auto_scan and the base I/O port to 0.

Select OK. In the Network Drivers dialog box, select Close. 
In the Network Setup dialog box, select OK. For the 
Microsoft-specific dialog boxes, select Skip. For the Install 
Driver dialog box, enter:
		\WFW311
Note:
If Auto_scan is selected no value need be specified; however, 
Windows for Workgroups 3.11 will issue a warning message 
regarding possible interrupt conflict. This is due to the 
temporary configuring of the interrupt to channel 0 until the 
real value is set according to the EEPROM configuration.

10) Select OK to exit. Then select Close. Windows for Workgroups 3.11
will ask you to reboot the machine once the installation is completed.

The installation of the NDIS 2.01 driver for Windows for 
Workgroups 3.11 is now complete.

Keyword Example

To set the LED0 keyword value, follow the instructions given 
above to access the Advanced settings for an adapter card. A 
dialog box will appear to set the LED keyword options. In the 
LED0 setting, enter the value desired from the list given in the 
Software Keywords section (Appendix A).

IBM LAN Server
=================================

The NDIS 2.01 driver can also be used with the IBM LAN Server 
(version 2.0, 3.x, 4.0) environment. IBM LAN Server requires a 
unique NIF file. This NIF file is included on the Supplemental 
Driver Disk (see the README.TXT file under the LANSRVR
directory).

Follow the steps listed below:

1) Insert the Supplemental Driver Disk into the floppy drive.

2) In IBM LAN Server, select or run the LAPS (LAN Adapter and 
Protocol Support) program. Please refer to the IBM LAN Adapter 
and Protocol Support Configuration Guide for more information on 
this utility and for more details on how to install additional 
adapters and device drivers.

3) From the IBM LAPS (MPTS in 4.0) dialog box, choose the INSTALL
button to install an adapter for the IBM LAN Server environment.
If the adapter has already been installed, go to step 6 below.

4) Specify the drive and path (e.g., LANSRVR) for the driver disk 
(e.g., A:\LANSRVR).

5) After installing/copying the appropriate NIF files from the 
Supplemental Driver Disk, the IBM LAPS dialog box will appear 
again.

6) From the IBM LAPS dialog box, select Configure.

7) In the Configuration dialog box, choose the Configure LAN 
transports (default) option and select Continue.

8) When the Configure Workstation dialog box is displayed, 
remove the current configurations from the Current 
Configuration list box.

9) Choose Microdyne NE2500/NE5500 Series Ethernet Adapter from
the Network Adapters list box, by highlighting the entry. Then 
choose Add to add your adapter to the Current Configuration 
list box.

10) Highlight the appropriate protocols in the Protocols list 
box. Then choose Add to add them to the Current Configuration 
list box.

11) Choose the adapter from the Current Configuration list 
box. Then choose Edit. The Parameters for Microdyne dialog box is
displayed. 

12) View the default configuration. If the default configuration 
is ok, choose OK.

If you need to change your configuration, change the options 
in this dialog box. Choose Range to display the available 
settings for each option. Press [F1] if you need help deciding on 
a setting.

The installation of the NDIS 2.01 driver for IBM LAN Server is 
now complete.

Note: Two directories have been created for IBM LAN Server 4.0
\IBMLSP should be used for the "Advanced LAN Support Program"
\IBMADOS should be used for the "Advanced LAN DOS Services"
Please refer to the IBM LAN Server documentation for installation
instructions.

Driver Installation For IBM Extended Services 1.0
-------------------------------------------------

Follow the steps listed below:

1) Insert the appropriate driver disk into the floppy drive.

2) Display the Communication Manager main menu and choose 
Advanced.

3) Choose Configuration.

4) Choose LAN Adapter and Protocol Support (LAPS).

5) At the Options dialog box, choose Copy additional 
network adapter drivers. Then choose OK.

6) At the Copy Additional Network Adapter Drivers dialog box, 
type the path (e.g., A:). Then choose OK.

7) When the Copy Disk dialog box is displayed, choose OK.

8) When the Options dialog box is displayed, choose 
Configure Workstation. Then choose OK.

9) When the Configure Workstation dialog box is displayed, 
remove the current configurations from the Current 
Configuration list box. 

10) Choose the Microdyne NE2500/NE5500 Series Ethernet Adapter
from the Network Adapters list box, by highlighting the entry. 
Then choose Add to add your adapter to the Current Configuration 
list box.

11) Highlight the appropriate protocols in the Protocols list 
box. Then choose Add to add them to the Current Configuration 
list box.

12) Choose the Microdyne NE2500/NE5500 Series Ethernet Adapter at 
the Current Configuration list box. Then choose Edit. The 
Parameters for Microdyne dialog box is displayed.

13) View the default configuration. If the default configuration 
is ok, choose OK.

If you need to change your configuration, change the options 
in this dialog box. Choose Range to display the available 
settings for each option. Press [F1] if you need help deciding on 
a setting.

The installation of the NDIS 2.01 driver for IBM Extended 
Services 1.0 (LAN Server) is now complete.

Sun PC-NFS
=================================

The NDIS 2.01 driver can also be used with the Sun PC-NFS 
(version 5.x) environment. Follow the steps listed below.

1) Be sure PC-NFS is installed on your system and configured 
for an NDIS 2.01 driver. See the PC-NFS Installation Procedure 
Manuals for more information.

2) Run NFSCONF. Select Adapter Menu. Select Ethernet. 
Select NDIS.

3) Insert the PC-NFS QUIKNDIS disk into the floppy drive. 
Change to the drive containing the QUIKNDIS disk (e.g., A:\).

4) At the prompt type:
		QUIKNDIS

5) A message will appear asking for the current boot drive. 
Enter the current boot drive and then press <Enter>.

6) Press Y to save the current PROTOCOL.INI file as 
PROTOCOL.OLD. Ignore this step if this dialog box does not 
appear.

7) In the Adapter Card List box, select the Custom option 
to install the NDIS driver for PC-NFS.

8) Remove the QUIKNDIS disk from the floppy drive. Insert the 
Supplemental Driver Disk into the floppy drive.

9) Follow the dialog boxes and enter the correct driver and 
path of the Supplemental Driver Disk to install the NDIS driver 
(e.g., A:\PCNFS).

10) Enter PCNTND for the NIF file name and then press <Enter>.

11) Make the appropriate changes to CONFIG.SYS and AUTOEXEC.BAT.

12) Reboot your system.

The installation of the NDIS 2.01 driver for PC-NFS is now 
complete.

Artisoft LANtastic
=================================

Support is provided for the Artisoft LANtastic (version 6.0) 
environment.

Note:
Artisoft LANtastic 6.0 is now based on the NDIS 2.01 
specification.

The driver is located on the Supplemental Driver Disk under the 
subdirectory:

\MSLANMAN.DOS\DRIVERS\ETHERNET\PCNTND

In order to install a driver for LANtastic 6.0, the operating 
system must be re-installed. Start from the DOS system prompt and 
follow the steps listed below:

1) Insert Disk 1 of LANtastic 6.0 into your floppy drive 
At the DOS prompt type:
		a:\install

2) Artisoft's installation program will then search for 
Microsoft Windows on your system. If Windows is not found, press 
<Enter> at the message to run the install program under DOS 
Otherwise, if Windows is found, Windows will be started. 

3) The Artisoft Install message will be displayed. Click OK to 
continue.

4) Select KEEP all previous LANtastic setup information and 
click OK to continue.

5) Select any additional LANtastic features you wish to install 
(see Artisoft LANtastic Manuals for more information). Click OK 
to continue.

6) Select NDIS Support for Network Adapters and click OK to 
continue.

7) Insert the Supplemental Driver Disk into the floppy drive 
and then click OK to continue.

8) Insert the appropriate Artisoft LANtastic 6.0 disk when 
prompted for. Click OK to continue.

9) Select OK to perform the installation and click OK to continue.

10) Information will appear on the screen, click OK to continue.

11) Insert the appropriate Artisoft LANtastic 6.0 disk when 
prompted for. Click OK to continue.

12) You will see the Installation complete and Need to reboot 
your computer message. Click OK to continue. Remove the disk 
from the floppy drive. Click OK to reboot.

13) On start-up you'll see the message:

		AMD PCNet Family Ethernet Adapter
		NDIS v2.0.1 MAC Driver, version x.xx
		Drivername
		Driver configuration information such as IOAddress, 
		Interrupt, and DMA.

14) Next, you will see some LANtastic configuration messages.

The installation of the NDIS 2.01 driver for Artisoft LANtastic 
6.0 is now complete.

=================================================================
Installing The NDIS 3.0 Driver
=================================================================

NDIS (Network Driver Interface Specification) 3.0 is a driver 
specification developed by Microsoft to offer a standard driver 
interface for adapter cards. The NDIS 3.0 driver supports the 
following environments:

o  Microsoft Windows NT 3.1, 3.5, 3.51
o  Microsoft Windows for Workgroups 3.11
o  Windows 95

Installation of the NDIS 3.0 driver for each specific environment 
listed above is described below.

Microsoft Windows NT
=================================

Support is provided for the Microsoft Windows NT (versions 3.1, 
3.5, 3.51) environment.

Note:
Only x86-based Windows NT platforms are supported.

Follow the steps listed below:

1) Insert the Supplemental Driver Disk into the floppy drive.

2) From the Control Panel in the Windows NT Main window, 
double click on the Network icon to install your adapter card.

3) In the Network Settings dialog box, choose Add Adapter.

4) In the Add Network Adapter dialog box, pull down the 
adapter card list menu and select <Other> Requires disk from 
manufacturer from the list and continue.

5) In the next window, enter:
		A:\WINNT or A:\WINNT351

WARNING: The Windows NT 3.51 driver is not backward compatible
with earlier versions. 

6) Then, select Microdyne NE2500/NE5500 Series Ethernet Adapter
from the dialog box to install your adapter.

7) In the Microdyne NE2500/NE5500 Series Ethernet Adapter Card 
Setup dialog box, select bus type All (defaults to All if nothing 
is selected). If more than one network adapter card is used,
select its bus type.

IRQ and DMA channel values are auto-detected. However, the 
values must be specified for multiple network cards. The IRQ and 
DMA values are set by using Jumpstart. Shutdown Windows NT and 
run Jumpstart from DOS. Full Duplex (FDUP) must be specified in a
configuration file for the NE5500plus Series.

Note:
Sometimes All will not work on PCI-based systems. In this 
case, try selecting PCI1 or PCI2 depending on the bus type.

If you are using an NE5500 adapter, you do not need to run 
Jumpstart.

8) Reboot your system to complete the driver installation 
process.

For additional information, please refer to your Microsoft 
Windows NT OS documentation. In addition, review the README.TXT
file in the WINNT directory of the Supplemental Driver Disk.

Keyword Example

To set the TP keyword, go into the Microdyne NE2500/NE5500 Series 
Ethernet Adapter Card Setup dialog box (see instructions above on 
how to access this dialog box), activate the TP button to use the
TP keyword described in the Software Keywords (Appendix A).

Microsoft Windows for Workgroups 3.11
=====================================

1) Insert the Supplemental Driver Disk into the floppy drive.

2) In the Windows for Workgroups 3.11 Program Manager, double 
click on the Windows Setup icon.

3) From the Options Menu, select Change Network Settings.

4) From the Network Setup dialog box, select the Drivers... 
button to install the NDIS 2.01 and NDIS 3.0 drivers.

5) In the Network Drivers dialog box, select the Add 
Adapter button to install the device drivers.

6) In the Add Network Adapter window, choose the Unlisted or 
Updated Network Adapter from the menu and then select OK.

7) The Install Driver dialog box will appear. Enter the 
floppy drive containing the Supplemental Driver Disk and specify 
the Windows for Workgroups 3.11 path to install the drivers. For 
example, enter:
		A:\WFW311
	Then select OK.

8) Your selection will appear under the Network Adapters list. 
Select OK to continue.

9) Answer the series of questions for the correct base I/O 
port, IRQ channel, and DMA channel.

o  In the Network Drivers dialog box, select Setup.
o  In the NE2500/NE5500 Series  dialog box:
o  Set interrupt (IRQ) to Auto_scan and the base I/O port 
	to 0. Select OK.
o  In the Network Drivers dialog box, select Close. In 
	the Network Setup dialog box, select OK.
o  For the Microsoft-specific dialog boxes, select Skip. 
For the Install Driver dialog box, enter:
		\WFW311

Note:
If Auto_scan is selected no value need be specified; however, 
Windows for Workgroups 3.11 will issue a warning message 
regarding possible interrupt conflict. This is due to the 
temporary configuring of the interrupt to channel 0 until the 
real value is set according to the EEPROM configuration.

10) Select OK to exit. Windows for Workgroups 3.11 will ask 
you to reboot the machine once the installation is completed.

The installation of the NDIS 3.0 driver for Windows for 
Workgroups 3.11 is now complete.

Keyword Example

To set the LED0 keyword value, follow the instructions given 
above to access the Advanced settings for an adapter card. A 
dialog box will appear to set the LED keyword options. In the 
LED0 setting, enter the value desired from the list given in the 
Software Keywords section (Appendix A).

Microsoft Windows 95
=================================
Support is provided for the Microsoft Windows 95 environment. 
For the NE500 Series, the card will automatically be detected
and installed as an AMD PCnet Family Ethernet Adapter.

For the NE2500 Series, follow the steps listed below:

1) Insert the Supplemental Driver Disk into the floppy drive.

2) Click on the Control Panel icon.

3) Click on the Network icon, select Add.

4) Select Adapter and click Add in the Select Network Component box.

6) Click on Have Disk button.

7) Type in A:\WIN95 and OK in the drive selection area.

8) From the list in the left hand box, highlight Microdyne.

9) Select the appropriate adapter from the Microdyne products listed.

10) Click on OK.

Follow any further instructions for adding software.
The installation of the network driver for Windows 95 is
now complete.

Note: Windows 95 allows you to configure the LED settings on
the NE5500plus Series. Please refer to the READ-LED.TXT file in
the WIN95 directory for further information on changing the
LED settings.

=================================================================
Installing The Packet Driver
=================================================================


The Packet Driver for the NE2500 series and NE5500 series 
adapters is based on the packet driver from Clarkson University.

Driver Installation Using Jumpstart
=====================================

Follow the steps listed below:

1) Run Jumpstart to configure your adapter's I/O base address, 
IRQ channel, and DMA channel.

See the Configuration section for more information on 
configuring your Microdyne adapter card.

2) Select the Configure button in the Configuration dialog 
box. The Driver Installation dialog box will appear.

3) Highlight the Packet driver to install the driver. Change 
the default path if necessary. The default directory is: 
C:\PAKTDRV.

4) Press the Install button to complete the installation. 
Jumpstart will copy the selected driver file into the specified 
directory and create a sample AUTOEXEC.NET file in the 
specified directory. 

AUTOEXEC.NET contains the following:
	PCNTPK INT=0x60 IOADDRESS=<ioaddress> IRQ=<irq> 
	DMA=<dma>

Note:
The Packet driver uses a software interrupt to provide a handle 
for a TCP driver to automatically scanwith a range of 0x60-66. 
Jumpstart uses a default value 0x60 for INT. If there is a 
conflict with other software settings, change this setting by 
editing the AUTOEXEC.NET file.

5) Exit Jumpstart when the installation has been completed. You 
may need to make modifications to the system files; use the 
sample files as a reference.

The installation of the Packet driver is now complete.

Driver Installation From The Command Line Prompt
================================================

Copy the Packet Driver, PCNTPK.COM, into a directory. The 
packet driver can be loaded from the DOS prompt or from the 
AUTOEXEC.BAT file.

The command line format for the packet driver is:

	PCNTPK [-n] [-d] [-w] <INT=packet_int_no> [IRQ=int_no]
		 [IOADDR=io_addr] [DMA=dma_no] [BUSTYPE=bus]
		 [DMAROTATE] [TP] [LED0=xx] [LED1=xx] [LED2=xx]
		 [LED3=xx] [FDUP=xx]

When using Windows the -w option. If the [IRQ=int_no], 
[IOADDR=io_addr], and [DMA=dma_no] are not specified for your 
adapter card, their default values are used.

Note:
The following:

	INT=packet_int_no
is a handle for an upper layer interface (normally 0x60-66). This 
is not optional. An upper layer application such as TCP scans for 
the INT handle between 0x60-66.

Additional common keywords may be specified. Please refer to the 
Software Keywords section in Appendix A for more information.

Keyword Example

An example command line is as follows:

	PCNTPK INT=0x60 IRQ=3 IOADDR=0x300 DMA=5


=================================================================
APPENDIX A - Software Keywords 
=================================================================

This section describes software keywords that may be needed while 
configuring adapters. There are two sections of keywords 
discussed below: common keywords and driver-specific keywords. 
Also, a table is provided to show the valid combinations of 
keywords with the various adapters.

Common Keywords
============================

Common keywords may be used by any of the operating systems to 
configure an adapter card.

PORT (IOADDRESS, IOBASE)
The I/O base address keyword may be used to specify the I/O 
address of the adapter, but it does not need to be specified for 
driver configuration. For the NE2500, the driver will use the 
interrupt channel set by the Plug and Play (PnP) ISA 
Configuration Manager for PnP mode or by the on-board EEPROM when 
PnP is disabled. The range is 220h-3FFh (per 20h offset) 
inclusive.

For the NE5500, the driver will use the interrupt set by the PCI 
system BIOS. The range is 0000-FFFFh inclusive.

INT
Jumpstart will determine the interrupt channel. For the NE2500, 
the driver will use the interrupt channel set by the Plug and
Play (PnP) ISA Configuration Manager for PnP mode or by the
on-board EEPROM when PnP is disabled. The range is: 3-5, 9-12,  
15. For the NE5500, the driver will use the interrupt set by
the PCI system BIOS. The range is 0-15. The interrupt channel 
keyword should not be used for these boards.

DMA
Jumpstart will determine the DMA channel. For the NE2500, this
will be the DMA channel set by the PnP ISA Configuration Manager
for PnP mode or by the on-board EEPROM when PnP is disabled.
The range is: 3, 5, 6, 7. The DMA keyword should not be used
for these boards.

FDUP
Full duplex. Enables/disables full duplex on the 10BaseT and AUI
ports of the NE2500plus/NE5500plus Series only. The default is
off. Full duplex operation on the NE5500plus Series may only be
enabled with this keyword. FDUP = (UTP, AUI, OFF).

Table of Valid Keyword Combinations

Keyword		NE2500	NE5500
INT               X	
DMA               X	
PORT              X	
BUSTYPE           X       X
DMAROTATE         X	
TP                X       X
LED[0-3]          X       X
FDUP              X       X 

Note:
If PORT is specified, then the BUSTYPE keyword will not function. 
If no PORT or BUSTYPE is specified, the software will 
automatically scan all buses until an adapter is found. Once the 
adapter is found, the driver will load.

Card Specific Keywords
===============================


DMAROTATE
This keyword applies to the NE2500 adapter card only. When 
present, this keyword will force the system 8237 controller into 
rotating priority mode. The default mode for the 8237 controller 
is fixed priority.

BUSTYPE (BUS_TO_SCAN)
If this keyword is specified with one of the above mentioned 
options, the driver software will only scan the specified bus for 
the presence of the adapter. If this keyword is not specified the 
software will scan all the buses. 
	Bus Type                 Adapter Card       Keyword
	ISA                      NE2500 Series        ISA
	Plug and Play (PnP)      NE2500 Series        PNP
	PCI Local Bus            NE5500 Series    PCI/PCI1/PCI2

For example:
NetWare
	For NE2500:	LOAD PCNTNW BUSTYPE=PNP
	For NE5500:	LOAD PCNTNW BUSTYPE=PCI
LAN Manager
To use the BUSTYPE keyword, remove the I/O Address and insert the 
BUSTYPE keyword in the PROTOCOL.INI file (located in the
Microdyne Driver (PCNTND) directory).


TP
When present, this keyword will force the adapter into using the 
10BASE-T port. The Microdyne controller will use the 10BASE-T
port even if no link beat pulse is generated from the 10BASE-T
hub. If not set, auto port detection will be used (this is the
default).

LED0 = XX
When present, this keyword should have a hexadecimal value which 
indicates the function of LED0. The software reads the hex value 
of the keyword and programs the LED0 register (BCR4) with the 
value specified. Choose this hex value carefully, since it is 
programmed directly into the device register.

xx is a hex value for the BCR4 register. Its range is 00-FFh. 
Some of the valid values are listed below:

00h	Indicates collision activity on the network
02h	Indicates PCNet is jabbering on the network
04h	Indicates promiscuous receive activity on the network
08h	Indicates the current receive polarity condition
10h	Indicates the transmit activity
20h	Indicates receive activity for this station
40h	Indicates the current link status
30h	Indicates the transmit and receive activity for this station
34h	Indicates the transmit and promiscuous receive activity

LED1 = XX
xx is a hex value for the BCR5 register. Otherwise, this is the 
same description as for LED0.

LED2 = XX
xx is a hex value for the BCR6 register. Otherwise, this is the 
same description as for LED0.

Note:
LED2 is not available for the NE5500.

LED3 = XX
xx is a hex value for the BCR7 register. Otherwise, this is the 
same description as for LED0.

Novell NetWare Operating System Keywords
========================================

FRAME (Multiple Frame Type Support)
The FRAME keyword should be used with the LOAD command to 
designate the desired frame type. In addition, to supporting 
multiple FRAME types, the BOARD keyword must be used in 
conjunction with the FRAME keyword if no I/O Address is 
specified. The available FRAME values are the following:

	Ethernet_802.2
	Ethernet_802.3
	Ethernet_SNAP
	Ethernet_II

Please refer to the appropriate Novell NetWare documentation for 
details regarding each frame type. The BOARD keyword value is 
designated by the user. The range available for BOARD is 0-254.

For example, to load multiple frame types for one physical 
adapter card, the following should be entered:

	LOAD PCNTNW FRAME=Ethernet_802.2 BOARD=1
	LOAD PCNTNW FRAME=Ethernet_802.3 BOARD=1
	LOAD PCNTNW FRAME=Ethernet_II BOARD=1
	LOAD PCNTNW FRAME=Ethernet_SNAP BOARD=1

Then press <Enter>.

Finally, the driver must be bound to the IPX protocol for each 
frame type based on the procedure provided in the Novell NetWare 
documentation. Please note the memory must be large enough to 
support multiple frames; increase the buffer size in the 
STARTUP.NCF file in NetWare. For example, the SET RESERVED 
BUFFERS below 16 Meg should be set to 32 from the default setting 
of 16:

	Set Reserved Buffers below 16 Meg=32

Appendix F, Help, shows an example of the LOAD and BIND 
statements for a single server with two boards, one NE2500 and 
two NE5500.

BOARD
The BOARD keyword may be used with the LOAD command to specify 
the board number to the selected physical adapter board. This 
keyword is used to load a different frame type to the same board. 
See the Multiple Frame Type Support section above for examples 
using the BOARD keyword.

Note:
If PORT and IO Port Address are specified, then the BOARD keyword 
should not be used. In this case, the same PORT should be used to 
load the different frame type.

Loading Multiple NE2500 or NE5500 Adapter Cards

The driver must be loaded again for each new adapter board 
installed in the system. Appendix F, Help, shows an example of 
loading four adapter cards in the system for the Novell NetWare 
environment.

FASTISA	
This is not supported for OS/2 ODI. FASTISA  increases the 
performance of the NE2500 Series by reducing the memory write 
cycle time from 450 ns to 350 ns. Some older machines with slower 
memory may not be compatible if they do not have an EISA mode. 
Refer to Appendix C for more details on NET.CFG options. The 
default is Not Present.

BTO 
Bus Timer Off. This is not supported for OS/2 ODI. BTO 
resets bit 13 in CSR4 to enable the Bus Timer register (CSR82). 
By default, the timer is always on (Not Present).

DMAPLUS	
This is not supported for OS/2 ODI. DMAPLUS sets the 
DMAPLUS bit (bit 14, CSR4) to disable the burst transaction 
counter in CSR80. The default is Not Present.

CDCOFF	
Disable write buffers (CDC chip). This is not supported 
for OS/2 ODI. CDCOFF disables the write buffers on the Intel CDC 
chip. The default is Not Present.

NAME  
Name of the Logical Board Number. Identifies the logical board
for different FRAME types. Any ASCII characters can be used;
the default is none (no NAME).

Note:
All of the keywords available to the Novell ODI client drivers 
may be automatically activated by creating or modifying the 
NET.CFG file. Please see Appendix C for sample NET.CFG files.
Also see the READVLM.TXT file for VLM keywords.

NDIS 2.01 Driver Keywords
=================================

TXBUFFERS 
Transmit Buffers. Transmit and Receive buffer sizes may be
increased or decreased using Transmit and Receive Buffer
keywords. Each network operating system environment has
different formats and syntax for interrupt settings. This number
should be a factor of 2; the default size is 4.

RXBUFFERS 
Receive Buffers. Transmit and Receive buffer sizes may be
increased or decreased using Transmit and Receive Buffer
keywords. Each network operating system environment has different
formats and syntax for interrupt settings. This number should be
a factor of 2; the default size is 4.

MAXMULTICASTS 
Maximum Multicasts. This designates the maximum number of
multicast addresses for the device. The default is 10.

NETADDRESS 
Net Address. This keyword specifies or overwrites the IEEE or 
manufacturer address. This must be edited in PROTOCOL.INI 
or NT registry. This value can be any valid IEEE address or Not 
Present (the default).

Note:
All of the keywords available to the NDIS 2.01 driver may be 
activated by configuring the PROTOCOL.INI file in some 
operating system environments or by selecting the options through 
a dialog box in other operating systems.

NDIS 3.0 Driver Keywords
=====================================

NETADDRESS	
Net Address. This keyword specifies or overwrites the IEEE or 
manufacturer address. This must be edited in PROTOCOL.INI or NT 
registry. This value can be any valid IEEE address or Not Present 
(the default).

Packet Driver Keywords
===============================

[-n]	Packet converter. The -n option converts 
Ethernet type 8137 and Novell PSO-like packets. This is required 
if you use a standard boot ROM, the Packet driver, and the IPX 
included in the Packet Driver package to load the drivers from 
the boot image file. The default is Not Enabled.

[-d]	Initialization delay. The -d option delays 
initialization. This will keep the initialization code after 
loading. This is required for boot ROM support. The default is 
Not Enabled.

[-w]	Windows option. The -w switch is used for 
Windows. Install the Packet Driver before running MS-Windows. 
This does not prevent Windows from swapping the network 
application out of memory, it simply detects when that has 
happened, and drops the packet. See the WINPKT Utility for 
enhanced mode applications. The default is Not Enabled.

<INT=packet_int_no>	Software Interrupt. This is the software 
interrupt used to communicate with the packet driver. See 
Appendix A of the install.doc file for more details. This can 
range from 0x60-0x66 inclusive. The default is 0x60.

[IRQ=int_no]	Interrupt. See the Common Keywords section in 
Appendix A.

[IOADDR=io_addr] I/O Address. See the Common Keywords section in 
Appendix A.

[DMA=dma_no	DMA. See the Common Keywords section in Appendix 
A.

Note:
Keyword options for the Packet driver may be activated by loading 
the driver at the command line or loading the driver from a batch 
file like AUTOEXEC.BAT.

=================================================================
APPENDIX B - DMI Installation
=================================================================

DMI support has been added to the ODI (DOS/OS2), NDIS2 (DOS/OS2), 
and WFW NDIS 3 Drivers. The following procedure can be used to 
manually install the required DMI files (see item #2 below for a 
description of the automated DMI installation utility):

- Install your Microdyne network driver for DOS, OS/2 or Windows 
using conventional installation procedures.

- Install the DMI package (SL, browser, etc) for the OS you plan 
to use. If you do not have a specific DMI package for your
system, one can be obtained from the Desktop Management Task
Force (DMTF). They can be contacted at:

          Desktop Management Task Force
          M/S JF2-51
          2111 N.E. 25th Avenue
          Hillsboro, OR  97124
          PHONE:(503) 696-9300
          FAX:  (503) 696-9027

- From the DMI disk, copy the files required for the operating 
system you are using to the corresponding DMI directory.

for OS/2:
        copy a:\dmi\pcnet.mif c:\dmi\os2\bin\mifs
        copy a:\dmi\pcnet.dll c:\dmi\os2\bin

for DOS and Windows with real mode (ND2/ODI) Pcnet driver installed:
        copy a:\dmi\pcnet.mif c:\dmi\dos\mifs
        copy a:\dmi\pcnet.ovl c:\dmi\dos\bin

for Windows for Workgroups 3.11 with NDIS 3 driver installed:
        copy a:\dmi\pcnet.mif c:\dmi\dos\mifs
        copy a:\dmi\pcnet.exe c:\dmi\win16\bin

- Edit the pcnet.mif file's 'Serial Number', 'Installation' and
'Connector Type' fields.

- Install the pcnet.mif file into the SL's database. In the 
simplest case, this can be done using the DMTF's browser.

- To verify that the installation was successfull, use your DMI
management application to explore the Pcnet information.

The manual procedure above can be effected using the DMINSTL.EXE 
program provided on the DMI disk in the A:\DMI subdirectory. It 
copies the necessary files. To invoke the program, place a copy
of the DMI disk into drive A:. Make sure the diskette is not
write protected. Enter the following commands:
    - C:>A:           <Enter>
    - A:\>CD \DMI     <Enter>
    - A:\DMI>DMINSTL  <Enter>

When the main panel is displayed, enter the serial number of 
distribution package you received (if none is provided, the field 
can be left blank). Press the Enter key or the Tab key to advance 
to the next field.
    
The Installation Date field displays the current system time by 
default. If you wish to change the value of this field, use the
left and right arrow keys to move about the text and type over
the old values. Note that DMINSTL uses the TZ environment
variable to determine the offset from GMT. If this variable is
not set, DMINSTL assumes PDT (e.g. an offset of +480).

Advancing to the Connector Type field, you can change its value 
by pressing the Alt-F4 key combination and selecting the
connector type in use on your system. To highlight different
values, use the up and down arrow keys. To select one of the
values, press the Enter key. To hide the pull-down list and leave
the selection unchanged, use the Esc key.

Finally, advancing to the Target Driver field, you can inform the
installation utility regarding which drivers you intend to run on 
the system. The choices are NDIS 3 for native operation under
Windows for Workgroups v3.11. Or, you can select NDIS 2 / ODI for
operation in DOS or in WFW 3.11 using real mode DOS drivers.

Once the information has been entered, press the F10 key to
initiate the installation. Pressing Alt-F4 anytime prior to
pressing F10 will cancel the installation and return to DOS.

The DMI installation utility will invoke the DMI SL if found to
assist with the installation. If the SL cannot be invoked,
DMINSTL will copy the necessary files into the DMI directory
structure which it will create if not already present on drive
C:. The next time the SL is loaded, it will complete the
installation on behalf of DMINSTL.

Note that DMINSTL expects to be executed out of the same
directory that contains the files:
      PCNET.MIF
      PCNET.EXE
      PCNET.OVL

*IMPORTANT*
To avoid conflicts with certain TSRs, it is best to run DMINSTL
in a minimally configured system. In other words, booting to a
plain vanilla DOS system (e.g. no CONFIG.SYS and AUTOEXEC.BAT
files) is preferred.
    

NOTES
~~~~~
When invoking the DMI Service Layer (SL.EXE), set the overlay
buffer size to 10k as follows:
      C:\DMI\DOS\BIN> SL o=10 <Enter>


=================================================================
APPENDIX C - NET.CFG Options For Novell NetWare
=================================================================

If a driver configuration is different from the default settings,
or if you are using multiple protocols, you should create a
NET.CFG file.

The NET.CFG file is a configuration file containing section 
headings and options that deviate from the established defaults 
of the ODI software. See the OS documentation specific to your 
protocol for additional NET.CFG information.
Use any DOS text editor to create the file. Specify only options 
that will change from the defaults.

Conventions

o  Main section headings must be left-justified and are not case 
sensitive.
o  The heading must precede the options you want to include in 
that section.
o  Options are not case sensitive and must be preceded by a tab 
or hard spaces.
o  Precede comments with a semicolon (;) and end each line with 
a hard return.
o  Write all numbers in decimal notation except where noted 
otherwise.

Options

The chart below lists the driver options defined by the DOS ODI 
software. The options available for the driver (PCNTNW and IPX) 
protocol stack are shown in a sample NET.CFG file. Protocol 
stacks other than IPX may have additional options not listed 
here. Refer to that protocol's documentation for more 
information.

In this chart, the main NET.CFG section headings are set off with 
a semicolon (;). NET.CFG options are listed under each heading 
and indented. The list of options shown in the chart below is not 
exhaustive. See the Software Keywords section in Appendix A for 
more information on which keywords may be used in NET.CFG.

; This is for a workstation
; Link Driver  drivername
	DMA [#1|#2] channel_number
	INT [#1|#2] interrupt_request_number
	MEM [#1|#2] hex_starting_address [hex_length]
	PORT [#1|#2] hex_starting_address [hex_number_of_ports]
	NODE ADDRESS hex_address
	SLOT number
	FRAME frame_type
	CDCOFF
	PROTOCOL name hex_protocol_ID frame_type
	SAPS number
	LINK STATIONS number
	ALTERNATE
	MAX FRAME SIZE number
	CONNECTOR DIX

; Link Support
	BUFFERS communication_number [size]
	MEMPOOL number[k]
; Protocol  protocol name
	BIND #board_number

Note:
The drivername here should be PCNTNW.

The PCNTNW driver has these NET.CFG options available for ISA 
buses:

o	DMA (3, 5, 6, 7)
o	INT (3-5, 9-12, 15)
o	PORT (200H-3A0H)
o	NODE ADDRESS
o	FRAME
o	PROTOCOL (IPX)
o	FASTISA This mode increases the performance of the NE2500 in
	ISA machines by reducing the memory read and write cycle 
	time. Older machines with slower memory may not support this 
	mode.

DMA, INT, and PORT are not required for the driver. In some 
cases, using these keywords would be a violation of the bus 
specification. Otherwise, all other keywords may be used. Those 
keywords listed in the Software Keywords section (Appendix A) may 
also be used in the NET.CFG.

		NET.CFG For Adapter Cards

		LINK DRIVER PCNTNW
			;Specify bus type for the NE5500 adapter.
			;Use PNP for the NE2500.
			BUSTYPE PCI
			;To change FRAME type to Ethernet_II
			FRAME Ethernet_II
			PROTOCOL IPX 8137 ETHERNET_II
			;(For the NE5500.)
			CDCOFF
			;For the NE2500plus/NE5500plus
			FDUP = UTP
		NetWare DOS Requester
			FIRST NETWORK DRIVE = F

Note:
Comment lines are proceeded by a semicolon (;) before each 
option line to indicate the option change.

Please refer to READVLM.TXT for valid NET.CFG entries for VLMs

=================================================================
APPENDIX D LAN Manager File Examples
=================================================================
File Examples
-------------
During installation, LAN Manager will automatically make 
modifications to the CONFIG.SYS, AUTOEXEC.BAT, and 
PROTOCOL.INI files. Below are sample files for a Microdyne ISA
adapter card.

	CONFIG.SYS
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\PCNET\PCNTND.DOS

	AUTOEXEC.BAT
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET START WORKSTATION
LOAD NETBEUI
NET LOGON bill.gates 

	PROTOCOL.INI

[PROTMAN]
		DRIVERNAME = PROTMAN$
	DYNAMIC	= YES
	PRIORITY	= NETBEUI

[NETBEUI_XIF]
	Drivername = netbeui$
	SESSIONS	= 6
	NCBS		= 12
	BINDINGS	= PCNTND_NIF
	LANABASE	= 0

[PCNTND_NIF]

;-----------------------------------------------------------;
; 
; Microdyne NE2500/NE5500 Series Ethernet Adapter
;-----------------------------------------------------------;

	DriverName = PCNTND$
	IOAddress  = 0x0300
	Interrupt  = 4
	DMAChannel = 5

Keyword Examples

To change the transmit and receive buffers, insert the following 
statements in the PROTOCOL.INI file (located in the Microdyne 
Driver (PCNTND) directory):

	RXBUFFERS	= 4
	TXBUFFERS	= 4


=================================================================
APPENDIX E - Installing A ROM 
=================================================================
A Universal Remote Boot ROM or a ROMshield anti-virus ROM may be
optionally installed in your NE2500, NE2500T, NE2500plus, 
NE2500plusT, or NE5500plus board. Both types on ROMs are
available from Microdyne.

A Universal Boot ROM permits remote booting from the following 
devices:

o  Novell Server
o  Microsoft LAN Manager (Server)
o  IBM LAN Server.

The Boot ROM is based on the IBM RPL protocol. To install the 
universal Boot ROM, follow the steps listed below:

1) Insert the Boot ROM supplied by Microdyne into the 28-pin 
socket.

2) Run Jumpstart by typing (at the system prompt):

		jmpstart
	Then press <Enter>.

o  Choose the Configuration option from the Main Menu. Then 
set the I/O base address, IRQ channel, DMA channel, and Boot ROM 
address.

o  Exit from Jumpstart.

3) Follow the Boot ROM installation procedure outlined in the 
Novell Installation Manual.

4) If you are going to do a remote boot for an OS/2 workstation 
on Microsoft LAN Manager, follow the steps listed below prior to 
performing a remote boot from the server. Otherwise, go to step 5 
below to continue.

o  Edit the file os213bb.cnf. The path to this file is:

		C:\LANMAN\RPL\BBLOCK\NETBEUI\PCNTD

Notes:
1) The file os213bb.cnf is a remote boot configuration file for 
OS/2 version 1.3. If you are running a different version of OS/2 
on your workstation, the file name may be slightly different.

2) In the path for the os213bb.cnf file, NETBEUI may be 
different depending on which protocol you are using.
Edit the following line in the os213bb.cnf file:

		DRV BBLOCK\NDIS\pcntnd.DOS ~ ~ ~

Note:
The DRV line shown above is the default. The tildes (~) 
represent parameter fields. By default a tilde means 0.
Change the second tilde to a value of 10.
The DRV line should now look like:

		DRV BBLOCK\NDIS\pcntnd.DOS ~ 10 ~

	Save the os213bb.cnf file.

5) Next, perform a remote boot from the server. The diskless 
workstation will display some sign on messages followed by this 
display:
	To boot from Novell Server,			press 1
	To boot from IBM LAN Server,			press 2
	To boot from Microsoft LAN Manager,		press 3
	To boot from the first available server,	press 4
	If no selection within 30 seconds, will use choice 4
	Please, make your choice now!

Make a selection by pressing the appropriate number. If 
nothing is selected within 30 seconds, the appropriate server 
will be selected by auto detect. Then the remote boot process is 
started.

Warning:
This version of Boot ROM does not display the Boot from Network 
(Y/N) message. Make sure you do not have a bootable device in 
the system (i.e., no A or C drive). In a diskless system 
without a bootable device, this Boot ROM will take over the boot 
process.

=================================================================
APPENDIX F - Help
=================================================================

Helpful Hints

1) If you are using a PCI machine with the Intel CDC chipset, 
use the keyword CDCOFF in the load line for your driver. For 
example,

	LOAD PCNTNW FRAME=your_frame_type CDCOFF

2) For the NE2500plus/NE5500plus Series, you may enable full
duplex with the statement FDUP = (UTP, AUI, OFF)

2) Enable the slot before installing an NE5500 in your system. 
Use the PCI SETUP utility to enable the board.

3) This example shows multiple Load statements for a single 
server with three Microdyne boards. Note the first board is a 
NE5500, the second a NE5500plus and the third is a NE2500.

load PCNTNW FRAME=Ethernet_802.2 BOARD=1 NAME=Ethernet_802.2 
CDCOFF FDUP=UTP
bind IPX to Ethernet_802.2 net=A0
load PCNTNW FRAME=Ethernet_802.3 BOARD=1 NAME=Ethernet_802.3 
CDCOFF FDUP=UTP
bind IPX to Ethernet_802.3 net=A2

load PCNTNW FRAME=Ethernet_802.2 BOARD=2 NAME=Ethernet_802.2 
CDCOFF 
bind IPX to Ethernet_802.2 net=B0
load PCNTNW FRAME=Ethernet_802.3 BOARD=2 NAME=Ethernet_802.3 
CDCOFF
bind IPX to Ethernet_802.3 net=B2
load PCNTNW FRAME=Ethernet_II BOARD=2 NAME=Ethernet_II CDCOFF
bind IPX to Ethernet_II net=B4
load PCNTNW FRAME=Ethernet_SNAP BOARD=2 NAME=Ethernet_SNAP CDCOFF
bind IPX to Ethernet_SNAP net=B6

load PCNTNW FRAME=Ethernet_802.2 PORT=300 INT=3 DMA=3 
NAME=Ethrnt_802.2
bind IPX to Ethrnt_802.2 net=C0
load PCNTNW FRAME=Ethernet_802.2 PORT=300 INT=3 DMA=3 
NAME=Ethrnt_802.3
bind IPX to Ethrnt_802.3 net=C2
load PCNTNW FRAME=Ethernet_II PORT=300 INT=3 DMA=3 NAME=Ethrnt_II
bind IPX to Ethrnt_II net=C4
load PCNTNW FRAME=Ethernet_SNAP PORT=300 INT=3 DMA=3 
NAME=Ethrnt_SNAP
bind IPX to Ethrnt_SNAP net=C6


Technical Support

You can reach us at:

		Microdyne Corporation
		3601 Eisenhower Avenue
		Alexandria, Virginia 22304  U.S.A.

Tel: (800) 255-3967                     FAX: (703) 683-8924
Tel: (703) 960-9661 (International)     BBS: (703) 960-8509

Microdyne's BBS supports V.32, V.42 bis, and MNP Level 5. To 
access the bulletin board, you will need a modem with the 
following settings.

	Baud Rate:      1200, 2400, 4800, or 9600
	Parity:         None
	Word length     8-bit
	Stop bit:       1

Getting Help

We can provide the best service if you have the following 
information ready before calling.

Board Configuration Information
Board configuration? Other boards installed in the system? Board 
settings and interrupt options?

Network Information
Network operating system and version, server configuration? 
Network topology: type of cable being used, size of network, 
number of workstations in network, etc.

Computer Information
Manufacturer, model number, operating system used on the 
computer?

History of the Problem
The symptoms of the problem? Did the board work for a period of 
time or fail immediately after installation? Was any workstation 
option changed (hardware or software) prior to the problem 
appearing?

Returning Defective Products

If you have a defective board, contact Microdynes Technical 
Support Group. They will verify that the board is defective and 
refer you to the RMA department.


FCC Notice

NOTE: This equipment has been tested and found to comply with the 
limits for a Class A digital device pursuant to Part 15 of the 
FCC Rules. These limits are designed to provide reasonable 
protection against harmful interference when the equipment is 
operated in a commercial environment. This equipment generates, 
uses, and can radiate radio frequency energy and, if not 
installed and used in accordance with the instruction manual, may 
cause harmful interference to radio communications. Operation of 
this equipment in a residential area is likely to cause harmful 
interference in which case YOU will be required to correct the 
interference at your own expense.

Changes or modifications not expressly approved by Microdyne, as 
the manufacturer, could void your right to operate this 
equipment. Contact Microdyne's Technical Support Group if you 
have any questions regarding this policy.

DECLARATION OF CONFORMITY
We, Microdyne Corporation, 
3601 Eisenhower Ave., Suite 300, Alexandria, VA 22304
declare under our sole responsibility that the product(s),
	NE2500plus, NE2500plusT  Ethernet Adapters,
to which this declaration relate(s) is in conformity with the 
following standard(s) or other normative document(s)
	EN 60950:1992
	EN 55022:1987
	EN 50082-1:1992
		IEC 801-2:1991
		IEC 801-3:1984
		IEC 801-4:1988
following the provisions of  the 73/23/EEC and 89/336/EEC Directives. 
P/N: 4230712-00 Rev. A




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