![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM) Adapter: Driver Installation on 3+Open v1.X Network
TOKENEXPRESS AND 3COM 3+OPEN
This file contains instructions for installing the TokenExpress adapter
driver. It contains information specific to the installation and
operation of Intel's TokenExpress adapters only. Refer to the
appropriate Network Operation System documentation for any NOS-specific
questions or other information.
These instructions apply to Release 4.0 of the software.
You'll always find the most current version of the driver instructions
and iIf the driver software has changed, you can get the latest drivers
and instructions from Intel's online services. Always check the
revision date of the document to make sure you have the most updated
copy.
Note: This software is only supported in the -001 release of
the TokenExpress drivers.
Installing the TokenExpress adapter driver in a 3+Open server
1. Install 3+Open as described in the 3COM documentation. When the
NETSETUP program displays a list of adapters to choose from, choose
any name from the list; you will have to change it later.
2. Install the TokenExpress adapter drivers for OS/2 and DOS LAN
Manager on your server.
Note: The following instructions assume you are installing onto
your server's hard drive C: with the 3OPEN directory present in the
root directory.
Insert the Intel diskette containing the MS LANMAN drivers in the
A: drive on your server, change to that drive, and copy the
following drivers to the server:
OS/2 drivers
1. Copy the OS/2 driver OLITOK.OS2 and OC16.BIN (adapter download
file) to the 3+Open directory \3OPEN\OS2DRV\MAC on your server by
entering:
COPY A:\MSLANMAN.OS2\DRIVERS\OLITOK\OLITOK.OS2 C:\3OPEN\OS2DRV\MAC
COPY A:\MSLANMAN.OS2\DRIVERS\OLITOK\OC16.BIN C:\3OPEN\OS2DRV\MAC
2. Copy OLITOK.3CO to the \3OPEN\OS2DRV\MAC directory on your server
while renaming it to OLITOK.NIF by entering:
COPY A:\MSLANMAN\OLITOK.3CO C:\3OPEN\OS2DRV\MAC\OLITOK.NIF
Use a text editor to merge the entire file PROTOCOL.3CO (under the
MSLANMAN directory on the Intel diskette) into the PROTOCOL.3CM
file in the 3OPEN\OS2DRV directory on your server. This operation
will add a section to PROTOCOL.3CM headed by "; Intel TokenExpress
16/4." The statements that follow will be of the type "keyword =
value." For information on these configuration values see
"Customizing PROTOCOL.3CM" at the end of this file.
DOS drivers
1. Copy the DOS driver OLITOK.DOS and OC16.BIN (adapter download file)
to the 3+Open directory \3OPEN\DOSDRV\MAC on your server, by
entering:
COPY A:\MSLANMAN.DOS\DRIVERS\OLITOK\OLITOK.DOS C:\3OPEN\DOSDRV\MAC
COPY A:\MSLANMAN.DOS\DRIVERS\OLITOK\OC16.BIN C:\3OPEN\DOSDRV\MAC
2. Copy OLITOK.3CD to the \3OPEN\DOSDRV\MAC directory on your server
while renaming it to OLITOK.NIF, by entering:
COPY A:\MSLANMAN\OLITOK.3CD C:\3OPEN\DOSDRV\MAC\OLITOK.NIF
Use a text editor to merge the entire file PROTOCOL.3CD (under the
MSLANMAN directory on the Intel diskette) into the PROTOCOL.3CM
file in the 3OPEN\DOSDRV directory on your server. This operation
will add a section to PROTOCOL.3CM headed by "; Intel
TokenExpress16/4". The statements that follow will be of the type
"keyword = value". For information on these configuration values
see "Customizing PROTOCOL.3CM" at the end of this file.
3. Add the OLITOK.NIF driver to the "ExMacDriver =" entry in the
CARDXNS.NIF file. This file is in the directory 3OPEN\DOSDRV\PROT.
4. Run the NETSETUP program again. Choose the "Modify Configuration
Settings" option. When you are prompted for an adapter, choose
the Intel TokenExpress adapter. Exit from NETSETUP to the OS/2
command prompt.
5. View your CONFIG.SYS file. You will see a DEVICE statment similar
to the following in the 3+OPEN section near the end of the file.
DEVICE=C:\3OPEN\SERVER\LANMAN\DRIVERS\OLITOK.OS2
Copy the adapter download code file OC16.BIN to the same directory
that contains the Intel driver OLITOK.OS2 by entering:
COPY C:\3OPEN\OS2DRV\MAC\OC16.BIN C:\3OPEN\SERVER\LANMAN\DRIVERS
Installing the TokenExpress adapter driver in a 3+OPEN OS/2 workstation
The previous section described installation of TokenExpress drivers on a
3+Open V1.x server. The installation procedure for a 3+Open OS/2
workstation is very similar, except that the directory \3OPEN\SERVER is
substituted by \3OPEN\OS2WKSTA.
Installing the TokenExpress adapter driver in a 3+OPEN DOS workstation
1. Put a DOS bootable diskette in drive A: of the server that you
installed the Intel TokenExpress adapter drivers on (see section
above).
2. Run the NETSETUP program at the server. Choose drive A:\ as the
target (or destination) path in the appropriate menu. When you are
prompted for the name of an adapter, choose the Intel TokenExpress
adapter. After NETSETUP completes, exit to the OS/2 command prompt.
3. Share the 3+Open directory structure on the server by typing a
command at the server similar to the following:
NET SHARE SERV=C:\
4. Boot the workstation with the newly created diskette. Your
workstation should be physically connected to the same LAN as your
server.
5. Login with ADMIN privileges at the workstation. Access the share
you created in step 3 by entering:
NET USE F: \\<ServerName>\SERV
6. Change to the F: drive you just specified with the NET USE command.
7. Run the NETSETUP program. Since it will not be in your PATH, you
will have to invoke it as follows:
3OPEN\SERVER\LANMAN\NETPROG\NETSETUP
Choose F:\ as your source path and C:\ as the target (if you want
to install 3+OPEN in the root directory on drive C:). When you are
prompted for the name of an adapter, choose the Intel TokenExpress
adapter.
When NETSETUP completes successfully 3+OPEN will be installed on
your DOS workstation's hard disk.
8. Copy the adapter download code file OC16.BIN from the Intel
diskette to the directory that contains the Intel driver
OLITOK.DOS by entering:
COPY A:\MSLANMAN.DOS\OLITOK\DRIVERS\OC16.BIN
C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS
Reboot for the installation to take effect.
Customizing the PROTOCOL.3CM files
This section explains how to modify the TokenExpress adapter board's
configuration in 3+OPEN's PROTOCOL.3CM files (located in the
\3OPEN\OS2DRV and the \3OPEN\DOSDRV directories).
If you need to change one of the TokenExpress adapter board's software
parameters after installation, find the section in PROTOCOL.3CM that
refers to the TokenExpress adapter. (The section should begin with ";
Intel TokenExpress".) Add or delete parameters to make the changes you
want. For the changes to take effect in 3+Open, you must run the
NETSETUP program.
The PROTCOL.3CM file (located in the \3OPEN\OS2DRV directory) has the
following parameters:
MAXTRANSMITS = value
RECBUFSIZE = value
RECBUFCOUNT = value
MaxTransmits sets the maximum number of oustanding "TransmitChain"
commands. On a server, this number should equal the product of the
following two numbers: [value of NetBEUI DLC.MAXOUT parameter]*[maximum
number of sessions].
For DOS: Can be any number from 2 to 6.
For OS/2: Can be any number from 2 to 100 (Default = 6).
RecBufSize sets the size (in bytes) of the buffers in the Receive Buffer
pool. Can be any number from 256 to 5000 (Default = 512).
The maximum size of the frames which may be received by the adapter is:
min (MaxFs, RecBufSize x (RecBufCount -1))
RecBufCount sets the number of buffers in the Receive Buffer Pool. Can
be any number from 4 to 10. Default = 10
The PROTCOL.3CM file (located in the \3OPEN\DOSDRV directory) has the
following parameters:
MAXTRANSMITS = value
RECBUFSIZE = value
RECBUFCOUNT = value
MAXREQUESTS = value
MaxTransmits - see description for MaxTransmits shown above.
RecBufSize - see description for RecBufSize shown above.
RecBufCount - see description for RecBufCount shown above.
MaxRequests - sets the maximum number of "General Requests." Can be any
value from 1 to 10. Default = 6
Customizing the PROTOCOL.INI file
This section explains how to modify the TokenExpress adapter
configuration in 3+OPEN's PROTOCOL.INI file. This file is located in
the \3OPEN\<system>\LANMAN\DRIVERS directory where <system> is the name
of the sytem, for example "SERVER", "OS2WKSTA" etc.
If you need to change one of the TokenExpress adapter's software
parameters after installation, find the section in PROTOCOL.INI that
refers to the Intel TokenExpress adapter. (The section begins with
"DRIVERNAME = OLITOK$.") Add the following keywords or change their
values as appropriate.
Refer to your 3+Open documentation for more details on the contents of
PROTOCOL.INI.
Required parameters
One entry is required in the [OLITOK] (Intel's MAC driver) section in
PROTOCOL.INI:
drivername = OLITOK$
The TokenExpress adapter implements the loopback function, so the [DLC]
section of PROTOCOL.INI does not need a "loopback =" entry.
Optional parameters
The optional entries in the OLITOK section may be divided into two
groups:
1. Entries related to the configuration of the board itself
2. Entries related to the driver software (OLITOK).
The entries and syntax for the two groups are listed below.
1. Adapter Card Configuration Entries:
Adapter = [adapter number]
NodeAddress = [hex value] [hex value] [hex value]
EarlyRelease = [YES/NO]
Adapter selects the board to configure. [adapter number] must be 0, 1,
2, or 3, where:
0 = "Primary" adapter (default, I/O address 0A20H)
1 = "Alternate" adapter (I/O address 0A24H)
2 = "Second primary" adapter (I/O address 0A50H)
3 = "Second alternate" adapter (I/O address 0A54H)
For an ISA board, use this parameter if you change the board's I/O
address switch setting.
For an MCA or EISA board, use this parameter if you change the I/O
address in the board's configuration file.
NodeAddress specifies the number with which you are replacing the
board's burned-in node address. (You must administer the new node
address locally.) [hex value] has the form 0xdddd; d = hexadecimal
digit
EarlyRelease enables or disables Early Token Release. YES = enable, NO
= disable. Default = YES.
2. 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 oustanding "TransmitChain"
commands. On a server, this number should equal the product of the
following two numbers: [value of NetBEUI DLC.MAXOUT parameter]*[maximum
number of sessions]
For DOS: Can be any number from 2 to 6.
For OS/2: Can be any number from 2 to 100 (Default = 6).
RecBufSize sets the size (in bytes) of the buffers in the Receive Buffer
pool. Can be any number from 256 to 5000 (Default = 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 = 10).
RecBufHigh determines where to load the Receive Buffer Pool. It can be
either 0 or 1. 0 = loads the recieve buffer into high memory; if that
fails it loads into low memory. 1 = loads the receive buffer into low
memory; if that fails it loads into high memory. Default= 0
EarlyRelease sets board to use early token release on 16 Mbps LANs. YES
= enable ETR, NO = disable ETR (Default = YES). 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. Use this only in a PROTOCOL.INI file if you've prepared the
server for RPL.
Trademark information