Using TERM or TinyTERM over a serial connection, with the emulation set to ANSI, the display is OK, but the arrow keys don’t work. With the emulation set to VT100, the arrow keys work, but instead of lines, it displays the letter d repeatedly.

To solve both the arrow key and line draw problems, check to see if the UNIX tty port is set to a word length of 7. If it is, set the port for a word lengthy of 8, 1 stop bit and no parity. The host application is sending 8-bit sequences for the line draw characters. With these changes, VT100 emulation will work.

Using TinyTERM on Windows 95 on a Packard Bell PC, it won’t disconnect or let go of the phone line. Instead it gives an error that fmedia and faxworks are active.When this happens, edit the file win.ini. Locate the run= line and delete everything after the equals sign. Reboot the PC to finish the fix.

Running TinyTERM on Windows 3.1, you may get a bind error 10049 when telnetting to a host. This usually happens when you have more than one TCP stack, such as Novell Client 32, running at the same time. In this case, do not use the TCP/IP stack that Century provides. Use the one installed before TinyTERM instead.

The TN5250 emulation available in TERM Professional and TinyTERM Plus will not work through an IBM 5250 card. The 5250 card has its own software and cabling. TinyTERM Plus and TERM Professional use TCP/IP.

Telnet is the only option available to both. TinyTERM Plus version 4.5 also has SSL/TLS capabilities.

Using TinyTERM 3.3 on Windows 3.1 with a serial connection, if you put TinyTERM in the Startup program group, you’ll get an error:

Error (4514) Bad argument to function vsetoption: expected vector, got integer

This will happen any time you use anything on the File menu. You also won’t be able to exit Windows unless you use Ctrl-Alt-Delete.

To fix this, change the icon properties to remove us.tap from the command line. Switch to default.tap instead.

Using TERM for UNIX, you may see a locked device error when connecting to a tty port. The port permissions are usually reset to 600 (-rw——-) when this happens, even if you’ve changed it to 666 (-rw-rw-rw-).

The following is a sample script. It will not execute on all UNIX systems. You will need to adjust it for your particular flavor of UNIX. It will resolve the inability of callin and callout being unable to enable and disable ports that use port monitors.

1. Place the script in /usr/bin.
2. Do a chmod 777 to make it executable and accessible to all users.

The script is very simple. It disables the port, makes it accessible to TERM, starts TERM, then re-enables the port after TERM exits.

/usr/sbin/pmadm -d -pttymon0 -s00
sleep5
chmod 0666/dev/term/00
term
/usr/sbin/pmadm -e -pttymon0 -s00


Please note: This script is from Unisys U6000 SVR4 UNIX. Other flavors of UNIX will have commands that do the same thing, but the syntax will be different.

CR 572

Using TERM for UNIX 6.2.5 on SCO Openserver 5, trying to run a script which dials the modem to make the connection may cause the modem to repeatedly redial the modem before doing the initialization string. To resolve this, increase the DTIMEOUT value, or insert a DINIT command with the correct initialization string prior to the CALL command.

Using TinyTERM Plus Edition 4.04, how do you connect through a telnet firewall to an IBM host with TN5250 or TN3270 terminal emulation?

Configure a sessions using the TTY terminal type and a telnet connection to connect to the firewall as follows:

• Connection host: firewall name or IP address
• Connection Type: telnet
• Terminal Emulation: TTY
• Telnet Terminal Type: (depends on IBM emulation required)
  • 3270
    • IBM-3278-2
    • IBM-3278-3
    • IBM-3278-4
    • IBM-3278-5
  • 5250
    • IBM-3179-2
    • IBM3477-FC
• Save the session.
• Telnet to the firewall using this configuration. When the firewall prompts for the host, enter the hostname or IP address of the destination host.
• Depending on your firewall, you may have to hit the Enter key once to display the initial host screen.

NOTE 1: TinyTERM senses telnet binary mode to know when to switch emulations from TTY to one of the IBM emulations. The IBM terminal emulation desired is specified by the Telnet Terminal Type configuration.

NOTE 2: To preserve the initial firewall connection configuration do not save the session after the IBM host connection is made. TinyTERM changes your session properties when the IBM connection is made.

After installing third-party software that uses TCP/IP, TinyTERM may fail to connect on Windows 95. This happens when the new software replaces Winsock2 with an older version. This is not an issue on newer versions of Windows.

To fix this, reinstall Winsock2 on Windows 95. You can download the install here.

Starting TinyTERM Plus Edition 4.03 on Windows 98 or NT , you may receive the error “Get Capture Failed,” followed by DLL errors. This usually indicates you do not have TCP/IP installed. To correct the problem, you will need to do the following:

1. Add TCP/IP to Windows.
2. Reboot your PC.
3. Uninstall TinyTERM, then reboot.
4. Reinstall TinyTERM. When the install completes, reboot your PC, whether or not you are prompted to do so.