Century Software has had a report that TinyTERM for iPad hangs when attempting a connection via VPN. We have not been able to duplicate this in TinyTERM version 1.2. The original report is as follows:

“Enable and connect the iPad VPN. Then connect to a host system through TinyTERM. It will tend to lock up, no connection visible. Once in a while it will connect and work properly, but generally it will lock up at connection time and stay that way. Closing TinyTERM is the only option.”

CR 928

TinyTERM and TERM for UNIX/Linux all use IPv4, regardless of the platform. Century Software has had a request to add Internet Protocol version 6 (IPv6) support to our products.

CR 923

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.

To setup Pathway 2.0 on Windows 95, with or without Novell installed, do the following:

1. In the Windows 95 Control Panel, double-click Network.
2. Add your network card if it is not already in place. It does not matter if you select the real-mode NDIS driver or the enhanced mode 32-bit NDIS driver, unless you add Novell IPX/ODI support. Then you must use the 16-bit real mode driver.
3. Client for Microsoft Networks and NetBEUI will automatically be added. Click OK and reboot the PC when asked.
4. During reboot hit the F8 function key. Choose Command prompt from the boot menu.
5. Install Pathway from the diskettes. Choose Ethernet|NDIS as the install type.
6. The directory containing the protocol.ini file is C:\Windows.
7. Choose the section of the protocol.ini that references your card driver name; for example, ms2000$.
   (Note: In one case the protocol.ini called for an ms2000$, but the driver that Windows 95 installed was ne2000.dos. To solve this problem, copy the ne2000.dos file to ms2000.dos.)
8. Let Pathway alter the AUTOEXEC.BAT file, but not the CONFIG.SYS.
9. Make the following changes to AUTOEXEC.BAT:
   1. Windows 95 adds the line NET START to the beginning of the file. Type “REM ” before it to comment out this line.
   2. After the line pwconfig -n:x add C:\Windows\net init.
   3. The next line reads ndis -i:x -d:x. After this line add C:\Windows\net start netbind.
   4. The next line should read pwtcp.
10. Reboot the computer and hit the F8 function key during boot-up. Choose Line by line confirmation from the boot menu. Load each line and make sure there are no errors during the Pathway load sequence. If you get an error in C:\Windows\net start netbind, change it to C:\Pathway\netbind.
11. Answer No to the Load Windows? prompt.
12. Ping in DOS to verify the install. If this works, enter Windows and use the winping.exe utility in the Pathway directory to test the stack in Windows.

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*************************

1. 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.
2. Ensure that Windows for Workgroups is installed for Real and/or Enhanced mode NDIS.
3. Check the CONFIG.SYS file. No Protocol Manager or MAC driver should be included.
4. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
5. 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.
6. 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.

Century Software, Inc., has had a request to add an option to port forwarding that would allow the remote system to assign TCP ports dynamically. Currently port forwarding can only use assigned TCP ports.

CR 643

In TinyTERM versions prior to 4.21, if there is a Winsock problem, you have to wait for TinyTERM to time out before you can do anything. TinyTERM 4.21 allows for an instant disconnect, regardless of the state of Winsock.

CR 170

Connecting to the server via modem, when you disconnect TinyTERM it may lock up. Even though it’s a modem connection, this is most likely a corrupted installation of Winsock2. You will need to reinstall Winsock2 to fix the problem.

This happens when TinyTERM connects via telnet, but America On-Line uses a dial-up connection. It’s due to a conflict between the TCP/IP stack for AOL and the Windows stack TinyTERM uses. TinyTERM can’t differentiate between the two.

TinyTERM versions 4.10 and higher have changes that correct for this. No patch is available for earlier versions.