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.

Using TinyTERM 4.2, transparent printing will skip pages at random. This is due to a bug in SSH communications. To fix it, download this patch. Unzip it into a temporary directory. Three files will be extracted:

regall.bat
cencomssh.dll
cencom.dll

Rename the existing copies of the two DLL files in your TinyTERM install directory as backups. Next, copy in the new versions and the batch file. Once that’s done, run the batch file from the TinyTERM directory. This will register the files and should take care of the printing problem.

CR 244, fixed in TinyTERM Plus 4.21

This error means one of two things:

1. Your version of TinyTERM is too old for your version of Windows. The version of TAPI is therefore too new for TinyTERM to use. Upgrading TinyTERM is the only solution.
2. TinyTERM has a specific incompatibility with the modem. Update the modem drivers in this case.

If both TinyTERM and the modem drivers are up to date, you will need to dial the modem manually.

As a security feature, some host systems will allow you to login over a modem, then disconnect you and call you back at a predetermined phone number. Functionality to allow TinyTERM to answer the phone in this situation was added in version 4.30, in the form of the te.WaitForCall property. Setting it to true causes TinyTERM to wait for the currently selected modem to ring, then answers it:

te.WaitForCall=true;

This property allows you to set up an automated callback login. We have a sample script that does exactly that. It only requires editing for the correct telephone number and prompts.

CR 342, script
CR 399, capability
CR 455, duplicates CR 342

A TCP/IP connection creates a pseudo-tty device (ptty) on the fly at the host system. The numbers assigned to them are not stored, but are lost at disconnect. The specific ptty may change with each connection.

Some configurations may require that users login through specified ptty ports. SCO UNIX has a solution for this in the recon command. Similar commands may exist for other host operating systems, but they are not as well documented.

This error generally indicates a firewall is blocking TERM or TinyTERM from connecting via TCP/IP. To get rid of the error, configure the firewall to allow TERM or TinyTERM to connect without restrictions. The specifics will depend on how your firewall is configured.

CR 708, firewall handling improved in TinyTERM 4.50

When making an RS232 serial connection in TinyTERM 4.20, you will need to set all three flow control options in most cases. To do that, go to the Edit menu and select Session Properties. Next to the COM port is a Setup button. Click that to get to the flow control options. Make sure all three are checked, then save the settings.

CR 257, fixed in TinyTERM 4.21

This error comes up in TinyTERM version 4.20, usually when trying to connect again after logging off a network connection. If you wait long enough, you don’t get the error on connecting. It’s not a problem in other versions.

It’s actually tied to the Ribbon Bar. To fix the error, go to the View menu and make sure the Ribbon Bar option is checked. Once that’s on, you won’t see the error again.

CR 275, HP-UX
CR 283, fixed in TinyTERM 4.21

Any network connection requires a TCP port be open and available on the server. There is an excellent list of common TCP ports at www.iss.net.

If you are using a non-standard port in TERM, you can specify the correct port by adding to the address, after a colon. For example:

term -l telnet:192.168.0.1:1023

will cause TERM to use telnet to connect to port 1023, rather than using the default port of 23. TinyTERM for DOS can also be configured this way.

In TinyTERM for Windows, you will need to go into the advanced setup for the telnet, SSH or SSL/TLS protocol. That dialog box will include a port number that can be edited.

At this writing, no file transfer protocol has this capability. This includes FTP in the emulator, as well as the protocols available in the Century FTP Client or SecureFT. The NFS client and server likewise cannot be changed.

CR 235, Century FTP Client
CR 620, FTP in emulator
CR 828, SecureFT

In TinyTERM 4.10 and 4.11, connecting via SSH requires you to save your username and password in the Session Properties. That is a potential security risk. It can be avoided by using this script. It will prompt for a username and password when connecting.

1. You must use the connect button on the ribbon bar when connecting. Auto connect will not work with this script.
2. Save the sshlogin.cs script to the C:\Program Files\Century\TinyTERM directory.
3. Open TinyTERM and click the Session button on the Ribbon Bar, or from the Edit menu select Session Properties.
4. Select the radio button labeled Post session start and click the Browse button below. Browse to the sshlogin.cs script in the TinyTERM directory.
5. Select OK.
6. On the Login tab, clear the username and password if they are saved there.
7. Save the changes and exit Session Properties.

The next time you open TinyTERM and connect with this configuration, you will be prompted for a username and password.

CR 86, prompt added in TinyTERM Plus 4.12
CR 96, sshlogin.cs fails to connect at times