This error means the serial port you’ve selected in TinyTERM isn’t usable on your PC. There are a few possible causes:

1. The serial port doesn’t exist. Older versions of TinyTERM offer ports COM1 through COM6, whether or not the ports are actually installed on the PC. Verify that the port number you’ve selected in TinyTERM has a matching physical port on the PC.
2. Another program is using the serial port you’ve chosen. This is common for software such as fax programs. The other program will monitor the COM port, even if it’s not currently in use. This prevents TinyTERM from connecting to it. Shut down or reconfigure any other software that uses serial ports to bypass this problem.
3. The serial port selected has a driver or hardware problem. Check with a trusted computer technician if this is the case.

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

To make an RS232 serial connection in TinyTERM 4.x, do the following:

1. From TinyTERM’s Edit menu, select Session Properties.
2. Under Connection type, click RS232 (Serial).
3. From the Available Devices drop-down list, select the COM port for this connection.
4. Next to Available Devices, click the Setup button. The RS232 Setup dialog box appears.
5. Set the baud rate, parity, word length, stop bits and flow control to match the port settings on the host.
6. Click OK to close the RS232 Setup dialog.
7. In the Emulation drop-down list, select the emulation required by your host.
8. Click OK to close the Session Properties dialog.
9. From TinyTERM’s File menu, select Save Session.
10. Click Connect. You may need to press the Enter key once or twice to get a login prompt.

TERM for UnixWare installes from the /termunix/u3 directory on the TinyTERM/TERM CD. As it installs, it asks which UNIX you are installing to. Choose INTERACTIVE.

In order for TERM to use a serial port, the port must be set up for bidirectional access. (More information on this is in the Setup and Configuration of the UnixWare manual.) The script below should work:

pmadm -r -p ttymon3 -s 01d
pmadm -a -p ttymon3 -s 01d -s login -fu -v `ttyadm -V` -m "`ttyadm -b -h -r0 -t 60 -d /dev/term/-1s -1 9600NP -s /usr/bin/shserv -m ldterm -p "tty01 login: "`"

Change the lockfile format within the TERM setup under communications to:

/var/spool/locks/LK.%m

You must now connect to /dev/ttyxxx, not /dev/term/ttyxxx.

TERM for Linux does not communicate through the Digi PortServer at all. It connects to the tty port generated, but there’s no response after that. The remote system doesn’t see anything you type in TERM, and TERM doesn’t echo anything back from the host.

CR 838

SCO OpenServer 6 addresses serial ports with /dev/term/XX numbering. TERM for SCO UNIX’s callin and callout routines require /dev/ttyNN format instead. While SCO OpenServer 6 also provides that format for serial ports, it’s not their preferred method.

CR 794

PIXIL Thin Client only connects over TCP/IP. Century Software, Inc., has had a request to allow the included xterm to connect via direct serial cable.

CR 744

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.

Several IBM RS/6000 models have two processors, a primary CPU and a service processor. When the system is powered down, but still plugged in, the service processor remains active. An IBM3151 terminal can be plugged into this processor via serial cable and used to manage the system.

TinyTERM plugged into the same port does not work until the RS/6000 is booted. At that point, TinyTERM works correctly.

CR 605

TERM for SCO UNIX cannot disable tty ports numbered higher than ttyA9. It can use the ports if they are already disabled, but it can’t disable them on its own.

CR 544