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.

UNIX and Linux applications that print forms generally control the printer through PCL or another set of printer control codes. Print spooling applications, such as the default Windows printer driver, can interpret these codes as print data instead, causing formatting problems. This can in terminal emulators when using transparent printing.

The solution is to print directly to the printer. In TERM for UNIX, specify the installed printer, rather than any third-party print spooling application. In TinyTERM or TERM for Windows, either print direct to the device or use the Bypass Printer Drivers option where available. This will prevent print spoolers from altering the printer control codes.

TinyTERM Plus 4.30 does not always bypass the drivers. In particular, printing to a printer on LPT1: on Windows XP caused printer control codes to print to the page when Bypass Printer Drivers was set.

CR 4, to Windows printer
CR 28, to file
CR 541, TinyTERM Plus 4.30

The “print on” code for Wyse50 emulation is ^X. That’s the same code used to end a file transfer in the ZMODEM and WTERMCRC protocols.

To avoid problems, use a different file transfer protocol with Wyse50. Or use a different emulation with ZMODEM and WTERMCRC. Either solution will work.

If your PC has more than one LPT (parallel) port, you can select any of them in TinyTERM. However, TinyTERM version 4.10 will not recognize the change until you save the session, then exit and restart TinyTERM.

There is no patch to fix this behavior. The only solution is to use a newer version of TinyTERM.

On Windows 95, 98 or Me, the currently active window can lose focus when the LPD server receives a print request. The server has to have focus briefly to initiate the print job, especially if it’s the first LPD request received since Windows was started, but it doesn’t always return focus properly.

When this happens, create a new icon in the Startup group of your Start menu. Link the to C:\Program Files\Century\TinyTERM\NetUtils\marlpd32.exe. Change the directory as appropriate, but make sure marlpd32.exe is loaded from your Startup group. That’s the application taking focus, so if it’s started with Windows, you shouldn’t see your main window lose focus again.

The LPD Server in Century Internet Services will sometimes hang when you add a printer. There is no patch for this. But you can just kill the process from Task Manager. The printer will still be added.

Century Internet Services includes an LPD (line printer daemon) server. However, it only runs on Windows 3.1 or higher. In TinyTERM 4.x, it only runs on Windows 95, 98 and Me.

To put a Century LPD Server on Windows NT 4, 2000, XP or Vista, you will need TinyTERM Plus 4.30 or higher. No prior release includes an LPD server.

CR 293

If you need to print to a Windows network printer from TinyTERM, but for whatever reason can’t select the printer, you can print directly to the device instead. Configure TinyTERM to print “Direct to device” or select DEVICE from the drop-down list. For the file or device name, enter:

\server\printer

Replace “server” with the name of the Windows print server. Replace “printer” with the share name for the desired printer. You may need to contact your system administrator to get those names. Most Windows network printers will accept this configuration.

For printers that will not, you may be able to capture the printer to an LPT port. Instructions for this are on Microsoft’s website. By operating system, the links are:

• Windows 95, 98 and Me
• Windows NT and 2000
• Windows XP, 2003 and Vista