Install TinyTERM on Windows Vista or Windows 7, then connect to a SCO OpenServer 5 system via telnet. 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 earlier versions of Windows.

This is due to a change in TCP/IP originally implemented in Windows Vista. More information is available from Microsoft support. This was fixed in TinyTERM version 4.65.4732.

CR 856, Delete key
CR 865, Escape key

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.

TinyTERM works as designed in this instance. Applications that take an arbitrarily high amount of time to generate a printout will have natural breaks in the data flow. If the break is long enough, which depends on the timeout value set or the time before key press, TinyTERM will release the print job as it should. The workaround is to print on timeout, with a timeout value equal to or greater than the job creation time. This is typically 60 seconds or more.

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

Originally data capture was the only method available in TinyTERM for saving the data stream. In version 4.61, the Save scrollback buffer option was added to the Tools menu. This option writes the contents of the scrollback buffer to a user-specified text file.

CR 850, added in TinyTERM 4.61

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=0x314 192.168.1.1-confighost PXEclient-config

To make an RS232 serial connection in TinyTERM 4.x, do the following:

1. From TinyTERM’s Edit menu, select Session Properties.
2. Under Connection type, click RS232 (Serial).
3. From the Available Devices drop-down list, select the COM port for this connection.
4. Next to Available Devices, click the Setup button. The RS232 Setup dialog box appears.
5. Set the baud rate, parity, word length, stop bits and flow control to match the port settings on the host.
6. Click OK to close the RS232 Setup dialog.
7. In the Emulation drop-down list, select the emulation required by your host.
8. Click OK to close the Session Properties dialog.
9. From TinyTERM’s File menu, select Save Session.
10. Click Connect. You may need to press the Enter key once or twice to get a login prompt.

To make an SSH connection in TinyTERM Plus 4.x, do the following:

1. From TinyTERM’s Edit menu, select Session Properties.
2. Under Connection type, select SSH. (If SSH is not available, you have TinyTERM rather than TinyTERM Plus.)
3. In the Emulation drop-down list, select the terminal emulation required by your host.
4. In the Host name, IP address, or phone number box, enter the hostname or IP address of the server.
5. Click OK to close the Session Properties dialog.
6. From TinyTERM’s File menu, select Save Session.
7. Click the Connect button.
8. A login dialog will come up. Enter your username and password, then click OK.
9. If this is the first time you’ve used TinyTERM to connect to the particular host, a fingerprint dialog will come up. Click OK to continue connecting.

For video instructions, please see this screencast.

TERM for SCO UNIX  and TERM for Linux version 6.28 also have the ability to connect via SSH. To do this, you’ll need to start TERM from the command line like so:

term -lssh:user@host.or.ip

Replace “user” with the appropriate username, and “host.or.ip” with the hostname or IP address of the target system.