If you do not save a username and password in the Session Properties of TinyTERM Plus, it will pop up a dialog box requesting them when you connect. However, if TinyTERM is configured to save settings on exit, or if you click Yes when asked to save the session, TinyTERM saves the login information automatically.

In TinyTERM Plus versions prior to 4.31, this will happen even if TinyTERM Plus is configured never to save settings on exit. This bug was fixed in TinyTERM Plus 4.31.

To prevent this in TinyTERM Plus 4.31 and higher versions, go to TinyTERM Plus’ Edit menu and select Preferences. Under Save settings on exit, select the Never radio button. You can also choose the Protect all settings option, which will prevent any changes from being saved as long as it is set.

CR 479, fixed in TinyTERM Plus 4.31
CR 640

Neither TinyTERM nor TERM includes a switch for silencing beeps sent by the host. However, you can do this through the included script languages. In TERM Script Language, the command is:

TRANS INPUT “\007” “”

As you can see, this takes the ASCII 7 character — ^G or the bell sound — and turns it into nothing. Unfortunately, there is no equivalent CScript command.

This error may list any number of CScript methods. It generally means that a command tried to execute before the TE or FT control it references has actually loaded.

It’s most common when a script is run as an application startup script. To bypass the error, configure TinyTERM to run the script at post-session start instead.

TinyTERM and TinyTERM Plus are normally licensed per installed seat. This means that a five-user license is valid for five installed PCs. It does not matter how many connections are made through TinyTERM on a single PC, only how many times it’s installed.

Per seat is the only licensing method for the following:

• TERM for Macintosh (discontinued), and
• TERM for Linux Desktop

All versions TinyTERM and TERM for DOS can be network installed with concurrent licensing. So can TinyTERM for Windows versions up to 3.2, and TERM for Windows versions up to 7.2. This involves installing most of the TinyTERM files to a network share, with only a few on the PC’s hard drive. A set number of users can then run TinyTERM simultaneously.

All versions of TinyTERM Thin Client, and TinyTERM Plus version 4.40 or higher, when installed in a terminal server environment, are also licensed for concurrent users. This means that a 40-user license will allow 40 users to run TinyTERM at a time. The 41^st user will get a message that all licenses are in use.

TinyTERM Web Server and TERM for UNIX/Linux are licensed per server. Any number of users up to the maximum the server supports may use these products simultaneously. TinyTERM Web Server does require that each user have the TinyTERM Web Server Client installed, unless the PC has a license for TinyTERM or TinyTERM Plus.

No Century Software, Inc., product is licensed per user. If only one person needs TinyTERM, for example, but needs it both on an office PC and a home PC, then a two-seat license must be purchased.

CR 256, request for concurrent network licensing in TinyTERM 4.x (not currently implemented)
CR 581, request for network install in TinyTERM 4.x (not currently implemented)

When using TinyTERM 4.21, if the Caps Lock is on, the Alt key does not access the TinyTERM menus. For example, normally Alt-F opens the File menu. If Caps Lock is on, you have to type Alt-Shift-F to do the same thing. This is the only workaround.

If the “Use Alt keys in emulation” option is checked, this is not a problem. But with that option checked, the Alt keys won’t access the menus anyway. This is by design, because they are passed to the terminal instead.

CR 357, fixed in TinyTERM 4.30

Some versions of TERM for UNIX, particularly prior to version 6.2.5b, can only read and write file names up to 14 characters long. This affects scripts, file transfer, log files, etc. The solution is to upgrade your version of TERM.

At this writing, TERM for AIX still exhibits the problem. The most current versions of TERM for all other operating systems do not have this restriction.

CR 70

TinyTERM versions from 4.00 through 4.30 do not always save the printer selected by the user in Printer Setup. This bug is related to the way printers are indexed in Windows.

CR 416, fixed in TinyTERM 4.31

When you go to TinyTERM’s Help menu and select “About,” it may show itself as “TinyTERM European Edition.” This does not mean you have the wrong product. The words “European Edition” are actually a holdover from TinyTERM 4.11, which was initially released in Europe.

“European Edition” was eventually removed from the Help | About dialog. Newer versions will just show “TinyTERM” there.

TinyTERM versions through 4.50 are hard-coded to use COM1 through COM6. While it’s possible to have more serial ports on a Windows PC, those versions of TinyTERM won’t be able to use them.

TinyTERM versions 4.52 and higher have no hard-coded serial ports. Instead, they request a list of available ports from Windows. Note that ports currently in use by other applications are not considered available. So the “Available devices” list in TinyTERM may not reflect all installed serial ports.

Regardless of the version of TinyTERM, COM ports above COM9 are not recognized in CScript. Only COM1 through COM9 can be accessed through the te.ComPort property.

CR 182, fixed in TinyTERM 4.52
CR 832, te.ComPort

When you are connected to a modem and manually entering commands, it may display OK when you type, but not echo your commands back. Or it may not display anything.

This indicates the modem is in silent mode. To change that, type the following and hit Enter:

ATE1Q0

This will deactivate silent mode on most modems. If it does not work, check your modem documentation for more information.