TinyTERM Enterprise for iOS can be installed via HTTP, among other methods. On iOS 7.1, this now requires that the manifest.plist file be served via HTTPS. Prior versions of iOS allowed this to be served via HTTP. More information is available at http://university.utest.com/question/ios-7-1-how-can-i-resolve-the-certificate-is-not-valid-error-when-performing-an-ota-install/.

TinyTERM for Linux is a 32-bit application. It requires 32-bit libraries for the Gnome and KDE desktop environments. These are not available on 64-bit Linux systems, so TinyTERM for Linux is not currently supported on those systems. Nor is it supported on any Linux system that does not include Gnome or KDE, such as Ubuntu 12.

However, TinyTERM can be made to run on some 64-bit Linux systems. It requires installing 32-bit libraries, which may be available. For example, the following shell script will allow TinyTERM to run on CentOS 6:

# Tell yum to install 32-bit packages in addition to 64-bit

grep -v multilib_policy /etc/yum.conf > /etc/yum.conf.TMP #if previously put in, remove it
mv -f /etc/yum.conf{.TMP,}

echo "multilib_policy=all" >> /etc/yum.conf

# Stuff needed by TinyTerm (itx)
# (add in 32-bit versions of these)

yum -y install glibc
yum -y install zlib
yum -y install libX11
yum -y install libXext
yum -y install libstdc++
yum -y install libXdmcp
yum -y install libSM
yum -y install libXrender
yum -y install libXfont
yum -y install fontconfig

Similar scripts should work for most other distros of Linux.

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

Ubuntu 11.04 introduced the Unity user interface, replacing the Gnome desktop required by TinyTERM ITX. Ubuntu also no longer includes a number of software packages required by TinyTERM ITX for install. This causes TinyTERM to report that its files were copied, but nothing is actually put into place.

Century Software is currently studying the changes to determine how much work will be needed for TinyTERM ITX to run under Unity.

CR 975

On some Windows 7 systems, TinyTERM version 4.65.4985 (August 2011 release) will fail to run. Instead, the following error comes up:

Error (4547) Method Redraw Called With Invalid Object Instance

This is due to User Access Control (UAC) settings interfering with the TinyTERM install process. It’s caused by a bug in the install routines. This was fixed in TinyTERM version 4.65.5012.

When running TinyTERM version 4.63 or higher, you may get an error message that reads, “This copy of TinyTERM is not licensed to run on Microsoft server operating systems.” It is most common on Windows Vista and later Windows versions.

This message indicates that the product is not licensed to run in a terminal server environment. TinyTERM uses concurrent licensing in Microsoft terminal server environments such as Windows 2008 Server.

If you believe you have received this message in error, please contact Century Software technical support at support@centurysoftware.com or 801-268-3088. Please have your activation key and your Windows version available. We will work with you to get this issue resolved.

When running TinyTERM version 4.63 or higher, you may see a “License Count Exceeded” error dialog. This happens when you open more windows than your product is licensed for. For example, a three-user TinyTERM Plus license will only allow three windows to open. The fourth will see this error.

This is by design. In terminal server environments such as Microsoft Windows 2008 Server, TinyTERM Plus is licensed concurrently. Only the licensed number of TinyTERM instances may be run at one time.

You may get this message in error on standalone PCs. If this is happening, and you believe it should not be, please contact technical support at support@centurysoftware.com or 801-268-3088. Please have your 25-character activation key available, and let us know which version of Windows you are using. We will resolve this issue for you.

When you enter a license into TinyTERM 4.60 or higher, it may accepts the activation key but not run. Instead, the next time TinyTERM starts, it will ask for the license again.

When this happens, the license doesn’t match the individual release installed. For example, TinyTERM 4.63 will appear to accept a TinyTERM 4.62 license, but can’t actually use it.

To fix this, install the correct version of TinyTERM for your license. To get that version, login to the Customer Portal. A list of your registered licenses will be displayed. Click the download button next to the license to get the matching TinyTERM install file.

CR 893

If TinyTERM 4.6 is installed it on a PC that had an older version of TinyTERM, adding the license may cause the program to close with no errors. This happens when the previous license file, CenLic32.dll, was not removed before installing the new version.

To fix the problem, uninstall TinyTERM, then delete the directory C:\Program Files\Century. Restart the PC, then reinstall TinyTERM 4.6. It will accept the license after that.

If TinyTERM Plus 4.60 or higher is installed on a Windows terminal server, every user has to license it to run it. This is due to the nature of licensing in TinyTERM 4.6, which uses a license certificate file license.crt, rather than a registry entry as in prior versions of TinyTERM.

When this happens, the license.crt file was written to the administrator’s My Documents folder. This is one of two locations where the file can be written, and is normal for domain systems.

As a local PC administrator, copy license.crt to C:\Program Files\Century\TinyTERM. Make sure all users have read access to the file. (On some systems, it’s also necessary to give all users write access.) That should resolve the issue.