Many problems can occur if Pathway is not properly configured. Here are some things to check in case of errors, slowness and lockups. Please be aware that some specific files may not be used; i.e., ODI installation does not use protocol.ini.

Installing

• ODI: lsl.com and a *.com network card driver must be loaded.
• NDIS: Use either the *.mac or *.dos driver and the protocol.ini supplied by the network card manufacturer.
• PDS: This is a packet driver. It’s often unstable in Windows, so not recommended.
• Dedicated: Only use a dedicated driver for one of the listed network cards. Even so, we recommend ODI or NDIS instead.
• ASI: This is used by token ring networks. It is similar to a normal NDIS installation and just as easy to troubleshoot.

Winsock.dll
There should be only one. Any others will need to be renamed. Make sure the winsock.dll you use belongs to the TCP/IP or transport layer in use.

The -I: option is the interrupt of the network card or COM port
Run the network card setup utility to verify the interrupt of the card. Also, verify that there are no conflicts with this IRQ and other hardware.

pwconfig.exe -N: should be different than the network card
This is an interrupt vector or software interrupt. The default for Wollongong is 65. Valid numbers are 60-66. Most network cards are on 60 or 61. Recommended numbers are 63, 65 and 66.

Check for errors on boot. Concentrate on the error description, not the number. The brief description tells more than the number. If a technician can find the error number, chances are it will be the same description. Do not worry if there are two error numbers and one description. They will be related.

NET.CFG syntax
Order and spacing are critical. In general, the order should be: “Wollongong” group, “Link driver” section, “Wollongong” group, and then extra additions such as buffers, Novell DOS requesters, etc. Make sure the frames are correct.

PROTOCOL.INI
Verify the ndis.exe -d: argument is pointing to the right [driver] section. You may also need to verify the protocol.ini file being used. You may find copies in multiple places: C:\Windows, C:\Pathway\Lanman, etc.

In Windows for Workgroups, make sure Windows has loaded the right network driver and that NetBEUI is running correctly.

IP addresses
Check to see if it is a duplicate or otherwise incorrect. Errors that occur from this are PC lockups, lost connection, and read/write errors.

A simple way to check for duplicate IP addresses is to change the PC’s address, then ping the old address.

Subnet mask bits
Make sure they are the same as other computers on the subnet. This will also cause PC lockups, lost connections and read/write errors.

STAT.EXE
Run this at a DOS prompt. Three parameters need to be checked:

• stat 2: Physical address of the network card. If it’s all zeroes, Pathway is not loaded or not loaded properly. Pathway needs to see the card, unless you are using PPP or SLIP.
• stat 3: Resolved IP addresses. If this reports no resolved addresses, the TCP stack could still be the problem. If there is a resolved address and there is still no reply from the ping, the problem is on the other end of the connection, not the PC.
• stat 4: This gives the local IP address and subnet mask bits.

Patch
Download the updated PCHRUN.EXE. Replace the existing copy on the PC with the new file.

Update the network card driver
Get latest drivers for network card from the manufacturer. Generally, the manufacturer’s website will have the files to download.

Watch for cards that do not support multiple protocols
Some older network cards only support one protocol at a time; e.g., IPX or NDIS. This is not common. If either protocol loads and connects properly when run alone, but combined one or the other fails, then it does not support multiple protocols.

Adjust Windows
See our other documents on NDIS, ODI and Windows 95 configuration.

With TinyTERM for DOS set for SCOANSI emulation, the UNIX TERM environment variable set to ansi or ansic, and the WPTERM environment variable set to either term or termcolor, the following lines can be added to the tt.rc file to allow TinyTERM to work with WordPerfect 5.0 for UNIX.

setkey sf10 reset
setkey f10 reset
setkey cf10 reset
setkey kp- "\E[-" !keypad -
setkey kp+ "\E[+" !keypad +
setkey c-home "\E[E" !Ctrl-Home
setkey c-pgup "\E[J" !Ctrl-PgUp
setkey c-pgdn "\E[K" !Ctrl-PgDn
setkey c-end "\E[0" !Ctrl-End
setkey c-left "\E[1" !Ctrl-LeftArrow
setkey c-right "\E[2" !Ctrl-RightArrow
setkey c-enter "\E[3" !Ctrl-Enter
setkey c-bs "\E[4" !Ctrl-BackSpace
setkey s-tab "\E[5" !Shift-Tab
setkey "^H" "\E{h" !Ctrl-H
setkey "^Q" "\E{q" !Ctrl-Q
setkey "^S" "\E{s" !Ctrl-S
setkey af1 "\E[w" !Map Ctrl-Shift-Fkeys to Alt-Fkeys
setkey af2 "\E[x"
setkey af3 "\E[y"
setkey af4 "\E[z"
setkey af5 "\E[@"
setkey af6 "\E[["
setkey af7 "\E["
setkey af8 "\E[]"
setkey af9 "\E[\^"
setkey af10 "\E[_"
setkey alta "\E|a" !Assign sequences to Alt-A through Alt-Z
!setkey altb "\E|b" ! Not mapped for default break key.
!setkey altc "\E|c" ! Not mapped for default compose key.
setkey altd "\E|d"
setkey alte "\E|e"
setkey altf "\E|f"
setkey altg "\E|g"
!setkey alth "\E|h" ! Not mapped for hot key.
setkey alti "\E|i"
setkey altj "\E|j"
setkey altk "\E|k"
setkey altl "\E|l"
setkey altm "\E|m"
setkey altn "\E|n"
setkey alto "\E|o"
!setkey altp "\E|p" ! Not mapped so we can print.
setkey altq "\E|q"
setkey altr "\E|r"
!setkey alts "\E|s" ! Not mapped so we can run setup.
setkey altt "\E|t"
setkey altu "\E|u"
setkey altv "\E|v"
setkey altw "\E|w"
!setkey altx "\E|x" ! Not mapped so we can exit.
setkey alty "\E|y"
setkey altz "\E|z"

You may want to comment out different lines than those selected above. The ones commented out are the default keys used by TinyTERM.

The Wollongong TCP/IP stack included with TinyTERM Plus NFS for DOS includes an NFS client that allows a DOS PC to use UNIX printers. To print using NFS, Wollongong TCP/IP must be running. It then requires the following steps:

1. At the DOS prompt type NFS, then press Enter. If NFS has been installed correctly, the following screen will be displayed:
   

   Century Client NFS for DOS (Version 2.0)
   Copyright (C) 1990,1993 The Wollongong Group.

   If the above lines are not displayed or an error message is received, check the NFS installation guide and try again.

2. The host system must be running version 2 of the pcnfsd daemon. To confirm this, log into the host and run the following command:
   

   rpcinfo -p

   This program can usually be found in the /usr/etc directory. If you can not run this program, you may not have permissions. Talk to your system administrator to use this program. Assuming you can run the above command, you will see a screen similar to the following:

   program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
150001 1 udp 1028 pcnfsd
150001 2 udp 1028 pcnfsd
150001 1 tcp 1024 pcnfsd
150001 2 tcp 1024 pcnfsd
100003 2 udp 2049 nfs
100005 1 udp 1027 mountd
100024 1 udp 1042 status
100024 1 tcp 1025 status
100020 1 udp 1050 llockmgr
100020 1 tcp 1026 llockmgr
100021 2 tcp 1028 nlockmgr
100017 1 tcp 1027 rexd
100021 1 tcp 1029 nlockmgr
100021 1 udp 1062 nlockmgr


   Under the program column you will be looking for the number 150001. Under the vers column you will need the number 2. You must have pcnfsd version 2 in order for the NFS services to work. Versions 1 and 2 can run in conjunction. If you only have version 1 running, you will have to upgrade to version 2 on your host.

3. Determine which hosts on your network are running NFS services. To do this, type the following:
   

   mount /n

   This command may take a few seconds to process, depending on the number of servers available and the current network traffic. It will return a screen similar to the following:

   NFS SERVERS
(192.168.0.25) century
(192.168.0.13) sconfs
(192.168.0.12) scoodt
(192.168.0.10) rs6000
4 servers available on your subnet.

   If no servers are available, talk with your network administrator.

4. Next you will need to see which servers, if any, have print services available. To do this, use the /l option along with the hostname in question. For example:
   

   mount /l century

   A screen similar to the following will be displayed:

   NAME DEVICE LOCATION
---------- ------------ ---------------
sunprint Local
epson1 /dev/lp0 Local

   Note that the sunprint line above doesn’t show a device. On some systems this is normal.

5. You are now ready to mount an NFS printer. In the example above, you might enter the following at the DOS prompt:
   

   mount lpt1 century:/sunprint user passwd

   In the above example the host is century, the printer is sunprint device, the username is user, and the password is passwd. If auth had been run, it would not be necessary to add the username or password, although doing so would not cause any problems.

   If all went well, you will see a line similar to the following:

   Device lpt1 redirected to \century\/sunprint successfully

Troubleshooting Tips
If you get “permission denied” or “invalid path” when mounting the printer:

1. Using the rpcinfo command outlined above, verify that pcnfsd version 2 is up and running on the NFS server.
2. Verify that the spool directory has been exported by looking for /usr/spool/pcnfs (or higher) in the /etc/exports file.
3. From the DOS prompt, type mount /e servername. You should see /usr/spool or higher directory exported.
4. Verify that you can mount /usr/spool and that you have permissions of 777 by copying a file to /usr/spool. On some systems the directory will be /var/spool instead.
5. From the DOS prompt execute PWSETUP and select View Current Settings. Make a note of the PC’s IP address, the user id and hostname of the PC. On the server, verify that the PC’s hostname is in the /etc/hosts file.
6. Finally, if you have any logical links to /usr/spool, verify that the linked file as well as /usr/spool is also exported.

Century Software, Inc., has had a report from a customer using TinyTERM Plus for DOS. The PC has an HP 1100 on LPT1: set up as an LPD printer. Printing from both SCO and Linux systems, each print job produces three copies. Printing from DOS applications does not do this, nor does printing to locally attached printers on the hosts.

The PC uses a 3C509 network card on IRQ 7 with a packet driver. Changing the network IRQ doesn’t affect the problem.

CR 612, not duplicated

Using Century Software’s DOS FTP client, connect to several FTP servers. Download a couple of files from each, then exit the FTP client after each connection and return to DOS. Around the 10th time you do this, the PC will hang. There is also an error on each quit or exit command:

run-time error R6001- null pointer assignment

CR 610

TinyTERM and TERM for DOS can both connect via IPX/SPX. They do not require TCP/IP as TinyTERM and TERM for Windows do.

This error comes up when using TinyTERM or TERM for DOS on a PC with no networking installed. You will need to configure the connection again, as it’s been changed to try to use a network.

On a PC with no hard drive, you can make a boot disk that also runs TinyTERM for DOS. To do that, insert a floppy into a system already running DOS, one that has TinyTERM installed as well. From the DOS prompt, execute this command:

format /s

This will make the diskette bootable. Next, copy the following files from the root of C: to the floppy:

COMMAND.COM (may already be in place)
AUTOEXEC.BAT
CONFIG.SYS

Edit the AUTOEXEC.BAT and CONFIG.SYS files on the floppy to remove all information relating to the C: drive. You want it stripped to the bare minimum required to use DOS.

Finally, copy the following files from the TinyTERM directory to the floppy:

default.con
tt.exe (the main executable, not the stub)
tt.ini
tt.sys
langus.str
ttsetup.exe
comnul.kdl
vidram.kdl
emansi.kdl
comasy.kdl

The files comnul.kdl and vidram.kdl are required .kdl files.

Next, copy the *.kdl file for the emulation you will be using. For example, if you are using ANSI or SCOANSI emulation, get the emansi.kdl file listed above. For WYSE60 emulation, get the emwy60.kdl file. Similar files exist for other emulations.

Finally, copy the *.kdl file for the kind of connection you will make. These files will begin with “COM.” For example, the comasy.kdl file listed above is for asynchronous connections, serial or RS232. For the Wollongong TCP/IP, get the comwol.kdl file.

Space permitting, copy over any other *.kdl files you may use in the future.

TERM and TinyTERM for DOS can both be loaded into high memory with the LOADHIGH or LH command.

To shell out to DOS in TERM, type Alt-F4. In TinyTERM, the hotkey is Alt-H. Either can be remapped through the included utilities.

Installing TinyTERM 3.3 on Windows 95 may produce an error message that the product is only for DOS. When this happens, copy the contents of the TinyTERM CD to a temporary directory on the hard drive. Reboot the PC in safe mode, then install TinyTERM from the hard drive copy.