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

For most terminal emulations, a function key sends an escape or control sequence. That sequence can be sent to the host using CScript or TERM Script Language (TSL).

For example, the F1 key in Wyse50 emulation sends Ctrl-A, then the @ sign, then a carriage return. This is usually abbreviated ^A@^M. The script commands to send that sequence are:

CScript: te.xmit(“\001@\015”);
TSL: xmit “\001@\015”

As you can see, the control characters are replaced in the strings by their octal values, preceded by the backslash character \. The octal values for control characters can be found at http://www.robelle.com/. Keyboard references for several emulations are available on our website.

The “print on” code for Wyse50 emulation is ^X. That’s the same code used to end a file transfer in the ZMODEM and WTERMCRC protocols.

To avoid problems, use a different file transfer protocol with Wyse50. Or use a different emulation with ZMODEM and WTERMCRC. Either solution will work.

When you click on a telnet link in a browser, TinyTERM should open and make the connection. If another application opens, you can restore TinyTERM as the helper application with these steps:

1. Open My Computer or Windows Explorer.
2. From the Tools menu, select Folder Options.
3. On the File Types tab, locate the “URL:Telnet Protocol” item in the N/A portion of the list and click it to highlight.
4. Click the Advanced button.
5. Click the word “open” in the list to highlight it, then click the Edit button.
6. Under “Application used to perform action,” enter this string:
   

   “C:\Program Files\Century\TinyTERM\tt.exe” /helperapp:%1

7. Click OK several times, until the Folder Options is closed.

When TinyTERM 4.x is connected via modem, some email attachments won’t open from Microsoft Outlook. In particular, documents from Microsoft Office applications such as Word and Excel are affected. As soon as TinyTERM disconnects, the documents will open. This was fixed in TinyTERM 4.30.

CR 209

TinyTERM versions 4.00-4.20 have a memory leak in the Session Properties dialog. If you change several settings at a time, eventually you’ll see a “Get property failed” error message.

When this happens, the solution is to save your settings and exit TinyTERM. When you start TinyTERM again, the error will not happen immediately. Some of your previous settings may be lost, though.

CR 254, fixed in TinyTERM 4.21
CR 401, duplicate

TERM and TinyTERM for Windows have an automated login function that can readily be extended to execute system commands as part of the connection. Under the Login setup, or the Advanced Login setup, there are four “Wait for” and “Then send” options. The first two lines are taken for the login and password prompts. The last two can be used for anything.

Note that the “Wait for” items are case-sensitive. That’s why the first letters are missing from the words “login” and “password” there. Some systems send these in upper case, others in lower. But the rest of the word is virtually always lower case, so leaving the first letter off bypasses guessing its case.

The default “Then send” strings are composed of what look like control characters. Here they are, explained:

• ^W – This causes TinyTERM to wait one second before performing the next operation.
• ^U – This sends the username from the Login dialog down the comm line.
• ^P – This sends the password. The password is stored encrypted, so it can’t be read directly from the configuration file.
• ^M – This sends a carriage return, ASCII value 13.

Any other characters entered in a “Then send” line will be sent as plain text. All characters in a “Wait for” line will be read as plain text.

Given that information, you can send any command to the host using those text boxes. For example, to wait for a $ prompt, then send an “ls” command, you would enter:

$

in the third “Wait for” line. In the accompanying “Then send” line, enter:

ls^M

The one-second wait given by ^W may or may not be necessary. Experiment with the timing to see how the commands work out. We also recommend you go through the login manually before automating it, so that you can note any differences from the defaults. Different or additional prompts are the most common changes.