You may want to print the TERM or TinyTERM screen without going to the menus. In that case, you can remap a key to perform this function.

In TERM for UNIX, the F6 key is mapped to print by default. To change this, use the SETKEY script command. For example, to map printing to Shift-F6 instead, the command is:

SETKEY SF6 PRINT

In TinyTERM for DOS the Alt-P key prints the screen by default. To change this, type Alt-S for the Setup menu, then select Keyboard. Change the Print Screen line to the desired key.

There is no default key mapped to print screen in TERM for DOS. To change that, type Alt-K to get the keyboard settings. Change the Print Screen line there to the desired key.

TERM and TinyTERM for Windows require more steps:

1. Open the keyboard editor.
2. Click the Chart Open button.
3. Click the F button in the upper right.
4. Click and drag the word PRINT from the chart to the key you want to use; i.e., F8.
5. Click the Chart Close button.
6. Click the Set button.
7. Click OK.
8. Click the “Save As” button to give the new keyboard scheme a name. You can use an existing scheme name to replace it if you desire. But if you replace the “Default” scheme, there’s no way to restore it to its previous settings.
9. Click on Apply and OK.

Using TinyTERM version 4.02, when you try to remap or edit a key using the keyboard mapper, you receive errors. After remapping a key, the new settings aren’t saved.

To resolve this problem, you will need to install the patch files found in this directory. Save them to a temporary directory on your PC. In the directory C:\Program Files\Century\TinyTERM, locate the files CenTE.ocx, tt.exe and TT.ini. Rename each file as a backup.

Copy the patch files into the same directory. The next time you start TinyTERM, the patches will be in effect. You won’t see the keyboard mapping errors any more.

This is normal behavior. To get TinyTERM 3.3 and earlier versions to erase when backspacing, go to the Configure menu and select Emulation. Check the “Backspace sends Delete” box there to cause backspace to erase characters.

When using TinyTERM 4.21, if the Caps Lock is on, the Alt key does not access the TinyTERM menus. For example, normally Alt-F opens the File menu. If Caps Lock is on, you have to type Alt-Shift-F to do the same thing. This is the only workaround.

If the “Use Alt keys in emulation” option is checked, this is not a problem. But with that option checked, the Alt keys won’t access the menus anyway. This is by design, because they are passed to the terminal instead.

CR 357, fixed in TinyTERM 4.30

When run inside a browser, some of TinyTERM’s function keys will not work. In particular, combining the Alt key with a function key will be intercepted and used by the browser first.

When this happens, configure TinyTERM to run standalone, instead of in the browser. To do that, on the administrator copy go to the Edit menu and select Preferences. In the Preferences dialog, click the OLE Settings tab. On that tab, click the Display as stand alone helper application radio button. Click OK, then save the session.

Upload the new .tpx file to your web server. When it’s clicked by a user, TinyTERM will open in a separate window, rather than in the browser.

CR 378

TinyTERM Web Server Client includes no user interface, no way for the user to customize the keyboard. Instead, you need to create any custom keyboard configuration on the administrator PC, the one used to create the .tpx files. This will make changes to the C:\Program Files\Century\TinyTERM\keyboard.dat file.

Once configured, the keyboard.dat file can be copied to your web server. Users can then download it to their own C:\Program Files\Century\TinyTERM directories, replacing the default file. That will make the custom keyboard mappings available to the .tpx files that need them.

All versions of TERM have the capability to record a user’s keystrokes and the host system’s responses. It’s accessed through the TERM Script Language command LEARN:

LEARN START filename
LEARN STOP

Replace filename with the name of the TSL command file you want to create.

In TERM for Windows, a “Learn mode” or “Macro recorder” option is also available from the Tools menu. It will request a file name in a Windows dialog, and otherwise functions the same way as the LEARN command.

Most versions of TinyTERM do not have such capability, as it requires a script language. However, TinyTERM versions 4.30 and above do have a macro recorder on the Tools menu. It behaves as the LEARN command in earlier versions, but creates a CScript file instead of TSL.

TERM and TinyTERM for Windows allow multiple sessions to be opened in a single window. You can switch through these sessions in order with the NEXTSESS keyboard function.

To access that function, open the keyboard mapper. Click the “Chart Open” button to bring up the key chart. On the right of the chart, click the “F” button for a list of functions. Using your mouse, drag the NEXTSESS function from the chart and drop it on the key you’ve chosen.

Click “Chart Close” to close the chart, then click OK to close the keyboard mapper. Click Save As to give the new keyboard scheme a name. OK everything and save the settings. From that point on, when you have the correct keyboard scheme chosen, you can cycle through the open sessions in a TinyTERM or TERM window by pressing the chosen key.

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’s keyboard mapper allows you to remap the NumLock key. Version 4 also has a Force Num Lock on setting that will keep NumLock on for the TinyTERM window.

Doing both of these on a Windows NT, 2000, XP, 2003 or Vista system causes a particular issue. When you hit the remapped NumLock key, it repeats the mapped action three times.

Those operating systems read both the key press and the key release as separate events. TinyTERM also reads the key press as an event. So what actually happens is that the mapped action is triggered once for each event.

If the NumLock key is not mapped in TinyTERM, there is no problem with the Numlock signal being processed more than once. But altering TinyTERM’s behavior for this would damage other keyboard mapping functions.

CR 231