TERM has several of the function keys preset for certain actions, such as opening the menu or help. You can reset those by editing the .termsys file in UNIX, or the term.sys file in DOS. Search the file for lines that start with the word setkey; for example:

setkey f1 menu

Change the word after the function key name (in this example, menu) to reset:

setkey f1 reset

This will reset the keys to their default values the next time you start TERM.

Using TinyTERM 3.3, with the Shift key pressed, the Escape key does nothing. This is a known limitation in that version. It can also happen with Caps Lock on, depending on the keyboard.

Using TinyTERM or TERM for Windows, Alt keys are ignored in the emulator by default, even if you’ve remapped them. Under the keyboard configuration there is a check box labeled, “Use Alt keys in emulation.” That needs to be set; otherwise, Windows uses the Alt keys.

Note that in TinyTERM versions prior to 4.0, and by extension all versions of TERM for Windows, that Alt-F4 can be remapped, but Windows will still read it. This will of course close the emulator, no matter what mapping you may have set for it.

If you need to map a non-printable character such as Escape or Tab to a key, there are a couple of ways to do this. On Windows versions of TERM or TinyTERM, do one of the following:

• In the keyboard mapper, drag the desired key into the Clipboard in the bottom left. You can then drag it from that clipboard to any other key on the keyboard.
• Click on the key you want to remap. Change the Action drop-down to MACRO. In the Value, enter the ASCII value of the key between angle brackets <>. For example, Ctrl-T is ASCII value 20, so it would be entered as <20>.
  You can also enter the control character somewhat literally, again inside the angle brackets. In that case, you’d put the caret ^ in front of the appropriate letter. For example, Ctrl-T would be entered as <^T>.

For DOS or UNIX products, you would use the SETKEY command. You can put the character in quotes directly, preceded by a ^ character:

setkey F5 “^X”

For a complete list of ASCII values, see www.robelle.com.

The SETKEY command redefines a key on the keyboard. The key then sends a different character of string of characters when pressed. SETKEY can also be used to cause a key to run a TinyTERM script or call one of TinyTERM’s internal functions.

The syntax for SETKEY is:

setkey keyname value

The keyname may be any of the following:

• F1 – F12 (Function keys 1 – 12)
• AF1 – AF12 (Alt-Function keys: hold the Alt key and hit F1 – F12)
• SF1 – SF12 (Shift-Function keys)
• CF1 – CF12 (Ctrl-Function keys)
• CSF1 – CSF12 (Ctrl-Shift-Function keys)
• “a” – “z” (Lower-case letters a-z, must be in quotation marks)
• “A” – “Z” (Capital letters A-Z)
• “^a” – “^z” (Ctrl- keys a-z)
• AltA – AltZ (Alt keys a-z, Windows may override)
• “0” – “9” (Top row number keys)
• kp0 – kp9, kp+, … (keypad number and symbol keys, NumLock must be on)
• c-kp0 – c-kp9, … (Ctrl-keypad number and symbol keys)
• “#”, “$”, … (Any symbol)
• up, home, end, … (Named keys)
• c-up, c-right, … (Named Ctrl-keys)

Only the letter keys are case-sensitive. The other keys can be typed upper- or lower-case for the SETKEY command.

The value may be one of the following:

• A single character or string of characters in quotation marks. This may include:
  • a special string character
  • \x42 – a hex value preceded by \x
  • \072 – an octal value preceded by \
  • ^M – a control character
  • or any other valid TERM string sequence
• the name of a pre-defined TERM function key such as PRINT or BREAK
• “@@command” – A valid TERM Script Language command

Examples

• setkey f1 “MyLoginName”
  causes the F1 key to send MyLoginName down the comm line.
  
• setkey “b” “MyPassword”
  causes the lower-case b key to send MyPassword down the comm line.
• setkey kp* abort
  causes the keypad * key to send the standard abort, usually ^C.
• setkey pgup “@@cls”
  causes the PageUp key to run TERM’s cls (clear screen) command.
• setkey SF1 “@@do myfile”
  causes the Shift-F1 key to run the TERM script myfile.cmd.
• setkey F11 “@@do wtermus@w_file_quit
  causes the F11 key to run the w_file_quit procedure within the TERM script wtermus.cmd.

Using TinyTERM 3.3 with IBM3151 emulation, the numeric keypad may fail. When that happens, copy and paste the following to the end of your .tap file:

[keyboard]
country=United States
;name=ibm3151-13
;[IBM 3151-13]
<^C>=<ABORT>
<^E>=<^E>
<C-RIGHT>=<SCRRIGHT>
<C-LEFT>=<SCRLEFT>
<C-PGUP>=<SCRPGUP>
<C-PGDN>=<SCRPGDN>
<C-UP>=<SCRLINEUP>
<C-DOWN>=<SCRLINEDN>
<F1>=<ESC>a<^M>
<F2>=<ESC>b<^M>
<F3>=<ESC>c<^M>
<F4>=<ESC>d<^M>
<F5>=<ESC>e<^M>
<F6>=<ESC>f<^M>
<F7>=<ESC>g<^M>
<F8>=<ESC>h<^M>
<F9>=<ESC>i<^M>
<F10>=<ESC>j<^M>
<F11>=<ESC>k<^M>
<F12>=<ESC>l<^M>
<SF1>=<ESC>!a<^M>
<SF2>=<ESC>!b<^M>
<SF3>=<ESC>!c<^M>
<SF4>=<ESC>!d<^M>
<SF5>=<ESC>!e<^M>
<SF6>=<ESC>!f<^M>
<SF7>=<ESC>!g<^M>
<SF8>=<ESC>!h<^M>
<SF9>=<ESC>!i<^M>
<SF10>=<ESC>!j<^M>
<SF11>=<ESC>!k<^M>
<SF12>=<ESC>!l<^M>
<CSF1>=<ESC>”a<^M>
<CSF2>=<ESC>”b<^M>
<CSF3>=<ESC>”c<^M>
<CSF4>=<ESC>”d<^M>
<CSF5>=<ESC>”e<^M>
<CSF6>=<ESC>”f<^M>
<CSF7>=<ESC>”g<^M>
<CSF8>=<ESC>”h<^M>
<CSF9>=<ESC>”i<^M>
<CSF10>=<ESC>”j<^M>
<CSF11>=<ESC>”k<^M>
<CSF12>=<ESC>”l<^M>
<KP0>=0
<KP.>=.
<KP1>=1
<KP2>=2
<KP3>=3
<KP4>=4
<KP5>=5
<KP6>=6
<KP7>=7
<KP8>=8
<KP9>=9
<KP/>=/
<KP*>=*
<KP->=-
<KP+>=+
<KPENTER>=<^M>
<NUMLOCK>=<NUMLOCK>
<AF1>=<MENU>
<AF2>=<HELP>
<AF3>=<GOLD>
<AF4>=<SHELL>
<AF5>=<CAPTURE>
<AF6>=<PRINT>
<AF9>=<COMPOSE>
<AF10>=<NEXTSESS>
<ALTB>=<BREAK>
<ALTT>=<SCANMODE>

Using TinyTERM 3.3 and PCTERM emulation on Windows 3.1, some keys give extra characters, such as:

pressing a key gives ad
x gives xx
l gives l_

To fix this, change the primary code page to “STD 437 MS-DOS Latin US.”

If your display is correct, but the application doesn’t respond to the function keys, try a different terminal emulation. Function keys send escape or control sequences that are emulation-specific. If the sequence doesn’t match what the application expects, the function key will fail.

If no emulation seems to work, check with the application software publisher. Find out what the application expects to see from each function key. You can then program the function keys in TinyTERM’s keyboard mapper.

The VT220 and VT320 emulations have two different function key modes, 7-bit and 8-bit. TinyTERM version 4 defaults to 8-bit handling of the function keys. But many host applications will only accept 7-bit function keys.

The VT220-7 and VT320-7 emulations in TinyTERM are strictly 7-bit emulations. Function keys in those emulations send the sequences required by applications requesting 7-bit key sequences.

Complicating the matter, some host systems do not recognize VT220-7 or VT320-7 as valid terminal types. For those cases, set the telnet terminal type to “vt220” or “vt320” as appropriate.

Century Software, Inc., also provides a replacement keyboard.dat with 7-bit definitions for VT function keys. To use the file, download it to your C:\Program Files\Century\TinyTERM directory. In that same directory, locate the existing keyboard.dat and rename it as a backup. Then rename the downloaded file to keyboard.dat.

The next time you start TinyTERM, open the Session Properties and go to the Keyboard tab. In the “Keyboard schemes” drop-down a new scheme will be available: VT220. Select that, then OK and save the changes. The same scheme will work for both VT220 and VT320 emulations.

CR 40, arrow keys
CR 500

In TinyTERM version 4.05, the PASTE function under keyboard mapping does not work. To map a key to paste, do the following:

1. Open the keyboard editor.
2. Click on the key you want to use for paste.
3. Change the Action field to COMMAND.
4. In the Value field, enter:
   

   TEObj.Paste(0);

5. Click Set, then close the keyboard editor.
6. Click Save As to give the keyboard scheme a name.