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
Posted in Thin Client | Comments Off on Error 1808 Within Citrix Client
TERM for UNIX/Linux acts as a monochrome emulator only, even when the terminal type chosen can display colors.
CR 16, TERM for Linux
CR 223, TERM for UNIX
Posted in Attributes, TERM | Comments Off on TERM Does Not Display Colors
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
Posted in License, Thin Client | Comments Off on Load Balancing Thin Client Servers
Under certain circumstances, the Wyse50 emulation will ignore control sequences that switch it between 80 and 132 columns. This cannot be reliably duplicated, but it has been conclusively demonstrated. At this point it’s undetermined exactly what the trigger is that causes the switch to be ignored.
CR 158
Posted in Wyse | Comments Off on Wyse50 and 132 Columns
Java API
April 25th, 2007
Neither TinyTERM nor TERM provides an API for use with Java. It would make some automation more convenient, and so has been requested in the past, but this enhancement has not been added at this time.
CR 156
Posted in Scripting | Comments Off on Java API
There is no way to set a default directory for file transfers in TinyTERM. When you save a session, the last used send and receive directories are saved with it instead.
CR 151
Posted in File Transfer | Comments Off on Default File Transfer Directory
32-Bit ZMODEM
April 25th, 2007
TinyTERM 4.41 and higher have an option to use 32-bit ZMODEM for file transfer, in addition to the older 16-bit ZMODEM. This has not been added to TERM for UNIX yet.
CR 63, TinyTERM
CR 147, TERM for UNIX
Posted in ZMODEM | Comments Off on 32-Bit ZMODEM
This problem was first noticed on SCO OpenServer 5.0.6 with dual Pentium III processors. When installing TERM through an xterm window, an error message came up: “Memory fault – core dumped.” The workaround is to install TERM at the console instead of through an xterm.
CR 136
Posted in Install, UNIX | Comments Off on TERM Install Fails Through xterm Window
The Use non font-based line draw characters option on the Attributes tab of Session Properties creates lines in bold white only. There is no way to change this.
CR 134
Posted in Attributes | Comments Off on Non Font-Based Lines Always White
When using modem pool software, the individual modem used by TinyTERM is not reset after disconnecting. This leaves the modem showing as “in use” to other applications until it times out.
CR 132
Posted in Modem | Comments Off on Modem Pool Doesn’t Reset Modem on Disconnect
|