![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress: Windows for Workgroups LANSUP Installation
WINDOWS FOR WORKGROUPS 3.11 INSTALLATION NOTES USING LANSUP AND DLC DRIVERS
Microsoft Windows for WorkGroups 3.11 Installation Notes For Intel's
TokenExpress LAN Adapter using LANSUP for NetWare connection and DLC
drivers for host connection.
General instructions:
1. Create the directory C:\NWCLIENT and copy the following files into
it:
LSL.COM v2.05 or later
v1.27 or later
v2.12 or later
v3.26 or later
OC01IA.SYS 11/19/93 or later
11/19/93 or later
Note: LANSUP.COM v1.27 will work in this configuration.
LANSUP.COM v2.07 will cause Windows for Workgroups to hang or drop
back to the c: prompt after starting Windows for Workgroups.
2. Create a NET.CFG in C:\NWCLIENT.
C:\NWCLIENT\NET.CFG:
LINK DRIVER LANSUP
FRAME TOKEN-RING
FRAME TOKEN-RING_SNAP
3. Create or edit your CONFIG.SYS and AUTOEXEC.BAT files to load the
DLC and ODI drivers before you start Windows for WorkGroups. Here
are samples:
CONFIG.SYS:
DEVICE=C:\WINDOWS\HIMEM.SYS
FILES=50
BUFFERS=25
DEVICE=C:\NWCLIENT\OC01IA.SYS
DEVICE=C:\NWCLIENT\OC02DLC.SYS
LASTDRIVE=E
DEVICE=C:\WINDOWS\IFSHLP.SYS
STACKS=9,256
AUTOEXEC.BAT:
C:\WINDOWS\NET START
PROMPT $P$G
PATH=C:\WINDOWS
SET TEMP=C:\WINDOWS\TEMP
CD\NWCLIENT
LSL
LANSUP
IPXODI
NETX
CD\
C:\WINDOWS\ODIHLP.EXE
4. Start up Windows for WorkGroups using the /N parameter. Example :
C:\WINDOWS WIN /N
5. After Windows for WorkGroups comes up, select the "NETWORK SETUP"
icon in the Network Group.
6. Click on *NETWORKS*.
7. Select *INSTALL MICROSOFT WINDOWS NETWORK* and click on *OK*.
8. <Optional> Click on *SHARING* and configure for printer and file
sharing and click on *OK*.
9. Click on *DRIVERS*.
10.If you are replacing a previous installed LAN adapter, click on
*Remove* to delete that adapter.
11.Click on *Add Adapter*.
12.Select *IPXODI SUPPORT DRIVER [TOKEN RING]" from the Add Network
Adapter list and click *OK*.
13.From the NetWork Drivers menu, click on *CLOSE*
14.From the NetWork Setup menu, click on *OK*
15.Windows for WorkGroups will ask if you want to replace the files
currently installed with the version you are installing now, click
on *YES TO ALL*.
16.Windows for WorkGroups will prompt you for Windows for WorkGroups
Disk 7 & Disk 8 as it updates the files.
17.After the files have been updated, Windows for WorkGroups will
notify that it has modified NET.CFG, CONFIG.SYS, SYSTEM.INI,
WIN.INI, and PROTOCL.INI. Click on *OK*
18.Windows for WorkGroups will prompt you to reset your computer for
the changes to take effect, click on *RESTART COMPUTER*.
Hints and tips:
Windows for WorkGroups creates the PROTOCOL.INI for you. This sample is
setup for Windows for Workgroups network with NetWare support and is
provided for reference:
C:\WINDOWS\PROTOCOL.INI:
[network.setup]
version=0x3110
netcard=ms$odimactr,1,MS$ODIMACTR,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$odimactr,1,ms$netbeui
lana1=ms$odimactr,1,ms$nwlinknb
[Link Driver ]
data=Frame Token-Ring
data=Link Driver
[NET.CFG]
PATH=C:\NWCLIENT\NET.CFG
[MS$ODIMACTR]
[Link Driver LANSUP]
data=Frame Token-Ring
data=Link Driver LANSUP
[Link Support]
NewMaxBoards=Max Boards 2
[NWLINK]
BINDINGS=LANSUP
[NETBEUI]
BINDINGS=LANSUP
LANABASE=0
SESSIONS=10
NCBS=12
Troubleshooting tips:
A. If the adapters passes diagnostics but still do not work in Windows
for WorkGroups, there could be a problem with the file
C:\WINDOWS\PROTOCOL.INI. If you have made several attempts to setup
networking in Windows for WorkGroups or had another adapter
installed before the TokenExpress, it may be necessary to restore
the PROTOCOL.INI to the default and then install the driver for
TokenExpress adapter. You can set this file back to default by
following these steps:
1. Start up Windows for WorkGroups using the /N parameter. Example
: C:\WINDOWS WIN /N
2. After Windows for WorkGroups comes up, select the "NetWork
SETUP" icon in the NetWork Group.
3. Click on *NETWORKS*.
4. Select *NO WINDOWS SUPPORT FOR NETWORKS* and click on *OK*.
5. From the NetWork Setup menu, click on *OK*
6. Windows for WorkGroups will notify that it has modified NET.CFG,
CONFIG.SYS, SYSTEM.INI, WIN.INI, and PROTOCL.INI. Click on *OK*
7. Windows for WorkGroups will prompt you to reset your computer
for the changes to take effect, click on *RESTART COMPUTER*.
This process will set the file C:\WINDOWS\PROTOCOL.INI back to
default and disable the Windows for WorkGroups network. After
the workstation reboots, start Windows for WorkGroups and
reconfigure the NetWork Setup as described above under General
Instructions.
B. If Windows for WorkGroups fails to detect that the ODI drivers are
loaded while running NetWork Setup, you will get this error
message when starting Windows for WorkGroups:
*THE FOLLOWING ERRORS OCCURRED WHILE LOADING PROTOCOL NUMBER 0:
ERROR 58: THE NETWORK HAS RESPONDED INCORRECTLY. YOU MAY NEED TO
RECONFIGURE THE PROTOCOL USING NETWORK SETUP*.
Because Windows for WorkGroups was not able to detect which ODI
driver was loaded, it will add the variable *XXXX* to the NET.CFG
and PROTOCOL.INI files where it should have specified *LANSUP*.
When this error occurs you will need to manually edit the NET.CFG
and PROTOCOL.INI that Windows for WorkGroups created to match the
sample NET.CFG and PROTOCOL.INI shown above.
Here are the entries that need to be changed:
1. In the PROTOCOL.INI, under the section heading [NET.CFG] change
*PATH=C:\Windows\NET.CFG* to *PATH=C:\nwclient\NET.CFG*
2. In the PROTOCOL.INI, change the section heading [Link Driver
XXXX] to [Link Driver LANSUP].
3. In the PROTOCOL.INI, under the section heading [NWLINK] change
both occurrences of *BINDINGS=XXXX* to *BINDINGS=LANSUP*
4. In the NET.CFG, change *Link Driver XXXX* to *Link Driver
LANSUP*
Compare your changes to PROTOCOL.INI and NET.CFG to the sample
files provided previously in this document for examples of the
correct format and syntax.
C. If you choose to add Novell NetWare support to Windows for
WorkGroups when selecting Networks, you will be prompted for the
following Novell NetWare files:
NETWARE.DRV, NETWARE.HLP, NWPOPUP.EXE, VIPX.386, VNETWARE.386
These files are Novell NetWare files and are not on the
TokenExpress driver diskette. You can get these files from
CompuServe in Novells forum called Novell NetWire by downloading a
self-extracting file called WINDR2.EXE. If you are not a member of
CompuServe, you can call Novell to have them mailed to you or
contact a Novell NetWare dealer in your area.
Trademark information