TinyTERM’s keyboard mapper allows you to remap the NumLock key. Version 4 also has a Force Num Lock on setting that will keep NumLock on for the TinyTERM window.

Doing both of these on a Windows NT, 2000, XP, 2003 or Vista system causes a particular issue. When you hit the remapped NumLock key, it repeats the mapped action three times.

Those operating systems read both the key press and the key release as separate events. TinyTERM also reads the key press as an event. So what actually happens is that the mapped action is triggered once for each event.

If the NumLock key is not mapped in TinyTERM, there is no problem with the Numlock signal being processed more than once. But altering TinyTERM’s behavior for this would damage other keyboard mapping functions.

CR 231

TinyTERM versions prior to 3.0 and TERM versions prior to 7.0 store connection information in files with the .con extension. TinyTERM 3 and TERM 7 use the .tap extension, and TinyTERM version 4 uses the .tpx extension. Century Software, Inc., provided utilities to convert between the various formats, so you don’t have to set the connections up all over again.

For updating .con files to .tap files, TinyTERM 3 and TERM 7 include a convtap.exe program. To use it, run it at a command prompt, using the name of the .con file as an argument. For example, to convert the file sample.con to sample.tap, the command would be:

convtap.exe sample.con

To convert a .tap file to a .tpx file, use the script TAPtoTPX.cs included in TinyTERM 4. (You can also download a copy.) See the file C:\Program Files\Century\TinyTERM\TAPtoTPX.wri for documentation of this script.

Both TinyTERM versions 3.x and 4.x store keyboard mappings in the file keyboard.dat. The format of the two files is nearly identical, in fact. The only difference is in the section heading. For example, a keyboard scheme named “My Keyboard” would be set apart in version 3 like so:

[My Keyboard.kbd]

In version 4, it would be set apart like so:

[My Keyboard.keyboard]

So to copy a keyboard scheme from version 3 to version 4, you can simply copy the entire section of keyboard.dat, changing .kbd to .keyboard in the process.

TinyTERM Plus version 4.05 will use 100% of the CPU if a session is configured for TN3270 or TN5250 emulation. TinyTERM Plus 4.10 will do the same thing with two or more sessions open using those emulations.

TinyTERM 3.3 will sometimes use 100% of the CPU regardless of the emulation chosen. Older versions of TERM or TinyTERM for Windows will do the same thing. TinyTERM does not need to be connected for this to happen.

There is no workaround for these situations. TinyTERM must be upgraded to improve its CPU utilization.

TinyTERM Plus Edition 4.05 may use 100% of the CPU after install on Windows NT 4.0, even when the TinyTERM Emulator is not running. That’s caused by the NFS client included with TinyTERM Plus Edition. To fix that, uninstall TinyTERM and NetUtils. Reboot the PC, then reinstall without the NFS component.

TinyTERM 4.31 and higher will use 100% of the CPU on Windows 98 or Me when connected via TCP/IP or modem. This does not happen on Windows 98 Second Edition, nor does it happen with serial connections.

CR 72, improved in TinyTERM 4.12
CR 294, reported in TinyTERM 4.20
CR 647, Windows 98 and Me

The TN3270 emulation type includes the HLLAPI programming interface. This was added to TinyTERM Plus in version 4.30 in the TN3232.exe program found in C:\Program Files\Century\TinyTERM\HLLAPI, rather than the default TinyTERM emulator.

TN3232.exe is no longer included in TinyTERM versions 4.60 and higher. For these versions, use the Whlapi32.dll for the HLLAPI interface.

CR 92

Using the included CScript language and the keyboard mapper, you can configure a key in TinyTERM 4.02 or higher to copy the entire screen to the clipboard. Earlier versions of TERM or TinyTERM for Windows do not have this capability. And there’s no default clipboard in DOS or UNIX.

Open the Session Properties and go to the Keyboard tab. Click Edit to bring up the keyboard map.

In the map, click the key you want to use. You can click Ctrl, Alt or Shift first, or even Ctrl+ Shift, if you prefer.

Change the Action field to COMMAND. In the Value field enter this string:

te.CopySelection(-1,-1,-1,-1);

Click Set, then close the keyboard map. Click the Save As button to give the new keyboard scheme a name, then OK and save everything. The next time you hit that key, the entire screen will be copied to the Windows clipboard.

TinyTERM version 4.x will sometimes bring up the Page Setup dialog when a data capture is started. If you OK the dialog, the capture goes to the printer instead of the specified file. If you Cancel the dialog, nothing is captured.

This is a bug in TinyTERM. It most often happens if you’re using a .tpx file that was opened after you started TinyTERM.

The only workaround is to exit TinyTERM, then double-click the .tpx file you want to use. While it is the only file open, try the data capture again. You may need to do this more than once. Changing the version of TinyTERM you have installed may also help.

CR 81, improved in TinyTERM 4.11
CR 501, fixed in TinyTERM 4.7.0

TinyTERM versions 4.20 and earlier will only accept plain text in the WRU Answer Back field. Version 4.21 and higher will accept the same special strings that are used in script.

There is a patch that will add this functionality to TinyTERM 4.20, but not earlier versions. You can download it here. To use it, copy it to your C:\Program Files\Century\TinyTERM folder. Locate the existing CenTE.ocx in that folder and rename it as a backup. Then rename the patch to CenTE.ocx. The next time you start TinyTERM, the WRU Answer Back will accept the special strings.

CR 240, added in TinyTERM 4.21

In some cases you may not hear beeps that should be generated by the host system. This is especially common on systems without sound cards.

TERM and TinyTERM automatically play the system default sound — a beep on systems without sound cards, the default sound otherwise — when they receive a ^G character, ASCII value 7. But on desktop systems that are fast enough, that beep may be played through the speaker as a faint, very fast click.

To test for this, go to a command prompt while you’re logged in and enter the following command. It may need to be changed slightly for your individual system:

echo “\007\007\007 \007\007\007”

This should play six beeps in a row, which will usually string together as a normal beep rather than a click. If you hear nothing then, check your PC’s sound settings. The default sound may be turned off.

There is one known incompatibility, the Toshiba Satellite Pro 6000 running Windows XP. TinyTERM plays no sounds in this environment.

CR 376

TinyTERM 4.40 added support for the UTF-8 character set. TinyTERM 4.42 added Unicode support for Big5, GB2312, Shift-JIS, and KOI-8. This expanded the languages that could be displayed to include Chinese, Japanese and Korean.

To use the available double-byte characters, you need an appropriate font installed in Windows. For example, you might use PMingLiU.ttf or simsun.ttc for Chinese support.

Once you have installed the right font for the language you want to display, open the TinyTERM Session Properties and go to the Fonts tab. Add the font to the list in TinyTERM, and change its matching code page to Unicode Font. Apply the change, but don’t click OK yet.

Go to the Code Page tab next. In the lower left, there’s a drop-down box. Select the appropriate Unicode option there, then click OK and save the settings. Double-byte characters should display correctly after that.

TERM for UNIX/Linux has no font settings. It relies on the operating system for all character display.

For more information about Unicode, see the official Unicode web site.

CR 334, Japanese added in TinyTERM 4.40
CR 531, Unicode added in TinyTERM 4.40
CR 667, enhancement request for UTF-8 support in TERM for UNIX/Linux

TinyTERM 4.13 has some color display bugs. To fix them, apply this patch.

Download the file to C:\Program Files\Century\TinyTERM. In that same folder, locate the existing CenTE.ocx file. Rename it as a backup. Rename the patch file to CenTE.ocx. The next time you start TinyTERM, it will be in effect.

CR 175, fixed in TinyTERM 4.20.