OS/2 v2.x Workstation, mixed environment
Installing and Configuring the Intel TokenExpress(TM) PRO
adapter for a mixed environment
=========================================================
Location of driver: disk 2 \IBMOS2
For sample configuration files, see the end of this document.
General Installation
--------------------
Extended Services / 2 - Communications Manager
IBM OS/2 LAN Requester - To connect to IBM LAN Server (TPRO.OS2)
NetWare OS/2 LAN Requester - To connect to NetWare Server (LANSUP.SYS)
Using Intel TokenExpress(TM) PRO adapter drivers with IBM OS/2 2.x
------------------------------------------------------------------
To connect in a mixed IBM/Novell operating environment, several
adapter drivers and protocols must co-exist concurrently. This
document describes how to install and configure the TokenExpress
PRO adapter NDIS driver and the ODI driver from Novell. The example
configuration files may vary slightly depending on your particular
network.
It is important to follow the sequence for installation described
in this document in order to minimize manual modifications.
Quick steps
-----------
1. Install IBM OS/2 2.x Base Operating System
2. Install Extended Services /2 and Communications Manager and configure
for network connectivity depending on your needs.
3. Install the TokenExpress PRO adapter and NDIS driver
4. Install IBM OS/2 LAN Requester (if connecting to IBM LAN Server)
5. Install NetWare OS/2 LAN Requester and ODI driver
6. Manually modify the CONFIG.SYS file
Detailed steps
--------------
1. Install IBM OS/2 2.x Base Operating System.
Use the IBM OS/2 2.x Installation Manual to install the
operating system.
2. Install Extended Services/2 and Communications Manager and
configure for network connectivity depending on your needs
such as 3270 or 5250 terminal emulation.
Use the IBM ES/2 Communications Manager installation manual
to install 3270 or 5250. When installing communications
manager you are asked to select a network adapter. Choose the
IBM 16/4 adapter. The CONFIG.SYS will be modified to include
drivers for the IBM adapter. When you reboot your system, you
will receive errors indicating this adapter is not installed
when these drivers try to load. Ignore these messages and go
on, we will be replacing the IBM adapter drivers with Intel
adapter drivers. At that time you will reboot and no longer
receive these errors.
3. Install the TokenExpress PRO adapter and driver.
To install the Intel TokenExpress PRO adapter, refer to the
adapter installation guide. Once the adapter has been installed
and diagnostics have been run, you are ready to install the
adapter drivers.
When running the diagnostics, be sure to write down the
adapter's burned-in address. You need this when you create
the NET.CFG file during Netware Requester installation.
Also, don't run diagnostics from a DOS window from OS/2.
You need to reboot with a DOS diskette and run the
diagnostics with running AUTOEXEC.BAT or CONFIG.SYS.
a. Reboot your system.
b. Start the Communication Manager and select "Advanced",
"Configuration", "LAN Adapter and Protocol Support".
Select "Copy additional network adapter drivers". When
requested, type in the path to the driver: A:\IBMOS2.
Insert the Drivers disk (disk 2).
c. Next, select "Configure workstation". After the drivers
have been copied to the hard drive, you need to "REMOVE"
the IBM adapter driver and protocols from the "Current
Configuration" window and "ADD" the Intel adapter driver
and protocols. Follow the instructions on the screen to
REMOVE and ADD adapter protocols and drivers.
d. Configure your workstation to fit your needs (refer to
your IBM documentation). If you want more information
about configuration parameters, please refer to the section
"Configuring the MAC Driver" at the end of this document.
e. When you complete the installation, the following files
will have been copied to the \IBMCOM\MACS directory:
TPRO.OS2 TokenExpress PRO adapter OS/2 NDIS driver
TPROEOS2.NIF TokenExpress PRO adapter Network
interface file
(used by config utility)
f. The CONFIG.SYS and PROTOCOL.INI files have been modified to
reflect removing the IBM adapter drivers and adding the Intel
TokenExpress PRO adapter NDIS driver.
g. This ends the NDIS driver installation.
4. Install IBM OS/2 LAN Requester (if connecting to IBM LAN Server).
Use the IBM OS/2 LAN Requester Installation Manual for
installation instructions. No driver installation is needed
since you installed the adapter driver through Communications
Manager.
5. Install NetWare OS/2 Lan Requester.
a. Follow Novell's installation instructions for installing
Netware Requester. During the installation you are asked
to enter the name of the Network Interface Card driver.
Enter "LANSUP.SYS" (this is the ODI driver for OS/2).
b. Choose the kind of session support you prefer depending on
your configuration.
c. Click on "Save" to save the configuration.
d. When prompted, enter the path\filename for the ODI driver.
This is the same path you chose when you installed the
Netware Requester files, probably "C:\NETWARE\LANSUP.SYS".
The CONFIG.SYS file will be modified to include the
statement, "DEVICE=C:\NETWARE\LANSUP.SYS".
e. Continue with the installation. When the installation is
complete select "Configuration", "This Workstation". Now
enter the following in the NET.CFG file.
Link Driver LANSUP
Frame Token-Ring
Frame Token-Ring_SNAP
Node Address nnnnnnnnnnnn
Link Support
Buffers 15 4210
For Node Address use the Universal Address you wrote down
during adapter hardware diagnostics, or use a locally
administered address.
f. Netware Requester installation is now complete. You need to
modify your CONFIG.SYS file before rebooting.
6. Manually modify the CONFIG.SYS file so that all the Netware
Requester statements are at the bottom. The main idea here
is to make sure the TokenExpress PRO adaper NDIS driver
(TPRO.OS2) is loaded before the ODI driver "LANSUP.SYS".
Hints and Tips
--------------
Installing multiple adapters in the same computer
-------------------------------------------------
You may install up to four TokenExpress PRO adapters in your PC.
To configure the PROTOCOL.INI file for two adapters in the same
computer, follow the steps below:
1. Configure the adapters so that they have different I/O
addresses and interrupts.
2. Follow the instructions in the IBM installation manuals for
multiple adapters, to establish CONFIG.SYS and PROTOCOL.INI
files that support multiple adapters.
3. Edit the PROTOCOL.INI file, and find the Intel adapter
sections that begin with "drivername = TPRO$" and
"drivername = TPRO2$". Make sure the TPRO$ adapter has a
lower I/O address than the TPRO2$ adapter. For example:
[TPROEOS2_nif]
DriverName = TPRO$
IOADDRESS = 300
[TPROEOS2_nif]
DriverName = TPRO2$
IOADDRESS = 310
Configuring the MAC driver
--------------------------
This section explains how to modify the NDIS driver configuration
file (PROTOCOL.INI) to use the TokenExpress PRO adapter drivers.
A sample file, containing the recommended entries for configuring
the TokenExpress PRO adapter DOS NDIS and OS/2 NDIS drivers, is
included on the Intel driver disk (disk 2).
The Intel-specific parameters needed to customize the PROTOCOL.INI
file are listed below.
If you need to change any of the TokenExpress PRO adapter's
parameters after installation, find the appropriate section in
the PROTOCOL.INI for the TokenExpress PRO adapter. This section
has the heading "[INTEL32_NIF]" or "[INTEL16_NIF]" and should
begin with the statement "drivername = OLISRV$" or "drivername =
OLITOK$". Add any new keywords or change their values as necessary.
Required Parameters
-------------------
The TokenExpress PRO adapter driver requires two entries in
PROTOCOL.INI: drivername = TPRO$ and IOaddress=xxx (where xxx
is the I/O Address of the card). "Drivername" can be any
characters (up to 7) followed by a dollar sign ($). The default
drivername is TPRO$. The driver name identifies the network driver.
The drivername (with small or capital letters) is the prefix portion
of the filename of the network driver in the DRIVERS directory
followed by $. The MAC drivername is TPROODI$.
Since the TokenExpress PRO adapter driver implements the loopback
function, the [DLC] section of PROTOCOL.INI does not need a
"loopback =" entry.
Optional Parameters
-------------------
Adapter Card Configuration Entries:
NodeAddress = [hex value] [hex value] [hex value]
EarlyRelease = [YES/NO]
NodeAddress
Specifies the address which replaces the adapter's Burned-In
Address (BIA). (The new address must be locally administered).
[hex value] has the form 0xdddd; d = hexadecimal digit.
EarlyRelease
Enables or disables Early Token Release.
MAC Driver Configuration Entries:
MaxRequests = value
MaxTransmits = value
RecBufSize = value
RecBufCount = value
RecBufHigh = value
Rpl
MaxRequests
Sets the maximum number of "General Requests." Can be any
value from 1 to 10. (Default = 6).
MaxTransmits
Sets the maximum number of outstanding "TransmitChain"
commands. On a server, this number should equal the product
of the following two numbers:
[NetBEUI DLC.MAXOUT parameter]*[max number of sessions]
For DOS, this can be any number from 2 to 6. For OS/2, any
number from 2 to 100. The default is 6.
RecBufSize
Sets the size (in bytes) of the buffers in the Receive Buffer
pool. This number ranges from 256 to 5000. Default is 512.
The maximum size of the frames which may be received by the
adapter is:
min (MaxFs, RecBufSize x (RecBufCount -1))
RECOMMENDED MAX SIZE: The maximum amount of receive buffers,
RecBufSize x RecBufCount, should not exceed 64K bytes. In
DOS workstations, this number should not exceed 20Kb. In DOS
RPL workstations, this number should not exceed 7Kb.
RecBufCount
Sets the number of buffers in the Receive Buffer Pool. Can
be any number from 4 to 10. Default is 10.
The maximum size of the frames which may be received by the
adapter is:
min (MaxFs, RecBufSize x (RecBufCount -1))
RecBufHigh
Determines where to load the Receive Buffer Pool. Can be
either 0 or 1. Default is 0.
0 = first try loading into high memory; if that fails, try
low memory.
1 = first try loading into low memory; try high memory if
that fails.
EarlyRelease
Sets board to use early token release on 16 Mbps LANs.
YES = enable ETR, NO = disable ETR.
This parameter is ignored for 4 Mbps LANs.
Rpl
If present, this postpones adapter initialization from
workstation boot-up time to NETBIND execution time. This
ensures that the remote boot process is not disturbed by
the board's initialization and diagnostics.
Sample configuration files
--------------------------
CONFIG.SYS
IFS=C:\OS2\HPFS.IFS /CACHE:384 /CRECL:4 /AUTOCHECK:C
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=C:\IBMLAN\NETLIB;C:\MUGLIB\DLL;.;C:\OS2.......
SET PATH=C:\IBMLAN\NETPROG;C:\OS2;C:\MUGLIB;C:\OS2\......
SET DPATH=C:\IBMLAN\NETPROG;C:\IBMLAN;C:\OS2;C:\MUGLIB\......
SET PROMPT=$i[$p]
SET HELP=C:\CMLIB\APPN;C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
PRIORITY_DISK_IO=YES
FILES=20
DEVICE=C:\ibmcom\lanmsgdd.os2 /I:C:\ibmcom
DEVICE=C:\ibmcom\protman.os2 /I:C:\ibmcom
DEVICE=C:\ibmcom\protocol\LANDD.OS2
DEVICE=C:\ibmcom\protocol\LANDLLDD.OS2
DEVICE=C:\OS2\R0CSDD.SYS
DEVICE=C:\OS2\TESTCFG.SYS
DEVICE=C:\OS2\DOS.SYS
DEVICE=C:\OS2\PMDD.SYS
BUFFERS=30
IOPL=YES
DISKCACHE=64,LW
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 4096
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
REM SET DELDIR=C:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=OS2DASD.DMD
SET BOOKSHELF=C:\IBMLAN\BOOK;C:\OS2\BOOK;
SET EPATH=C:\OS2\APPS
REM DEVICE=C:\OS2\APPS\SASYNCDA.SYS
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /P
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DOS=LOW,NOUMB
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VCDROM.SYS
DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_VGA
SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=C:\OS2\MDOS\VSVGA.SYS
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\MOUSE.SYS SERIAL=COM1
DEVICE=C:\OS2\COM.SYS
DEVICE=C:\OS2\MDOS\VCOM.SYS
CODEPAGE=437,850
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
DEVICE=C:\CMLIB\ACSLDLAN.SYS
RUN=C:\OS2\EPW.EXE
RUN=C:\ibmcom\protocol\landll.exe
RUN=C:\ibmcom\protocol\netbind.exe
RUN=C:\ibmcom\lanmsgex.exe
DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=C:\IBMCOM\MACS\TPRO.OS2
DEVICE=C:\CMLIB\APPN\CMKFMDE.SYS
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
rem --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
DEVICE=C:\NETWARE\LANSUP.SYS
rem DEVICE=C:\NETWARE\TPROODI.SYS
DEVICE=C:\NETWARE\IPX.SYS
rem DEVICE=C:\NETWARE\SPX.SYS
rem RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
rem --- NetWare Requester statements END ---
PROTOCOL.INI
[PROT_MAN]
DriverName = PROTMAN$
[IBMLXCFG]
INTELTOK_nif = TPRO.nif
LANDD_nif = LANDD.nif
NETBEUI_nif = NETBEUI.nif
rem * PROTOCOL SECTION *
[LANDD_nif]
DriverName = LANDD$
Bindings = INTEL16_nif
ETHERAND_TYPE = "I"
SYSTEM_KEY = 0x0
OPEN_OPTIONS = 0x2000
TRACE = 0x0
LINKS = 8
MAX_SAPS = 3
MAX_G_SAPS = 0
USERS = 3
TI_TICK_G1 = 255
T1_TICK_G1 = 15
T2_TICK_G1 = 3
TI_TICK_G2 = 255
T1_TICK_G2 = 25
T2_TICK_G2 = 10
IPACKETS = 250
UIPACKETS = 100
MAXTRANSMITS = 6
MINTRANSMITS = 2
TCBS = 64
GDTS = 30
ELEMENTS = 800
[NETBEUI_nif]
DriverName = netbeui$
Bindings = INTEL16_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
SESSIONS = 40
NCBS = 95
NAMES = 21
SELECTORS = 5
USEMAXDATAGRAM = "NO"
ADAPTRATE = 1000
WINDOWERRORS = 0
TI = 30000
T1 = 500
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 8
NAMECACHE = 0
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 2
PACKETS = 350
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 5
rem * MAC SECTION *
[TPRO_nif]
DriverName = TPRO$
IOADDRESS = 300
MAXTRANSMITS = 30
RECBUFSIZE = 2048
RECBUFCOUNT = 10
NET.CFG
Link Driver LANSUP
Frame Token-Ring
Frame Token-Ring_SNAP
Node Address nnnnnnnnnnnn
Link Support
Buffers 15 4210
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.