Century Software, Inc., has had several reports that the TinyTERM cursor does not blink when used over a thin client connection. When used at the terminal server console, the cursor does blink. We have not been able to duplicate this issue in-house.

CR 853

After TinyTERM Plus is installed, users with no administrator privilege can only use existing .tpx connection profiles. They can’t create new .tpx files or update the existing ones. This is because .tpx files are saved in C:\Program Files\Century\TinyTERM, and after installation, non-administrator users have read-only permission for that folder.

Century Software, Inc., has received a request to change that folder’s default permission to “Modify” for normal users during installation. After installation, this would allow all users to create their own connection profiles in that directory.

By design, TinyTERM Thin Client or TinyTERM Plus in a terminal server environment creates a TTweb folder for each user, in that individual user’s profile. Users should save custom configuration files to that folder, rather than to the TinyTERM install folder.

CR 722

When using TinyTERM Thin Client or TinyTERM Plus in a Windows terminal server environment, the local client printers are automatically recognized by the terminal server. They can be used by any Windows application installed on the server.

TinyTERM Plus and TinyTERM Thin Client can use these RDP printers as standard Windows printers; however, they can’t be saved. Every time you start TinyTERM, you must select the RDP printer again.

CR 671

Install TinyTERM Thin Client to Windows 2003 Server with Citrix Metaframe XP. It works properly at the 2003 console or on a remote desktop.

Century Software has had a report that if TinyTERM is published to run in an independent window, it comes up completely. There is no text, no menus, no title bar — no display at all. This has not been duplicated

CR 628

When run in a terminal server environment, TinyTERM Thin Client (or TinyTERM Plus 4.40 or higher) creates a TTWeb directory in each user’s default directory path. If the user profile isn’t stored in Windows’ default install location, but on a different drive or UNC path, the attempt to create TTWeb fails with a “can’t create” message. You can click OK on that and continue in TinyTERM, but it will keep popping up.

CR 430

Configure TinyTERM Thin Client on Windows 2000 with Citrix Metaframe XP as a published application. Also configure it to establish connection on open. Occasionally TinyTERM will not accept keyboard input at the login prompt. Clicking Disconnect, then Connect fixes the problem. The problem can also be duplicated by disconnecting and reconnecting repeatedly.

CR 299

When you use the file tttc.exe from the zipse directory on the TinyTERM 4.20 CD, it does start to run. Shortly after that you get the message, “Setup has detected some old dll files on your system. You must restart to continue installation.” After rebooting you get a “missing shortcut” error. The install never starts back up. If you manually restart the install, it does the same thing.

CR 197, fixed in TinyTERM Thin Client 4.21

Connect to a Citrix terminal server using a Citrix client. If any application from Microsoft Office 2000 is open — for example, Outlook, Excel, or Word — TinyTERM will not open. Instead, it gives the error, “Could not run CSL entry point: main”. This was originally observed on Citrix MetaFrame 1.8 with Service Pack 2.

The error only occurs if one of the Office applications is running on the Citrix server. It does not happen if the Office application is running on the client PC.

CR 166

TinyTERM Thin Client and TinyTERM Plus (thin client install, version 4.40 or higher) are licensed for install on a single terminal server. They are not licensed to be installed on multiple nodes in a load-balancing environment.

If you have terminal servers set up in such an environment, each server must have its own TinyTERM license. To balance the load, you’ll need to purchase a fraction of the licenses you need for each. For example, if you need 30 users spread over three servers, you must have three ten-user TinyTERM Thin Client or TinyTERM Plus licenses. One is then installed on each server.

CR 161

Install TinyTERM Thin Client on a Citrix server. Connect to the server from a Windows 3.11 PC. If TinyTERM is configured to print direct to device LPT1: without the Flush Output option checked, the print job does not print until TinyTERM is closed. With the Flush Output option checked, the print job prints slowly and the emulation screen does not return control until the entire print job is finished.

This is not a TinyTERM issue. It was resolved by removing the printers, then reconnecting to Citrix. That re-adds the printers, fixing the printing problem.

CR 73