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.

In TinyTERM Plus 4.20, the cursor will sometimes disappear when using TN3270 emulation. There is no patch.

CR 301, fixed in TinyTERM Plus 4.21

Using TinyTERM 4.2, transparent printing will skip pages at random. This is due to a bug in SSH communications. To fix it, download this patch. Unzip it into a temporary directory. Three files will be extracted:

regall.bat
cencomssh.dll
cencom.dll

Rename the existing copies of the two DLL files in your TinyTERM install directory as backups. Next, copy in the new versions and the batch file. Once that’s done, run the batch file from the TinyTERM directory. This will register the files and should take care of the printing problem.

CR 244, fixed in TinyTERM Plus 4.21

TinyTERM and TERM for Windows include a vertical scrollbar through versions 3.3 and 7.2 respectively. This allowed the user to scroll backward through a session quickly.

The scrollbar was temporarily removed in TinyTERM 4.00-4.20. It was re-added in version 4.21 as part of the View menu.

CR 38

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.

TinyTERM allows you to choose between block and underline cursors. If you choose a solid or blinking block, it may still come up as an underline when you start TinyTERM. Opening Session Properties will show it as a block cursor, and when you click OK to close it, the cursor will change. This was fixed in TinyTERM 4.30.

CR 393

This is normal. Full-screen applications, also called screen-oriented applications, don’t actually scroll the screen at all. Instead, they use cursor control commands to move around a static screen. This means there’s nothing to scroll back to, as the screen hasn’t really advanced.

To test this, go to a command prompt in UNIX and run a few line-oriented commands such as echo or ls. You should be able to scroll back through all those. But if you use a screen-oriented application such as vi, that won’t scroll as you would expect.

When you copy text in the TinyTERM screen that includes line draw characters, they will paste into other applications as text instead. The underlying cause is the way line draw characters are displayed.

Virtually all terminal emulations use a separate display font for line draw characters. The host sends a signal, usually an escape sequence, that tells the terminal to switch to the alternate font. The host then sends the letters you see when you copy and paste, and the emulation does the display substitution.

TinyTERM version 4 uses an ActiveX control for display. When you copy out of that ActiveX control, you get the underlying data, which is not what’s displayed in the emulator window. But it is what gets pasted.

CR 222
CR 457

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.