Using TERM for Linux 6.2.5b, executing the command:

term -x server

brings TERM up in server mode normally. Typing  “q” to quit causes TERM to hang. This is fixed in TERM 6.28.

CR 424

Using TERM for Linux 6.2.5b, connect to a tty that has a modem installed. Connect to the modem, then go to the TERM menu, or type ^E to get the c=> prompt, and type H for Hangup. TERM locks up. The TSL HANGUP command will do the same thing. This is fixed in TERM 6.28.

CR 349

WAIT and DWAIT do not time out in TERM for Linux 6.2.5b. This was fixed in TERM 6.28.

CR 267

The TERM Script Language command CONFIG SET causes Linux to produce a segmentation error and exit TERM 6.2.5b with a core dump. That TSL command loads the configuration variables into the current settings. It was fixed in TERM 6.28.

CR 219

Connecting via modem, when TERM tries to XMIT a string the connection dies. This was tracked to the parity not being sent. There was no option to set parity in the modem initialization string.

The workaround was to use the TERM Script Language command SET MASKPAR ON. This masks the parity being sent.

CR 176

It is possible to open multiple sessions over a single serial connection. It requires software such as mscreen or FacetTerm on the host system. Without that, only one session can run on a serial connection.

You also need to set the screen pages. That’s handled differently by different versions of TERM and TinyTERM:

• TERM: Use the TERM Script Language command PAGES:
  

  pages 4

• TinyTERM (up to 3.3) or TERM for Windows: Go to the Configure menu and select Emulation. Change the Screen Pages line.
• TinyTERM for DOS: From the main menu, select Emulation. Change the Screen Pages line.
• TinyTERM 4.00-4.20: Edit the .tpx file in Notepad or another text editor. Search for the “pages=” line. Edit the number there.
• TinyTERM 4.21 and higher: Go to the Edit menu and select Preferences. Change the Screen Pages drop-down.

Regardless of which product you’re using, accepted values for the screen pages are 1-6.

CR 26, added to user interface in TinyTERM 4.21

Using the TERM Script Language included in TERM for UNIX, the ABORT command and ^C both fail to stop the script. This is normal. You will need to add:

SET ABORT ON

near the beginning of the script, before you would type ^C or enter the ABORT command in the script. Otherwise, the abort attempt is ignored.

Any version of TERM or TinyTERM that can run a script can also have the host system it’s connected to execute a TSL or CScript command. To do that, precede the command with an escape character ^[ (ASCII 27) and the string &oF, then follow it with a carriage return ^M (ASCII 13). Send the entire sequence as screen display information. When TinyTERM receives the ^[&oF string, it stops screen display and accepts everything until the ^M carriage return is received. It then processes the appropriate data as script commands.
A sample shell script for Linux might look like this (\033 is the octal value of the escape character, and \015 is the octal value of the carriage return):

echo -e “\033&oFspawn(1,”notepad.exe”,”notepad readme.txt”);\015″

Sent to TinyTERM 4.x, this string executes the CScript command spawn(), which in turn runs Notepad and opens the file readme.txt. A similar command in TERM Script Language would read:

echo -e “\033&oFrun vi readme.txt\015”

This feature is not documented in most releases of TERM or TinyTERM. It was added to the TinyTERM 4.30 CScript documentation.

CR 384

If you need to debug a script, there are two ways to do it. If you are using TERM Script Language, add the following two commands, to the beginning of your script:

SET VIEW ON
SET ECHO ON

This will cause all script output and error messages to display to the TERM window.

If you are using CScript from TinyTERM version 4, you will need the Debug Monitor. Running the executable called DBMon32.exe located in the C:\Program Files\Century\TinyTERM\dbmon32 directory. After launching the DBMon32 program, you will need to launch TinyTERM with the -debug switch. For example, you could change your shortcut target to:

“C:\Program Files\Century\TinyTERM\tt.exe” -debug -PL3 default

You can also type this in at a command prompt. The quotation marks are required. After doing this, TinyTERM will display all debug information in the Debug Monitor, including script errors.

When TERM for UNIX displays this error, test cu or uucp against the same port. If either of those works, there may be a lockfile on the port. To bypass that, enter the command:

term -i

If that fails, list the port explicitly in the command line:

term -l/dev/ttyS0

Replace ttyS0 with the actual tty port. You can also combine this with the -i command-line parameter.

If everything above checks out, look at the number you’re dialing with the CALL command. The # character will cause the “unknown transport” error. This is problematic, particularly if your phone system requires you to dial something like #8 to get an outside line.

CR 412, CALL