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.

TinyTERM versions 4.8.0 (February 2013) and higher are fully supported on Windows 8. However, TinyTERM must run in the Desktop interface. It is not enabled for the Metro interface at this writing.

TinyTERM does not currently run on Windows RT. The CPUs used for the RT platform do not support instruction sets required by TinyTERM for Windows.

CR 1086

When using TN3270 emulation in TinyTERM Plus over an RDP connection, the right Ctrl key – normally used as the Enter key – acts the same as the left Ctrl key. This works properly at the Windows server console.

CR 1046

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

Scripts that use TSL compatibility commands for dialog boxes, etc., generate this error in TinyTERM version 4.7.x. The same error comes up when running TSL scripts directly, allowing them to convert on the fly.

CR 1034

TinyTERM does not save Windows printer settings. It will write information to the .tpx file about the current printer settings, but that does not properly restore due to the binary hash table Windows uses for such things as margins, lines and columns.

CR 1021

TinyTERM for Windows currently includes the option to add a carriage return when copying data, for pasting into other applications that require CR/LF pairs at line ends. This does not cover all possible application behavior. Century Software, Inc., has had a request to add options that would include:

• Strip out only line feed (hex 0A) characters
• Strip out only carriage return (hex 0D) characters
• Leave existing line delimiters intact

CR 1003, fixed in TinyTERM 4.8.0

TinyTERM 4.7.0 will lose focus from the emulator window when switching between Windows applications. The focus often goes to the address bar, so that hitting Enter will open a second session with the same connection information. If the address bar is turned off under Options | Global Preferences, this does not happen. But the focus is still lost.

Prior versions of TinyTERM do not exhibit this behavior.

CR 991, fixed in TinyTERM 4.7.1

When pasting the character Ø into TinyTERM, it becomes O instead. It can be typed correctly from an appropriate keyboard, or with the Alt+0216 combination. Only pasting from another Windows application causes this. It happens independent of the font TinyTERM is using.

CR 986, fixed in TinyTERM 4.7.1

TinyTERM Plus includes a switch to enable extended attributes when using TN3270 emulation. However, most of the extended attributes are not displayed properly, even with that switch on. In particular color settings are not used.

CR 981, fixed in TinyTERM Plus 4.7.1