A Web essay by Tom Van Vleck gives us some perspective on
how serial computer terminals have been used and improved since
the 1960s.
For glimpses of how computer hobbyists of the early 1980's used
character-cell video terminals with the home computers of the day,
you can visit a library and look up these
articles ftom BYTE magazine.
Information on setting up a Unix or Linux system for use with terminals
or terminals emulations is
here, whereas, information on terminal emulations themselves is
here.
When you are trying to use any
dumb terminal
(or even a
smart terminal)
with a remote host, it is
helpful to remember that there are two sets of parameters in play:
settings within the local terminal that determine exactly how it
will behave
information that the remote host computer has about
what type of terminal it is talking to
The two sets of parameters interact: the host computer can
sometimes discover how the local terminal is set, and the computer will
likely adjust what control characters it sends according to its guess
of how the video terminal may behave.
To view the text parts of web pages using a character-cell terminal, you
can use the
Lynx web browser.
But, if you have some idea of using a character-cell terminal to connect
to a remote computer running Microsoft's Windows NT, you'd better
read this first, and then have a look at
this.
BitFontEdit: Soft font editor for Wyse and VT220 terminals (Lawyer)
JPIG: display JPEG images on the Linux text console
Supporting different kinds of terminals...
Unix and Linux systems typically supply a function library and a database
that permit applications programs to work with many different kinds of
character-cell terminals. The library is "curses" (or "ncurses") and
the database is either "terminfo" or "termcap".
O'Reilly & Associates published a book called
termcap & terminfo
by John Strang, Linda Mui, and Tim O'Reilly.
From the same publisher, another helpful book is
Programming with curses by John Strang, which describes the
UNIX library of functions for controlling a terminal's display screen from
a C program.
The original reference on curses is the BSD project documentation volume
Screen Updating and Cursor Movement Optimization (here in PDF).
Now, however, curses functions are part of the X/Open Unix Standard,
as documented
here.
Another book is UNIX Curses Explained by Berny Goodheart
(Prentice Hall, ISBN 0-13-931957-3),
which discusses programming both using the curses package and using
low-level
control codes
obtained directly from terminfo.
And there is Pradeep Padala's
NCURSES Programming HowTo.
A book on a related topic is
The Working Programmer's Guide to Serial Protocols by
Tim Kientzle. This volume discusses Kermit, Zmodem, and
other protocols, and provides sample code in C++. Although now
out of print, you may possibly be able to locate a copy. Select
this and that
to find out more. Some source code described in the book is available
here at the Dr. Dobbs site.
Another way to cope is to repair the terminal-database entry yourself.
Walter Zinz of Unix World wrote chronicles of how he
repaired the
termcap
and
terminfo
entries for his AT&T 7300 screen.
qterm is a program originated by <jmg@dxcoms.cern.ch>
(and now maintained in release 6.0 by <mcooper@usc.edu>) that
helps a Unix computer identify which type of remote terminal it is
talking to.
(You can retrieve an older qterm from the
archive here or from its
original location.)
Another Unix program for identifying the remote terminal type is
termset.
The Computer Journal had an "asynchronous serial data
communications" page for MS-DOS and embedded systems.
As of 2006, there is
an online archive of David Baldwin's article.