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.

Transferring a file using ASCII format in TinyTERM 4.0x, line feeds are not properly converted. This is a known issue in versions 4.00-4.04. It was resolved TinyTERM 4.05. There is no patch.

TinyTERM version 4 introduced much greater color and attribute flexibility for display. Not all users find the default settings to their liking, though. It’s easy to change the color pallette and other font attributes.

In TinyTERM, open the Session Properties and go to the Attributes tab. In the “Mappable attribute combinations” box are 16 different combinations: NORMAL, BOLD, REVERSE, etc. As you highlight each one by clicking on it, you can change both the foreground and background color, as well as the display attributes assigned to it. Use the “Display Attribute As” and color boxes on the right of the dialog.

Once you have configured each attribute the way you like, click the Save As button to give the new attribute scheme a name. It will be saved to the file attr.dat. If you would like to distribute the new scheme to other users, simply copy that file to their PCs in the C:\Program Files\Century\TinyTERM folder.

To add a full license to an evaluation copy of TinyTERM for Windows, do the following:

1. Click on Start, then Programs, then TinyTERM.
2. Run the License Manager.
3. Click the Upgrade button.
4. Enter your serial number and activation key.
5. Click Update License.
6. Close the License Manager.

To add a license to an evaluation copy of TERM for UNIX/Linux, the command is:

brand /usr/bin/term

Select option 2 to enter a serial number and activation key. They are case-sensitive.

If you have any problems with either licensing procedure, check the serial number and activation key for typographical errors. Also verify that the version of TinyTERM or TERM matches the version the license is for.

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

There is a command in the CScript language that will launch a Windows-based application: spawn(). Here is the function definition from the TinyTERM Programmers Reference Manual:

Void Spawn(iWait, sCmdString, sArguments )
Passes sCmdString to the operating system to be run with the arguments sArguments. Note that the command name, without an extension, must always be the first argument in sArguments. Note that you cannot use quotes as part of sCmdString or sArguments, so if you must launch an application with a space in its Windows filename, you must use DOS 8.3 filenames to refer to that application with the spawn command.

iWait
0 Wait until spawned process ends before running next command
1 No wait
2 Detach spawned process from the console
3 Wait for spawned process to complete its startup procedures before continuing with the next command


For example, the following script command will launch the Notepad application and open the file untitled.txt:

spawn( 0, “notepad.exe”, “notepad untitled.txt”);

A similar command would look like this for Acrobat Reader 5.0:

spawn(1,”C:\Progra~1\\Adobe\\Acroba~1\\Reader\\AcroRd32.exe”,”AcroRd32 D:\path\document.pdf”);

Note the use of \\ as a directory separator. You can also use / if you prefer.

This doesn’t work with some command-line programs, like the ECHO command and batch files. Batch files and a number of Windows internal commands run through the COMMAND.COM or CMD.EXE program. You have to make that program part of the spawn() string, using the /C option. Whether you use COMMAND.COM or CMD.EXE depends on your version of Windows.

For example, suppose you need to copy a text file to the printer port. COPY is part of COMMAND.COM, so the equivalent spawn() item would be:

spawn(1,”command.com”,”command /c copy file.txt > lpt1:”);

The same syntax will work for a Windows batch file:

spawn(1,”command.com”,”command /c execute.bat”);

You can also use this to launch any document with the Windows START command. Again turning to Adobe as an example, the following command will run any version of Acrobat Reader that’s installed, loading the file document.pdf:

spawn(1,”cmd.exe”,”cmd /c start D:\\path\\document.pdf”);

Century Software, Inc., has had a request to bypass the need for START. When a file name is passed, it would use the existing Windows file associations to determine the correct application.

CR 687

If you installed a demo of TinyTERM, then added a license later, it’s still possible to get a message that the evaluation is about to expire. If you then enter the license in License Manager again, it says, “This serial number and activation key have already been used.” If you just click OK on the error message, TinyTERM starts.

This can happen if you installed the demo for one TinyTERM product, such as TinyTERM Plus, but bought a different product. To fix it, right-click on the shortcut you’re using to start TinyTERM. Select Properties from the menu.

In the shortcut properties, go to the Shortcut tab. The Target line will read something like this:

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

The -P52 option is the first three letters of the evaluation serial number. Change it to the first three letters of your serial number. For example:

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

OK the changes, and you should not see the error any more. But if it does come back, you may need to edit the registry.

TinyTERM won’t start. Instead, it gives the error, “Could not run CSL entry point: main.”

“CSL entry point: main” is another name for the TinyTERM program tt.exe. So the error only means TinyTERM can’t start. There are three probable causes for this:

1. The first is a corrupt .tpx file. Rename the .tpx file you’re using, then start TinyTERM. If you get a “file not found” error, click Yes and configure your connection again. The old file was corrupt.
2. Another program may have replaced DLL files TinyTERM uses. If the problem started right after installing other software, try uninstalling that software. If you have a “rollback” utility that can restore Windows to a previous configuration, that’s even better. Test TinyTERM to see if it works again after the uninstall or rollback.
3. If you still get the “CSL entry point” error after renaming the .tpx file, and no new software was installed, one of TinyTERM’s main files is corrupt. The only way to fix that is to uninstall TinyTERM. Delete the Century folder from Program Files after uninstalling, then reboot and reinstall.

CR 140, DLLs replaced

When installing TinyTERM from CD, you may get the message, “The specified path does not exist.” But the CD reads in My Computer without a problem.

This occasionally happens with some newer DVD-RW drives, particularly on laptop computers. To bypass the error, create an empty temporary directory on your hard drive. Copy the contents of the TinyTERM CD to that directory. Then boot the PC in safe mode. Run the hard drive copy of the install once the safe mode boot is complete.

Using the Linux emulation in TinyTERM 4.x, you may not get the correct line draw characters. Changing the font in TinyTERM and setting the Use non font-based line draw characters option in the Session Properties don’t help.

Newer Linux systems use UTF-8 or Unicode characters for their console, but many applications still don’t. To disable Unicode for the session, at a system prompt enter:

unicode_stop

To turn it back on, the command is:

unicode_start

To disable UTF-8 on an English-language system, the command is:

LANG=en_US;export LANG

Restoring UTF-8 uses thie command:

LANG=en_US.UTF-8;export LANG

TinyTERM 4.40 or higher also has a Unicode mode that may resolve the issue on some systems. Open the Session Properties and go to the Code Page tab. In the lower left, change the drop-down option from “Pass through” to “UTF-8.” OK and save the changes. That will work on most systems using UTF-8.