1.0 CONTENTS
_____________
1.1 About This File . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Card Services Aware Device Drivers for DOS . . . . . . . . . . . . . 1
1.2.1 FME_NDIS.DOS . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1.1 Error Indications . . . . . . . . . . . . . . . . . . . . . 3
1.2.2 FME_NET.COM . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.2.1 What's New With Novell ? . . . . . . . . . . . . . . . . . . 4
1.2.2.2 Error Indications . . . . . . . . . . . . . . . . . . . . . 4
1.3 Connectivity Enabler Software for DOS . . . . . . . . . . . . . . . 5
1.3.1 POINTFME.EXE syntax . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Card Services Aware Device Drivers for OS/2 . . . . . . . . . . . . 7
1.4.1 FME_NDIS.OS2 . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4.1.1 Error Indications . . . . . . . . . . . . . . . . . . . . . 8
1.4.2 FME_NET.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4.2.1 Error Indications . . . . . . . . . . . . . . . . . . . . 11
1.4.3 OS/2 Configuration Examples . . . . . . . . . . . . . . . . . 11
1.5 Diagnostic Software . . . . . . . . . . . . . . . . . . . . . . . 17
1.5.1 Error Indications . . . . . . . . . . . . . . . . . . . . . . 18
1.6 System Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6.1 Super Client Drivers . . . . . . . . . . . . . . . . . . . . . 18
1.6.2 Memory Conflicts and Memory Managers . . . . . . . . . . . . . 19
1.6.3 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7 Modem Operation . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.7.1 Modem Enabler Syntax for DOS . . . . . . . . . . . . . . . . . 23
1.7.2 Card Services-aware Modem Enabler Syntax for OS/2 . . . . . . 23
1.7.3 Error Indications . . . . . . . . . . . . . . . . . . . . . . 23
1.8 Corrections to the User's Guide . . . . . . . . . . . . . . . . . 24
1.1 ABOUT THIS FILE
____________________
This file describes additional information on the Fax/Modem/Ethernet Combo
Adapter. It also describes the Card Services Aware device drivers,
Connectivity Enabler Software and Diagnostic Software.
1.2 CARD SERVICES AWARE DEVICE DRIVERS FOR DOS
_______________________________________________
The device drivers on this diskette (FME_NET.COM, FME_NDIS.DOS) are Card Ser-
vices Aware and may be used with Card Services for configuration.
FME_NET.COM and FME_NDIS.DOS must be loaded after Card Services in
CONFIG.SYS. They may also be used with a Connectivity Enabler if Card Ser-
vices is unavailable.
Contents 1
1.2.1 FME_NDIS.DOS
FME_NDIS.DOS is the NDIS Ethernet device driver for DOS. The PROTOCOL.INI
file is used to pass parameters to the driver. The valid keywords are listed
below:
BUSSIZE8 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.
COMPORT is the COM port used by the modem.
INTERRUPT allows the user to select the interrupt used by the computer for
this PC Card (Optional for Card Services).
IOBASE is the base I/O port address for the Ethernet function (Optional for
Card Services).
NETADDRESS is a locally administered address, using canonical format
(Optional).
PCMCIA is the keyword that signals the driver to look for Card Services prior
to looking for the adapter.
RAMADDRESS is the beginning of the memory segment address for the Ethernet
function. 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.
20KB + 1 byte of RAM is required.
VXDPATH is the path to the virtual device driver used to run concurrently
under Windows.
See the FME_NDIS.NIF file for valid values for these keywords.
Below is a sample PROTOCOL.INI entry for this driver:
žFME_NDIS_NIFŽ
;Fax/Modem/Ethernet Combo Adapter
DriverName = FME_CS$ <--- Driver name; not user changeable
IOBASE = 0x300 <--- I/O start address for Ethernet
INTERRUPT = 5 <--- Interrupt value for card
COMPORT = 2 <--- COMPORT value for modem
RAMADDRESS = 0xD4000 <--- Shared memory address - Ethernet
VXDPATH = C:\WINDOWS\SYSTEM <--- Path for concurrent mode windows VxD
PCMCIA <--- Inserted if Card Services is present
The parameters can be commented out by placing a ";" (semi-colon) in front of
the entry. The default values are:
INTERRUPT = 5 <-- if these parameters are NOT specified, the
RAMADDRESS = 0xD400 <-- driver searches for a valid address or
COMPORT = 2 <-- available interrupt value until one is
IOBASE = 0x300 found (Autoset mode) or the valid values
VXDPATH = C:\WINDOWS\SYSTEM tried are exhausted.
2
1.2.1.1 Error Indications
The NDIS driver signals the user when a Card Services call fails. The error
signal is an alternating beep. If you hear this sound, a problem is occur-
ring during configuration. Other indications of a configuration error
include the adapter failing to initialize and failing to bind to the network.
At this time, review your PROTOCOL.INI and CONFIG.SYS to verify proper param-
eters. It is vitally important that memory areas requested are available.
If using Card Services, try commenting out the IOBASE and INTERRUPT keywords
and set RAMADDRESS = 0 and reboot. If this doesn't help, check for any pro-
grams (e.g. EMM386.EXE) that may be conflicting with the memory requested.
Refer to the section on Memory Conflicts and Memory Managers for further
information. Other computer and system-specific pitfalls are li sted later
in this file.
1.2.2 FME_NET.COM
FME_NET.COM is the ODI Ethernet driver for DOS Novell Environments. It uses
the NET.CFG to get specific configuration information. The valid keywords
are listed below:
COMPORT is the COM port used by the modem.
FRAME is the frame type allowed for Ethernet. The form is ETHERNET_value
where value is any of the following frame types:
o 802.3 (Novell Netware 3.xx networks)
o 802.2 (Novell Netware 4.xx networks and Universal Client)
o SNAP (Use when 802.2 SNAP extension is required)
o II (Networks connected to DEC or using TCP/IP protocol)
INT allows the user to select the interrupt used by the computer for this PC
Card (Optional for Card Services).
MEM is the memory segment address for the ethernet function. If your machine
has Card Services 2.0 installed and you want Card Services to select your RAM
location for you, MEM FFFFFFFF must be used. 20KB + 1 byte of RAM is
required.
NODE ADDRESS is a locally administered address, using canonical format. If a
node address is not specified, the card must be installed in the slot at
startup.
PCMCIA is the keyword that signals the driver to look for Card Services prior
to looking for the adapter.
PORT is the base I/O port address for the Ethernet function (Optional for
Card Services).
Contents 3
VXDPATH is the path to the virtual device driver used to run concurrently
under Windows.
Below is a sample NET.CFG entry for this driver:
Link Driver FME_NET <--- Driver name; not user changeable
PORT 300 <--- I/O start address for Ethernet
INT 5 <--- Interrupt value for card
COMPORT 2 <--- COMPORT value for modem
MEM D4000 <--- Shared memory address - Ethernet
VXDPATH C:\WINDOWS\SYSTEM <--- Path for concurrent mode windows VxD
PCMCIA <--- Inserted if Card Services is present
FRAME ETHERNET_802.3 <--- Media Frame type
Most of the parameters can be commented out by placing a ";" (semi-colon) in
front of the entry. The default values are:
INT 5 <-- if these parameters are NOT specified, the
MEM D4000 <-- driver searches for a valid address or
COMPORT 2 <-- available interrupt value until one is
PORT 300 found (Autoset mode) or the valid values
VXDPATH C:\WINDOWS\SYSTEM tried are exhausted.
FRAME ETHERNET_802.2
1.2.2.1 What's New With Novell ?
The ODI driver meets the Novell 4.0 specification and includes support for
NESL (Network Event Support Layer) 1.0 which provides better operation in a
PCMCIA environment and more reliable Hot-plugging. Since earlier versions of
Novell do not include this support, we are shipping the NESL and LSL layers
so that earlier versions will work with these benefits. The installation
program should take care of this for you, but if you experience problems,
these files can be found in the NETWARE directory on the installation
diskette. NESL.COM should load after LSL.COM and before FME_NET.COM.
Novell Universal Client drivers are being shipped with the adapter installa-
tion. The client drivers will support Novell servers versions 3.11 and
above.
1.2.2.2 Error Indications
The ODI driver signals the user when a Card Services call fails. The error
signal is an alternating beep. If you hear this sound, a problem is occur-
ring during configuration. Other indications of a configuration error
include the adapter failing to initialize and failing to bind to the network.
At this time, review your NET.CFG and CONFIG.SYS to verify proper parameters.
It is vitally important that memory areas requested are available. If using
Card Services try commenting out the PORT and INT keywords and set MEM
FFFFFFFF and reboot. If this doesn't help, check for any programs (e.g.
EMM386.EXE) that may be conflicting with the memory requested. Refer to the
4
section on Memory Conflicts and Memory Managers for further information.
Other computer and system-specific pitfalls are l isted later in this file.
1.3 CONNECTIVITY ENABLER SOFTWARE FOR DOS
__________________________________________
POINTFME.EXE is an enabler that communicates directly to Intel 82365SL (or
equivalent) hardware. It is a PCMCIA socket controller common in many
systems. This enabler should be used when Card and Socket Services do not
exist on your computer. The installation will notify you if you do not have
a compatible controller.
The enabler has parameters that allow it to be customized to the communi-
cation software. The parameters allow the selection of which socket is used
for the card and memory areas used by the card. The default parameters
should be sufficient for most users.
Connectivity Enabler software is used to configure the PCMCIA socket hardware
and the Fax/Modem/Ethernet Combo Adapter hardware for operation. It must be
loaded as a device driver in CONFIG.SYS BEFORE the FME_NDIS.DOS. If your
driver is not loaded at CONFIG.SYS time, e.g. FME_NET.COM, you can execute
the enabler at any time BEFORE you execute your driver. Card and Socket Ser-
vices are NOT required for operation of the Fax/Modem/Ethernet Combo Adapter.
After the Connectivity Enabler has run, it removes itself from the system
memory.
The DOS NDIS (FME_NDIS.DOS) and ODI (FME_NET.COM) drivers on this diskette do
not require the use of an enabler when used with Card Services. They have a
built-in interface to Card Services for configuration purposes. They can be
used without Card Services if Card Services is unavailable or incompatible
with the driver.
It has been noticed that on some machines, notably Toshiba machines, the
point enabler, POINTFME.EXE, needs to load later in CONFIG.SYS. The instal-
lation puts it at the beginning, but it can be placed anywhere BEFORE
FME_NDIS.DOS in CONFIG.SYS or run some time BEFORE FME_NET.COM is loaded.
For the adapter to function properly in systems without Card Services, it is
essential that the enabler and the LAN communications software used agree on
three parameters. These parameters are the IRQ level, the Shared RAM
address, the I/O Port address. The enabler and the Modem software must agree
on the COM port address. Compare the parameters on the POINTFME.EXE line in
the config.sys with those in the FME_NDIS_NIF section of your protocol.ini or
the FME_NET section of your net.cfg.
LAN Communications software selects where the shared RAM will reside in the
computer's memory space. This is NOT done by the enabler. The Shared RAM
address set by the enabler must match the memory location selected by the LAN
software or communication will not occur.
Contents 5
1.3.1 POINTFME.EXE SYNTAX
Be sure when using the point enabler, POINTFME.EXE, that all resources chosen
are available.
Complete Syntax:
DEVICE=\path\POINTFME.EXE SA/SB/SC/SD IRQ=X SRAM=XXXX WS=0,1,2,3,4
DS=16/DS=8 PCIC=XXXX COM=1,2,3,4 IOBASE=XXX ?
SA/SB/SC/SD - Socket A, Socket B, Socket C, or Socket D
IRQ - Interrupt Level (PCMCIA controller interrupt)
SRAM - Shared Ram address XXXX
WS - Wait state selection
DS - Data size (16 or 8 bit bus)
PCIC - PC Card Interface Controller base I/O port
COM - Com port number
IOBASE - I/O Ports base address
? - Display available parameters
note: X is a hexadecimal number
sample:
DEVICE=C:\POINTFME.EXE SB SRAM=D400 WS=0 COM=2
This would configure a Fax/Modem/Ethernet Combo Adapter for socket B, Shared
RAM at D400 segment, no wait states, and COMPORT 2.
The default parameters are:
SA (Socket A)
IRQ=5 (PCMCIA controller interrupt at IRQ 5)
SRAM=D400 (Shared RAM at D400 segment)
WS=1 (1 wait state)
DS=16 (Data Bus size of 16 bits)
PCIC=03E0 (Standard Intel 82365SL base I/O port)
COM=2 (COM port is 2)
IOBASE=300 (I/O port base address is 300)
The PCIC parameter has been added to support the Port Replicator device or
Dock II device that attaches to the IBM ThinkPad family of notebook computers
and any other Intel 82365SL (or compatible) based device that does not use
3E0 as its base I/O port for configuration. The Port Replicator and Dock II
use 3E2 as its I/O port base address.
Here is a sample invocation on a machine using the Port Replicator/ Dock II ,
6
DEVICE=C:\LAN\POINTFME.EXE PCIC=03E2
The PCIC parameter is also used for socket C on the AST Ascentia 900N. It
uses 3E4 as its I/O port base address.
Here is a sample invocation on an AST Ascentia 900N for slot C.
DEVICE=C:\LAN\POINTFME.EXE SC PCIC=03E4
1.4 CARD SERVICES AWARE DEVICE DRIVERS FOR OS/2
________________________________________________
The device drivers on this diskette (FME_NDIS.OS2 and FME_NET.SYS) are Card
Services-aware and must be used with Card Services for configuration.
1.4.1 FME_NDIS.OS2
FME_NDIS.OS2 is the NDIS Ethernet device driver for OS/2. The PROTOCOL.INI
file is used to pass parameters to the driver. All parameters except PCMCIA
are optional and can be used to fix a value. If omitted from PROTOCOL.INI,
the driver will search for the first unused value and use it. The valid
keywords are listed below:
COMPORT is the COM port used by the modem.
INTERRUPT allows the user to select the interrupt used by the computer for
this PC Card.
IOBASE is the base I/O port address for the Ethernet function.
NETADDRESS is a locally administered address, using canonical format.
Canonical format is often called "Ethernet Format". Non-Canonical format is
often called "Token-Ring Format". A sample address is shown below in both
formats:
Canonical: 0200 005A 646B
Non-Canonical: 4000 005A 26D6
Remember to use the canonical format for this driver. The Universally Admin-
istered Address on the back of the adapter is in canonical format.
PCMCIA is the keyword that signals the driver to look for Card Services prior
to looking for the adapter.
RAMADDRESS is the beginning of the memory segment address for the Ethernet
function. If you want Card Services to select your RAM location for you,
RAMADDRESS = 0 must be used, or simply omit the keyword.
COMIOBASE is the base I/O port address for the COM port function.
Contents 7
MODEMONLY is used to disable the Ethernet function and only enable the COM
port function. You must still have the LAN software loaded, it just will not
work. This keyword is mainly used for software that cannot work with the
shared interrupt mode of this card. One such sofware package is Communi-
cations Manager/2 Version 1.11 configured for the SNA Phone Connect Feature.
See the FME_NDIS.NIF file for valid values for these keywords.
Below is a sample PROTOCOL.INI entry for this driver:
žFME_NDIS_NIFŽ
DriverName = FME_CS$ <--- Driver name; not user changeable
IOBASE = 0x300 <--- I/O start address for Ethernet
INTERRUPT = 5 <--- Interrupt value for card
COMPORT = 2 <--- COMPORT value for modem
RAMADDRESS = 0xD4000 <--- Shared memory address - Ethernet
COMIOBASE = 0x4F8 <--- I/O start address for COM port
PCMCIA <--- Inserted if Card Services is present
The parameters can be commented out by placing a ";" (semi-colon) in front of
the entry. The default values are:
PCMCIA <--- The driver searches for available
resources until one is found or
all valid values tried are exhausted.
1.4.1.1 Error Indications
o Ensure when installing OS/2 that you have selected to install PCMCIA
support and serial support. Both of these are required to use all the
capabilites of the adapter. PCMCIA support is not an OS/2 installation
default. You may add this feature later by doing a Selective install.
Serial support may not be installed if you had disabled your board serial
port.
o If you have OS/2 2.11, your Card Services support needs to be in a spe-
cific order. Card Services (PCMCIA.SYS) should be followed by the
Resource Map (i.e. ICRMU0X.SYS) and then the Socket Services (i.e.
IBMSS0X.SYS). The Resource Map and Socket Services also need to be the
last two statements in the CONFIG.SYS.
o If you have any error messages installing LAPS or MPTS, please check the
LAPSHIST.LOG file in the \OS2\INSTALL subdirectory for more information
on the error condition and how to correct it.
o If you have any error messages installing IBM LAN Requester, please check
the IBMLSHST.LOG and IBMLANER.LOG files in the \OS2\INSTALL subdirectory
for more information on the error condition and how to correct it.
o SYS0053 errors or lost connections using LAN Server 3.0/4.0
If you start to experience these errors, either your requester or
server is timing out on large raw data transfers and is dropping con-
8
nections. You should disable large raw data transfers on either your
requester or server. To do this, edit your IBMLAN.INI file and change
either SRVHEURISTIC 19 from 1 to 0 on your server, or change
WRKHEURISTIC 11 from 1 to 0 on your requester. A sample of each
follows:
Requester
; The next lines help you to locate bits in the wrkheuristics entry.
; 1 2 3
; 0123456789012345678901234567890123
wrkheuristics = 1111111121311111110001011120111221
^
|
| Change this from 1 to 0
Server
; The next lines help you to locate bits in the srvheuristics entry.
; 1
; 01234567890123456789
srvheuristics = 11110141111311001331
^
|
| Change this from 1 to 0
o If you would like to boot your PC without the PC card inserted in a
socket, you must have the INTERRUPT and NETADDRESS keywords specified in
PROTOCOL.INI.
o Occassionally, after installing or re-installing networking applications,
your CONFIG.SYS file can get some important statements out of order. If
you experience any errors at boot up time saying that NETWKSTA.200 cannot
be installed, it is probably out of order in CONFIG.SYS. Refer to the
sample NDIS with IBM OS/2 LAN Requester in section 1.4.3 for an example.
1.4.2 FME_NET.SYS
FME_NET.SYS is the ODI Ethernet device driver for OS/2 Novell environments.
It uses the NET.CFG to get specific configuration information. All parameters
except PCMCIA and NODE ADDRESS are optional and can be used to fix a value.
If omitted from NET.CFG, the driver will search for the first unused value
and use it. The valid keywords are listed below:
COMPORT is the COM port used by the modem.
FRAME is the frame type allowed for Ethernet. The form is ETHERNET_value
where value is any of the following frame types:
o 802.3 (Novell Netware 3.xx networks)
Contents 9
o 802.2 (Novell Netware 4.xx networks and Universal Client)
o SNAP (Use when 802.2 SNAP extension is required)
o II (Networks connected to DEC or using TCP/IP protocol)
INT allows the user to select the interrupt used by the computer for this PC
Card.
MEM is the memory segment address for the ethernet function. If you want
Card Services to select your RAM location for you, MEM FFFFF must be used or
simply omit the keyword.
NODE ADDRESS is a locally administered address, using canonical format. A
node address must be specified or an error will be reported at startup.
Canonical format is often called "Ethernet Format". Non-Canonical format is
often called "Token-Ring Format". A sample address is shown below in both
formats:
Canonical: 0200 005A 646B
Non-Canonical: 4000 005A 26D6
Remember to use the canonical format for this driver. The Universally Admin-
istered Address on the back of the adapter is in canonical format.
PCMCIA is the keyword that signals the driver to look for Card Services prior
to looking for the adapter.
PORT is the base I/O port address for the Ethernet function.
COMIOBASE is the base I/O port address for the COM port function.
Below is a sample NET.CFG entry for this driver:
Link Driver FME_NET <--- Driver name; not user changeable
PORT 300 <--- I/O start address for Ethernet
INT 5 <--- Interrupt value for card
COMPORT 2 <--- COMPORT value for modem
MEM D4000 <--- Shared memory address - Ethernet
PCMCIA <--- Inserted if Card Services is present
FRAME ETHERNET_802.3 <--- Media Frame type
COMIOBASE 5F8 <--- I/O start address for COM port
Most of the parameters can be commented out by placing a ";" (semi-colon) in
front of the entry. The default values are:
PCMCIA
NODE ADDRESS 400000000000 <--- During installation, if you did not
enter either a Locally Administered
Address or your Universally
Administered Address, this value
was entered for you and must be
changed prior to rebooting.
10
1.4.2.1 Error Indications
o Ensure when installing OS/2 that you have selected to install PCMCIA
support and serial support. Both of these are required to use all the
capabilites of the adapter. PCMCIA support is not an OS/2 installation
default. You may add this feature later by doing a Selective install.
Serial support may not be installed if you had disabled your board serial
port.
o If you have OS/2 2.11, your Card Services support needs to be in a spe-
cific order. Card Services (PCMCIA.SYS) should be followed by the
Resource Map (i.e. ICRMU0X.SYS) and then the Socket Services (i.e.
IBMSS0X.SYS). The Resource Map and Socket Services also need to be the
last two statements in the CONFIG.SYS tn
o If you would like to boot your PC without the PC card inserted in a
socket, you must have the INT and NODE ADDRESS keywords specified in
NET.CFG. During the boot process you will receive the following message:
REQ0815: The program cannot get the connection ID. Error: 0x880F.
Press <ESC> to continue.
You should press the ESC key to continue. Later when you insert the PC
card you will be connected to the network.
1.4.3 OS/2 CONFIGURATION EXAMPLES
Occassionally, after installing or re-installing networking applications,
your CONFIG.SYS file can get some important statements out of order. If you
experience any errors at boot up time saying that NETWKSTA.200 cannot be
installed, it is probably out of order in CONFIG.SYS. Three sample
CONFIG.SYS files follow: The first for an NDIS environment using LAN
Requester, the second for an ODI environment using Novell NetWare, and the
third for a modem-only environment.
Contents 11
First: NDIS with IBM OS/2 LAN Requester
IFS=D:\OS2\HPFS.IFS /CACHE:64 /CRECL:4 /AUTOCHECK:E
PROTSHELL=D:\OS2\PMSHELL.EXE
SET USER_INI=D:\OS2\OS2.INI
SET SYSTEM_INI=D:\OS2\OS2SYS.INI
SET OS2_SHELL=D:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,LAUNCHPAD
SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE
SET COMSPEC=D:\OS2\CMD.EXE
LIBPATH=E:\IBMLAN\NETLIB;E:\MUGLIB\DLL;D:\IBMCOM\DLL;.;D:\OS2\DLL;
D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;E:\MMOS2\DLL;
SET PATH=E:\IBMLAN\NETPROG;E:\MUGLIB;D:\IBMCOM;D:\OS2;D:\OS2\SYSTEM;
D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;D:\;D:\OS2\MDOS;D:\OS2\APPS;E:\MMOS2;
SET DPATH=E:\IBMLAN\NETPROG;E:\IBMLAN;E:\MUGLIB;D:\IBMCOM;D:\OS2;
D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;D:\;D:\OS2\BITMAP;
D:\OS2\MDOS;D:\OS2\APPS;E:\MMOS2;E:\MMOS2\INSTALL
SET PROMPT=ž$pŽ
SET HELP=D:\OS2\HELP;D:\OS2\HELP\TUTORIAL;E:\MMOS2\HELP;
SET GLOSSARY=D:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
BASEDEV=IBMKBD.SYS
DEVICE=D:\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=D:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=D:\IBMCOM\LANMSGDD.OS2 /I:D:\IBMCOM
DEVICE=D:\IBMCOM\PROTMAN.OS2 /I:D:\IBMCOM
DEVICE=D:\OS2\BOOT\TESTCFG.SYS
DEVICE=D:\OS2\BOOT\DOS.SYS
DEVICE=D:\OS2\BOOT\PMDD.SYS
BUFFERS=90
IOPL=YES
DISKCACHE=D,LW,AC:D
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=D:\OS2\SYSTEM 2048 4096
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
SET BOOKSHELF=D:\OS2\BOOK;E:\MMOS2;
SET SOMIR=D:\OS2\ETC\SOM.IR;D:\OS2\ETC\WPSH.IR;D:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=D:\OS2\ETC\DSOM
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;F:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
SET EPMPATH=D:\OS2\APPS;
PROTECTONLY=NO
12
SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=D:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=D:\OS2\MDOS\VDPMI.SYS
DEVICE=D:\OS2\MDOS\VDPX.SYS
DEVICE=D:\OS2\MDOS\VWIN.SYS
DEVICE=D:\OS2\MDOS\VW32S.SYS
DEVICE=D:\OS2\BOOT\APM.SYS
DEVICE=D:\OS2\MDOS\VAPM.SYS
DEVICE=D:\OS2\MDOS\VMOUSE.SYS
DEVICE=D:\OS2\BOOT\POINTDD.SYS
DEVICE=D:\OS2\BOOT\MOUSE.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP
BASEDEV=PCMCIA.SYS /P /E
DEVICE=D:\OS2\MDOS\VPCMCIA.SYS
REM DEVICE=D:\OS2\BOOT\COM.SYS
DEVICE=D:\IBMCOM\MACS\COM.SYS
DEVICE=D:\OS2\MDOS\VCOM.SYS
DEVICE=D:\OS2\BOOT\AUTODRV2.SYS D:\OS2\AUTODRV2.INI
BASEDEV=IBM2SS01.SYS /S0=2
DEVINFO=SCR,VGA,D:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=D:\OS2\MDOS\VSVGA.SYS
DEVICE=E:\MMOS2\CS4231.SYS N:BSAUD1$
DEVICE=E:\MMOS2\VCS4231.SYS BSAUD1$
SET MMBASE=E:\MMOS2;
SET DSPPATH=E:\MMOS2\DSP;
SET NCDEBUG=4000
DEVICE=E:\MMOS2\SSMDD.SYS
DEVICE=E:\MMOS2\R0STUB.SYS
CALL=D:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=D:\IBMCOM\LANMSGEX.EXE
DEVICE=D:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=E:\IBMLAN\NETPROG\RDRHELP.200
IFS=E:\IBMLAN\NETPROG\NETWKSTA.200 /I:E:\IBMLAN /N
DEVICE=D:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=D:\IBMCOM\MACS\FME_NDIS.OS2
RUN=E:\IBMLAN\NETPROG\LSDAEMON.EXE
DEVICE=E:\IBMLAN\NETPROG\VNETAPI.OS2
RUN=E:\IBMLAN\NETPROG\VNRMINIT.EXE
SET NWDBPATH=E:\IBMLAN\NETPROG
Second: ODI with Novell NetWare Requester
PROTSHELL=D:\OS2\PMSHELL.EXE
SET USER_INI=D:\OS2\OS2.INI
SET SYSTEM_INI=D:\OS2\OS2SYS.INI
SET OS2_SHELL=D:\OS2\CMD.EXE
Contents 13
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,LAUNCHPAD
SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE
SET COMSPEC=D:\OS2\CMD.EXE
LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;E:\MMOS2\DLL;
F:\NETWARE;
SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;
D:\;D:\OS2\MDOS;D:\OS2\APPS;E:\MMOS2;F:\NETWARE;
SET DPATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;
D:\;D:\OS2\BITMAP;D:\OS2\MDOS;D:\OS2\APPS;E:\MMOS2;E:\MMOS2\INSTALL;
F:\NETWARE;
SET PROMPT=ž$pŽ
SET HELP=D:\OS2\HELP;D:\OS2\HELP\TUTORIAL;E:\MMOS2\HELP;
SET GLOSSARY=D:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=20
BASEDEV=IBMKBD.SYS
DEVICE=D:\OS2\BOOT\TESTCFG.SYS
DEVICE=D:\OS2\BOOT\DOS.SYS
DEVICE=D:\OS2\BOOT\PMDD.SYS
BUFFERS=90
IOPL=YES
DISKCACHE=D,LW,AC:D
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=D:\OS2\SYSTEM 2048 4096
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
SET BOOKSHELF=D:\OS2\BOOK;E:\MMOS2;
SET SOMIR=D:\OS2\ETC\SOM.IR;D:\OS2\ETC\WPSH.IR;D:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=D:\OS2\ETC\DSOM
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;F:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
SET EPMPATH=D:\OS2\APPS;
PROTECTONLY=NO
SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=D:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=D:\OS2\MDOS\VDPMI.SYS
DEVICE=D:\OS2\MDOS\VDPX.SYS
DEVICE=D:\OS2\MDOS\VWIN.SYS
DEVICE=D:\OS2\MDOS\VW32S.SYS
DEVICE=D:\OS2\BOOT\APM.SYS
14
DEVICE=D:\OS2\MDOS\VAPM.SYS
DEVICE=D:\OS2\MDOS\VMOUSE.SYS
DEVICE=D:\OS2\BOOT\POINTDD.SYS
DEVICE=D:\OS2\BOOT\MOUSE.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP
BASEDEV=PCMCIA.SYS /P /E
DEVICE=D:\OS2\MDOS\VPCMCIA.SYS
REM DEVICE=D:\OS2\BOOT\COM.SYS
DEVICE=D:\IBMCOM\MACS\COM.SYS
DEVICE=D:\OS2\MDOS\VCOM.SYS
DEVICE=D:\OS2\BOOT\AUTODRV2.SYS D:\OS2\AUTODRV2.INI
BASEDEV=IBM2SS01.SYS /S0=2
DEVINFO=SCR,VGA,D:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=D:\OS2\MDOS\VSVGA.SYS
DEVICE=E:\MMOS2\CS4231.SYS N:BSAUD1$
DEVICE=E:\MMOS2\VCS4231.SYS BSAUD1$
SET MMBASE=E:\MMOS2;
SET DSPPATH=E:\MMOS2\DSP;
SET NCDEBUG=4000
DEVICE=E:\MMOS2\SSMDD.SYS
DEVICE=E:\MMOS2\R0STUB.SYS
DEVICE=F:\NETWARE\LSL.SYS
RUN=F:\NETWARE\DDAEMON.EXE
DEVICE=F:\NETWARE\FME_NET.SYS
DEVICE=F:\NETWARE\IPX.SYS
DEVICE=F:\NETWARE\NWREQ.SYS
IFS=F:\NETWARE\NWIFS.IFS
RUN=F:\NETWARE\NWDAEMON.EXE
Third: Card Services-aware Modem Enabler
PROTSHELL=D:\OS2\PMSHELL.EXE
SET USER_INI=D:\OS2\OS2.INI
SET SYSTEM_INI=D:\OS2\OS2SYS.INI
SET OS2_SHELL=D:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,LAUNCHPAD
SET RUNWORKPLACE=D:\OS2\PMSHELL.EXE
SET COMSPEC=D:\OS2\CMD.EXE
LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;D:\OS2\APPS\DLL;E:\MMOS2\DLL;
F:\NETWARE;
SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;D:\;
D:\OS2\MDOS;D:\OS2\APPS;E:\MMOS2;F:\NETWARE;
SET DPATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS\WINOS2;D:\OS2\INSTALL;D:\;
D:\OS2\BITMAP;D:\OS2\MDOS;D:\OS2\APPS;E:\MMOS2;E:\MMOS2\INSTALL;
F:\NETWARE;
SET PROMPT=ž$pŽ
SET HELP=D:\OS2\HELP;D:\OS2\HELP\TUTORIAL;E:\MMOS2\HELP;
SET GLOSSARY=D:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
Contents 15
PRIORITY_DISK_IO=YES
FILES=20
BASEDEV=IBMKBD.SYS
DEVICE=D:\OS2\BOOT\TESTCFG.SYS
DEVICE=D:\OS2\BOOT\DOS.SYS
DEVICE=D:\OS2\BOOT\PMDD.SYS
BUFFERS=90
IOPL=YES
DISKCACHE=D,LW,AC:D
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=D:\OS2\SYSTEM 2048 4096
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,D:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
SET BOOKSHELF=D:\OS2\BOOK;E:\MMOS2;
SET SOMIR=D:\OS2\ETC\SOM.IR;D:\OS2\ETC\WPSH.IR;D:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=D:\OS2\ETC\DSOM
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;F:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
SET EPMPATH=D:\OS2\APPS;
PROTECTONLY=NO
SHELL=D:\OS2\MDOS\COMMAND.COM D:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=D:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=D:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=D:\OS2\MDOS\VDPMI.SYS
DEVICE=D:\OS2\MDOS\VDPX.SYS
DEVICE=D:\OS2\MDOS\VWIN.SYS
DEVICE=D:\OS2\MDOS\VW32S.SYS
DEVICE=D:\OS2\BOOT\APM.SYS
DEVICE=D:\OS2\MDOS\VAPM.SYS
DEVICE=D:\OS2\MDOS\VMOUSE.SYS
DEVICE=D:\OS2\BOOT\POINTDD.SYS
DEVICE=D:\OS2\BOOT\MOUSE.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,D:\OS2\KEYBOARD.DCP
BASEDEV=PCMCIA.SYS /P /E
DEVICE=D:\FMECS.SYS
DEVICE=D:\OS2\MDOS\VPCMCIA.SYS
REM DEVICE=D:\OS2\BOOT\COM.SYS
DEVICE=D:\IBMCOM\MACS\COM.SYS
DEVICE=D:\OS2\MDOS\VCOM.SYS
DEVICE=D:\OS2\BOOT\AUTODRV2.SYS D:\OS2\AUTODRV2.INI
BASEDEV=IBM2SS01.SYS /S0=2
16
DEVINFO=SCR,VGA,D:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=D:\OS2\MDOS\VSVGA.SYS
DEVICE=E:\MMOS2\CS4231.SYS N:BSAUD1$
DEVICE=E:\MMOS2\VCS4231.SYS BSAUD1$
SET MMBASE=E:\MMOS2;
SET DSPPATH=E:\MMOS2\DSP;
SET NCDEBUG=4000
DEVICE=E:\MMOS2\SSMDD.SYS
DEVICE=E:\MMOS2\R0STUB.SYS
The above examples are for OS/2 Warp. There are several differences between
OS/2 Warp and OS/2 2.1x.
1. The BASEDEV=IBM2SS01.SYS would be a DEVICE=C:\THINKPAD\IBM2SS01.SYS and
it would be located at the bottom of CONFIG.SYS.
2. Another device driver known as the Resouce Map Utility would be just
below Socket Services. The statement would be
DEVICE=C:\THINKPAD\ICRMU01.SYS.
3. Card Services would also be a DEVICE. Its position in CONFIG.SYS would
remain the same, but the statement would be DEVICE=C:\OS2\PCMCIA.SYS.
1.5 DIAGNOSTIC SOFTWARE
________________________
The diagnostic software is used to determine if a properly installed
Fax/Modem/Ethernet Combo Adapter is performing correctly. It runs through a
series of tests that checks the operation of the card, checks the connections
to the network and phone lines, and does a series of loopback tests to deter-
mine hardware operation. It CAN NOT determine configuration errors or
network configuration errors. It will also show the universal node address
of the adapter and the firmware version of the modem.
The diagnostics are started by booting from the Installation diskette. The
adapter must be the ONLY adapter in the machine OR it must be in slot A (1)
to run the diagnostics successfully. The adapter will fail to initialize or
false errors may be posted by the diagnostics if you do not do this!
Instructions will appear on the screen to connect and disconnect from the
network. Power for the socket must also be enabled. This is typically done
with a setup utility that comes with the computer.
After executing the diagnostics, switch off the system power. Remove the
diskette and then switch on the system power.
Contents 17
1.5.1 ERROR INDICATIONS
MEMORY TESTS: If you experience any problems during memory tests you may
have a problem with the card.
MODEM TESTS: The modem test determines if the modem controller can be con-
tacted and shows the firmware version of the modem. If the Modem Cable Test
fails and the other modem tests pass, try using a different wall outlet. If
you are using a modem saver, try watching the lights and make sure the green
light comes on. If the yellow light comes on you have a problem with the
phone line, see the section in the User's Guide on the modem saver for more
detail about the lights.
STNIC ADDRESS TEST: This test determines if the ethernet controller can be
contacted. If you experience problems during this test, you may have a
problem with the card.
LOOPBACK TESTS: During the loopback tests, network traffic can cause a false
failure of the test. Also, be sure to connect or disconnect from the network
when directed. Failure to do so can cause a failure of the test.
1.6 SYSTEM PITFALLS
____________________
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 Fax/Modem/Ethernet Combo Adapter.
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.
If you are using Card and Socket Services, make sure your PCMCIA socket is
enabled. If your socket is not enabled, Socket Services will not load and
will not display an error message; Card Services will not load, but will
display an error message that Socket Services is not present.
1.6.1 SUPER CLIENT DRIVERS
Many vendors are providing customers with Super Client drivers. This is a
driver that will enable many different PCMCIA cards. PC-DOS 6.1 includes one
called PCMSCD.EXE, for example. They are best used for modems and other
cards that do not have a Card Services client driver of their own. The
Fax/Modem/Ethernet client drivers have been written to take advantage of Card
Services and this advantage would be taken away if a super client driver
enabled the adapter.
The adapter DOS drivers use a feature called "Request Exclusive". This
allows the DOS drivers to coexist with a super client driver. Basically, the
drivers take control away from the super client driver when the driver con-
figures our card.
18
Another product which can enable adapters is PC Card Director. PC Card
Director can not enable the Fax/Modem/Ethernet Combo adapter because it is a
multifunction adapter.
1.6.2 MEMORY CONFLICTS AND MEMORY MANAGERS
The Fax/Modem/Ethernet Combo Adapter is a shared RAM adapter and utilizes
20KB + 1 byte of the system memory space. Many computers cache or shadow
sections of memory to speed up operations. Some 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.
The DOS utility EMM386.EXE, if used, must be configured to exclude the memory
used by the adapter for its Shared RAM. A different memory range is excluded
wheninstalling the Modem ONly option. Here is an example invocation of
EMM386.EXE in your CONFIG.SYS:
Ethernet:
DEVICE=C:\DOS\EMM386.EXE X=D400-D900
Modem Only:
DEVICE=C:\DOS\EMM386.EXE X=D000-D100
This would exclude the memory areas necessary for standard default operation.
Notice that the range for ethernet is from D400 to D900 (20Kb + 1byte).
When using utilities like QEMM or 386MAX, it is important to exclude the
memory used by these utilities from the memory used by the PC Card. The
operation of the PC Card will be affected.
The installation program will add the proper excludes for EMM386 automat-
ically based on your selections. If you change your memory location, add
EMM386, or use some other memory manager you must edit your CONFIG.SYS file
or rerun the installation.
The installation will NOT check for conflicts with the page frame or with
other includes. For example either of the following :
DEVICE=C:\DOS\EMM386.EXE FRAME=D000 X=D400-D900 or
DEVICE=C:\DOS\EMM386.EXE I=D000-D600 X=D400-D900
would result in warning messages issued by EMM386 and would cause unpredict-
able results. If you are unsure of the memory manager syntax, refer to the
documentation for the memory manager or DOS manuals.
Contents 19
1.6.3 MISCELLANEOUS
o If you plan on using your Fax/Modem & Ethernet Credit Card with OS/2 Warp
or OS/2 Warp Connect as both modem and ethernet functions, you must
specify the adapter interrupt in your PROTOCOL.INI or NET.CFG files. The
COM.SYS shipped with this diskette does not notify the Resource Manager
of which COM resources are in use. It is possible that if an interrupt
is in use by a COM port, Card Services may also let the adapter have it.
Example of a PROTOCOL.INI file :
;Fax/Modem/Ethernet Combo Adapter
DriverName = FME_CS$ <--- Driver name; not user changeable
IOBASE = 0x300 <--- I/O start address for Ethernet
INTERRUPT = 5 <--- Interrupt value for card
COMPORT = 2 <--- COMPORT value for modem
RAMADDRESS = 0xD4000 <--- Shared memory address - Ethernet
PCMCIA <--- Inserted if Card Services is present
Example of a NET.CFG file :
Link Driver FME_NET <--- Driver name; not user changeable
PORT 300 <--- I/O start address for Ethernet
INT 5 <--- Interrupt value for card
COMPORT 2 <--- COMPORT value for modem
MEM D4000 <--- Shared memory address - Ethernet
PCMCIA <--- Inserted if Card Services is present
FRAME ETHERNET_802.3 <--- Media Frame type
o Tested Card and Socket Services include IBM versions 1.18 and 1.20,
Phoenix CardManager Plus version 3.00, Phoenix version 1.0, and
SystemSoft CardSoft versions 2.02, 2.03, 2.0 7 and 3.1.
o It is important to have a Fax/Modem/Ethernet Combo Adapter inserted in
your computer before starting some Local Area Network software. Unpre-
dictable results may occur if the adapter is not present and the software
is executed.
o It is also important not to remove your PC Card once communication on a
LAN has begun. Unpredictable operation can occur if this happens (pos-
sible system hang).
o The FME_NDIS.NIF file is intended for use only with the
Fax/Modem/Ethernet Combo Adapter. Errors may result if used with other
Ethernet cards.
o Notebook computers typically use Card and Socket Services. If you do not
want to use Card and Socket Services, POINTFME.EXE can be used (DOS
only). A system hang may result if POINTFME.EXE is used with Card Ser-
vices. Use the Installation program to remove any connectivity enablers.
o If you plan to use DOS LAN Requester and your machine has MS-DOS on it,
you may run into a problem where the DOS LAN Requester installation indi-
cates you have an incorrect DOS version. If you have this problem, use
20
the SETVER command and driver to alter the version of DOS reported to
CIP_MAIN.EXE. Change the version of DOS to 5.00 for this program and you
should be able to finish the installation. See your MS-DOS manual for
implementation details. This is not a problem with PC-DOS.
o If you will be running DOS LAN Requester 3.0 on a busy network, or if you
see the error NET807(?): drive n: no longer exists, abort, retry , fail?
when the connection still exists, you should modify the /WRK parameter in
the DOSLAN.INI file to disable the block RAW SMB protocol. The RAW SMB
protocol is better suited to Token-Ring networks, where collisions are
not a problem. This function is disabled by setting the 15th variable to
1, i.e.: /WRK:111121101021211
o On the IBM 750P Thinkpad there may be a conflict between the Pen inter-
rupt and the interrupt for the Fax/Modem/Ethernet Combo Adapter. There
are several ways to solve this problem. If you are using Card Services,
please get the latest PCMCIA Features Diskette. This should be Version
1.20 or above. If you are using the enabler, the installation will
choose a different default that does not conflict with the Pen interrupt.
You can determine or change the pen interrupt by running PS2.
o If you have an IBM PS/2 E and you are installing the Fax/Modem/Ethernet
Combo Adapter under a Card Services environment, you will likely need to
upgrade your Card and Socket Se rvices. You will need the latest PCMCIA
features diskette, level 1.20 or above. The features diskette for the
IBM Thinkpad 350 or 75X can be used on the PS/2 E. Older versions o f
Card and Socket Services may hang your computer when you start your
network.
o The following machines have two PCMCIA sockets. Here are their socket
assignments:
Socket A (or 1) Socket B (or 2)
--------------- ---------------
AST Powerexec Bottom Top
IBM ThinkPad 360 Top Bottom
IBM ThinkPad 750 Top Bottom
IBM ThinkPad 755 Top Bottom
NEC UltraLite VERSA Bottom Top
o The PS/2-E Model 9533 has four PCMCIA sockets. Here are their
assignments:
Socket A - Front Top
Socket B - Front Bottom
Socket C - Back Top
Socket D - Back Bottom
Contents 21
o The IBM Port Replicator and Dock II has two PCMCIA sockets. If you are
using a point enabler (DOS only) , they have the following assignments.
You must use the PCIC=03E2 parameter with the POINTFME.EXE enabler. Note
that sockets A and B are in the replicator or Docking station and the
computer sockets become C and D.
Socket A - Additional Top Socket
Socket B - Additional Bottom Socket
Socket C - Computer Top Socket
Socket D - Computer Bottom Socket
o Single Socket machines use Socket A.
o The AST Ascentia 900N has two PCMCIA sockets. Here are their assign-
ments. You must use the PCIC=03E4 with the POINTFME.EXE enabler (DOS
only) if you are using Socket C.
Socket A - Bottom Socket
Socket C - Top Socket
o If you plan on using the SNA Phone Connect feature of Communications
Manager/2 1.11, you must use the Card Services-aware modem enabler
FMECS.SYS or the NDIS driver FME_NDIS.OS2 with the MODEMONLY keyword in
the FME_NDIS_nif section of PROTOCOL.INI. CM/2 will report an error that
it cannot open the COM port if you have the Fax/Modem/Ethernet NDIS
driver loaded without the MODEMONLY keyword. You must also use the
standard COMx port assignments shown later in this README.
o If you plan on using the Internet Access Kit with Warp, a good choice for
a modem is the IBM PCMCIA. This modem seemed to have the best results.
o If you plan on connecting to the Internet via OS/2 TCP/IP, you will need
at least verion 3.0 to have simultaneous ethernet LAN support and modem
support. OS/2 WARP Connect ships with OS/2 TCP/IP Version 3.0.
o If you are using an Ambra NB9800A and you plan on using the OS/2 Debug
Kernel you must set the COMPORT to 3. To do this:
NDIS Add COMPORT = 3 to the FME_NDIS_nif section in
PROTOCOL.INI
ODI Add COMPORT 3 to the Link Driver FME_NET
section in NET.CFG
Modem Enabler Add /COM 3 to the DRIVER=FMECS.SYS line
in CONFIG.SYS
22
1.7 MODEM OPERATION
____________________
The COM port chosen during Fax/Modem/Ethernet Combo Adapter installation must
match the COM port chosen for your modem software. This can usually be
changed in the modem software rather easily.
If you are asked to choose a modem type while installing your modem software,
choose Boca Research, Zoom or Hayes Compatible modem.
1.7.1 MODEM ENABLER SYNTAX FOR DOS
MODEMCS.SYS Syntax :
DEVICE=\path\MODEMCS.SYS /COMX
X = 1, 2, 3, 4
POINTMOD.EXE Syntax :
DEVICE=\path\POINTMOD.EXE SA/SB/SC/SD WS=0,1,2,3 COM1/COM2/COM3/COM4
SRAM=XXXX PCIC=XXXX
SA/SB/SC/SD - Socket A, B, C, or D
WS - Wait State selection
COM1/COM2/COM3/COM4 - Com Port selection
SRAM - shared RAM Address
PCIC - PC Card Interface Controller base I/O port
XXXX - a hexidecimal number
1.7.2 CARD SERVICES-AWARE MODEM ENABLER SYNTAX FOR OS/2
FMECS.SYS Syntax :
DEVICE=FMECS.SYS /COM port /IRQ level /IO addr
port: 1, 2, 3, 4. The default is 2.
level: 2, 3, 4, 5, 7, 9, 10, 11, 12, 14, 15.
The default is based on the standard COM port definition.
addr: 0000-FFF8 (hexadecimal) in multiples of 8.
The default is based on the standard COM port definition.
1.7.3 ERROR INDICATIONS
If you get a message when trying to start windows such as: "Cannot find a
device file that may be needed to run Windows in 386 enhanced mode" and it
mentions VFMED.386 you may have specified the wrong path for your windows
directory during the installation. Compare the path given in the
PROTOCOL.INI or NET.CFG with the actual location of the VFMED.386 file.
If your modem communications software posts an error about a com port con-
flict or possibly hangs, ensure that the modem software is configured to use
the com port selected during the fax/modem/ethernet installation. If these
Contents 23
comport settings match and you are still having difficulties, verify that the
com port is available. The four COM ports, COM1 through COM4, and their
associated base-address values, are shown as follows :
COM1: 03f8h IRQ4
COM2: 02f8h IRQ3
COM3: 03e8h IRQ4
COM4: 02e8h IRQ3
Your modem communication software may be dependent on these com port set-
tings. The Fax/Modem/Ethernet installation will ensure the adapter's values
are set up appropriately.
1.8 CORRECTIONS TO THE USER'S GUIDE
____________________________________
o Page 53, the range for the COM I/O port is incorrectly stated as
0120h-3C00h. It is actually 0100h-FFF8h and is in increments of 8.
o Pages 80-81, error messages LTU0076 through LTU0078 have been modifed.
They now read:
24
LTU0076E Fax/Modem/Ethernet Credit Card Cannot allocate
COM%1. Return code %2.
The requested COM port could not be allocated.
Either add or change the COMPORT keyword in
PROTOCOL.INI to an un-used COM port value in
the range 1-4.
Another possible problem is that you do not
have the correct version of COM.SYS loaded.
Check the COM.SYS in your CONFIG.SYS and ensure
that it is the same one that came with your
Fax/Modem/Ethernet Combo Credit Card Adapter.
If it is not, run the Install program for the
Credit Card Adapter.
LTU0077E Fax/Modem/Ethernet Credit Card Cannot find a free
COM port.
There are no COM ports available.
Free up a COM port. On most notebook computers this
can be done through a setup program that disables
specific COM ports.
Another possible problem is that you do not
have the correct version of COM.SYS loaded.
Check the COM.SYS in your CONFIG.SYS and ensure
that it is the same one that came with your
Fax/Modem/Ethernet Combo Credit Card Adapter.
If it is not, run the Install program for the
Credit Card Adapter.
LTU0078E Fax/Modem/Ethernet Credit Card Cannot attach to
COM.SYS.
COM.SYS cannot be found in CONFIG.SYS.
Make sure that COM.SYS is in CONFIG.SYS. If
it is not, run OS/2 Selective Install and select
Serial Support. Then run the Install program
for the Credit Card Adapter. If there already
is a COM.SYS in CONFIG.SYS, ensure that it is the
same one that came with your Fax/Modem/Ethernet
Combo Credit Card Adapter. If it is not, run the
Install program for the Credit Card Adapter.
o Page 72, the last bullet is incorrect. It should read,
Contents 25
If you are using the modem only enabler, FMECS.SYS:
A message will only be displayed if the syntax for
any of the parameters is incorrect. You will not
see a message if a resource request could not be
satisfied. If a resource could not be requested,
you will hear a number of alternating beeps (one
high and one low) indicating the resource request
that failed.
1 alternating tone (high, low)
COM.SYS could not be found.
2 alternating tones (high, low, high, low)
PCMCIA.SYS could not be found or is at a
wrong level.
3 alternating tones
Could not get the I/O port needed.
4 alternating tones
Could not get the IRQ needed.
5 alternating tones
Could not configure the card.
6 alternating tones
Could not configure the COM port requested.
This indicates that either COM.SYS is not
present or is at the wrong level.
Sometimes it can be difficult to differentiate between
errors. For example,
if you have the following line in CONFIG.SYS:
DEVICE=C:\FMECS.SYS /COM 1
and COM1 already exists, you will hear 3 (high, low) alternating tones.
This is because the driver will first try to acquire all of its resources
(I/O, IRQ) before trying to add the COMx port. If one of those requests
fails, the tones heard will be for that request. The series of tones is
not cumulative. As soon as a resource cannot be acquired, the tones will
be heard and all the rest of the resource requests will be abandoned.
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. INTEL is a trade-
mark of the INTEL Corporation. NEC is a trademark of the NEC Corporation.
DATABOOK is a trademark of Databook Incorporated.
26