1. Make sure that Windows for Workgroups is installed correctly and can connect to other Windows for Workgroups PCs using the NetBEUI protocol.
2. Ensure that Windows for Workgroups is installed for ODI drivers.
3. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
4. PWSETUP will prompt you for a modification of net.cfg. Respond with Yes.

Sample Files for Windows for Workgroups 3.11 and Novell 3.11

*************************AUTOEXEC.BAT*********************************

@ECHO OFF
cd \novell
lsl
smcplus
ipxodi
netx ;(or VLM for 4.x)
E:\WINWORK\SMARTDRV.EXE
PROMPT $P$G
PATH E:\NFS20\PATHWAY;E:\UTILS\UNIX;e:\norton
SET TEMP=E:\WINWORK\TEMP
SET TMP=E:\TMP
LOADHIGH DOSKEY
COPY C:\DOS\COMMAND.COM C:\ > NUL
rem #—————– The Wollongong Group ——————–#
rem # The following lines are for PathWay Runtime setup. Please DO NOT #
rem # modify or remove any of them. If you DO want to, please run the #
rem # setup program to modify or deinstall PathWay for DOS. #
PATH E:\PATHWAY;%PATH%
PWCONFIG -N:65
ODI -i:5
PWTCP
rem #——————- The Wollongong Group ——————#
NFS
mount g: \phaedra\/home/sm sm
C:\DOS\SHARE.EXE /F:4096 /L:400

**********************END OF AUTOEXEC.BAT*****************************

The -I: parameter on the ODI line refers to the IRQ level of your network card. Please verify your card setting and make sure the Pathway setting matches. Remember to use the hex value for 10 and above. Symptoms of an IRQ mismatch include slow connection speed, intermittent hanging or loss of connection, and kernel initialization failure.

Once you have installed Pathway, reboot your PC. Watch for any errors. If no errors occur, first try to ping from a DOS prompt, then make sure Windows for Workgroups loads successfully. You should then be able to use FTP, telnet or NFS to connect to your host.

***********************CONFIG.SYS************************************

DEVICE=E:\WINWORK\HIMEM.SYS
DEVICE=E:\WINWORK\EMM386.EXE noems x=d000-d3ff
DOS=HIGH,umb
files = 70
stacks=9,256
buffers = 40
lastdrive=P
DEVICE=C:\DOS\SETVER.EXE
SHELL=c:\dos\command.com /p /e:600
DEVICE=E:\WINWORK\IFSHLP.SYS

*********************END OF CONFIG.SYS********************************

**************************NET.CFG*************************************

#—————- The Wollongong Group —————-#
# The following lines are inserted for PathWay driver #
# interface setup for ODI. Please DO NOT remove them. #
Protocol IP
Bind SMCPLUS

Protocol ARP
Bind SMCPLUS
#—————- The Wollongong Group —————-#

Link Driver SMCPLUS
Port #1 300
Mem #1 000d8000
Int #1 5
Frame Ethernet_802.3
Frame Ethernet_SNAP
Protocol IPX 0 Ethernet_802.3
#—————- The Wollongong Group —————-#
# The following lines are inserted for PathWay driver #
# interface setup for ODI. Please DO NOT remove them. #
frame ETHERNET_II
PROTOCOL IP 000000000800 ETHERNET_II
PROTOCOL ARP 000000000806 ETHERNET_II
#—————- The Wollongong Group —————-#

#For 4.x Novell the Novell DOS requestors will go here.

LINK SUPPORT
Max Boards 4
Buffers 8 1514

**************************END OF NET.CFG******************************

***************************PROTOCOL.INI*******************************

[network.setup]
version=0x3110
netcard=ms$w13ep,1,MS$W13EP,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$w13ep,1,ms$netbeui
lana1=ms$w13ep,1,ms$nwlinknb

[MS$W13EP]

[NWLINK]
BINDINGS=SMCPLUS

[NETBEUI]
BINDINGS=SMCPLUS
LANABASE=0

[net.cfg]
PATH=E:\NOVELL\NET.CFG

[Link Driver SMCPLUS]
data= Frame Ethernet_SNAP
data= Frame Ethernet_802.2
data= Frame Ethernet_II
data= Frame Ethernet_802.3
data=Link Driver SMCPLUS

**************************END OF PROTOCOL.INI*************************

This entry was posted on Tuesday, May 8th, 2007 at 8:06 am and is filed under Install, TCP/IP. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.