In TinyTERM 4.0x, the Source file to get box in the Get File dialog will not accept upper case letters when using the FTP protocol. The only solution is to upgrade to a newer version of TinyTERM. There is no patch.

Using TERM on a DEC ALPHA system, the arrow key definitions changed. The TERM the emulation was set to TTY because the connection was UNIX to UNIX, no conversion at all.

After some digging, the end user discovered that the cursor keys were switching to application mode. Closing TERM resets the keys to normal cursor mode. The solution was:

1. Copy /etc/termcap to /usr/term/termcap.mod.
2. Change the following in /usr/term/termcap.mod for the console emulation type:
   

   ks=\E=ke=\E>ku=\E[Akl=\E[Dkr=\E[Ckd=\E[B3

3. Set the TERMCAP environment variable to /usr/term/termcap.mod and export it:
   

   TERMCAP=/usr/term/termcap.mod;export TERMCAP

On starting TERM the keypad is turned on, but the arrow keys stay unaltered. TERM is looking at the keypad arrow keys, which now reflect the standard arrow keys.

After installing TinyTERM Plus Edition version 4.05 or earlier, at reboot you may see an error about vxdldr or vcdfsd. You can only boot in safe mode after that.

This error comes from a timing conflict with a virtual device loader. To fix it, uninstall TinyTERM Plus Edition, then reboot. On reinstall, deselect the NFS component.

When using an HP JetDirect device, do not print directly to the IP address in TinyTERM. Instead, set up the JetDirect drivers on a server, then specify the printer as a shared printer. Configure TinyTERM to print to the shared printer on the server instead of printing directly to the JetDirect device.

In this situation TinyTERM works with telnet, but SSH sessions connect and immediately disconnect. This only happens if you have “Login at connect” checked in the Login tab of TinyTERM’s Session Properties.

Early versions of SSH in TinyTERM require a username and password on the Login tab, but the “Login at connect” caused connection problems. Without that set, TinyTERM connects and logs in properly. In later versions of TinyTERM, that option is grayed out when SSH is set.

If that option is not checked, check the version of sshd running on the host. TinyTERM versions 4.10-4.13 use SSH version 1.5. SSH 2.0 daemons must be configured to allow pre-2.0 connections when using those versions of TinyTERM.

Using the telnet connection type, TinyTERM 4.0x may fail to connect. Older versions of TinyTERM work, as does Windows telnet. Switching between the hostname and IP address makes no difference. TinyTERM just seems to hang.

This happens when the host sends a signal that puts TinyTERM into binary mode. Binary mode is typically only used by TN3270 and TN5250 emulations. It can cause problems for other terminal emulations.

CR 65, fixed in TinyTERM 4.10

To check the amount of time remaining on an evaluation install of TinyTERM, open its License Manager. Select the product you have installed in the Suites drop-down list. The Status line at the bottom will display the expiration date for the evaluation copy.

When configuring a new printer port in the LPR client, you may see a General Protection Fault error in Spool32.exe. This indicates a conflict with some other software running on the PC.

To locate the process, type Ctrl-Alt-Delete to get the Task Manager. Close one process at a time, except for Explorer and Systray. Test LPR after closing each. You can determine from that which process causes the error.

After uninstalling TinyTERM Plus, on reboot you may see load errors about mar_nfs.386 and ncdnp32.dll. To fix that, do the following:

1. Open Windows Explorer or My Computer and remove any Century folder (C:\Century or C:\Program Files\Century).
2. Go to the C:\Windows\Temp folder. Remove any files or folders that start with _istmp.
3. Search the C: drive for files named mar*.*. From the list of files found, delete the following:
   • marathon.*
   • marsetup.*
   • mar_inet.exe
     You may receive an error that this file is in use. If so, check the far right of the Start bar, next to the clock. If a hammer&wrench icon is there, right-click it and select Exit. You will then be able to delete mar_inet.exe
4. Click the Start menu and select Programs. Delete any Century or TinyTERM Program group.
5. Click Start and select Run. In the Open line, type regedit and click OK.
6. In the Registry Editor, go to HKEY_Current_User\Software. Delete any “Century” or “NCD Software” folders found there.
7. Still in the Registry Editor, go to HKEY_Local_Machine\Software. Delete any “Century” or “NCD Software” folders found there. Close the Registry Editor.
8. Right click on Network Neighborhood and select Properties.
9. Remove “Century NFS” and “Century Internet Services” from the list of installed network components
10. Reboot your PC.

In contrast to other Century Software, Inc., products, TinyTERM Web Server requires several additional steps after it’s installed.

First, you’ll install TinyTERM Web Server on an administrator’s PC (the “administrator copy”). This is a full copy of the TinyTERM Emulator, licensed for install on a single PC only. It allows you to create and modify .tpx connection files, as well as the .dat files used by TinyTERM. The administrator copy also includes a TinyTERM Web Server overview in the file C:\Program Files\Century\TinyTERM\ttws_admin\index.htm.

Once you have the administrator copy installed and your .tpx files created, you will need to upload them to the web server, together with some framing HTML code. A sample upload structure is available in the administrator copy as the directory C:\Program Files\Century\TinyTERM\ttwc.

You will also need to upload the TinyTERM Web Server Client install program. You’ll find that on your TinyTERM CD, in either the zipse or the downloadable directory, depending on the version you have. Each user must install the TinyTERM Web Server Client in order to access the .tpx files you’ve uploaded. It has no user interface and includes no default connection files, so it can only be used for Web-based connections. It includes both an ActiveX control for Internet Explorer and a Netscape plugin.

Once the end user has the TinyTERM Web Server Client installed, clicking a link to a .tpx file will offer the choice to open the file, or save it to disk. Select the option to open the file, and set the browser not to ask the question again for that file type. TinyTERM will open in the browser, using the connection parameters specified in the .tpx file.

Please note that TinyTERM Web Server does not change the look and feel of the host application. It’s still a character-based display.

Additional information is available in this screencast.