The following is information from the READ.ME file on the 'IBM Ethernet Credit Card adapter II' card. This README file is
also valid for the Noteworthy Ethernet adapter.



ETHERNET CREDIT CARD ADAPTER II




1.1 ABOUT THIS FILE
____________________

This file contains additional information on the Ethernet Card Adapter.
It also describes the Card Services Aware device drivers, Connectivity
Enabler Software and Diagnostic Software that is included.



1.2 CARD SERVICES AWARE DEVICE DRIVERS
_______________________________________

The device drivers on this diskette (PCMNICCS.DOS, PCMDMCS.COM, PCMNICCS.OS2
and PCMDMCS.SYS) are Card Services Aware and can be used with Card Services
for configuration. The DOS drivers (PCMNICCS.DOS and PCMDMCS.COM) also can
be used with Connectivity Enabler software if Card Services is unavailable.

1.2.1 DOS NDIS DRIVER (PCMNICCS.DOS)

The Ethernet Credit Card Adapter's configuration information for the DOS NDIS
driver (PCMNICCS.DOS) is stored in the PROTOCOL.INI file. The section of the
PROTOCOL.INI file that contains configuration information for this card must
begin with "[PCMNICCS_NIF]". The valid entries in this file are listed
below.

[PCMNICCS_NIF]
DRIVERNAME = PCM_CS$
This constant line must always be present.
IOBASE = value (optional for Card Services environments)
where value is any base I/O address between 0x120 and 0x3C0
on a 0x20 byte increment.
The driver default value of 0x300 is suggested.
The leading "0x" for hex notation is required.
INTERRUPT = value (optional for Card Services environments)
where value is one of the following interrupts,
3, 4, 5, 7, 9, 10, 11
The driver default value of 5 is suggested.
RAMADDRESS = value
where value is one of the following memory segment addresses:
0, 0xC8000, 0xCC000, 0xD0000, 0xD4000, 0xD8000, 0xDC000
The driver default value is 0xD4000 if no keyword is supplied.
The leading "0x" for hex notation is required.
-If your machine has Card Services 2.0 installed and you want
Card Services to select your RAM location for you,
RAMADDRESS = 0 must be used.
NETADDRESS = (Optional parameter, use cannonical format)
PCMCIA
Use this keyword when using PCMCIA card and socket services.
This keyword signals the driver to look for Card Services
prior to looking for the adapter. Do not use when using a super
client driver or connectivity enabler.
SOCKET = n (Optional parameter, starting with 0)
This is the PCMCIA socket number in which the driver should
recognize the Ethernet card. This entry is required only if
you are using more than one Ethernet Credit Card Adapter.
If no slot is specified, the driver uses the first Ethernet
Credit Card Adapter found.
BUSSIZE8
This keyword signals the driver to use 8-bit data transfers.
This is required on machines that only have 8-bit data buses,
such as the Grid Convertible and the AST Pen Exec.

The following is an example of a PROTOCOL.INI entry for use with Card Ser-
vices environments:

[PCMNICCS_NIF]
DRIVERNAME=PCM_CS$
RAMADDRESS=0
INTERRUPT=5
IOBASE=0x300
PCMCIA


The following is an example of a PROTOCOL.INI entry used with an enabler:
[PCMNICCS_NIF]
DRIVERNAME=PCM_CS$
INTERRUPT=5
RAMADDRESS=0xD4000
IOBASE=0x300


1.2.2 DOS ODI DRIVER (PCMDMCS.COM)

The Ethernet Credit Card Adapter's configuration information for the NetWare
DOS ODI driver (PCMDMCS.COM) is stored in the NET.CFG file. The first line
of the NET.CFG file configuration information for this adapter must be "Link
Driver PCMDMCS". The valid entries in this file are listed below.

Link Driver PCMDMCS
PORT value (optional for Card Services environments)
where value is one of the following base I/O hex addresses:
200, 220, 240, 260, 280, 2A0, 2C0
300, 340, 360
INT value (optional for Card Services environments)
where value is one of the following interrupts,
3, 4, 5, 7, 9, 10, 11, 15
MEM value
where value is one of the following hex memory addresses:
FFFFFFFF, C0000, C4000, C8000, CC000
D0000, D4000, D8000, DC000
Use FFFFFFFF where Card Services will assign memory location.
FRAME ETHERNET_value
where value is one of the following frame types:
802.3 (Novell Netware 3.xx networks)
802.2 (Novell Netware 4.xx networks)
SNAP (Use when 802.2 SNAP extension is required)
II (Networks connected to DEC or using TCP/IP protocol)
The default is 802.2 if no keyword is supplied.
NODE ADDRESS value (optional for locally administered address)
where "value" is 12 hex bytes of node address
If a node address is not specified, the card must be installed
in the slot at startup.
PCMCIA
Use this keyword when using PCMCIA card and socket services.
This keyword signals the driver to look for Card Services
prior to looking for the adapter.
Do not use when using a super client driver or connectivity
enabler.
SLOT value (Optional parameter, starting with 0)
where value indicates which PCMCIA socket an Ethernet
card is located in, and is required only if you are using
more than one Ethernet Credit Card Adapter.
If no slot is specified, the driver uses the first Ethernet
PCMCIA Card found.


The following is an example NET.CFG entry for machines with Card Services 2.0
installed, and for a Netware 3.11 environment:

Link Driver PCMDMCS
MEM FFFFFFFF
FRAME ETHERNET_802.3
PCMCIA

The following is an example NET.CFG entry for use without Card Services with
Netware 4.0:

Link Driver PCMDMCS
Node Address 000123456789
INT 5
PORT 300
MEM D8000


1.2.3 WINDOWS FOR WORKGROUPS SUPPORT

An OEMSETUP.INF file is provided for Windows for Workgroups installations.
During Windows for Workgroups installation, use the Credit Card option
diskette for the automated installation utility.


1.2.4 OS/2 NDIS DRIVER (PCMNICCS.OS2)

The Ethernet Credit Card Adapter's configuration information for the OS2 NDIS
driver (PCMNICCS.OS2) is stored in the PROTOCOL.INI file. The section of the
PROTOCOL.INI file that contains configuration information for this card must
begin with "[PCMNICCS_NIF]". The valid entries in this file are listed
below.

[PCMNICCS_NIF]
DRIVERNAME = PCM_CS$
This constant line must always be present.

IOBASE = value (optional for Card Services environments)
where value is any base I/O address between 0x120 and 0x3C0
on a 0x20 byte increment.
The driver default value of 0x300 is suggested.
The leading "0x" for hex notation is required.

INTERRUPT = value (optional for Card Services environments)
where value is one of the following interrupts,
3, 4, 5, 7, 9, 10, 11
The driver default value of 5 is suggested.

RAMADDRESS = value
where value is one of the following memory segment addresses:
0, 0xC8000, 0xCC000, 0xD0000, 0xD4000, 0xD8000, 0xDC000
The driver default value is 0xD4000 if no keyword is supplied.
The leading "0x" for hex notation is required.
-If your machine has Card Services 2.0 installed and you want
Card Services to select your RAM location for you,
RAMADDRESS = 0 must be used.

NETADDRESS = (Optional parameter, use cannonical format)

PCMCIA
This keyword signals the driver to look for Card Services
prior to looking for the adapter.

SOCKET = n (Optional parameter, starting with 0)
This is the PCMCIA socket number in which the driver should
recognize the Ethernet card. This entry is required only if
you are using more than one Ethernet Credit Card Adapter.
If no slot is specified, the driver uses the first Ethernet
Credit Card Adapter found.

The following is an example of a PROTOCOL.INI entry for use with Card Ser-
vices environments:

[PCMNICCS_NIF]
DRIVERNAME=PCM_CS$
RAMADDRESS=0x0
INTERRUPT=5
IOBASE=0x300
PCMCIA


1.2.5 OS/2 ODI DRIVER (PCMDMCS.SYS)

The Ethernet Credit Card Adapter's configuration information for the NetWare
OS/2 ODI driver (PCMDMCS.SYS) is stored in the NET.CFG file. The first line
of the NET.CFG file configuration information for this adapter must be "Link
Driver PCMDMCS". The valid entries in this file are listed below.

Link Driver PCMDMCS
PORT value (optional for Card Services environments)
where value is one of the following base I/O hex addresses:
200, 220, 240, 260, 280, 2A0, 2C0
300, 340, 360

INT value (optional for Card Services environments)
where value is one of the following interrupts,
3, 4, 5, 7, 9, 10, 11, 15

MEM value
where value is one of the following hex memory addresses:
FFFFFFFF, C0000, C4000, C8000, CC000
D0000, D4000, D8000, DC000
Use FFFFFFFF where Card Services will assign memory location.

FRAME ETHERNET_value
where value is one of the following frame types:
802.3 (Novell Netware 3.xx networks)
802.2 (Novell Netware 4.xx networks)
SNAP (Use when 802.2 SNAP extension is required)
II (Networks connected to DEC or using TCP/IP protocol)
The default is 802.2 if no keyword is supplied.

NODE ADDRESS value (optional for locally administered address)
where "value" is 12 hex bytes of node address
If a node address is not specified, the card must be installed
in the slot at startup.

PCMCIA
This keyword signals the driver to look for Card Services
prior to looking for the adapter.


SLOT value (Optional parameter, starting with 0)
where value indicates which PCMCIA socket an Ethernet
card is located in, and is required only if you are using
more than one Ethernet Credit Card Adapter.
If no slot is specified, the driver uses the first Ethernet
PCMCIA Card found.

The following is an example NET.CFG entry for machines with Card Services 2.0
installed, and for a Netware 3.11 environment:

Link Driver PCMDMCS
MEM FFFFFFFF
FRAME ETHERNET_802.3
PCMCIA


1.2.6 MULTIPLE CARD SUPPORT

If multiple cards are installed in one system, make sure that the settings
for memory, interrupt and I/O for each adapter in the NET.CFG or
PROTOCOL.INI, do not conflict with the other adapters settings.

To enable the ODI driver to support multiple Ethernet Credit Card adapters in
one computer system, you should specify which socket the card is in in the
NET.CFG file. This is done with the "SLOT" keyword. For example,

SLOT 1

means the Ethernet Credit Card Adapter is in the second PCMCIA socket since
PCMCIA sockets are numbered beginning at zero.

To enable the NDIS driver to support multiple Ethernet Credit Card Adapters,
use the SOCKET keyword in the PROTOCOL.INI file. For example,

SOCKET = 0

means that the adapter is in the first PCMCIA socket.

If you are using two Ethernet Credit Card Adapters with OS/2 you must add an
INTERRUPT=i statement to the [PCMNICCS_nif2] section, where 'i' can be any
un-used interrupt. You can either use LAPS to do this or edit your
PROTOCOL.INI file. A sample follows:

[PCMNICCS_nif]
DriverName = PCM_CS$
RAMADDRESS = 0x0
PCMCIA

[PCMNICCS_nif2]
DriverName = PCM_CS$
RAMADDRESS = 0x0
INTERRUPT = 10
PCMCIA


1.2.7 ERROR INDICATIONS

The drivers signal the user when a Card Services call fails. The error signal
is an alternating beep. If you hear this sound, a problem is occurring during
initialization. Review your PROTOCOL.INI and CONFIG.SYS to verify proper
parameters. It is vitally important that memory areas requested are avail-
able. Memory contention can be a big problem. Check for any DOS programs
(e.g. EMM386.EXE) that may be conflicting with the memory requested.



1.3 POINT CONNECTIVITY ENABLER SOFTWARE FOR DOS
________________________________________________

If your machine is not configured with PCMCIA Card Services 2.0, a point
Connectivity Enabler is required to configure the PCMCIA socket hardware and
the Ethernet Credit Card Adapter hardware for operation. It is loaded as
a device driver in CONFIG.SYS BEFORE any Ethernet device drivers and AFTER
the Socket services device driver (if any). Once the Connectivity Enabler
has run, it removes itself from the system memory.

In systems without Card Services, it is essential that the correct enabler is
used and that the Ethernet communications software used agree on one param-
eter. The parameter is the Interrupt Request level (IRQ).

The default value of IRQ 5 is used by the software. This can be changed in
either PROTOCOL.INI for the NDIS driver or in NET.CFG for the Netware driver.
If you find that IRQ 5 does not function on your machine, IRQ 3 is another
common choice. Be sure to change both the enabler parameter and the
PROTOCOL.INI for the NDIS driver or the NET.CFG file for the Netware driver.

An example PROTOCOL.INI entry for changing the interrupt to 3 follows:

[PCMNICCS_NIF]
DRIVERNAME=PCM_CS$
INTERRUPT=3
RAMADDRESS=0xD4000
IOBASE=0x300

The following is a sample NET.CFG entry for changing the interrupt to 3:

Link Driver PCMDMCS
Node Address 000123456789
IRQ 3

There are three different point connectivity enablers included with this
package. They are:

o ETHERNET.SYS

o POINTETH.SYS

o TOSHETH.SYS


ET0.MSG contains the screen messages for the connectivity enablers.

ETHERNET.SYS is a Socket Services 1.01 interface enabler. It uses the socket
services that is included in some computers to configure the socket and card.
It is used on machines with DATABOOK PCMCIA controllers that support the
Socket Services 1.01 interface and not Card Services.


POINTETH.SYS is an enabler that communicates directly to Intel 82365SL (or
equivalent) hardware. This is a PCMCIA socket controller common in many
systems such as Dell, AST, and NCR Safari. This enabler should be used when
socket services does not exist on your machine or the version of socket ser-
vices on your machine does not communicate with ETHERNET.SYS correctly.

TOSHETH.SYS is an enabler that is used with the Toshiba T3300SL computer.



1.4 CONNECTIVITY ENABLER PARAMETERS FOR DOS
____________________________________________

Each enabler has parameters that allow the enabler to be customized to the
communication software. The parameters allow the selection of which socket
is used for the card and memory areas used by the card. The default parame-
ters should be sufficient for most users.



1.4.1 ETHERNET.SYS SYNTAX

Complete Syntax:

DEVICE=\path\ETHERNET.SYS [SA/SB] [IRQ=X] [DS=16/DS=8] [SRAM=XXXX] [IO=XXX]

SA/SB (Socket A or Socket B)
IRQ (Interrupt Level (PCMCIA controller interrupt))
DS (Data size (16 or 8 bit bus))
SRAM (Shared RAM address)
IO (Memory mapped I/O address)

Note: X is a hexadecimal number

Example:

DEVICE=C:\LAN\ETHERNET.SYS SA IRQ=3

This would configure an Ethernet credit card for socket A and the IRQ
value would be 3.

The default parameters are:

SA (Socket A)
IRQ=5 (PCMCIA controller interrupt at IRQ 5)
DS=16 (Data Bus size of 16 bits)
SRAM=D400 (Memory segment address)
IO=300 (Base I/O address)



1.4.2 POINTETH.SYS SYNTAX

Complete Syntax:

DEVICE=\path\POINTETH.SYS [SA/SB/SC/SD] [IRQ=X] [WS=0,1,2,3,4] [DS=16/DS=8]
[SRAM=XXXX] [IO=XXX] [PCIC=XXXX]
DEFAULTS
SA/SB/SC/SD (Socket A, B, C or D) - A
IRQ (Interrupt Level (PCMCIA controller interrupt)) - 5
WS (Wait state selection) - 0
DS (Data size (16 or 8 bit bus)) - 16
SRAM (Shared RAM segment address) - D400
IO (I/O base port address) - 300
PCIC - PC Card Interface Controller base I/O port - 03E0

note: X is a hexadecimal number

Example

DEVICE=C:\LAN\POINTETH.SYS SB WS=0 IO=320

This will configure an Ethernet credit card for socket B and no wait states.
The base I/O port address would be 320h.

The default parameters are:

SA (Socket A)
IRQ=5 (PCMCIA controller interrupt at IRQ 5)
WS=1 (1 wait state)
DS=16 (Data Bus size of 16 bits)
SRAM=D400 (Shared RAM at D400 in the workstation)
IO=300 (Base I/O port at 300h)


The PCIC parameter has been added to support the Port Replicator Model I,
that attaches to the IBM ThinkPad 750 notebook computer, and any other Intel
82365SL-based device that does not use 3E0 as its base I/O port. The Port
Replicator uses 3E2 as its I/O port base address.

Here is a sample invocation on a machine using the Port Replicator.
sample:

DEVICE=C:\LAN\POINTTR.SYS RS=16 PCIC=03E2


1.4.3 TOSHETH.SYS SYNTAX

Complete Syntax:

DEVICE=\path\TOSHETH.SYS [IRQ=X] [SRAM=XXXX] [IO=XXX]

IRQ (PCMCIA controller interrupt level)
SRAM (Shared RAM in the workstation)
IO (Base I/O port)

note: X is a hexadecimal number


EXAMPLE:

DEVICE=C:\LAN\TOSHETH.SYS

This would configure an Ethernet credit card for IRQ=5.

The default parameters are:

IRQ=5 (PCMCIA controller interrupt at IRQ 5)
SRAM=D400 (Shared RAM at D400 in the workstation)
IO=300 (Base I/O Port at 300h)



1.5 DIAGNOSTIC SOFTWARE
________________________

The diagnostic software is used to determine if the Ethernet Credit card is
performing correctly. It runs through a series of tests that check the opera-
tion of the card, determines if there are conflicts with I/O, memory and
interrupts, checks for connection to the network, and does a series of
loopback tests to determine hardware operation. The driver also determines
what type of environment you are operating in: Card Services 2.0, Socket Ser-
vices 1.01 or a hardware enabler.

NOTE: The diagnostics program will not execute if your system uses a Databook
PCMCIA socket controller.

1.5.1 RUNNING THE DIAGNOSTIC PROGRAM

For DOS: The diagnostics are started by typing A:ECCTEST from the DOS
prompt. Instructions will appear on the screen to connect and disconnect
from the network. During the loopback tests, network traffic can cause a
false failure ofthe test. If he network has no traffic,the diagnostics can be
run without disconnecting from the network.

For OS/2: The workstation must be booted from the installation diskette. It
will ask for your machine type and socket where the adapter is installed.
The diagnostic program will be run with a connectivity enabler.

On a 10BASE2 network (thinnet), a T-connector with two 50 ohm terminators
attached to the Media Access Module (MAM) will enable the diagnostics to run
loopback tests. If a terminated T-connector is not available, the diagnos-
tics will give you the option to bypass the loopback tests.



1.6 USING A MEMORY MANAGER WITH YOUR CREDIT CARD ADAPTER
_________________________________________________________

If your computer comes with a memory manager (preinstalled), or if you would
like to use one, you must configure your computer so the memory manager does
not use the same memory as your card. If you do not configure your computer
properly, there will be memory conflicts, and your card will not operate. To
prevent memory conflicts, there are some guidelines you must follow. It is
not possible to describe here the requirements for all cards and all memory
managers but these guidelines should help you to make the necessary deci-
sions.


The following 4 sections address the use of a memory manager with different
machine configurations. Please read the section appropriate for your config-
uration.

1.5.1: A Point Connectivity Enabler with a memory manager
(If you do not install Card and Socket Services on your
DOS computer, the installation program will install a
point connectivity enabler for you.)

1.5.2: IBM Card and Socket Services with a memory manager
(ThinkPad 720 and ThinkPad 750)

1.5.3: Phoenix Card and Socket Services with a memory manager


1.5.4: Using Expanded Memory (EMS)
It is recommended you read the appropriate section above
(section 1, 2, or 3) before reading this section.

Note: Throughout these 4 sections, you will see a given memory address
specified different ways. For example, you will see the same
address, D4000, specified as D4000, D400, or D4. It is important
for you to realize these are all the same. It's just that,
depending on the option used, it may have to be specified a
certain way.



1.6.1 POINT CONNECTIVITY ENABLER WITH A MEMORY MANAGER

1. If you have a DOS machine without Card and Socket Services
installed, the installation program will install a point
connectivity enabler for you. On DOS machines, you have the option
of using either the point connectivity enabler OR Card and Socket
Services with your Ethernet card. Please see the installation
guide for more information on these two options.

2. Your card requires memory in order to operate. You must configure
your computer so a memory manager and/or other PC cards do not use
the same memory range as your card, otherwise, your card will not
operate.

To prevent the memory manager from using the same memory as your
card, you must exclude the memory range being used by your card.
Important: For computers with multiple PC cards, you must exclude
the memory ranges being used by all of them.

To prevent other PC cards from using the same memory, the memory
ranges of all cards in use in your machine cannot conflict
(overlap) with one another.

3. To add the required excludes on your memory manager line, you must
edit your CONFIG.SYS file after completing the installation.

A. If you use the default values for the card, the following
exclusion is required on the memory manager line:
D400-D7FF for 16KB memory (memory base address default of D400)

The required exclusion is shown in the example below (using
EMM386, this is done using the "X=" parameter):

DEVICE=C:\POINTETH.SYS SA IRQ=5 WS=0 SRAM=D400 IO=300
:
DEVICE=C:\DOS\HIMEM.SYS
:
DEVICE=C:\DOS\EMM386.EXE 1024 RAM X=D400-D7FF

B. If you do not use the default values, but instead specify the
base address of the memory you want your card to use (this
capability is provided on a screen during the installation),
you must exclude the memory range that starts at the base
address that you specified. Please see the table below.

Important: When specifying the base address, you must make
certain that the memory range being used by your card does not
conflict (overlap) with memory that is being used by any other
cards in your computer.

MEMORY RANGE TO EXCLUDE ON THE MEMORY MANAGER LINE
(for EMM386, use the "X=" option)

Exclude the
If following
Memory Base range
address is... (16KB size)
------------- -----------

D0000 D000-D3FF
D4000 D400-D7FF
D8000 D800-DBFF
DC000 DC00-DFFF



1.6.3 PHOENIX CARD AND SOCKET SERVICES WITH A MEMORY MANAGER

1. Your card requires memory in order to operate. You must configure
your computer so a memory manager and/or other PC cards do not use
the same memory range as your card, otherwise, your card will not
operate.

It is recommended that you do not use the default value of
"autoset," but instead specify the base address of the memory
range you want your card to use (this capability is provided on a
screen during the installation).

Important: When specifying the base address, you must make certain
that the memory range being used by your card does not conflict
(overlap) with memory that is being used by any other cards in your
computer. Also, the memory base address must NOT be equal to (or
within a 4KB range above) the value set by the /ADDR option. (The
/ADDR option may be found on the "DEVICE=C:\DOS\PCMCS.EXE" line in
your CONFIG.SYS. For the IBM ThinkPad 350, it is set to C8 in the
preinstalled CONFIG.SYS.)

2. To prevent the memory manager from using the same memory as your
card, you must exclude the memory range being used by your card
starting at the base address that you specified.
Important: For computers with multiple PC cards, you must exclude
the memory ranges being used by all of them.

3. To add the required excludes on your memory manager line, you
must edit your CONFIG.SYS file after completing the installation.



1.7.3.1 Hot plugging in PCMCIA environments

It is important to have an Ethernet credit card adapter inserted in your com-
puter before starting some Local Area Network software. Unpredictable results
may occur if the adapter is not present and the software is executed.

It is also important not to remove your Ethernet credit card once communi-
cation on a LAN has begun. Unpredictable operation can occur if this happens.


If you do not want to use Card and Socket Services, POINTETH.SYS
can be used. You must use the WS=0 parameter on the command line of the
enabler for the card to function properly in this machine. A system hang may
result if POINTETH.SYS is used with Card Services. Use the Credit Card
Installation program to remove any connectivity enablers.


1.7.3.3 Toshiba T3300SL

The Toshiba T3300SL computer comes with a utility called SETVER.EXE that is
executed in CONFIG.SYS. This is a special version of MS-DOS 5.0 that only
comes with the Toshiba. This particular version is incompatible with network
operating environments like DOS LAN Requestor. An error indicating an incor-
rect DOS version occurs. This has not been found on other MS-DOS machines.
The installation utility will remark out this utility in CONFIG.SYS on the
Toshiba.




1.9 OS/2 DEVICE DRIVER STATEMENT ORDER
_______________________________________

For OS/2, the order of statements in your CONFIG.SYS is very important. The
order must be:

NDIS ODI
DEVICE=C:\OS2\PCMCIA.SYS DEVICE=C:\OS2\PCMCIA.SYS
. .
. .
DEVICE=C:\IBMCOM\MACS\PCMNICCS.OS2 DEVICE=C:\netware\PCMDMCS.SYS
. .
. .
DEVICE=C:\IBM2SS02.SYS DEVICE=C:\IBM2SS02.SYS
DEVICE=C:\ICRMU02.SYS DEVICE=C:\ICRMU02.SYS

The installation program will examine your CONFIG.SYS and move Socket Ser-
vices and the Resource Map Utility to the bottom of the file, if they are not
there already. They do not have to be the last statements in CONFIG.SYS, they
must be after every PCMCIA client driver you have installed; the bottom of
CONFIG.SYS is the most logical place to ensure they are after every client
driver.