On some systems, upgrading to Windows 10 Creators Update (version 1703) causes TinyTERM to come up to a blank screen, with no font display. It apparently connects and runs normally, but no text can be seen. This can affect applications other than TinyTERM as well.

When this happens, a registry change can fix this. You can download the registry edit file here. Or if you prefer to create the file yourself, create a text document with the .reg extension; e.g., FontFix.reg. Enter the following contents:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize]
	"DisableFontBootCache"=dword:00000001

Either way, save the file to the affected PC. Close all running Windows applications, then double-click the file to execute it and make the change.

Once the registry edit finishes, reboot the PC. This step is crucial; otherwise, the fix will not be permanent. After the reboot, font display in TinyTERM will return to normal.

In reverse text mode, non-font-based line draw characters are not drawn. This happens across the board in all TinyTERM product lines.

On Windows with the “Use non font-based line draw characters” option turned off, the characters draw correctly. That option is not available on other platforms.

CR 1049

Most versions of Windows ship with the Lucida Console font installed. TinyTERM also installs the same font into its own directory, as lucon.ttf. However, it also overwrites the existing Windows copy of the font with a shortcut to the TinyTERM copy.

Uninstalling TinyTERM removes the shortcut. It does not replace the font.

CR 1040

In TinyTERM ITX for Mac, the number 0 and the capital letter O look identical. They can be distinguished by context in most cases, but not by looking at them.

CR 1036

On a widescreen monitor, if TinyTERM is maximized to fill the screen, the letters will probably be spaced far enough apart to be distracting and hard to read. Widescreen monitors use a 16:9 or similar aspect ratio intended to be like a movie screen. The dedicated terminals TinyTERM emulates all used a 4:3 aspect ratio, similar to a standard television. That makes a widescreen monitor about 1/3 wider than an equivalent terminal, so the letters are spaced that much farther apart. There are two ways to compensate for this in TinyTERM.

The preferred method is to run TinyTERM in a window, rather than full screen. You can resize the window to use the full height of the screen, widening it until it looks correct to the user.

The alternate method is to change the number of columns TinyTERM displays. To do that, open the Session Properties. In the lower right of the Session tab, check the “Use custom emulation size” box. Change the number of columns to 132. Leave the number of lines as-is. This will cause TinyTERM to display the maximum number of letters it can support in each line. However, it will cause display oddities for text longer than the terminal standard of 80 characters.

Once you have either resized TinyTERM to match your preference or increased the number of columns, go to the File menu and select Save Session to save your settings. This will ensure that the spacing does not automatically reset.

Century Software, Inc., has had a request for an option to set the font size when transparent printing. Setting the Lines and Columns in Page Setup allows this in a roundabout way, but there is no way to set the font size directly.

CR 80

Changing the font used by TN3270 or TN5250 emulation can improve its readability. However, it doesn’t necessarily make the emulator look and feel like a standard terminal.

Century Software, Inc., has had a request to create a new font to change that. The font would be the default used by the TN3270 and TN5250 emulations, to make their displays look more like the IBM terminals they emulate.

CR 763

The xterm terminal emulator in PIXIL Thin Client comes up in bright green on a black background. There is no way to change that color at present.

CR 754

The TN3270 and TN5250 emulations only print in Courier New font, regardless of the font selected for screen display. This was changed in TinyTERM Plus 4.40, so that the display font would also be the font used for printing. To make this work, you must print to the Windows printer, with the Bypass Printer Drivers option not set.

CR 9

Instead of the ż character, TinyTERM has ź listed a second time. This is due to a bad entry in the “STD TERM TCS2” code page.

CR 837, fixed in TinyTERM 4.53