Using TinyTERM 3.3 on Windows 95, it hangs when clicking the Modem button in the communications setup screen. This will happen if the modem is not configured correctly in Windows. You can do that through Control Panel.

If the modem looks like it’s set up correctly, but TinyTERM still hangs when trying to configure it, delete the modem from Windows. Reboot the PC and re-add it. That will refresh the modem driver.

Using TinyTERM Plus Edition 4.02 on Windows 98, a modem session connects properly. However, once connected the keyboard response is extremely slow, and it seems like it is using all the laptop’s system resources.

This happens when the baud rate for the modem is set too high; i.e., 115,000. Lower the baud rate in Control Panel to match the remote host’s maximum speed. If there is no exact match, use the baud rate that is just higher than the host’s.

This happens on Windows 95 when the modem is listed twice in Control Panel. HyperTerminal can ignore the second modem, but TinyTERM 3.3. and earlier versions can’t. Deleting the duplicate modem will solve the problem.

Windows defaults to disconnecting a modem after a set idle period. To increase that timeout, open the Control Panel and go to the Phone and Modem Options. Open the properties for your modem. On the Advanced tab, click the Change Default Preferences button. You can set the idle timeout there.

You may see sporadic Winsock errors in TinyTERM when connecting to an Ishare modem server. This happens when the Ishare modem server conflicts with the TCP/IP settings for the local network. You will need to redirect Ishare to look at the modem server only, and redirect the local network to look at the network configuration only. This may require a hosts file on the PC.

Using TinyTERM 3.2 on Windows 3.1, Netscape will not load pages if the Marathon Winsock.dll is in place. However, using Netscape’s Winsock.dll causes TinyTERM to dial the modem, rather than connecting to an ISP.

To bypass this, use the Century Internet Dialer to connect to the ISP before starting Netscape or TinyTERM. This will allow the use of Netscape’s Winsock.dll, while TinyTERM will still recognize the ISP connection.

If TinyTERM gives errors when trying to use the dialer or on boot, it usually means the PC does not have networking installed. To fix the errors, uninstall TinyTERM and reboot the PC. When you reinstall TinyTERM, uncheck Network Utilities and any other network option.

Using TinyTERM on Windows 95 on a Packard Bell PC, it won’t disconnect or let go of the phone line. Instead it gives an error that fmedia and faxworks are active.When this happens, edit the file win.ini. Locate the run= line and delete everything after the equals sign. Reboot the PC to finish the fix.

Using TERM for UNIX 6.2.5 on SCO Openserver 5, trying to run a script which dials the modem to make the connection may cause the modem to repeatedly redial the modem before doing the initialization string. To resolve this, increase the DTIMEOUT value, or insert a DINIT command with the correct initialization string prior to the CALL command.

When setting up a modem connection in TERM or TinyTERM, do not use any country or area code options offered by the operating system. Instead, enter the entire phone number just as you would dial it from a standard telephone. For example, if it’s long distance in the United States, include the leading 1 and area code.

You can use dashes to separate the numbers for readability, but they are not required. To add a two-second pause, such as you might need when dialing 9 to get an outside number, enter a comma in the phone number:

9,1-801-268-3088

CR 89, country code usage added to TinyTERM 4.20