In TinyTERM 4.63, select rlogin as the connection type. Add a username to the Login tab, then connect. TinyTERM closes with no errors. The debug monitor shows a disconnect, then nothing.

This is due to a bug in TinyTERM’s communications file cencom.dll. A replacement file is available for download.

CR 892

If TinyTERM Plus 4.6 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 can read the file, and that should resolve the issue.

TinyTERM does support 28800 baud as a connection speed. You can set that with this script command:

te.baud = 28800;

But this option is not available in the user interface. Century Software has received a request to add it.

CR 887

Change the default background color in TinyTERM to anything other than the default blue. Then read the background color in CScript:

var test = te.GetBGColor(0);

test will always equal 0, regardless of the current background color.

CR 888

Set a background image in TinyTERM using CScript:

te.SetBackgroundImage("file.jpg",0);

The display does not change, though the command reports as running successfully.

CR 889

Century Software, Inc., has received a report in reference to Windows Vista Business Edition running in VMware, with an Agere OCM Serial Modem installed. Any attempt to configure a TAPI connection in that environment causes TinyTERM to crash with:

CSL Run Engine has encountered a problem and needs to close.

The same configuration works fine when using Windows XP in the same environment. Century Software has not been able to duplicate this error.

CR 881

Century Software, inc., has had a request to add GSSAPI support to TinyTERM Plus. This has not yet been implemented.

CR 880

There is no documentation available for the Century FTP graphical file transfer client. The Help menu only offers an about option.

CR 879

Open multiple sessions in a single TinyTERM window, at least three. Check the session number for each with this command:

te.displaynl(_str(IsSess(CSESS)));

They will be numbered in sequence left to right, starting with session 0.

Now close session 0, the one at the left. The remaining sessions will update their index numbers. The leftmost, which used to be 1, is now 0.

Click on the tab for session 0 to make it active. Then open another session. It opens as the leftmost session, pushing the active session’s tab to the right, but indexes to be the highest-numbered session. So the second session is 0, not 1.

Make that leftmost session active again, and open another session. It will open immediately to the right of the current session, leaving it at the far left. The new session will be the highest numbered. This makes the third tab session 0.

While this does not affect TinyTERM’s basic functionality, scripts that look for specific session numbers don’t find them in the correct place.

CR 878

When connecting via SSH to a new system, TinyTERM asks the user to approve the host’s fingerprint. This dialog cannot be bypassed.

When using TinyTERM’s ActiveX control CenTE.ocx programatically, this dialog does not come up. If the host’s fingerprint is not already registered with TinyTERM, the connection fails silently. The only workaround is to connect to the host using TinyTERM to register the fingerprint first.

Century Software, Inc., has had a customer request that this dialog have an option to bypass it programatically. This would remove the need for manual connections to register the fingerprint.

CR 876