TinyTERM 4 automatically adjusts its font size for the number of lines and columns required in the available space. The default TERM font is a bitmapped font, though, which means sometimes the letters don’t fit smoothly into their spaces. They appear to overlap or just display too close to each other. There are a few ways to improve this:

1. Change the size of the available window space. The easiest way to do this is to resize the TinyTERM window. But if the window is already maximized, there are still things you can do.
2. Turn the tool bars on or off. From TinyTERM’s View menu, you can turn on or off several items:
   • Ribbon Bar, the buttons across the top of the window
   • Status Bar, the line of indicators at the bottom of the window
   • Menu Bar, the standard Windows menu items at the top
   • Session Bar, the session buttons just above the Status Bar
   • Address Bar, which shows the connection address (this is automatically turned off when you turn off the Ribbon Bar)
   • Vertical Scrollbar, which is available on the right side in some versions of TinyTERM
3. Change the display font. To do this, open the Session Properties and go to the Fonts tab. Click on the Term font to highlight it, then click the Down button once to make it second in the list. TermCS1 will move to the top. It’s a TrueType font, so it scales much better to different window sizes.

TinyTERM 4.31 and higher also have improved font scaling, particularly in 132-column mode.

CR 276, 132-column scaling
CR 352, font cut off on right at TinyTERM start
CR 682, Ribbon Bar must be on

If you have multiple sessions open in a single TinyTERM window, you may see information from a hidden session “bleed” into the active session. There are two causes for this.

1. Your Windows video driver needs to be updated. Contact the video card or PC manufacturer for an updated video driver.
2. One of the background sessions updates the screen regularly. When this happens you can see the updates in any active session, not just the correct one. This was corrected in TinyTERM 4.10.

CR 71

The euro symbol € was added to the TERM font in TinyTERM 4.20. In earlier versions, you will need to use a different font to display that symbol.

To add a font to TinyTERM, open the Session Properties and go to the Fonts tab. Click the Add font button. Select the font you want to use, then click OK to add the font to TinyTERM’s list.

To make the font primary, click on it in the font list to highlight it. Then click the Up button repeatedly to move it to the top of the list. TinyTERM will then display text using that font first.

CR 148

You may want your UNIX application to change the TinyTERM window title. For example, you may want the title bar to show the application module when a user changes screens.

You can do this in TinyTERM 4.02 or higher by sending a CScript command from the UNIX application. The sequence:

<ESC>&oFSetPropNow(158,”Module”);AppRedraw();^M

will do what you need. Taken piece by piece, the string

<ESC>&oF

tells TinyTERM that what follows are CScript commands. <ESC> should be replaced with the Escape character, ASCII value 27.

^M

signals the end of the CScript commands. Similar to <ESC>, ^M should be replaced with the Ctrl-M character, ASCII value 13.

SetPropNow(158,”Module”);

sets the Windows title bar remark. “Module” can be replaced with any quoted string.

AppRedraw();

redraws the TinyTERM window. This forces the title bar to refresh.

Other CScript commands can be run from the host system in the same manner. For a full list of CScript commands, refer to the documentation included with TinyTERM.

CR 17

When printing from TinyTERM 4.02 or higher to a Windows printer, you may need to save the settings for lines and columns so it will print correctly. On some versions, every time you exit TinyTERM it loses those settings.

To save those settings, place the attached script into your .tpx file with these steps:

1. Copy this script to the C:\Program Files\Century\TinyTERM directory.
2. Open the Session Properties and go to the Session tab.
3. Click the “Post Session Start” radio button.
4. Click the Browse button
5. Locate and select the st.cs script
6. Click OK and close the Session Properties.
7. From TinyTERM’s File menu select Printer Setup.
8. Configure printing to the desired Windows printer.
9. Click the Setup button to get the Page Setup dialog.
10. Set the lines and columns.
11. OK all settings, then save the .tpx file and exit TinyTERM.
12. Restart TinyTERM.

It should have the lines and columns settings saved. You may need to set them one more time, now that the script is running.

Lines and Columns options were permanently added to the Page Setup dialog in TinyTERM 4.30. From that version on, the st.cs script is never necessary.

CR 400

The error might also reference dlgwsus.res, dlgplbr.res, or a similar file. It’s the name of a missing file. There are backup copies installed normally.

Go to the folder C:\Program Files\Century\TinyTERM and look for the files named “*.res”. You’ll see one or more of the following:

dlgplus.res
dlgtcus.res
dlgwsus.res
dlgwcus.res

Just copy the existing file and rename it to match the missing file. For example, if the error showed that dlgplus.res is missing, copy dlgwsus.res and rename the copy as dlgplus.res.

When you start TinyTERM right after install, the screen can be completely blank. This most often happens when an earlier version of TinyTERM was installed on the PC, but not completely uninstalled. The existing fonts interfere with the install of the new fonts, causing the display problem. Restarting the PC will fix it.

CR 312

This error happens when running TinyTERM 4.10 on Windows NT 4.0 or 2000. It’s not actually trying to update the registry, but it does check to see if it can.

You can resolve the error by downloading and applying this patch. It is a replacement for the existing tt.exe program.

To use the patch, save it into the C:\Program Files\Century\TinyTERM directory. In that same directory, locate the file tt.exe and rename it as a backup. Then rename this patch as “tt.exe”. The next time you start TinyTERM, it will be in effect.

WARNING: This patch only applies to TinyTERM version 4.10. If used with earlier versions of TinyTERM, or on operating systems newer than Windows NT 4.0 or 2000, TinyTERM licensing problems and system instability could result.

The patch is not needed for Windows 95, 98 or Me. The patch is incorporated into later versions of TinyTERM already.

When you start TinyTERM, if there’s something wrong in the connection settings, you’ll get an error message. If TinyTERM closes after you click OK on the message, it means TinyTERM is set to close automatically on disconnect. A connection error is handled like a disconnect.

To fix the problem, use Notepad to edit the .tpx file you’re using with TinyTERM. Search for the line:

closedisc=1

Change the 1 to a 0 (zero):

closedisc=0

Save the changes and exit Notepad. The next time you start TinyTERM, you’ll still get the connection error. However, TinyTERM won’t close, so you can fix the connection settings. You can then set the Close session on disconnect and exit option once you know the connection is working properly.

Century Software, Inc., has been asked to change this behavior, so that connection errors don’t trigger the “close on disconnect” behavior. This is problematic, as a Winsock error includes a disconnect event. So this enhancement has not yet been added.

CR 226

TinyTERM can open up to nine sessions in a single window. However, through the included CScript language you can limit TinyTERM 4.05 or higher to one session. The script available for download here does just that. Every time a new session is opened, it checks to see if it’s the first one. If not, it immediately closes the session.

To use the script, go to TinyTERM’s Tools menu and select Script Editor. Enter the above script commands. (The comment lines set off with // are not necessary.) Click the Save button and give the script a name, such as “onesess.cs”, then close the Script Editor.

Next, go to TinyTERM’s Edit menu and select Preferences. Next to the “Application startup script” line, click the Browse button. Select the onesess.cs script and click OK. Save all settings. The next time you start TinyTERM, the script will run automatically.

This script will not work if TinyTERM is opened inside a Web browser. The browser takes over some of the functions outfirst.cs needs to catch a disconnect or session close.

There is no equivalent script that will prevent TinyTERM from being opened multiple times.

CR 566, multiple TinyTERM instances