Telnet and SSH servers can automatically detect the terminal type at connection. However, most systems don’t have separate definitions for VT220-7 or VT320-7 emulations. You can correct that with the Telnet terminal type option. Set it to VT220 or VT320 as appropriate, and the host system will recognize the emulation.

The Wyse50 and Wyse60 terminals have several status lines, lines of text separate from the main screen at the top and bottom. There are both standard and extended lines at the top of the screen, and shifted and unshifted label lines at the bottom. TinyTERM currently supports only the unshifted label line.

CR 103, unshifted label line added in TinyTERM 4.21
CR 798, requested in TERM for AIX
CR 1006

When using the AT386 emulation, the cursor may disappear. Opening the Session Properties, then clicking OK without making changes will bring it back. For TinyTERM versions 4.00-4.10, this patch will resolve the issue.

To use the patch, locate your exising CenTE.ocx file in C:\Program Files\Century\TinyTERM. Rename it as a backup. Copy the patch into the same directory, and rename it CenTE.ocx. The next time you start TinyTERM, it will be in effect.

CR 97, fixed in TinyTERM 4.11

Using SCOANSI emulation, Medical Manager menu items should highlight as you use the arrow keys. When they don’t, it means there’s a setting in Medical Manager that needs to be changed. To get to it, go to a command prompt and type:

install su

Accept the default path when offered, then say no to changing terminal characteristics. Login to Medical Manager normally after that.

From the resulting menu, select option 1. Type “n” once to go to the next page. At the top of the screen there’s a “Color Init” line. In that line, change the number 49 to 48. Save the changes and exit. The next time you start Medical Manager, the color highlights will work properly.

CR 642

Different versions of TinyTERM for Windows handle copying and pasting text differently. Pasting into another application, such as Lotus Notes, may give a graphic instead of text. Or the lines may break incorrectly: too many spaces between, or none. And pasting into the emulator may put extra blank lines in, or erase the line feeds badly. Furthermore, exactly what happens will vary with the version of TinyTERM.

Oddly enough, all these behaviors came about because of customer requests. Depending on the source or destination for the copied text, different applications have different needs.

The ability to copy a part of the screen as an image was removed permanently in TinyTERM 4.20. But the line feed issues varied by version from there until TinyTERM 4.53, when an interface option was added.

To get to that option, open the Session Properties. Next to the Emulation line is a Setup button. The Add carriage return to copy check box in the resulting dialog allows the user to control the copy/paste behavior as desired.

CR 30
CR 186
CR 636, interface option

A TCP/IP connection error usually includes a five-digit number that starts with 100 or 110; e.g., 10057. These errors always come from the operating system, not TERM or TinyTERM.

There is an excellent reference to the error numbers at sockets.com. Toward the bottom of the page is a list of all the errors in numeric order for quick reference. It’s an excellent way to troubleshoot TCP/IP socket errors.

In TinyTERM 4.10 with multiple sessions open, you may see your active session close. This happens when you have “Close on disconnect and exit” set in one of the inactive sessions. But it only happens when the inactive session is disconnected remotely.

The host may have a timeout set. (See this entry for more details.) When the inactive session is timed out, it should close automatically. But due to a bug in TinyTERM 4.10, the active session gets closed instead. There is no patch to fix this. You must use a newer version of TinyTERM.

CR 101, fixed in TinyTERM 4.11.

TERM and TinyTERM can use a cell modem, as long as the operating system recognizes it. There is only one change needed. In the modem’s configuration, set it up so that it dials without waiting for a dial tone. Otherwise the connection will fail.

This error means that a system somewhere in the connection sent a reset signal, which will disconnect TinyTERM or TERM. Any system from the PC to the server — and any router, firewall or gateway in between — can generate this error.

To find the source of the problem, you will need to run a packet capture utility such as Ethereal. That will show you which system is sending the reset signal. With that information you can correct the error on that system.

This is a display bug in some versions of TinyTERM 4. There is no patch to fix it.

It does not affect functionality at all, though. You can ignore the display.