Open TinyTERM’s Session Properties. On the Session tab, configure a modem connection. Click the Setup button next to the selected modem in Available Devices. Change the maximum speed. Whatever speed you select becomes the maximum available until you close and reopen TinyTERM.

This is purely a cosmetic issue. The dialog that allows the user to change the baud rate is actually a Windows dialog, even though the same thing does not happen through Control Panel. And actually, the baud rate set there doesn’t affect TinyTERM.

The reason is that Windows TAPI sets the baud rate when it initializes the modem. It resets the value in the dialog, then doesn’t use that dialog again. There is no real way to change the baud rate in TinyTERM. It’s not necessary, either, because TAPI should select the best available rate. If it fails to do so, try updating your modem drivers first. If that still does not help, you can manually dial the modem instead.

CR 174

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

TERM for HP-UX will not connect to tty ports on HP-UX 11. There are no problems with this on earlier versions of HP-UX.

CR 121

TinyTERM 3.3 has a (new) tab at the bottom of the emulator screen. Clicking that allows you to select and open a .tap file for a new connection.

TinyTERM 4.x does not have anything similar. You must use the Open button on the Ribbon Bar, or the Open Session option on the File menu to open a new .tpx file.

CR 106 (enhancement request)

TinyTERM cannot use pulse dialing to connect. It has to use tone dialing. For phone lines that require pulse instead of tone dialing, connect to the serial port and use the Hayes commands to connect. The specific command for pulse dialing is:

ATDP18012683088

Replace the telephone number as appropriate.

CR 105

When you go into Session Properties while connected via modem and click OK, you lose the connection even if you don’t make any changes. This is due to the way Windows TAPI handles modems. TAPI configures the modem dynamically. When you click OK in Session Properties, it wipes out those dynamic changes.

CR 84, fixed in TinyTERM 4.20

Over a telnet session, everything works fine. With SSH, opening a file in vi puts the first line halfway down the screen. Paging forward and back with ^B and ^F produce similar results.

This is not a TinyTERM error. Running vi with the -w24 command-line parameter fixes the problem.

CR 564

It is sometimes necessary to connect to a host via serial cable, then change the baud rate, word length or other connection information while connected. TinyTERM versions prior to 4.31 require you to disconnect before settings changes take effect. TinyTERM 4.31 and higher allow you to make the change on the fly.

CR 460

Set up an SSH connection on a Web server, then click the link from a PC using TinyTERM Web Server Client. The fingerprint dialog may or may not come up. That appears to be OS-dependent. Either way, it never completes the connection.

It does write the fingerprint to the registry, though. You can make the connection happen after a failure by editing the registry. In HKEY_CURRENT_USER\Software\Century Software\HostKeys, rename “last_key” to the hostname or IP address of the target system.

CR 450, fixed in TinyTERM Web Server Client 4.31

Open TinyTERM’s Session Properties and click on the Port Forwarding tab. It comes to the front, but no other changes happen. Click it again and you get the correct tab. This happens the first time you click Port Forwarding, regardless of which other tab you come from. After you do this, you can move around the tabs normally.

CR 446, fixed in TinyTERM Plus 4.30