Term/2 Readme File

Version 2.60 Built June 15, 1997

Maintenance release before the PM version.

What this program does:

This utility provides a "terminal server" capability for OS/2 machines.

What this program does not do:

The program cannot provide OS/2 support to a terminal. Some people do use the application to "telnet" into their OS/2 machines to simulate this ability. However, Term/2 is not optimized for this sort of work.

What do I need to make this program run?

Term/2 has three pre-requisits. You must be running OS/2. You must have a TCP/IP stack installed (PPP or SLIP is fine) and you must have a serial port available for Term/2 to use.

So what do you mean by "terminal server?"

Term/2 can let a async external terminal like a Dec Vt-100, VT-220 or ADM-3A access a telnet session from your OS/2 machine. Your terminal can then telnet to either the OS/2 machine its connected to or some other telnet server on your intranet or the internet.

Why would I use this?

Async terminals can be had for less than $20. This may provide very cost effective way's for people to have internet access. A school, church, government agency or even business can use this to provide a inexpensive entry point onto the internet.

Usage

Your going to have to setup your own communication parameters under this Beta. A mode statement entered at a OS/2 command prompt will do the trick. The one I use for the VT-320 is MODE com1:19200,n,8,1,dtr=on,octs=off,xon=on
Your particular setup may require different settings.
The term2 executible takes two parameters,
The com port is your available serial port. The terminal type is the terminal emulation you want the telnet client to negotiate on your part. For example, I leave mine at the default vt-100 setting because the vt-320 has at least that capability. To keep the default, leave off the last paramenter. If you type anything after the com port, Term/2 will send that string to the telnet server as terminal type information. There is NO type checking, so if you enter term2 com1 PURPLE-NEWT term2 will use that exact text sequence as its response to a terminal negotiation. There is a file named termtype that is directly from the RFC, outlining valid and recognized names for terminal types.

Trouble shooting.

Most of the problems are setting up the correct mode statement. The above statement worked for my setup, with my particular terminal. Your setup will almost guaranteed be different. One quick way to determine the right mode statement was to use a terminal program to try the various combinations until you find one that works. If you can exchange keystrokes your on the right track. If that's not workable, try "echo test>com?" and see if the word test shows up. Async setup is beyond the scope of this BETA release, its just like configuring a modem (but with pins 2 & 3 swapped).

Some implementation notes:

The Term/2 program is a telnet client that just runs through the serial port. It negotiates a telnet connection using the terminal emulation you list. If the server you wish to connect with doesn't offer your terminal type as a supported emulation, your going to have problems with that connection.

Features pending....

Feedback...

Feedback is definitely appreciated. The application is freeware, all I ask is that if you have problems to let me know.

Contacting the author or updating....

You may reach me at this email address.
tfry@universe.digex.net
Or you can update your version by checking the web page.
Term/2 support page