Support Bulletin 2020: DOS ODI With Windows for Workgroups 3.11

DOS ODI WITH WINDOWS FOR WORKGROUPS V3.11 INSTALLATION

Token Ring and 100VG Adapters

Support Bulletin: 2020 Rev: C

ABSTRACT: This document contains the instructions on installing and configuring Windows for Workgroups to provide both Windows network connectivity (NDIS 3) and NetWare network connectivity (ODI). It uses the Microsoft ODIHLP shim instead of NetWare's ODINSUP; this provides you with "enhanced mode" (protected) operation instead of just "real mode".

IMPORTANT NOTE: It is strongly recommended that this procedure NOT be performed on an existing WFW install. Instead, it should be performed immediately following a new installation of WFW where NO network configurations have been selected.

Although it is possible to perform this procedure on an existing WFW install, great care must be taken to examine each new generation of the PROTOCOL.INI, WIN.INI, SYSTEM.INI,CONFIG.SYS, AUTOEXEC.BAT and NET.CFG files. Where previous configurations exist, these files frequently get built incorrectly following a change in the WFW Network Setup utility.

ADDITIONAL MATERIALS NEEDED:

1. NetWare support files for Windows (use same or newer than dates shown) These can beobtained from either NetWire or from the NetWare 4.x installation CD.

NETWARE.DRV (3-30-93)
NETWARE.HLP (2-9-93)
NWPOPUP.EXE (1-14-93)
VIPX.386 (5-12-93)
VNETWARE.386 (5-14-93)

2. NetWare workstation files: LSL.COM, IPXODI.COM, VLM.EXE and related *.VLM files

3. Racore distribution diskette: (DOS ODI driver and related INS file).

STARTING POINT:

OPTION 1: WFW is to have just been installed, preferably via Custom Setup; no network options should have been chosen during installation. The AUTOEXEC.BAT and CONFIG.SYS files should be exactly as WFW built them. No additional changes should be made at this time. There should NOT be any NetWare device statements.

NOTE: Be sure to exclude the network adapter's ROM/RAM space on the EMM386 command line: X=??00 - ?FFF, where ? is the beginning character of the memory space that the adapter is actually set to. Example: CC00 - CFFF

OPTION 2: WFW is already installed with network options. The following files will need to be re-

set to a non-network configuration: PROTOCOL.INI, SYSTEM.INI, WIN.INI. This can sometimes be accomplished from inside WFW as follows:

1. Open the Networks window
2. Select "Network Setup"
3. Select "No Windows Support for Networks"
4. Exit Windows.
5. Using an ASCII editor, examine the PROTOCOL.INI file. There should be no protocol sections or bindings statements, otherwise you'll have to delete the PROTOCOL.INI file before beginning this procedure. Sometimes, selecting "No Windows Support for Networks" fails to clear out all of the network lines from the PROTOCOL.INI file.

EXAMPLE of what NOT to see in PROTOCOL.INI: [NETBEUI] (protocol section)
BINDINGS=RTR16ODI (bindings statement)

If you see lines resembling these, delete the PROTOCOL.INI file, then continue with this procedure.

INSTALLATION PROCEDURE:

1. Exit WFW.
2. Retrieve the NetWare support files for Windows. This may be done one of three ways:
a. From the NetWare installation CD (workstation install utility)
b. From diskette: copy the following files to the C:\WINDOWS\SYSTEM directory:

NETWARE.DRV
NETWARE.HLP
NWPOPUP.EXE
VIPX.386
VNETWARE.386.

c. From diskette: as prompted in step 6 below

3. From a DOS prompt, edit the AUTOEXEC.BAT file to install the NetWare workstation files and correct Racore DOS ODI driver for the adapter being used. Place these command lines

following the NET START command:

LSL
RTR16ODI (example for 16/4 Token Ring ISA adapter)
IPXODI
VLM

NOTE: The above example assumes that the necessary files have been copied to the root directory.

Instead, you may copy them to the C:\WINDOWS directory and make the appropriate path statements on these lines.

ALTERNATE: You may use the Novell Install utility; however, this will create a STARTNET.BAT file which WINDOWS may not properly modify when network choices are made from within WINDOWS Network Setup.

4. Reboot the computer. Verify that the NetWare workstation drivers have loaded. If there is a NetWare server attached to the network, you should get the message "Attached to Server

XXX", but DO NOT LOGIN TO THE NETWARE SERVER AT THIS TIME.

5. Run Windows: WIN [enter]

6. Select the NETWORK window.

- select NETWORK SETUP
- select NETWORKS

- select "Install Microsoft Windows Network"

- at bottom of window, select "OTHER"

- select "Novell NetWare (workstation shell 4.0 and Above)"

push [OK]

- select SHARING (optional)

- select "I want to be able to give others access to my files"

push [OK]

- select DRIVERS

- select ADD ADAPTE

- scroll down listings and select:

for Token Ring adapters: IPXODI SUPPORT DRIVER (Token Ring)

for 100VG adapters: IPXODI SUPPORT DRIVER (Ethernet)

push [OK]

push [CLOSE]

push [OK]

You may then be taken to a Network Names window. Enter your name choices and select [OK]

At this point, you will come to a WINDOWS SETUP window which will ask you if you want to

replace files with versions now being installed. Select [NO]. You may be prompted for this up to

eight times; in all cases, select [NO].

NOTE: If you did not retrieve or copy the NetWare support files for Windows in step 2 above, you will now be prompted to provide each of these files. Insert a diskette which contains these files; type the path in the window and select [OK]. You will be prompted for each file.

After Windows copies all of the necessary files, you should see a window that advises you that the PROTOCOL.INI, SYSTEM.INI, etc. have been modified. Select [CONTINUE], then exit Windows.

7. From a DOS prompt, examine the PROTOCOL.INI file in the C:\WINDOWS directory and the NET.CFG in the directory you chose to contain the NetWare workstation files. They should resemble the sample PROTOCOL.INI and NET.CFG files at the end of this document. If the files matched, proceed to step 8.

For 100VG ADPTERS: Windows will create a NET.CFG file with several frame type command lines.

You must modify the NET.CFG file by removing all frame-type command lines other than Ethernet 802.2, otherwise you'll be unable to connect to the NetWare server. Windows will alsoinsert these same frame type lines in the PROTOCOL.INI file; however, they will not interfere and removal is optional.

NOTE: The order in which the sections of the PROTOCOL.INI file appear is not important.

If the files don't match:

a. If you see XXXXX in protocol, binding, or link driver statements, change the XXXXX to the Racore DOS ODI driver name for the adapter being used. Example:

"BINDINGS = XXXXX" should be changed to "BINDINGS=RTR16ODI" (for M8119)

b. If they significantly differ from the sample files, manually edit them so they match.

8. Reboot the computer.

9. Start Windows. From here, you should be able to bring up the File Manager window and connect to your NetWare and WFW networks.

SAMPLE FILES (Token Ring):

NET.CFG (sample)

Link Driver RTR16ODI

Frame Token-Ring

CONFIG.SYS (sample)
DEVICE=C:\WINDOWS\HIMEM.SYS
FILES=40
BUFFERS=40
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p
DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
DEVICE=C:\WINDOWS\IFSHLP.SYS
STACKS=9,256
LASTDRIVE=Z
AUTOEXEC.BAT (sample)
C:\WINDOWS\net start
C:\WINDOWS\SMARTDRV.EXE
@ECHO OFF
PROMPT $p$g
path=C:\WINDOWS;c:\;c:\dos;c:\qdos;
SET TEMP=C:\WINDOWS\TEMP
c:\nwclient\lsl
c:\nwclient\rtr16odi
c:\nwclient\ipxodi
C:\WINDOWS\odihlp.exe
c:\nwclient\vlm
PROTOCOL.INI (sample)
[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
[net.cfg]

PATH=C:\WINDOWS\net.cfg
[NETBEUI]
BINDINGS=RTR16ODI
LANABASE=0
SESSIONS=10
NCBS=12
[MS$ODIMACTR]
[Link Driver RTR16ODI]

[NWLINK]

BINDINGS=RTR16OD
SAMPLE FILES (100VG):
NET.CFG (sample)
Link Driver RVGODI
Frame Ethernet 802.2
CONFIG.SYS (sample)

device=C:\WINDOWS\HIMEM.SYS /testmem:off
device=C:\WINDOWS\EMM386.EXE noems x=d000-dfff
files=30
buffers=40
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p
DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFERDEVICE=C:\WINDOWS\IFSHLP.SYS
STACKS=9,256

AUTOEXEC.BAT (sample)
C:\WINDOWS\net start
@ECHO OFF
C:\WINDOWS\SMARTDRV.EXE /L /X
PROMPT $p$g
PATH=C:\WINDOWS;c:\dos;c:\nwclient;
SET TEMP=C:\WINDOWS\TEMP

doskey
c:\nwclient\lsl
c:\nwclient\rvgodi
c:\nwclient\ipxodi
C:\WINDOWS\odihlp.exe

c:\nwclient\netx

PROTOCOL.INI (sample)

network.setup]

version=0x3110

netcard=ms$odimac,1,MS$ODIMAC,4

transport=ms$nwlinknb,NWLINK

transport=ms$netbeui,NETBEUI

lana0=ms$odimac,1,ms$netbeui

lana1=ms$odimac,1,ms$nwlinknb

[net.cfg]

PATH=C:\NWCLIENT\NET.CFG

[NETBEUI]

BINDINGS=RVGODI

LANABASE=0

SESSIONS=10

NCBS=12

[NWLINK]

BINDINGS=RVGODI

Token Ring and 100VG Adapters

Support Bulletin: 2020 Rev: C

IMPORTANT NOTE: It is strongly recommended that this procedure NOT be performed on an existing WFW install. Instead, it should be performed immediately following a new installation of WFW where NO network configurations have been selected.

ADDITIONAL MATERIALS NEEDED:

1. NetWare support files for Windows (use same or newer than dates shown) These can beobtained from either NetWire or from the NetWare 4.x installation CD.

NETWARE.DRV (3-30-93) NETWARE.HLP (2-9-93) NWPOPUP.EXE (1-14-93) VIPX.386 (5-12-93) VNETWARE.386 (5-14-93)

2. NetWare workstation files: LSL.COM, IPXODI.COM, VLM.EXE and related *.VLM files

3. Racore distribution diskette: (DOS ODI driver and related INS file).

STARTING POINT:

NOTE: Be sure to exclude the network adapter's ROM/RAM space on the EMM386 command line: X=??00 - ?FFF, where ? is the beginning character of the memory space that the adapter is actually set to. Example: CC00 - CFFF

OPTION 2: WFW is already installed with network options. The following files will need to be re-

set to a non-network configuration: PROTOCOL.INI, SYSTEM.INI, WIN.INI. This can sometimes be accomplished from inside WFW as follows:

EXAMPLE of what NOT to see in PROTOCOL.INI: [NETBEUI] (protocol section) BINDINGS=RTR16ODI (bindings statement)

If you see lines resembling these, delete the PROTOCOL.INI file, then continue with this procedure.

INSTALLATION PROCEDURE:

1. Exit WFW. 2. Retrieve the NetWare support files for Windows. This may be done one of three ways: a. From the NetWare installation CD (workstation install utility) b. From diskette: copy the following files to the C:\WINDOWS\SYSTEM directory:

NETWARE.DRV NETWARE.HLP NWPOPUP.EXE VIPX.386 VNETWARE.386.

c. From diskette: as prompted in step 6 below

3. From a DOS prompt, edit the AUTOEXEC.BAT file to install the NetWare workstation files and correct Racore DOS ODI driver for the adapter being used. Place these command lines

following the NET START command:

LSL RTR16ODI (example for 16/4 Token Ring ISA adapter) IPXODI VLM

NOTE: The above example assumes that the necessary files have been copied to the root directory.

Instead, you may copy them to the C:\WINDOWS directory and make the appropriate path statements on these lines.

ALTERNATE: You may use the Novell Install utility; however, this will create a STARTNET.BAT file which WINDOWS may not properly modify when network choices are made from within WINDOWS Network Setup.

4. Reboot the computer. Verify that the NetWare workstation drivers have loaded. If there is a NetWare server attached to the network, you should get the message "Attached to Server

XXX", but DO NOT LOGIN TO THE NETWARE SERVER AT THIS TIME.

5. Run Windows: WIN [enter]

6. Select the NETWORK window.

- select NETWORK SETUP - select NETWORKS

- select "Install Microsoft Windows Network"

- at bottom of window, select "OTHER"

- select "Novell NetWare (workstation shell 4.0 and Above)"

push [OK]

- select SHARING (optional)

- select "I want to be able to give others access to my files"

push [OK]

- select DRIVERS

- select ADD ADAPTE

- scroll down listings and select:

for Token Ring adapters: IPXODI SUPPORT DRIVER (Token Ring)

for 100VG adapters: IPXODI SUPPORT DRIVER (Ethernet)

push [OK]

push [CLOSE]

push [OK]

You may then be taken to a Network Names window. Enter your name choices and select [OK]

At this point, you will come to a WINDOWS SETUP window which will ask you if you want to

replace files with versions now being installed. Select [NO]. You may be prompted for this up to

eight times; in all cases, select [NO].

NOTE: If you did not retrieve or copy the NetWare support files for Windows in step 2 above, you will now be prompted to provide each of these files. Insert a diskette which contains these files; type the path in the window and select [OK]. You will be prompted for each file.

After Windows copies all of the necessary files, you should see a window that advises you that the PROTOCOL.INI, SYSTEM.INI, etc. have been modified. Select [CONTINUE], then exit Windows.

7. From a DOS prompt, examine the PROTOCOL.INI file in the C:\WINDOWS directory and the NET.CFG in the directory you chose to contain the NetWare workstation files. They should resemble the sample PROTOCOL.INI and NET.CFG files at the end of this document. If the files matched, proceed to step 8.

For 100VG ADPTERS: Windows will create a NET.CFG file with several frame type command lines.

You must modify the NET.CFG file by removing all frame-type command lines other than Ethernet 802.2, otherwise you'll be unable to connect to the NetWare server. Windows will alsoinsert these same frame type lines in the PROTOCOL.INI file; however, they will not interfere and removal is optional.

NOTE: The order in which the sections of the PROTOCOL.INI file appear is not important.

If the files don't match:

a. If you see XXXXX in protocol, binding, or link driver statements, change the XXXXX to the Racore DOS ODI driver name for the adapter being used. Example:

"BINDINGS = XXXXX" should be changed to "BINDINGS=RTR16ODI" (for M8119)

b. If they significantly differ from the sample files, manually edit them so they match.

8. Reboot the computer.

9. Start Windows. From here, you should be able to bring up the File Manager window and connect to your NetWare and WFW networks.

SAMPLE FILES (Token Ring):

NETWARE.DRV (3-30-93)
NETWARE.HLP (2-9-93)
NWPOPUP.EXE (1-14-93)
VIPX.386 (5-12-93)
VNETWARE.386 (5-14-93)

EXAMPLE of what NOT to see in PROTOCOL.INI: [NETBEUI] (protocol section)
BINDINGS=RTR16ODI (bindings statement)

1. Exit WFW.
2. Retrieve the NetWare support files for Windows. This may be done one of three ways:
a. From the NetWare installation CD (workstation install utility)
b. From diskette: copy the following files to the C:\WINDOWS\SYSTEM directory:

NETWARE.DRV
NETWARE.HLP
NWPOPUP.EXE
VIPX.386
VNETWARE.386.

LSL
RTR16ODI (example for 16/4 Token Ring ISA adapter)
IPXODI
VLM

- select NETWORK SETUP
- select NETWORKS