M16ANDIS.OS2). Intel ETHEREXPRESS PRO/100

Configuration Reference

NET.CFG

M16AODI.OS2

Network configuration file

Intel ODI driver for OS/2

Most installations will be able to use the settings implemented in the

NET.CFG file by the Intel Installation Program. If any parameters need to be changed, use an ASCII text editor to open and modify the

NET.CFG file and insert the appropriate keywords and values after the line

LINK DRIVER M16AODI

Parameters can also be implemented on the command line. Keyword syntax can be found below. Keywords are not case sensitive. A

Keyword Alphabetical Reference follows the discussion of keyword syntax.

NET.CFG Example

LINK DRIVER M16AODI

INT 5

PORT 280

MEM D2000

M16AODI.OS2 Keywords

Keyword Default Valid Values

FULLDUPLEX

INTERRUPT

IOADDRESS

IOWAITSTATES

LINESPEED

LINKDISABLE

NOLED

SOCKET

WORDSIZE

(NO KEYWORD = FULL-DUPLEX DISABLED)

5

320

(3 - 15)

(240 - 380)

0

AUTO

(1 - 3)

(10 OR 100)

(NO KEYWORD = LINK INTEGRITY EN

ABLED)

LINK DRIVER M16AODI (REQUIRED FIRST ITEM IN NET.CFG)

MEMORY D2000 (C0000 - EE000)

MEMWAITSTATES

MODE

0

MEM

(1 - 3)

(MEM OR IO)

NOCHECK

VERI-

NOEARLYRX

(NO KEYWORD = ADAPTER RESOURCE

ABLED)

FICATION ENABLED)

(NO KEYWORD = EARLY RECEIVE EN

NOEARLYTX (NO KEYWORD = EARLY TRANSMIT EN

ABLED)

(NO KEYWORD = LEDS ENABLED)

AUTO (1 - 4)

16 (8 OR 16)

NDIS 2.0.1 Settings (for drivers M16ANDIS.EXE and

M16ANDIS.OS2)

Custom parameters for the NDIS driver can be set up with the Intel

Installation Program or entered manually, using an ASCII editor, in the PROTOCOL.INI file. If Card and Socket Services are being used, the Intel M16ACFG.EXE resource manager program will

75

C H A P T E R 3 implement the appropriate parameters when the network driver is loaded.

NDIS 2.0.1 DOS Driver Configuration Notes

The DOS NDIS driver M16ANDIS.EXE conforms to the 3Com/

Microsoft LAN Manager Network Driver Interface Specification

(NDIS) version 2.0.1. It is a DOS-based executable terminate-andstay-resident (TSR) program that will configure itself according to the options specified in the PROTOCOL.INI file, which is supplied on the

Network Drivers Disk.

The files required for using M16ANDIS.EXE are:

PROTOCOL.INI

M16ADOS.NIF

M16ANDIS.EXE

Configuration and binding information file

Intel installation file for Microsoft LAN

Manager

Intel DOS NDIS 2.0.1 driver

If Card and Socket Services are loaded, the Intel resource manager

M16ACFG.EXE must be run before M16ANDIS.EXE to establish connection between the PRO/100 PC Card and the computer.

Most installations will be able to use the settings implemented in the

PROTOCOL.INI file by the Intel Installation Program. If any parameters need to be changed, use an ASCII text editor to modify the

PROTOCOL.INI file with the appropriate keywords and values.

Keyword syntax for PROTOCOL.INI can be found below. Keywords are not case sensitive, and can be abbreviated to a unique sequence of initial characters (for example, IN for INTERRUPT, IO for

IOADDRESS). A Keyword Alphabetical Reference follows the keyword listings.

NDIS 2.0.1 OS/2 Driver Configuration Notes

The OS/2 NDIS driver M16ANDIS.OS2 conforms to the 3Com/

Microsoft LAN Manager Network Driver Interface Specification

(NDIS) version 2.0.1. It is an IBM OS/2-based device driver for use with OS/2 versions 2.0 and later.

The files required for using M16ANDIS.OS2 are:

PROTOCOL.INI

M16AOS2.NIF

Configuration and binding information file

Intel installation file for Microsoft

LAN Manager

76

Configuration Reference

M16ANDIS.OS2

Intel OS/2 NDIS 2.0.1 driver

Most installations will be able to use the settings implemented in the

PROTOCOL.INI file by the Intel Installation Program. If any parameters need to be changed, use an ASCII text editor to modify the

PROTOCOL.INI file with the appropriate keywords and values.

Keyword syntax for PROTOCOL.INI can be found below. Keywords are not case sensitive, and can be abbreviated to a unique sequence of initial characters (for example, IN for INTERRUPT, IO for

IOADDRESS). A Keyword Alphabetical Reference follows the keyword listings.

PROTOCOL.INI Example

[INTELNET]

DRIVERNAME=INTEL$

MEM=0XD2000

MODE=IO

NDIS 2.0.1 Keywords (M16ANDIS.EXE and M16ANDIS.OS2)

Keyword Default Valid Values

DRIVERNAME=INTEL$ (REQUIRED FIRST ITEM IN PROTOCOL.INI)

FULLDUPLEX

INTERRUPT=

IOADDRESS=

IOWAITSTATES=

LINESPEED=

LINKDISABLE

MEMORY=

MEMWAITSTATES=

MODE=

NOCHECK

NOEARLYRX

NOEARLYTX

NOLED

SOCKET=

WORDSIZE=

(NO KEYWORD = FULL-DUPLEX DISABLED)

5 (3 - 15)

320

0

(240 - 380)

(1 - 3)

AUTO (10 OR 100)

(NO KEYWORD = LINK INTEGRITY EN-

ABLED)

D2000

0

MEM

(C0000 TO EE000)

(1 - 3)

(MEM OR IO)

(NO KEYWORD = ADAPTER RESOURCE VERI

FICATION ENABLED)

(NO KEYWORD = EARLY RECEIVE EN

ABLED)

(NO KEYWORD = EARLY TRANSMIT EN

ABLED)

(NO KEYWORD = LEDS ENABLED)

AUTO (1 - 4)

16 (8 OR 16)

NDIS Driver Example - MS-DOS

The following example illustrates the use of M16ACFG.EXE with the

M16ANDIS.EXE driver in a CONFIG.SYS file supporting Microsoft

LAN Manager:

DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /

I:C:\LANMAN.DOS

DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\INTEL\M16ACFG.EXE

DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\INTEL\M16ANDIS.EXE

DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP\TCPDRV.DOS

I:C:\LANMAN.DOS

77