In TinyTERM’s Session Properties, configure a script to launch at Post session start. It starts while the splash graphic is still displayed. For many scripts this is not a problem, but if the script has a te.read() command or something similar, the script pauses at that point waiting for input. Since the splash is still on the screen, the user can’t see the prompt, and TinyTERM is effectively hung before it has finished loading.

This isn’t a problem for the second session and beyond. If you launch tt.exe with multiple .tpx files, and the first does not have a post-session start script defined, there is no problem.

This is due to a timing error. Commands like te.read() require an active TE object. That loads much later in the process, and forms the main screen of TinyTERM. For multiple sessions, the second and subsequent do not load until the first is finished, bypassing the timing problem. It was fixed in TinyTERM 4.30.

CR 346

The te.terminal() method works in most situations. However, if it’s immediately followed by an FTGet() command, FTGet() hangs until the user hits a key on the keyboard. If you replace the te.terminal() command with an equivalent te.wait() command, FTGet() does not hang. This was fixed in TinyTERM 4.21.

CR 295

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

CR 267

The CScript commands te.wait(), tsl_wait(), and tsl_dwait() all accept a timeout value from 0-99 seconds. Setting the wait to 0 seconds causes them to wait exactly that long, which is to say not at all.

In TSL, setting a wait value of 0 meant to wait forever, never timing out. CScript was changed to behave the same way in TinyTERM 4.20. However, if you set a timeout value higher than 99, only the first two digits will be used. So a timeout value of 100 is the same as a timeout value of 10.

CR 220, timeout 0 waits forever
CR 674, two-digit max timeout

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

TERM Script Language includes a TERMINAL command. It returns control of TERM to the user until a match string is received. That capability was added to CScript in TinyTERM 4.21 with the te.Terminal() method.

CR 188

The early releases of the CScript documentation were difficult to follow and often cryptic. Also, several commands were undocumented. The documentation was significantly improved in TinyTERM 4.21.

The TinyTERM Programmers Reference Manual compiles the current CScript documentation into a single PDF file. If you have suggestions for further improvements, please contact Technical Support.

CR 153
CR 246
CR 676

There is a bug with the te.wait() command in TinyTERM 4.02-4.12. It returns 0 even if it times out. It should return -1 on a timeout, or -2 on a user interrupt. There is no patch.

CR 152, fixed in TinyTERM 4.13.

A “Script” button was added to the ribbon bar in TinyTERM 4.10. This eliminates the need to go through the Tools menu to run an existing script.

CR 13

This error comes from the FTGet() command in TinyTERM 4.11. There is no patch or workaround. This was fixed in TinyTERM 4.12.

CR 124