1.0 CONTENTS
_____________
1.1 About This File . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Card Services Aware Device Drivers . . . . . . . . . . . . . . . . . 1
1.2.1 NDIS DRIVER (PCMNICCS.DOS) . . . . . . . . . . . . . . . . . . . 1
1.2.2 ODI DRIVER (PCMDMCS.COM) . . . . . . . . . . . . . . . . . . . . 2
1.2.3 Multiple Card Support . . . . . . . . . . . . . . . . . . . . . 3
1.2.4 Error Indications . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Connectivity Enabler Software . . . . . . . . . . . . . . . . . . . 4
1.4 Connectivity Enabler Parameters . . . . . . . . . . . . . . . . . . 5
1.4.1 ETHERNET.SYS SYNTAX . . . . . . . . . . . . . . . . . . . . . . 5
1.4.2 POINTETH.SYS SYNTAX . . . . . . . . . . . . . . . . . . . . . . 6
1.4.3 TOSHETH.SYS SYNTAX . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 Diagnostic Software . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5.1 Running the Diagnostic Program (ECCTEST.EXE) . . . . . . . . . . 8
1.6 Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6.1 Diagnostic Pitfalls . . . . . . . . . . . . . . . . . . . . . . 9
1.6.2 Memory Conflicts and Memory Managers . . . . . . . . . . . . . . 9
1.6.3 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . 10
1.6.3.1 Machines using SystemSoft Card and Socket Services . . . . 11
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 and PCMDMCS.COM) are Card
Services Aware and can be used with Card Services for configuration. They
also can be used with Connectivity Enabler software if Card Services is una-
vailable.
1.2.1 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)
Contents 1
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, 0xD000, 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
and not look for the adapter initially.
If you do not want to use Card Services, take out this keyword.
SOCKET = n (Optional)
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=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
2
1.2.2 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)
-ETHERNET_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
and not look for the adapter initially.
If you do not want to use Card Services, take out this keyword.
SLOT value (Optional)
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:
Contents 3
Link Driver PCMDMCS
Node Address 000123456789
INT 5
PORT 300
MEM D8000
1.2.3 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 DOS 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 DOS 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.
1.2.4 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 programs (e.g.
EMM386.EXE) that may be conflicting with the memory requested.
1.3 CONNECTIVITY ENABLER SOFTWARE
__________________________________
If your machine is not configured with PCMCIA Card Services 2.0, a
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.
4
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 connectivity enablers included with this package.
They are:
o ETHERNET.SYS
o POINTETH.SYS
o TOSHETH.SYS
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.
POINTETH.SYS is an enabler that communicates directly to Intel 82365SL hard-
ware. 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 services on your machine
does not communicate with ETHERNET.SYS correctly.
TOSHETH.SYS is an enabler that is used with the Toshiba T3300SL computer.
Contents 5
1.4 CONNECTIVITY ENABLER PARAMETERS
____________________________________
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. To change the defaults, the user
must update their CONFIG.SYS file with an editor.
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
6
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]
SA/SB/SC/SD (Socket A, B, C or D)
IRQ (Interrupt Level (PCMCIA controller interrupt))
WS (Wait state selection)
DS (Data size (16 or 8 bit bus))
SRAM (Shared RAM segment address)
IO (I/O base port address)
note: X is a hexadecimal number
sample:
DEVICE=C:\LAN\POINTETH.SYS SB WS=0 IO=320
This would 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)
1.4.3 TOSHETH.SYS SYNTAX
Contents 7
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
sample:
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 oper-
ation 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 your are operating in: Card Services 2.0, Socket
Services 1.01 or a hardware enabler.
1.5.1 RUNNING THE DIAGNOSTIC PROGRAM (ECCTEST.EXE)
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 of the test. If the network has no traffic, the diagnostics can be
run without disconnecting from the network.
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 PITFALLS
_____________
8
1.6.1 DIAGNOSTIC PITFALLS
IRQ and Shared Memory address conflicts are more easily detected than I/O
space conflicts. If the Diagnostic program does not report an I/O space
resource conflict, but the CARD TEST section of the Diagnostic program fails,
it may still be due to an I/O space conflict.
If problems are encountered running the diagnostics with Card Services,
remove the Card Services and retry the diagnostics.
Memory managers in the CONFIG.SYS file can cause various problems to be
detected and reported incorrectly by the Diagnostic program. If you experi-
ence Shared Memory address conflicts, delete any EMM driver or any other
memory management drivers that are in the CONFIG.SYS file and rerun the Diag-
nostic program. The diagnostics attempts to find memory managers and warns
of their existance during the diagnostic routine.
A mouse or trackball can cause Interrupt Request (IRQ) conflicts. The Diag-
nostic program attempts to detect this type of conflict and report it on the
display. However, if your system has a mouse or a trackball and the Diag-
nostic program reports an IRQ error, reassign the interrupt (IRQ) that the
Ethernet Credit Card Adapter uses. This latter step requires that you edit
the NetWare driver's NET.CFG file if you are using Novell NetWare, or edit
the NDIS driver's PROTOCOL.INI file if you are using IBM LAN Support Program
or Microsoft LAN Manager. You must also modify the IRQ specification in the
CONFIG.SYS file entry for the Enabler, if one is used, to match the required
interrupt setting. See "Connectivity Enabler software" above for information
on setting the IRQ.
Some of the new systems that support PCMCIA 2.0 I/O cards have features that
the user must be aware of when using the Ethernet Credit Card.
For the PCMCIA socket to receive power, many computers must have the power to
the PCMCIA socket enabled. This is typically done with a setup utility that
comes with the computer.
1.6.2 MEMORY CONFLICTS AND MEMORY MANAGERS
Many computers cache or shadow sections of memory to speed up operations.
The Ethernet Credit Card is a shared RAM adapter and utilizes some of the
system memory space. Some computers cache the segment C000 to D000. You may
want to consult the manufacturer's manual for your computer or contact the
manufacturer if you find you are having problems.
Contents 9
The DOS utility EMM386.EXE, if used, must be configured to exclude the memory
used by the adapter for its Shared RAM. Here is an example invocation of
EMM386.exe in your config.sys:
DEVICE=C:\DOS\EMM386.EXE X=D400-D800
This would exclude the memory areas necessary for standard default operation.
When using utilities like QEMM or 386MAX, it is important to exclude the
memory used by these utilities from the memory used by the Ethernet credit
card. The operation of the Ethernet credit card will be affected.
1.6.3 MISCELLANEOUS
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
(possible system hang).
The IBM ThinkPad 720/720C notebook computer typically uses Card and Socket
Services. 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.
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.
The AST PowerExec series computers come with a utility called CCU.EXE that is
executed in CONFIG.SYS. This program allows the Ethernet Credit Card
Adapter to be used in conjunction with other PCMCIA feature cards. It is
recommended that you use CCU.EXE since this program performs the same func-
tion as the connectivity enabler. A system hang may result if you attempt to
use both CCU.EXE and the POINTETH.SYS connectivity enabler. Consult your AST
computer documentation for information on setting CCU.EXE parameters.
10
The following machines have two PCMCIA sockets. Here are their socket assign-
ments:
Socket A (or 1) Socket B (or 2)
--------------- ---------------
AST Powerexec Bottom Top
IBM ThinkPad 720 Top Bottom
NEC UltraLite VERSA Bottom Top
Single Socket machines use Socket A.
1.6.3.1 Machines using SystemSoft Card and Socket Services
In order for machines with SystemSoft Card and Socket services installed to
be able to use the Token-Ring Credit Card Adapters, the following proce-
dure should be followed:
Make sure your system is using the level of Card Installation Client
(CIC.EXE) dated 3-25-93 or later. If you're using an earlier level, update
your system software.
After installing the Ethernet Credit Card Adapter and the appropriate
device drivers, make the following parameter changes:
1. Edit the CONFIG.SYS and locate the CIC.EXE line.
Update the parameters so that the line appears as below:
DEVICE=C:\path\CIC.EXE /CSBAS D8 /NWBAS D4 /NWSIZ 04
2. If running in a Novell environment:
Edit the NET.CFG file and remove the PCMCIA keyword.
3. If running in an NDIS environment:
Edit the PROTOCOL.INI file and remove the PCMCIA keyword.
Please refer to the SystemSoft CardSoft Reference Guide for further informa-
tion.
For a list of compatible notebook computers, dial 1-800-643-7409 (U.S.A. and
Canada).
Toshiba is a trademark of Toshiba America, Incorporated.
Dell is a trademark of Dell Computer Corp, Incorporated.
AST is a trademark of AST Research Incorporated.
NCR is a trademark of the NCR Corporation.
Contents 11
INTEL is a trademark of the INTEL Corporation.
NEC is a trademark of the NEC Corporation.
12