3Com (R) Corporation
TokenDisk (R) Diskette for
The 3C319 TokenLink Velocity ISA Token Ring Network Interface Card
IBM LAN Server Installation Notes
IBM LAN Server
--------------
This TokenDisk diskette contains Token Ring driver import files for
IBM LAN Server.
IBM LAN Server 4.0
------------------
OS/2 LAN Server 4.0 and MPTS (LAPS) Installation
1. Insert the IBM MPTS diskette 1 in the floppy drive. Type :
INSTALL
2. Click OK at the first screen.
3. Click the INSTALL button.
4. Enter the target drive, e.g. C.
5. When prompted, insert the MPTS diskette 2 in the floppy drive.
Click OK.
6. Click OK when the copy is done.
7. Click CONFIGURE to configure and install network adapter.
8. Select LAN ADAPTERS AND PROTOCOLS. Click CONFIGURE.
9. At the LAPS Configuration dialog box, click OTHER ADAPTER.
10. Insert the TokenDisk diskette in the floppy drive.
11. Enter the path name for the TokenLink OS/2 NDIS driver :
A:\NDIS2\OS2
Click OK.
12. Scroll down the NETWORK ADAPTERS list, select the 3COM TOKENLINK
FAMILY OS/2 adapter. Click ADD.
13. Scroll down the PROTOCOLS list, select the protocol to use.
Click ADD. Repeat for more protocols.
14. Click OK when complete.
15. Continue with installation and configuration as prompted or
click CLOSE to exit and follow the prompts.
DOS LAN Support (DXMAID) Installation
1. At the DOS prompt on a DOS machine, run the DXMAID installer from
the IBM LAN Support Program diskette.
2. Press ENTER at the first three Information screens.
3. From the Setup screen, press ENTER to accept all the default values.
4. Insert the TokenDisk diskette in the floppy drive.
5. From the Process Driver Diskette screen, enter the path name of the
NDIS driver on the TokenDisk :
A:\NDIS2\DOS
6. Insert the LAN Support Program diskette into the floppy drive when
prompted.
7. The Primary Adapter Driver shown is 3COM TOKENLINK FAMILY DOS.
Press F4 to install the driver.
This completes the installation of DXMAID. Reboot and install IBM LAN
Server 4.0 if not installed yet.
DOS LAN Services Installation
1. On a DOS machine, create a temporary directory, for example :
MKDIR C:\TEMP
2. Insert the TokenDisk diskette in the floppy drive.
3. Copy the following files from the TokenDisk to the temporary directory.
COPY A:\NDIS2\DOS\OEMSETUP.INF C:\TEMP
COPY A:\NDIS2\DOS\TLNK3.DOS C:\TEMP
4. Insert the IBM DOS LAN Services disk 1 in the floppy drive.
5. From the DOS prompt, enter
A:\INSTALL
6. Press ENTER at the welcome screen.
7. Press ENTER to accept default directory C:\NET as the location to
install DOS LAN Services.
8. From the list of network cards presented, select NETWORK CARD NOT
SHOWN IN LIST BELOW.
9. Enter the path of the temporary directory where the oemsetup.inf file
is:
C:\TEMP
10. The 3COM TOKENLINK FAMILY network card is highlighted. Press
ENTER to select the network card.
11. Enter the machine ID, user name and domain name.
12. Press Enter to accept the list of options chosen.
13. Finish installing files from the DOS LAN Services diskettes.
This completes the installation of DOS LAN Services.
IBM LAN Server 3.0
------------------
IBM LAN Server 3.0 contains an installer for both OS/2 (LAPS) and DOS
(DXMAID). Both of these installation utilities fully support OEM network
adapter driver import capability.
DOS Installation
1. Run the DXMAID installer from the IBM LAN Support diskette.
2. From the first menu, select YES - HAVE ADAPTER OPTION DISK.
3. Remove the LAN Support diskette, put the 3Com TokenDisk diskette in
the floppy drive, and type
A:\NDIS2\DOS
for the drive and path.
4. Select F4 to install 3COM TokenLink Family DOS. The installer
will pause after it copies the files needed from the TokenDisk
diskette.
6. Place the LAN Support diskette back in the drive, and continue with
the installation.
OS/2 Installation
1. Run the LAPS installer from the LAN Adapter and Protocol diskette.
2. From the first menu, select the INSTALL option.
3. Enter target drive e.g. C.
4. LAPS then installs itself and other files. Click OK when done to
return to the first menu.
5. Select INSTALL again.
6. Remove the LAPS diskette and insert the TokenDisk diskette in the
floppy drive. Type
A:\NDIS2\OS2
for the drive and path. Click OK.
7. LAPS will copy the needed files from the TokenDisk diskette. When
the acknowledge message appears at the end of the copy, click OK.
8. Reinsert the LAPS diskette. Click OK. Continue with the installation
by configuring the driver as prompted.
9. Click CONFIGURE.
10. Select CONFIGURE LAN TRANSPORTS. Click CONTINUE.
11. Select 3COM TOKENLINK FAMILY OS/2 from the NETWORK ADAPTERS
box. Click ADD.
12. Select protocols required. Click ADD for each protocol to add.
13. Select OK when complete.
14. Continue with installation or exit as prompted.
IBM LAN Server 2.0
LAN Server 2.0 is not as sophisticated as LAN Server 3.0. Installation can
be done successfully, but manual intervention is required. In all cases,
the user is required to edit files. For OS/2, the E editor is fine. For
DOS, use either EDLIN or EDIT.
DOS Installation
Run the DXMAID installer from the LAN Support diskette. Specify the
Token Ring adapter installation from the menu. When DXMAID is
completed, do the following to complete the installation.
1. Copy the TokenLink NDIS driver to the hard disk. Type:
COPY A:\NDIS2\DOS\TLNK3.DOS C:\LANMAN
2. Edit the CONFIG.SYS file.
a. Change the line:
device = \LANMAN\PROTMAN.DOS
to
device = \LANMAN\PROTMAN.DOS /I:\LANMAN
b. Change the line:
device = XX.DOS
to
device = \LANMAN\TLNK3.DOS
c. Save the file and exit the editor.
3. Enter the LANMAN subdirectory. Type:
CD LANMAN
4. Rename the PROTOCOL.INI file to save it. Type:
REN PROTOCOL.INI PROTOCOL.OLD
5. Append the PROTOCOL.INI fragment from the 3Com TokenDisk diskette.
Type:
COPY PROTOCOL.OLD + A:\NDIS\DOS\PROTOCOL.INI PROTOCOL.INI
6. Edit the new PROTOCOL.INI file.
a. Four lines after the line [TOKEN RING], change the line:
Bindings = IBMAC
to
Bindings = TLNK3
b. Two lines before the line:
;3Com TokenLink adapter
change the blank line to
[TLNK3]
c. Save the file and exit the editor.
The installation is complete. The LAN Support program activates the next
time the machine boots.
OS/2 Installation
1. Insert the IBM OS/2 Requester Diskette #1 and run the LAPS installation
program. Select Advanced Installation on the second menu.
2. Insert the OS/2 Protocol and Drivers diskette when the prompt appears.
After LAPS has completed copying the files from the Protocol and Drivers
diskette, select the Copy Additional Drivers option from the next menu.
The next menu prompts for the drive and path for the additional
drivers.
3. Insert the TokenDisk diskette and type A:\NDIS2\OS2. LAPS copies the
appropriate 3Com adapter files to the hard disk and returns to the
options menu.
4. Select the Configure Workstation option. The next menu prompts for
adapter and protocol options. In the adapters window, page down until
the 3Com TokenLink Family OS/2 menu item appears. Select this item and
continue the installation. When the installation is complete, exit the
installer.
The installer presents a message that the system needs to be rebooted for
the changes to take effect. However, you must complete the following
steps before you reboot the computer.
1. Edit the CONFIG.SYS file. After the line:
device=C:\IBMCOM\PROTMAN.OS2
insert the line:
device=C:\IBMCOM\MACS\TLNK3.OS2
2. Save the file and exit the editor.
3. Reboot the computer, and the OS/2 requester will activate.
(%VER LANSRV.TXT - IBM LAN Server Installation Notes V1.0a)
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.