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

Currently data capture is the only method TinyTERM supports for saving the data stream. Century Software, Inc., has had a request to add an option to write the contents of the scrollback buffer to a text file.

CR 850

When using an SSH connection, the mouse wheel will not scroll back through the buffer. You must go to the View menu and turn the Vertical Scrollbar option on, then use the scrollbar instead.

CR 849

The brief install instructions for PIXIL Configuration Server running on Windows 2003 (available here) require some adjustment for Windows 2003 Server systems using Service Pack 2.

First, “Remote Installation Services” referred to in the above document is now named “Windows Deployment Services.” That Windows component must be added in step 1, along with the DHCP server included in Networking Services.

Second, you must initialize Windows Deployment Services. This must be done after the client files are copied into C:\pixilboot. Open a command prompt and execute this command:

wdsutil /initialize-server /reminst:”C:\pixilboot”

Once these two steps have been taken, your PXE clients will boot PIXIL Thin Client correctly from the server. However, custom configurations will not load. This is due to a difference between the DHCP server available in Windows 2003 Server, and similar features in UNIX and Linux. To bypass the problem, add <server>-confighost to the append line of the configuration file in C:\pixilboot\pxelinux.cfg. For example, if your server’s IP address is 192.168.1.1, and your client’s configuration files are in C:\pixilboot\PXEclient, the append line might read:

append ramdisk_size=158000 root=/dev/ram0 initrd=/pixil-initrd.gz init=/linuxrc rw vga=0×314 192.168.1.1-confighost PXEclient-config