- Make sure that Windows for Workgroups is installed correctly and that a connection can be made to other Windows for Workgroup machines using the NetBEUI protocol.
- Ensure that Windows for Workgroups is installed for Real and/or Enhanced mode NDIS.
- Check the CONFIG.SYS file. No Protocol Manager or MAC driver should be included.
- Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
- PWSETUP will prompt you for a modification of CONFIG.SYS. Respond with No. This will avoid having to modify it later. If this was missed for some reason, remark out or delete the Wollongong Group section of that file.
- In AUTOEXEC.BAT add the bolded lines to the Wollongong section as indicated:
SET PATH=C:\PATHWAY;%PATH%
PWCONFIG -N:65
C:\WFW3.11\NET INIT ;this loads the device driver
NDIS -I:X -D:Y ;this loads the NDIS driver interface
C:\WFW3.11\NET START NETBIND ;this completes the binding process
PWTCP
Make sure that the NET START command is not executed at the beginning of AUTOEXEC.BAT.
The -I: parameter on the NDIS line refers to the IRQ level of the 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.
The -D: parameter on the NDIS line refers to the bracketed section in your protocol.ini file which contains your card name and settings. For example, if the sixth section in your protocol.ini contains this information, the NDIS line should read -D:6. Errors which indicate “unable to bind” or “incomplete binding” can be resolved by double-checking this value and/or verifying that the protocol.ini contains the proper information for your network card.
Once you have installed Pathway, reboot the machine. Watch for any errors. If no errors occur, first try to ping at 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.
This entry was posted
on Tuesday, May 8th, 2007 at 7:59 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.