***********************************************************
***********************************************************
***********************************************************

INSTALLING THE NDIS DRIVER SOFTWARE FOR LAN MANAGER

The file describes the installation instructions for
the DCA 10BASE NDIS driver.

The 10BASE NDIS driver supports the Microsoft/3Com Network 
Driver Interface Specification version 1.01 for network adapter
drivers. Therefore it interoperates with the Microsoft 
Netbeui protocol stack.

Required hardware

One of the following adapters:
* DCA 10BASE Coaxial ISA Adapter
* DCA 10BASE Coaxial Micro Channel Adapter
* DCA 10BASE Twisted Pair ISA Adapter
* DCA 10BASE Fiber Optic ISA Adapter


Required documentation

*  See the DCA 10BASE Adapter Hardware Installation Guide for 
   information about the DCA 10BASE Adapters.

Required software

* LAN Manager version 2.0 or later.  For DOS and OS/2
requirements, refer to the installation documentation
provided with your network operating system and protocol
stack.

This file contains the following sections.  These sections
are separated by asterisks in this document.

* Installing the driver while installing LAN Manager
* Installing the driver after installing LAN Manager
* MAC586 Keyword Descriptions
* Installation Failure Messages
* Fatal Error Messages
* Trademarks

************************************************************
************************************************************

Installation Procedures

You can install the NDIS driver during or after the LAN
Manager software installation.  Installing the NDIS driver
involves using the LAN Manager Setup program to import the
driver from the distribution diskette, then installing it in
your system.

************************************************************

Installing the driver while installing LAN Manager

To install the NDIS driver while you're installing the LAN
Manager software in an MS-DOS workstation or an OS/2
workstation or server, complete the following steps.  When
you have completed the installation, the adapter will be
configured for default DRIVERNAME, INTERRUPT, IOADDRESS,
MAXTRANSMITS, and RAM values.  These keywords and their
values are located in the [MAC586_NIF] section of the
PROTOCOL.INI file.  To modify this default configuration
after completing the installation, use your ASCII text
editor to change keyword entries in the [MAC586_NIF] section
of your PROTOCOL.INI file.  These keywords and parameters
are listed in Table 1.

NOTE: If you are installing the driver on a Micro Channel
machine, run the system's Reference Diskette with the
appropriate .ADF file to specify the values for the
INTERRUPT, IOADDRESS, and RAM parameters before completing
the following steps.  See the DCA 10BASE Adapter Hardware
Installation Guide for complete instructions.

1.  Make a working copy of the 10BASE driver distribution
diskette.

2.  Install Microsoft LAN Manager as described in the
Microsoft LAN Manager Installation Guide & Network Device
Driver Guide.

3.  When the program displays a dialog box asking if you
want to import network device drivers, select Yes.  The
program displays a dialog box that asks you to insert a
diskette with the additional network drivers.

4.  Insert the adapter driver distribution diskette in drive
A and select OK.  The program displays the Import Network
Drivers dialog box.

5.  At the Import Network Drivers dialog box, select the DCA
adapter and the Netbeui protocol.  Then, select OK.  The
program displays a dialog box asking if you want to import
other network drivers.

6.  Select No to exit the Import Network Drivers dialog box.

7.  Continue installing LAN Manager as described in the
Microsoft LAN Manager Installation Guide & network Device
Driver Guide.

8.  At the Network drivers dialog box, select the Add driver
option.  The program displays the DCA adapter in the Network
configuration list box.

9.  Press [Tab] to move to the Protocols list box.  Then,
select the Netbeui protocol.

10.  Select the Add protocol option.  The program displays
the Netbeui protocol in the Network configuration list box.

11.  Proceed with the LAN Manager installation as described
in the Microsoft LAN Manager Installation Guide & Network
Device Driver Guide.

12.  Once the LAN MANAGER is installed, using an editor you 
     must add a line to the Netbeui section of the protocol.ini 
     file which sets the MAXTRANSMITS=1.  The path for the 
     for the protocol.ini file under OS/2 is: \LANMAN\DRIVERS.
     The path for the protocol.ini file under DOS is: 
     \LANMAN.DOS\DRIVERS.	

[NETBEUI_XIF]
    drivername = NETBEUI$
    bindings = MAC586
    MAXTRANSMITS=1
    mintransmits=1


 

************************************************************

Installing the driver after installing LAN Manager

You can install the NDIS driver after you install the LAN
Manager software in an MS-DOS workstation or OS/2
workstation or server, as described in the Microsoft LAN
Manager Installation Guide & Network Device Driver Guide.
When you have completed the installation, the adapter will
be configured for default DRIVERNAME, INTERRUPT, IOADDRESS,
MAXTRANSMITS, and RAM values.  These keywords and their
values are located in the [MAC586_NIF] section of the
PROTOCOL.INI file.  To modify this default configuration
after completing the installation, use your ASCII text
editor to change keyword entries in the [MAC586_NIF] section
of your PROTOCOL.INI file.  These keywords and parameters
are listed in Table 1.

NOTE: If you are installing the driver on a Micro Channel
machine, run the system's Reference Diskette with the
appropriate .ADF file to specify the values for the
INTERRUPT, IOADDRESS, and RAM parameters before completing
the following steps.  See the DCA 10BASE Adapter Hardware
Installation Guide for complete instructions.

1.  Make a working copy of the 10BASE driver distribution
diskette.

2.  At the Actions menu in the Setup program, select Import.
The program displays a dialog box that shows the current
diskette drive.

3.  To use the drive that is shown for inserting the
distribution diskette, select OK.  To use a different drive,
type the drive letter and select OK.

4.  Insert the distribution diskette in the appropriate
drive and select OK.  The program displays the Import
Network Drivers dialog box.

5.  At the Import Network drivers dialog box, select the DCA
adapter and the Netbeui protocol.  Then, select OK.  The
program displays a dialog box asking if you want to import
other network drivers.

6.  Select No to exit the Network Drivers dialog box.

7.  Select View/modify from the Actions menu.  The system
displays the Primary Parameters dialog box.

8.  Select OK to skip this dialog box and display the
Network Drivers dialog box.

9.  Select the Add driver option.  The program displays the
DCA adapter in the Network configuration list box.

10.  Press [Tab] to move to the Protocols list box.  Then,
select the Netbeui protocol.

11.  Select the Add protocol option.  The program displays
the Netbeui protocol in the Network configuration list box.

12.  Select the Done option to install the driver and return
to the Setup program's main screen.

13.  Once the LAN MANAGER is installed, using an editor you 
     must add a line to the Netbeui section of the protocol.ini 
     file which sets the MAXTRANSMITS=1.  The path for the 
     for the protocol.ini file under OS/2 is: \LANMAN\DRIVERS.
     The path for the protocol.ini file under DOS is: 
     \LANMAN.DOS\DRIVERS.	

[NETBEUI_XIF]
    drivername = NETBEUI$
    bindings = MAC586
    MAXTRANSMITS=1
    mintransmits=1

************************************************************

MAC586 Keyword Descriptions

Table 1 describes possible keyword descriptions and
parameters for installing the driver.  The keywords
described here are DRIVERNAME, INTERRUPT,IOADDRESS,
MAXTRANSMITS, RAM, and SLOT.

NOTE: If you are installing the driver on a Micro Channel
machine, the values for the INTERRUPT, IOADDRESS, and RAM
parameters are entered when you run the .ADF file on the
PS/2 Reference Diskette.  See the DCA 10BASE Adapter
Hardware Installation Guide for complete instructions and
possible values.

NOTE: If you are installing the driver on a Micro Channel
machine, and you want to specify a value for the 
MAXTRANSMITS parameter, you must add the parameter and an
appropriate value to the PROTOCOL.INI file using an ASCII
text file editor.  A description of this parameter and
possible values for Micro Channel machines are given in
Table 1.

Table 1. MAC586 Keyword Descriptions
________________________________________________________
DRIVERNAME=MAC586$ identifies the device driver for the
network adapter.

INTERRUPT=n is the interrupt request (IRQ) level the MAC586
uses to interrupt the host machine.  The value of the
keyword may be 3, 4, 5, or 7 (plus a value of 2 for the DOS
version of the driver) for the IBM PC/AT (or compatible),
machines.  All other values are rejected.  The default is 3.
The OS/2 version of the MAC586 driver will not accept
INTERRUPT= 2.  This keyword is ignored on a Micro Channel
machine.

IOADDRESS=0xnnn is the base I/O port address used by the
MAC586 as an interface to the adapter.  The MAC586 uses a
range of 16 ports, starting at the base I/O address. On an 
ISA machine, this value must match the switch settings on 
the adapter.  See the DCA 10BASE Adapter Hardware Installation 
Guide for complete instructions about adjusting the adapter 
switch settings.  The value of this keyword may be 0x300, 0x310, 
0x330, or 0x350 for the 10BASE Twisted Pair ISA Adapter on an 
IBM PC/AT or compatible.  The value of this keyword may be 0x300 
or 0x310 for the 10BASE Coaxial ISA Adapter on an IBM PC/AT or
compatible.  All other values are rejected.  The default is
0x300.    This keyword is ignored on a Micro Channel machine.

RAM=0xnnnn is the base SEGMENT address of the dual-port
memory for the adapter.  The MAC586 uses this 16K memory 
block for data transfers.  For IBM PC/AT and compatible
machines, the following values are possible:

0xA000  0xCC00
0xA400  0xD000
0xA800  0xD400
0xAC00  0xD800
0xC000  0xDC00
0xC400  

If the machine has 512K of base RAM, the following values
are also available.

0x8000  0x9000
0x8400  0x9400
0x8800  0x9800	
0x8C00  0x9C00

All other values are rejected.  The default value is 0xD800.
This keyword is ignored on a Micro Channel machine.

SLOT=n specifies which slot in a Micro Channel machine the
10BASE adapter is located which the NDIS driver should
initialize.  Normally, if this keyword is not present, the
driver will find the adapter in any slot.  This parameter
should only be used if more than one 10BASE adapter is
present in the machine.  This keyword is ignored on an
ISA machine.

____________________________________________________________

************************************************************
************************************************************

Error Messages

Possible error messages and instructions for solving the
problem(s) are listed here.  Only the error messages
specific to the MAC586 drivers have been included.  Refer to
the documentation for the other products for other possible
error messages.

************************************************************

Installation Failure Messages

If driver installation fails, one of the following error
messages will appear.



Message

M586001: No module found with DRIVERNAME=MAC586$

Possible cause

The MAC586 NDIS driver could not locate the
DRIVERNAME=MAC586$ keyword in the PROTOCOL.INI file provided
by the Protocol Manager module.

Action

Make certain that a DRIVERNAME = MAC586$ statement has been
specified in the PROTOCOL.INI file.  The path for the
PROTOCOL.INI file is referenced in the CONFIG.SYS file's
DEVICE= statement for the Protocol Manager 
(PROTMAN.xxx /I:PATH).



Message

M586002: Protocol manager not installed

Possible cause

The MAC586 NDIS driver could not find the Protocol Manager
loaded in the system.

Action

Verify that a DEVICE= statement for the Protocol Manager
exists in the CONFIG.SYS file.  The path for the
PROTOCOL.INI file is referenced in the CONFIG.SYS file's
DEVICE= PATH\PROTMAN.xxx  /I:PATH statement.



Message

M586005: Interrupt value out of range

Possible cause

The value associated with the INTERRUPT= statement in
the MAC586 section of the PROTOCOL.INI file is not 2, 3, 5,
or 7 (on an ISA machine running DOS), or is not 3, 5, or 7
(on an ISA machine running OS/2).  INTERRUPT=2 will generate
this message on a machine running OS/2).  This message will
not appear on Micro Channel machines.

Action

Make certain that the value associated with the
INTERRUPT= keyword is one of these values.


Message

M586006: RAM value out of range

Possible cause

The value associated with the RAM= statement in the
MAC586 section of the PROTOCOL.INI file is not 0xA000,
0xA400, 0xA800, 0xAC00, 0xC000, 0xC400, 0xCC00, 0xD000, 
0xD400, 0xD800, or 0xDC00.  If your machine has 512K
of RAM, these values are also available: 0x8000, 0x8400,
0x8800, 0x8C00, 0x9000, 0x9400, 0x9800, 0x9C00.  This
message will not appear on Micro Channel machines.

Action

Make certain that the value associated with the RAM=
keyword is one of these values.



Message

M586007: IOADDRESS value out of range

Possible cause

The value associated with the IOADDRESS= keyword in the
MAC586 section of the PROTOCOL.INI file is not 0x300, 0x310,
0x330, or 0x350.  This message will not appear on Micro
Channel machines.

Action

Make certain that the value associated with the
IOADDRESS= keyword is one of these values.





Message

M586010: SLOT value out of range

Possible cause

The value associated with the SLOT= keyword in the
MAC586 section of the PROTOCOL.INI file is not 1 through 8.
This message will appear only on a Micro Channel machine.

Action

Make certain that the value associated with the SLOT=
keyword is one of these values.



Message

M586015: Too many values for INTERRUPT keyword
M586016: Too many values for RAM keyword
M586017: Too many values for IOADDRESS keyword
M586020: Too many values for SLOT keyword

Possible cause

More than one value has been entered for the associated
keyword in the MAC586 section of the PROTOCOL.INI file.
M586015, M586016, and M586017 will not appear on
Micro Channel machines.  M586020 appears on Micro Channel
machines only.

Action

Make certain that there is only one value for the
keyword, and that no hidden characters exist on the same
statement.



Message

M586030: Value is wrong type for INTERRUPT keyword
M586031: Value is wrong type for RAM keyword
M586032: Value is wrong type for IOADDRESS keyword
M586035: Value is wrong type for SLOT keyword

Possible cause

The values associated with the keyword in the MAC586 section 
of the PROTOCOL.INI file are the wrong type.  If you enter
hexadecimal data it must be preceded by 0x.
M586030, M586031, and M586032 will not appear on
Micro Channel machines.  M586035 appears on Micro Channel
machines only.

Action

Make certain that there is only one value for the
keyword, and that no hidden characters exist on the same
statement.



Message

M586045: DCA/10NET 10 megabit adapter not found

Possible cause

The MAC586 NDIS driver could not locate the 10BASE adapter
at the I/O address specified in the PROTOCOL.INI file on an
ISA machine.  On a Micro Channel machine, the MAC586 NDIS
driver could not locate the adapter in any slot.

Action

On an ISA machine, verify that a MAC586 board is installed,
the base address jumper setting does not conflict with any
other adapters in the machine, and the IOADDRESS parameter
in the PROTOCOL.INI file matches this jumper setting.  On a
Micro Channel machine, make certain that the adapter is
installed and has been configured using the PS/2
Configuration Utility on the Reference Diskette.



Message

M586050: GDT is not available

Possible cause

The number of Global Descriptor Table entries provided by
the OS/2 operating system cannot support all of the software
drivers installed in the machine.  This message will appear
only on machines running OS/2.

Action

Remove any other device drivers that are not absolutely
required.  You can do this by deleting the appropriate
DEVICE= statements from the CONFIG.SYS file, and rebooting
the machine.  If this does not solve the problem, the
operating system may be corrupted.  The MAC586 NDIS driver
requires 3 GDT selectors.



Message

M586051: Device Helper error

Possible cause

The OS/2 operating system has returned an error to the
MAC586 NDIS driver.  This message will appear only on
machines running OS/2.

Action

Verify that OS/2 is version 1.2 or later.  The operating
system may be corrupted or incompatible with version 1.01 of
the Microsoft Network Driver Interface Specification.  The
MAC586 driver follows this specification.


************************************************************

Fatal Error Messages

Message

PRO0028: HARDWARE FAILURE in binding <xxx> to MAC586

Possible cause

The MAC586 NDIS driver detected an error during intialization
of the 82586 LAN Controller.  As a result, the MAC586 NDIS
driver returned a HARDWARE FAILURE error to the Protocol
Manager during the "BIND" request.

Action

This may indicate that the board is not operational, or that the
configuration parameters (IOADDRESS, INTERRUPT) may conflict
with another board in the machine.  It may also mean that
the RAM parameter selected is not an available memory
window, or is used by another driver or board.



Message

PRO0028E: HARDWARE FAILURE in binding <xxx> to MAC586

Under the DOS LAN Manager, this error can occur when the
NETBIND utility binds the protocol stack to the NDIS driver.

Possible cause

The MAC586 NDIS driver detected an error during intialization
of the 82586 LAN Controller.  As a result, the MAC586 NDIS
driver returned a HARDWARE FAILURE error to the Protocol
Manager during the "BIND" request.

Action

This may indicate that the board is not operational, or that the
configuration parameters (IOADDRESS, INTERRUPT) may conflict
with another board in the machine.  It may also mean that
the RAM parameter selected is not an available memory
window, or is used by another driver or board.



Message

PRO0030: INTERRUPT CONFLICT in binding <xxx> to MAC586

Under OS/2 LAN Manager, this error can occur when the
NETWRKSTAT.SYS utility "binds" the protocol stack to the
NDIS driver.

Possible cause

The MAC586 NDIS driver detected that the interrupt selected
is already in use by another driver or adapter.  As a
result, the MAC586 NDIS driver returned an INTERRUPT
CONFLICT error to the Protocol Manager during the "BIND"
request.  This message appears only on machines running
OS/2.

Action

On an ISA machine, make sure that the value selected for
the INTERRUPT= statement in the MAC586 section of the
PROTOCOL.INI file does not conflict with other installed
boards or drivers.  If no INTERRUPT= statement exists, the
driver selects interrupt 3 (ISA machines only).



Message

PRO0032: INITIALIZATION FAILED in binding <xxx> to MAC586

Under OS/2 LAN Manager, this error can occur when the
NETWRKSTAT.SYS utility "binds" the protocol stack to the
NDIS driver.

Possible cause

The MAC586 NDIS driver received an error from the OS/2
operating system when performing the initialization.  As a
result, the MAC586 NDIS driver returned an INITIALIZATION
FAILED error to the Protocol Manager during the "BIND" request.
This message appears only on machines running OS/2.

Action

Verify that OS/2 is version 1.2 or later.  Your operating
system may be corrupted or may be incompatible with version
1.01 of the Microsoft Network Driver Interface
Specification.  The MAC586 NDIS driver follows this
specification.


************************************************************

Trademarks

10BASE is a trademark of Digital Communications Associates,
Inc.
DCA and 10NET are registered trademarks of Digital
Communications Associates, Inc.
3Com is a registered trademark of 3Com Corp.
Micro Channel, OS/2 and PS/2 are registered trademarks of
International Business Machines, Inc.
Microsoft is a registered trademark of Microsoft Corp.
***********************************************************
***********************************************************
***********************************************************

