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

To make a modem connection in TinyTERM 4.x, do the following:

1. From TinyTERM’s Edit menu, select Session Properties.
2. Under Connection type, select Modem.
3. From the Available Devices drop-down list, select the correct modem for this connection.
4. Next to Available Devices, click the Setup button. The Modem Setup dialog box appears.
5. Click the Configure button. The Modem Properties dialog box appears.
6. Set the Maximum Speed to match the speed the host modem supports.
7. Click OK to close the Modem Properties dialog.
8. Click OK to close the Modem Setup dialog.
9. In the Emulation drop-down list, select the terminal emulation required by your host.
10. In the Host name, IP address, or phone number box, enter the host’s phone number, including any dial-out prefix and area code.
11. Click OK to close the Session Properties dialog.
12. From TinyTERM’s File menu, select Save Session.
13. Click Connect to dial.

When you get the error “modem not responding,” there are several steps you can take:

1. Check to see that the modem is connected and turned on.
2. Check the modem initialization string in the modem setup:
   1. Make sure that the init string is correct for your modem. Check your modem documentation for details.
   2. If there is a “^M” at the first of that string, remove it.
   3. Make sure that there is a carriage return or line feed character at the end of that string: “^M” in DOS or Windows, or “\r” in UNIX.
3. Try using a slower baud rate.
4. Ensure the modem is functioning by using HyperTerminal in Windows, cu in UNIX, or by typing echo ath1>comx (where “x” is the COM port that the modem resides on) at the command prompt in DOS.

There is also one known issue with TERM for UNIX, documented here.

TinyTERM does not pass on modem error messages received via TAPI. This makes it difficult to determine what’s happening when a modem connection fails. For example:

1. Dial a known busy number. (It’s easiest to call the same line TinyTERM is using to dial.) You can hear the modem dial and get a busy signal, but TinyTERM displays no errors. It shows as disconnected the whole time, though a “busy” message should pop up.
2. Dial a line and don’t answer it. You’ll hear the modem dial and the line ringing. TinyTERM shows as disconnected until it hangs up. The expected “no answer” message doesn’t come up.

CR 757, fixed in TinyTERM 4.65

TinyTERM will not dial the Best Data 56USB-P modem on Windows XP. All other applications can successfully use the modem.

CR 745

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

TinyTERM’s current TAPI implementation dials and accepts calls. Century Software, Inc., has had a request that TinyTERM support the standard TAPI dialogs and settings, rather than the dialogs it currently uses.

CR 448

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

“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