Terminal Emulator and Thin Client Software: Century Software

Multifunction printers generally install two printer drivers: one for the printer itself, and one for the fax capability. Often these two names are identical, except the word “Fax” is appended to one. For example, these two printers might appear in your Windows printer list:

Lexmark X5070
Lexmark X5070 Fax

The near-identical names can cause problems selecting the correct printer. The solution is to make the names less identical. Renaming the fax driver by moving the word “Fax” to the beginning of the name will take care of the problem. In the above example, you would then have these two printers:

Lexmark X5070
Fax Lexmark X5070

Please note also that any multifunction printer is likely to be a USB printer. More information on using USB printers with TinyTERM is in this knowledge base entry.

(Century Software, Inc., does not endorse particular printer brands or models, nor do we manufacture or sell printers. The use of Lexmark above is intended as an example only. No trademark infringement is intended.)

Century Software, Inc., now has screencasts on our website, video recordings that demonstrate different TinyTERM features and capabilities. The topics covered are:

When connecting via SSH with an RSA key, you might see this message:

Connection failed (969) - Private key decryption failed

There are a couple of possible causes for this:

You entered the wrong username or pass phrase. The RSA key is unique to the user on the host system, and requires a specific pass phrase. If either of these does not match the RSA key, the key will not decrypt properly.
You have the wrong RSA key loaded in TinyTERM for the server. Each host requires its own RSA key, even if the username is the same for multiple systems.

To fix the error, verify the username and pass phrase you are using. Make sure there are no typos in either. If that does not help, you’ll need to double-check the RSA key you have loaded, and may need to regenerate it.

When using CenTE.ocx in a custom application, pressing F1 in the control will normally bring up the help file. The file name auto-generated by the OCX is TECTRL.HLP, which does not exist. Documentation for the TE control is actually in the TinyTERM Programmers Reference Manual.

CR 857

Install TinyTERM on Windows Vista, then connect to a SCO OpenServer 5 system. If you hit the Delete key at a shell prompt, it gives a new prompt on the next line. Do this enough times and TinyTERM will disconnect. This does not happen on other versions of Windows.

CR 856

Configure TinyTERM’s transparent printing option to spool the print job. Whether set to Print on Key Press or Print on Timeout, a printout that takes a long time to generate will put extra form feeds into the print job. This happens regardless of the timeout value as well.

CR 855

When run on a Dell Optiplex GX620, PIXIL Thin Client plays no sounds. Other platforms tested work properly.

CR 854

Century Software, Inc., has had several reports that the TinyTERM cursor does not blink when used over a thin client connection. When used at the terminal server console, the cursor does blink. We have not been able to duplicate this issue in-house.

CR 853

Using TERM-to-TERM server mode transfer, download a file to your Linux PC. Nothing transfers. The same is true for uploading to TERM in server mode using term -1x or term -2x. Both manual and scripted file transfers fail. This works using TinyTERM connecting to Linux.

CR 852