With TinyTERM Plus Edition 4.05 installed, you can’t capture a network printer to LPT1:. The problem goes away when TinyTERM is uninstalled. To fix the problem, reinstall TinyTERM Plus Edition without the NFS component.

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.

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.

TinyTERM won’t start. Instead, it gives the error, “Could not run CSL entry point: main.”

“CSL entry point: main” is another name for the TinyTERM program tt.exe. So the error only means TinyTERM can’t start. There are three probable causes for this:

1. The first is a corrupt .tpx file. Rename the .tpx file you’re using, then start TinyTERM. If you get a “file not found” error, click Yes and configure your connection again. The old file was corrupt.
2. Another program may have replaced DLL files TinyTERM uses. If the problem started right after installing other software, try uninstalling that software. If you have a “rollback” utility that can restore Windows to a previous configuration, that’s even better. Test TinyTERM to see if it works again after the uninstall or rollback.
3. If you still get the “CSL entry point” error after renaming the .tpx file, and no new software was installed, one of TinyTERM’s main files is corrupt. The only way to fix that is to uninstall TinyTERM. Delete the Century folder from Program Files after uninstalling, then reboot and reinstall.

CR 140, DLLs replaced

Using the Linux emulation in TinyTERM 4.x, you may not get the correct line draw characters. Changing the font in TinyTERM and setting the Use non font-based line draw characters option in the Session Properties don’t help.

Newer Linux systems use UTF-8 or Unicode characters for their console, but many applications still don’t. To disable Unicode for the session, at a system prompt enter:

unicode_stop

To turn it back on, the command is:

unicode_start

To disable UTF-8 on an English-language system, the command is:

LANG=en_US;export LANG

Restoring UTF-8 uses thie command:

LANG=en_US.UTF-8;export LANG

TinyTERM 4.40 or higher also has a Unicode mode that may resolve the issue on some systems. Open the Session Properties and go to the Code Page tab. In the lower left, change the drop-down option from “Pass through” to “UTF-8.” OK and save the changes. That will work on most systems using UTF-8.

There are several possible solutions to this error:

1. If the version printed on the activation key card or listed in the license email does not match the install version, then this error will come up. Verify that the serial number you have matches the TinyTERM version you are installing. For example, older serial numbers will not work with the current TinyTERM download. And the serial number that comes with a TinyTERM CD is specific to that version of TinyTERM.
2. Check the serial number and activation key for typographical errors. The serial number will always be 11 characters long: one to three letters, six to eight numerals, then two letters. No serial number ends in the letters “OEM”. The capital letter O will actually be the number zero in all cases.The activation key is always eight letters. Depending on the font, this may make the lower-case letter l look like the number 1. It’s never a number, though.
3. When installing TinyTERM 4.52 from CD, you’re seeing a timing error. Despite what the install says, it’s not ready for the license yet.In this case, click the 30-Day Eval button instead. The install will continue from there. Once the install is done, go to Start | Programs | TinyTERM and run the License Manager.

   In License Manager, click the Upgrade button. Enter your serial number and activation key, then click Update License. Close the License Manager. TinyTERM will then be licensed, rather than an eval copy.

4. For a serial number that starts with the letters MMA, do not let the CD autorun. Instead, on the TinyTERM CD you’ll find a folder named “setup32_v33.” Run the setup.exe program in that directory instead. That will accept your license information.

You may see this error when installing TinyTERM on Windows 2000 or XP. It will reference the file AUTOEXEC.NT or CONFIG.NT.

It usually happens when the specified file is missing. You can find a replacement in either C:\Windows\Repair or C:\Windows\i386. Copy the file into C:\Windows\System32, then start the install again.

If AUTOEXEC.NT already exists in C:\Windows\System32, the error means that file has a setting that’s interfering with TinyTERM’s install. To fix the error, back up AUTOEXEC.NT by copying it to another location, then edit it to have the following three lines only:

lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx

You won’t need to reboot. TinyTERM will install after those changes are made.

CR 730, fixed in TinyTERM 4.50

TinyTERM
By default, if you make any changes to the session properties, TinyTERM will prompt you to save the settings. There are a few ways to protect the settings:

1. The “Save settings” prompt can be turned off. To do this, go to TinyTERM’s Edit menu and select Preferences. For the “Save all settings on exit” option, select “Never.” Save the session after making that change. You won’t get the prompt again; however, this doesn’t prevent someone from using the File menu to save future changes.
2. On the same Edit | Preferences dialog, there’s a check box labeled “Protect all settings.” Save the session after selecting that. TinyTERM will prevent any changes to the session after that.
3. In My Computer or Windows Explorer, locate the connection file you’re using; e.g., default.tpx. Right-click the file and select Properties from the pop-up menu. Check the box labeled “Read-only” in the Properties window. Click OK, and Windows will prevent the file from being changed.

Combining options 2 and 3 will provide the most protection for the settings. Option 3 will also work for all Windows or DOS products.

TERM
In TERM for UNIX, the only way to protect connection settings is to change permissions on the connection file. Users must have read permissions to use a .con file, but that’s all. So you can set the permissions to 544 (-rw-r–r–) on any file or directory you wish to protect.

TinyTERM or TERM for Windows can open up to nine sessions in a single window. Available memory is the only limit to the number of windows a single PC can open, so if you need more than nine, you can open more windows.

TERM for UNIX, as well as all DOS products, will only open a single session at a time. In TERM for UNIX, you can open as many instances of TERM as your UNIX OS will support.

Century Software, Inc., has had a request that the second time you start TinyTERM, it adds a new session to the existing instance, rather than opening a new window. This enhancement has not been implemented thus far.

CR 218