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

TinyTERM Web Server Client version 4.20 will generate “Could not run CSL entry point: main” when run on Windows XP. It works properly on earlier versions of Windows. The only solution is to switch to a different version of TinyTERM Web Server Client.

CR 286, fixed in TinyTERM Web Server Client 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

When printing via LPR and LPD, this error means that no LPD printer was found on the system receiving the print job. To fix the error, you’ll need to do one or more of these things:

• Start the Line Printer Daemon on the print server. Without the LPD daemon, of course, it can’t receive print jobs.
• Verify that the client has the correct hostname or IP address for the print server, and the correct name for the printer on the server.
• Add each system to the other system’s hosts file.
• If you are using SCO UNIX as the client, the print server must also be listed in /etc/hosts.equiv.

Once these items are verified, LPD printing should work properly.

If you have more than five or six printers installed in Windows, TinyTERM may not list them all in its Printer Setup dialog box. Some may also be listed twice, especially if the printer name is longer than the line for the printer list. This can cause lost print jobs.

This is a bug in TinyTERM. It can list more than six printers, but it will lose some at random from the list. It will also truncate printer names so they fit in the printer list line. These issues were fixed in TinyTERM 4.33.

CR 530, missing printers
CR 592, truncated printer names
CR 651, network printers disappear, fixed in TinyTERM 4.41

This error comes up sometimes when trying to print the TinyTERM 4.20 screen to a Windows printer. It only happens on Windows NT, 2000 or XP, and only in that version of TinyTERM.

The workaround is to use the Bypass printer driver option in TinyTERM’s Printer Setup. It’s also fixed in TinyTERM 4.21.

CR 252

Occasionally you’ll add a new printer in Windows, but after restarting TinyTERM, you won’t see it in the list of available printers. To use it anyway, open TinyTERM’s Printer Setup dialog. Click the Setup button next to the Windows printer. In the Page Setup dialog, click the Printer button.

Choose the printer from the drop-down list there. Click OK from there until you’re back at TinyTERM’s Printer Setup dialog.

If the printer is still not visible after this, exit TinyTERM. Edit the .tpx file with Notepad or another text editor. Search it for the line:

prnwnlst=

Delete everything on that line after the equal sign. Save the changes and start TinyTERM. The printer should be available at that point.

This error happens on some Windows systems running TinyTERM version 4.30 or higher. It stems from the CenLPDStatus.exe item added to the Startup group.

That program is the interface to the CenLPD service, which provides an LPD daemon for Windows NT 4.0, 2000, XP and Vista. If the service is unavailable, then CenLPDStatus.exe gives the above error to show that it can’t access CenLPD. Some of the things that might cause this error are:

• Insufficient user privileges. If the user does not have local PC administrator rights, then CenLPDStatus.exe is automatically locked out of the services.
• CenLPD has not finished starting. This is a timing error, with the interface loading before the service is ready.
• CenLPD is disabled or has been removed. In that case, of course, there’s no service to connect to.

You can safely ignore the message. If you’re not using LPD at all, you can delete CenLPDStatus.exe from your Startup group to get rid of the message. You’ll also want to go through Control Panel’s Services applet to stop the CenLPD service in that case, to conserve system resources.

CR 545, timing improved in TinyTERM Plus 4.40