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

You may encounter a situation where you can upload files to the remote system, but not download them to your PC. Or download may work, but uploading fails. There is a set of configuration changes that will fix this problem in most cases.

For systems running TinyTERM 3.3 for Windows, or any version of TERM on any operating system, write a script that includes three lines:

SET ESC8BIT ON
SET COMPRESS OFF
PROTOCOL NONE

Save that script as “onewayft.cmd”, then run it when you start TERM by adding it to the command line:

term onewayft.cmd

Add any other command-line arguments as needed. If you are transferring files between two versions of TERM, create and use the script on both systems.

For TinyTERM 4.x for Windows, the settings are in the file transfer properties. To access them, go to the Edit menu and select File Transfer Properties. On the resulting dialog, clear the check box marked Use automatic data compression.

Next, click the Setup button in the upper right. In the resulting File Transfer Protocol Setup dialog, check the Use 7bit transfer over 7bit connection (esc8bit) box. Click OK twice, then save the session.

This will take care of the problem in most cases. Once in a while, you may need to add this command to the TERM script:

SET ESCCTL ON

In TinyTERM 4, go to the File Transfer Protocol Setup dialog and check the Escape Control Characters option to accomplish the same thing.

CR 229

The TSL compatibility command tsl_atobjaddarray() does not work. It should populate a list box or similar control with the contents of an array. Instead, it does nothing.

You can work around this with a simple while() loop. For example, the following CScript fragment adds the contents of a ten-item array named Items:

tsl_atobjinit();
counter = 0;
while (counter < 10) {
tsl_atobjaddlist(Items[counter]);
counter++;
}
tsl_atobjdone(111,9,5,5,250,200,(0)|16385,"","",0,0,-1,"chosen", "");

The closing tsl_atobjdone() command must be included, but the format will vary depending on the control you’re populating.

CR 611, fixed in TinyTERM 4.40

This error is the result of a bug in TinyTERM 4.11. The only solution is to use a different version of TinyTERM.

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.

TinyTERM 4.x includes a script translation utility, tsltrans.exe, which will convert scripts written in TERM Script Language (TSL) to CScript. That utility is documented in the file tsltrans.wri and in the Programmers Reference Manual. Most releases of TinyTERM 4 will also execute TSL scripts without translation.

That is the only script translation utility available in any Century Software, Inc., product. No version of TERM will translate from CScript to TSL. Nor will any version of TERM or TinyTERM translate scripts written in any other scripting language.

TinyTERM version 4 includes a DDE server and client, documented in the Programmer’s Reference Manual. The server is configured and enabled through CScript commands.

It’s possible using the DDE server to send script commands to TinyTERM from another application. However, it only accepts TERM Script Language commands in that manner, which are not documented in the Programmer’s Reference Manual. PDF documentation for TSL can be downloaded from this link.

That documentation also applies to TinyTERM Application Developer 3.3. That version of TinyTERM uses TSL exclusively, not CScript, so the notes above do not apply.

CR 499

TinyTERM versions prior to 3.0 and TERM versions prior to 7.0 store connection information in files with the .con extension. TinyTERM 3 and TERM 7 use the .tap extension, and TinyTERM version 4 uses the .tpx extension. Century Software, Inc., provided utilities to convert between the various formats, so you don’t have to set the connections up all over again.

For updating .con files to .tap files, TinyTERM 3 and TERM 7 include a convtap.exe program. To use it, run it at a command prompt, using the name of the .con file as an argument. For example, to convert the file sample.con to sample.tap, the command would be:

convtap.exe sample.con

To convert a .tap file to a .tpx file, use the script TAPtoTPX.cs included in TinyTERM 4. (You can also download a copy.) See the file C:\Program Files\Century\TinyTERM\TAPtoTPX.wri for documentation of this script.

Both TinyTERM versions 3.x and 4.x store keyboard mappings in the file keyboard.dat. The format of the two files is nearly identical, in fact. The only difference is in the section heading. For example, a keyboard scheme named “My Keyboard” would be set apart in version 3 like so:

[My Keyboard.kbd]

In version 4, it would be set apart like so:

[My Keyboard.keyboard]

So to copy a keyboard scheme from version 3 to version 4, you can simply copy the entire section of keyboard.dat, changing .kbd to .keyboard in the process.

This error is caused by a bug in TinyTERM 4.11. The only solution is to use a different version of TinyTERM.

Using the included CScript language and the keyboard mapper, you can configure a key in TinyTERM 4.02 or higher to copy the entire screen to the clipboard. Earlier versions of TERM or TinyTERM for Windows do not have this capability. And there’s no default clipboard in DOS or UNIX.

Open the Session Properties and go to the Keyboard tab. Click Edit to bring up the keyboard map.

In the map, click the key you want to use. You can click Ctrl, Alt or Shift first, or even Ctrl+ Shift, if you prefer.

Change the Action field to COMMAND. In the Value field enter this string:

te.CopySelection(-1,-1,-1,-1);

Click Set, then close the keyboard map. Click the Save As button to give the new keyboard scheme a name, then OK and save everything. The next time you hit that key, the entire screen will be copied to the Windows clipboard.