Once you connect TinyTERM via SSH, some system memory is tied up until you restart Windows. In TinyTERM Plus 4.31, this was reduced to about 15 kb that becomes unavailable, but the problem has not been eliminated.

CR 426

TinyTERM will not use Windows TAPI to dial through Spartacom MPTS modem pool software for Windows. Instead, it gives the error, “Error (4513) Subscript out of bound: 13.” Other Windows applications work properly.

The workaround is to dial the modem manually.

CR 408

This problem had TinyTERM 4.21 connecting to a UNIX system on a LAN. On the WAN was a proxy server used for Internet Explorer only. With that proxy server enabled, TinyTERM wouldn’t connect to the UNIX host, getting the TCP/IP 10050 “Network is down” error instead.

At the same time, ping and Windows telnet would both connect properly. So would TinyTERM 4.0. With the proxy server down, any version of TinyTERM would connect.

CR 395

Century Software, Inc., has had a request to add PKI capability to SSH. It has not been implemented thus far.

Public Key Infrastructure (PKI) is a system where digital certificates are used to increase the reliability and scalability of authentication. Using certificate authentication requires that certificates are first created with certification authority (CA) software. Full details are available from ssh.com.

CR 343

“TAPI error: Line not available to place a call” comes up whenever TinyTERM tries to dial using the modem included in a Compaq Presario 4660 running Windows 98. Other applications can use the modem normally. Updating the modem drivers does not help.

This appears to be a modem-specific incompatibility. The workaround is to dial the modem manually.

CR 320

Century Software, Inc., has received a request to implement RFC 2217 – Telnet Com Port Control Option in TinyTERM. That has not been implemented thus far.

CR 310

If you use TERM for SCO UNIX to transfer a file to a directory that does not exist, TERM drops the connection.

CR 280

This error has only been seen on the IBM Thinkpad T21 using an IBM 10/100 Ethernet Mini-PCI Adapter with 56k Modem (MiniPCI Combo), running on Windows 2000. Any attempt to use TAPI in TinyTERM gives, “Error (4555) Get property ‘IsConnected’ failed: Invalid object instance.”

No other TAPI-using application gives an error. Updating the modem drivers does not work. However, connecting directly to the COM port and dialing the modem manually works.

CR 273

On a system with Microsoft Word XP installed, configure TinyTERM for a modem connection. Once TinyTERM has dialed in, open a Word document. This takes several minutes to complete, or completes as soon as TinyTERM hangs up. It doesn’t matter if you double-click the file, or if you use Word’s File menu to open the document.
This does not happen with serial or network connections.

CR 250

On a UNIX system, disable getty on a modem port. Then run a TERM script that does an answer wait on the modem. The script should continue to execute when someone dials into that modem.

When you run this script in the background using the ampersand character:

term modemscript.cmd &

the script never answers the modem, even if the script works properly run without the & switch. The TERM process runs, but it does not answer the modem.

CR 224
CR 228, all background scripts fail on Sun