TinyTERM supports up to nine open sessions in a single browser window, the same as if it’s run standalone. However, open anywhere from four to six sessions in a single browser. Sooner or later, one of the sessions will not show up in the Session Bar at the bottom. Instead, if you click the browser’s Back button, then Forward again, the session will come up by itself. Using Back again will sometimes take you to the other open sessions, sometimes to a blank page.

Also, sometimes opening more than one session causes a .tpx file to bring up a blank page. If you click the link again, it opens properly.

CR 747

In TinyTERM go to the File menu and select Save As. In a standalone environment, it always defaults to TinyTERM’s install directory. Century Software, Inc., has received a request for an option to change that default directory.

CR 737

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

Century Software, Inc., has had a request to make TinyTERM run as a service in Windows, rather than as a standard application. This has not been implemented thus far.

CR 699

Open TinyTERM inside Internet Explorer. Execute a simple CScript, such as the following:

te.xmit(“?\r”);
te.wait(“H”,2);
te.xmit(“A\r”);

The cursor disappears. If you’re not running TinyTERM Web Server Client, you can open the Session Properties and click OK, and the cursor comes back. But the Session Properties aren’t available in TinyTERM Web Server Client.

CR 697

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

On Solaris 8, TERM gives the error, “Cannot open device” when connecting to a tty port. This works properly on earlier versions of Solaris. Changing the port permissions does not help, nor does starting TERM with the -i command-line parameter.

Configure a .tpx file to print to the Windows printer, with Bypass Printer Drivers checked. Open the .tpx file in Internet Explorer. Transparent print jobs come to the screen. A print job shows as spooling in Windows until the emulator is closed. Then the job disappears.

CR 634

With TERM for HP-UX, if you specify a .con file on the command line:

term connection.con

it does not successfully connect via modem. You get the error, “Modem not responding” instead. The modem responds normally if the .con file is not specified.

CR 633

Century Software, Inc., has had requests for a PDA-based terminal emulator. We do not publish one at this time, though it’s been reported that TinyTERM 4.30 and higher will run on a PocketPC, but the text is almost unreadably small.

Operating systems that have been requested at least once: PocketPC, Windows CE, PalmOS, Blackberry.

CR 631