- For a quick attempt to install a terminal see [ For a quick attempt to install a text-terminal see ][.
] Copyright, Trademarks, Disclaimer, & Credits
@@ -196,13 +209,15 @@ as a console for a monitorless PC (using ttysnoop). Numerous other
people have made a suggestion or two or found a few typos. Thanks.
Future Plans: You Can Help
-Real text terminals are pretty
-much obsolete except for legacy applications, but GUI terminals
-(variously known as thin clients, ultra-thin clients, and
-zero-clients) are claimed to be the wave of the future. What is
-needed today is for someone to start with the brief overview of GUI
-terminals in this HOWTO and create a new and up-to-date HOWTO on thin
-clients.
+
The author is looking for someone to take over maintaining this
+howto. Since real text terminals are pretty much obsolete, there is not
+a lot of work to do except that links sometimes disappear and
+automatically finding devices such a dumb terminals on a serial port may
+not work right. One project is to rewrite this howto oriented towards
+text-terminal emulation with the command line interface. Another
+project would be to start with the brief overview of GUI terminals in
+this HOWTO and create a new and up-to-date HOWTO on thin clients or the
+like.
Please let me know of any errors in facts, opinions, logic,
spelling, grammar, clarity, links, etc. But first, if the date is
@@ -212,8 +227,10 @@ Please send me any info that you think belongs in this document.
In order to fully utilize all the features of a certain real terminal,
one needs the terminal manuals that came with the terminal when it was
new. If you don't have a manual, this HOWTO may be of some help. One
-way to have solved this problem would be for terminal manufacturers put
-their manuals on the Internet but they never did.
+way to have solved this problem would be for terminal manufacturers to
+put their manuals on the Internet but they never did. Except that Wyse
+made available some of their user manuals and someone scanned old VT-100
+manuals.
New Versions of this HOWTO
New versions of the Text-Terminal-HOWTO should be released every
@@ -222,38 +239,27 @@ couple of years. To get the latest version go to an LDP mirror sites (see:
of the latest version look at . The version your are currently
-reading is: v1.42 January 2010 .
+reading is: v1.43 March 2013 .
For a full revision history going back to the first version in
1998 see the source file (in linuxdoc format):
+- v1.43 Mar. 2013 Putty's pterm emulation. Cleanup. Shuford's website
+ now defunct. Looking for a new maintainer. Wyse data missing from
+ Internet. Rewrote abstract. Clarity in stty raw problem. Links to Wikipedia.
- v1.42 Jan. 2010 PuTTY serial terminal emulator, cutecom (dumb
emulator), colors, links to wikipedia, Boundless still selling
terminals, small footprint terminals, link to art. on text browsers.
-
- v1.41 Feb. 2008" Better clarity re emulation. Illusion when
- revere-video is reversed. Problem with slow scrolling. Wyse text
- terminals discontinued and Boundless was bankrupt. Update on text web
- browsers. gtkterm, X Window now has many terminal emulators.
- Symantec no longer selling Procomm.
-
- v1.40 Dec. 2006 Picocom is like minicom. Devfs obsolete so removed
- tts/1, etc. Updated pseudo terminals. More about telnet, ssh, and
- non-serial port interfaces. IBM terminal emulation over telnet.
- Kermit for MS does terminal emulation. Ports of minicom to Mac.
- Fixed/removed broken links. "reset" is an alias for "tset"
- Related HOWTOs, etc.
+ Related HOWTOs
Go to the nearest mirror site (per above) to get HOWTOs.
- Serial-HOWTO has info on Multiport Serial Cards used for both
terminals and banks of modems. It has general technical info on the
serial port including troubleshooting it.
-
-
part of "GNU C Library Reference
-Manual" (in libc (or glibc) docs package). It covers the detailed
-meaning of "stty" commands, etc.
- NCURSES-Programming-HOWTO
- MacTerminal mini-HOWTO
- Modem-HOWTO
@@ -333,7 +339,7 @@ x-terminal-emulator because the simple character images that get
displayed on the text-terminal are stored right inside the terminal in
it's memory. For a monitor or x-terminal-emulator, the images are
stored in the video card of the PC and/or in the PC's memory itself.
-The text-terminal's keyboard plugs into the the terminal and is part
+The text-terminal's keyboard plugs into the terminal and is part
of the terminal while a PC's keyboard plugs into the computer.
For a monitor, the video images are sent by a short cable running from
@@ -1667,11 +1673,12 @@ may be programmed to send out a sequence of bytes (characters). See
Mouse
A few text-terminals support a mouse. When the mouse is clicked,
an escape sequence is sent to the host to tell it where the mouse is.
-For a mouse on VT terminals see These
-escape codes for mice are called "DEC Locator sequences". The FALCO
-Infinity Series of terminals, model ANSI-G supports it. Do any linux
-applications support this ??
+An article for a mouse on VT terminals was once at
+http://www.cs.utk.edu/~shuford/terminal/dec_vt_mouse.html but it's now a
+dead link (2013). Try the "Wayback" machine." These escape codes for
+mice are called "DEC Locator sequences". The FALCO Infinity Series of
+terminals, model ANSI-G supports it. Did any linux applications support
+this ??
Terminal Emulation (including the Console)
@@ -1716,13 +1723,13 @@ PC a terminal"> This can be used to connect a Windows PC (as a
Text-Terminal) to a Linux PC.
Most Linux free software can only emulate a VT100, VT102, or
-VT100/ANSI, xterm, or Wyse60 (but not fully). Since most PC's have color
-monitors while VT100 and VT102 were designed for a monochrome monitor,
-the emulation usually adds color capabilities (including a choice of
-colors). Sometimes the emulation is not 100% perfect but this usually
-causes few problems. None of them provide programmable function keys.
-The non-free emulation software running under MS Windows can emulate
-many more terminals than free Linux can.
+VT100/ANSI, xterm, pterm, or Wyse60 (but not fully). Since most PC's
+have color monitors while VT100 and VT102 were designed for a
+monochrome monitor, the emulation usually adds color capabilities
+(including a choice of colors). Sometimes the emulation is not 100%
+perfect but this usually causes few problems. None of them provide
+programmable function keys. The non-free emulation software running
+under MS Windows can emulate many more terminals than free Linux can.
Don't Try to Use TERM Variable for Emulation
@@ -1731,40 +1738,43 @@ at a Linux console (monitor) by setting the environment variable TERM
to the type of terminal they would like to emulate. This does not
work. The value of TERM only tells an application program what
terminal you are using. This way it doesn't need to interactively ask
-you this question. If you're at a Linux PC monitor (command line
-interface) it's a terminal of type "Linux" and since you can't change this
-TERM must be set to "Linux". This should happen without you needing to
-do anything.
+you this question (and it's too dumb to be able to probe the terminal to
+find out what type it is). If you're at a Linux PC monitor (command
+line interface) it's a terminal of type "Linux", and since you can't
+change this, TERM must be set to "Linux". But this "Linux" should be
+set automatically, without you needing to do anything.
-If you set it to something else you are fibbing to an application
+If you set it to something else, you are fibbing to an application
program. As a result, it will incorrectly interpret certain escape
sequences from the console resulting in a corrupted interface. Since
the Linux console behaves almost like a vt100 terminal, it could still
work almost OK if you falsely claimed it was a vt100 (or some other
terminal which is close to a vt100). In this case it may seeming work
-OK most of the time but once in a while will make a mistake.
+OK most of the time but once in a while will give errors.
- Serial Communication programs (mostly dialing) while the
-newer free PuTTY program can connect directly to a serial line but
-can't dial, most of of the older programs did dialing out via a serial
-port modem. Some dialing programs are for making a PPP connection to
-the Internet via a modem, such as wvdial, and don't normally include
-any terminal emulation. But some other programs (such as minicom or
-seyon) do both terminal emulation and modem dialing (without PPP so
-it's not easy to use them to connect to the internet). But since
-these programs connect to a modem via a specified serial port
-(including "internal" serial ports that have no connector on the back
-of the PC), they may be used to connect to a serial line via a
-possible serial port connector on the back of a PC. For this case you
-just set them up to connect without dialing a phone number. The
-program "picocom" just does terminal emulation although it's possible
-to type in a modem command and a phone number to dial out manually.
-These programs are also useful for testing modems. Seyon is only for
-use with X Window and can emulate Tektronix 4014 terminals. In the
-past one could use dialing programs to dial up some public libraries
-to use their catalogs and indexes, or even read magazine articles on
-line before the Internet was widely available. But today such
-activity is almost always done using the Internet.
+ Serial Communication programs
+while the newer free PuTTY and Terra-Term programs can connect
+directly to a serial line but can't dial out, most of of the older
+programs did dialing out via a serial port modem. Some dialing
+programs are for making a PPP connection to the Internet via a modem,
+such as wvdial, and don't normally include any terminal emulation.
+But some other programs (such as minicom or seyon) do both terminal
+emulation and modem dialing (without PPP so it's not easy to use them
+to connect to the internet). But since these programs connect to a
+modem via a specified serial port (including "internal" serial ports
+that have no connector on the back of the PC), they may be used to
+connect to a serial line via a possible serial port connector on the
+back of a PC. For this case you just set them up to connect without
+dialing a phone number. The program "picocom" just does terminal
+emulation although it's possible to type in a modem command and a
+phone number to dial out manually. These programs are also useful for
+testing modems. Seyon is only for use with X Window and can emulate
+Tektronix 4014 terminals. In the past (before the Internet was
+widespread) one could use dialing programs to dial up some public
+libraries to use their catalogs and indexes, or even read magazine
+articles on line. But today such activity is almost always done using
+the Internet where there is a much larger choice of connections and no
+long-distance telephone bills.
The communication program C-Kermit (sometimes just called kermit)
doesn't do terminal emulation for Linux (in 2006). But Kermit can
@@ -1798,11 +1808,13 @@ name="Ubuntu -- x-terminal-emulator"> for a brief list of such
emulators. Some are multilingual. Your Linux distribution has likely
installed one for you.
- Real terminals may be better
- Unless you are using X Window with a large display, a real
+ Real terminals once were better
+ Unless one was using X Window with a large display, a real
terminal was often nicer to use than emulating one. It often had
better resolution for text (since it's monochrome), and had no disk
-drives to make annoying noises.
+drives to make annoying noises. Today, the resolution of modern color
+displays is better than that of the old text-terminals and disk drives
+are quieter.
Testing Terminal Emulation
For the VT series terminals there is a test program: Make a Linux PC a serial port terminal
- Unless you want to emulate the standard vt100 (or close to it),
-xterm, or a Wyse 60, there doesn't seem to be much free terminal
-emulation software available for Linux. The free programs are minicom,
-picocom, and for GUI: seyon and PuTTY. Both seyon and PuTTY can
-emulate either xterm or vt100 (or close to it). PuTTY is much newer
-but its main use is an SSH client. Seyon is much older but with more
-features (some of which are seldom needed). There are also more
-recent (but weaker) "emulators" for a GUI interface: gtkterm and
-cutecom, neither of which can emulate any terminal except of type
-"dumb" ??). Seyon can also emulate a Tektronix 4014 terminal. For
-Wyse see .
+id="pc_as_terminal">
+ Unless you want to emulate the standard vt100
+(or close to it), xterm, or a Wyse 60, there doesn't seem to be much
+free terminal emulation software available for Linux. The free
+programs are minicom, picocom, and for GUI: seyon and PuTTY. Seyon
+can emulate either xterm or vt100 while PuTTy uses its own termcap
+(terminfo) named "putty" (put the terminal type "putty" in
+/etc/inittab). Putty's "pterm" can be used as a replacement for
+xterm.
+
+PuTTY is much newer than most other emulations and a major use of it
+is as an SSH client but you can set its configuration for a serial
+port connection. Seyon is much older but with more features (some of
+which are seldom needed). There are also more recent (but weaker)
+"emulators" for a GUI interface: gtkterm and cutecom, neither of which
+can emulate any terminal except of type "dumb" ??). Seyon can also
+emulate a Tektronix 4014 terminal. For Wyse see .
Both gtkterm (and likely cutecom) don't use escape sequences, and
might be said to emulate a terminal of type "dumb" so they would be
@@ -1917,13 +1934,12 @@ which may be found using their search engine at . And if you check the Internet (in
2008), it's still being sold here and there.
-There's a specialized Linux distribution: Serial Terminal Linux. It
-will turn a PC to into a minicom-like terminal. It's small (fits on a
-floppy) and will not let you use the PC for any other purpose (when
-it's running). See . It will let you
-have more than one session running (similar to virtual terminals), one
-for each serial port you have.
+There was a specialized Linux distribution: Serial Terminal Linux. It
+would turn a PC to into a minicom-like terminal. It's small (fits on a
+floppy) and will not let you use the PC for any other purpose (when it's
+running). The link to it is broken, but one similar to it (in 2013),
+but on CD, is
TERM (non-free commercial software from Century Software) .
+historical interest is an article in Byte magazine from Feb 1994
+entitled "DOS Serial Communications. It was onetime at
+http://www.byte.com/art/9402/sec8/art1.htm.
Today Windows comes with "HyperTerminal" (formerly simply called
"Terminal" in Windows 3.x and DOS). Competing with this is both the
@@ -1986,11 +2002,6 @@ Both the "fink" and "darwinports" projects have ported minicom to the
Mac, but they may not have the most recent version and you might need
to compile minicom yourself.
-One place to check terminal emulation products is Shuford's site, but
-it seems to lists old products (which may still work OK). The fact
-that most only run under DOS (and not Windows) indicates that this
-info is dated. See .
Colors on Emulated Terminals
Since displays used for text terminal emulation are almost always
@@ -4165,13 +4176,21 @@ the serial device driver. You normally never need to use it, provided
that you only use the one or two serial ports that come as standard
equipment with a PC. Even in other cases, most extra serial ports
should be auto-detected by modern kernels. Except you'll need to use
-setserial if you have an old ISA serial port set by jumpers on the
+setserial if you have an obsolete ISA serial port set by jumpers on the
physical hardware or if your kernel (such as 2.2 or older) doesn't
-both detect and set your add-on PCI serial ports.
+both detect and set your add-on PCI serial ports. In some cases the
+setserial program may have been previously used and the wrong serial
+port data has been manually given by the some past user (perhaps by
+you). If setserial hasn't been configured to accept what the kernel
+says, it will override the (likely correct) kernel data with what
+someone previously set.
"stty sane" . Don't try to learn all the settings unless you
+want to become a serial historian since many of the settings are only
+for slow antique dumb terminals of the 1970's. Most of the defaults
+should work OK.
"man stty" or "info stty" .
-Whereas to
understand it.
- Two interfaces at a terminal
+ Two interface modes at a terminal
When using a shell (such as bash) with command-line-editing
-enabled there are two different terminal interfaces (what you see when
-you type stty -a). When you type in modern shells at the command line
-you have a temporary "raw" interface (or raw mode) where each
-character is read by the command-line-editor as you type it. Once you
-hit the <return> key, the command-line-editor is exited and the
-terminal interface is changed to the nominal "cooked" interface
-(cooked mode) for the terminal. This cooked mode lasts until the next
-prompt is sent to the terminal (which is only a small fraction of a
-second). Note that one never gets to type any command in this cooked
-mode but what was typed in raw mode on the command line gets read by
-the shell while in cooked mode.
+enabled there are two different terminal interfaces (or line
+disciplines: what you see when you type stty -a). When you type in
+modern shells at the command line you have a temporary "raw" interface
+(or raw mode) where each character is read by the shell's
+command-line-editor as you type it. Once you hit the <return>
+key, the command-line-editor is exited and the terminal interface is
+changed from raw to the nominal "cooked" interface (cooked mode) for the
+terminal using the stty configuration that was used for the last cooked
+mode (the shell has saved it and it gets restored). This cooked mode
+lasts until the next prompt is sent to the terminal (which is only a
+small fraction of a second) but it exists during the execution of the
+command (or at least during the first stage of the command execution).
+Note that one never gets to type any command into this cooked mode but
+what was typed in raw mode on the command line starts execution by the
+shell while in cooked mode.
When a prompt is sent to the terminal, the terminal goes from "cooked"
to "raw" mode (just like it does when you start an editor such as vim.
@@ -4699,32 +4744,36 @@ The prompt signals starting the command-line editor. The settings for
the "raw" mode are based only on the basic stty settings taken from the
"cooked" mode. Raw mode keeps these setting but changes several other
settings in order to change the mode to "raw". It is not at all based
-on the settings used in the previous "raw" mode. Thus if one uses
-stty to change settings for the raw mode, such settings will be
-permanently lost as soon as one hits the <return> key at the
-terminal that has supposedly been "set".
+on the settings used in the previous "raw" mode (as contrasted to
+"cooked" mode which gets restored by the shell to its previous
+settings). Thus if one uses stty to change settings for the raw mode,
+such settings will be permanently lost as soon as one hits the
+<return> key at the terminal.
Now when one types stty to look at the terminal interface, one may
either get a view of the cooked mode or the raw mode. You need to
figure out which one you're looking at. It you use stty from a
-foreign terminal (other than the terminal you are currently typing
-at) then you will see the raw mode settings. Any changes made will
-only be made to the raw mode and will be lost when someone presses
-<return> at the foreign terminal you tried to "set". But if you
-type a stty command to view/change the configuration of the terminal
-you are using, and then hit <return> it's a different story.
-The <return> puts the terminal in cooked mode. Your changes are
-saved and will still be there when the terminal goes back into raw
-mode (unless of course it's a setting not allowed in raw mode).
+foreign terminal (other than the terminal you are currently typing at)
+then you will likely see the raw mode settings since the terminal is in raw
+mode almost all the time. Any changes made will only be made to the raw
+mode and will be lost when someone presses <return> at the foreign
+terminal you tried to "set". But if you type a stty command to
+view/change the configuration of the terminal you are using, and then
+hit <return> it's a different story. The <return> puts the
+terminal in cooked mode and your changes are saved by the shell before it
+returns to raw mode. Since going into raw mode doesn't change all stty
+settings, some of the changes you made via stty may still be present in
+raw mode and will not get destroyed by <return>.
This situation can create problems. For example, suppose you corrupt
-your terminal interface. To restore it you go to another terminal and
-"stty -F dev/ttyS1 sane" (or the like). It will not work! Of course
-you can try to type "stty sane ..." at the terminal that is corrupted
-but you can't see what you typed. All the above not only applies to
-dumb terminals but to virtual terminals used on a PC Monitor as well
-as to the terminal windows in X. In other words, it applies to almost
-everyone who uses Linux.
+your terminal interface so that it's not displaying what you type, etc.
+To restore it you go to another terminal (on the same PC) and type "stty
+-F dev/ttyS1 sane" (or the like). It will not work because the terminal
+is in raw mode! Of course you can try to type "stty sane ..." at the
+terminal that is corrupted but you can't see what you typed. All the
+above not only applies to dumb terminals but to virtual terminals used
+on a PC Monitor as well as to the terminal windows in X. In other
+words, it applies to almost everyone who uses Linux.
Luckily, when you start up Linux, any file that runs stty at boot-time
will likely deal with a terminal (or serial port with no terminal)
@@ -4941,8 +4990,8 @@ are sent to the screen (output). This is nice for remapping the
keyboard for foreign language alphabets. Most distributions don't
seem to supply it (let me know if any do). Source code by Yura
Kalinichenko (Ukraine, partly in Russian )
+url="http://sourceforge.net/projects/mapchan/" name="download mapchan
+etc.">
Terminfo and Termcap (detailed)
@@ -5314,14 +5363,17 @@ screen for cases where it slows down the "progress". If it just
updates progress numbers a few times per second or less, it shouldn't
be a problem.
- Bugs in Bash
- One problem still outstanding is that if certain terminal
-keys send bytes with the high order bit set to 1, then Bash seems to
-ignore the meaning for them as defined in a terminfo entry. I've
-reported this as a bug in Bash. Other programs such as the vim editor
-and the lynx browser work OK with such keys.
+ Bugs in Bash ?
+ One problem still outstanding is that if certain terminal keys
+send bytes with the high order bit set to 1, then Bash seems to ignore
+the meaning for them as defined in a terminfo entry. This may be
+because, unless one is using 7-bit ASCII, bytes with the high order
+bit set to 1, may represent a non-English letter. I reported this as
+a bug in Bash (but years later realized that it may not have been a
+bug). Other programs such as the vim editor and the lynx browser work
+OK with such keys (when they are set to use 7-bit ASCII).
-To work around this problem one may define what these keys should do
+To work around this problem, one may define what these keys should do
in Bash by putting such definitions into /etc/inputrc. For
example, A Wyse 60 will send D0-D3 when the arrow-keys are hit
provided the terminal is in "application key mode". After modifying
@@ -5330,7 +5382,7 @@ line in the Bash shell. So I explicitly defined the arrow-keys in
/etc/inputrc like this:
-# Arrow keys in 8 bit keypad mode: Sends d0-d4. -ap means application.
+# Arrow keys in 8 bit keypad mode: Sends d0-d3. -ap means application.
$if term=wy60-25-ap
set enable-keypad on
"\xd0": backward-char
@@ -5343,8 +5395,8 @@ $endif
If the terminal is already in "application key mode" there's no need
to "set enable-keypad on". enable-keypad will send the terminal the
escape sequence named smkx in terminfo (which for wyse60 is \E˜3
-and makes the arrow keys send D1-D3). Many other application send
-this without needing to be told to do so.
+and makes the arrow keys send D0-D3). Many other applications (other
+than Bash) send this without needing to be told to do so.
A fixed Bash bug
There have been problems with the readline interface to the Bash
@@ -6264,15 +6316,15 @@ mistake in your set-up. Some terminals allow setting different values
(such as baud rate) for send and receive so the receive could be OK
but the send bad.
-You should also (at the console) try "stty < /dev/ttyS1" (if you use
-ttyS1) to see that it's set up correctly. It will often be in raw
-mode (and this is probably OK) with -icanon and -echo etc. If the
-terminal incorrectly set at half-duplex (HDX), then one set of the
-characters you see when you type are coming from the terminal itself.
-If the characters are doubled, then the echos from the computer are OK
-and you may switch to full-duplex to fix this. But if half-duplex is
-set and you only see what looks like normal "echos", then they are not
-coming from the computer as they should be.
+You should also try at another terminal (such as the console) "stty -F
+/dev/ttyS1" (or ttyS whatever) to see that it's set up correctly. It
+will often be in raw mode (and this is probably OK) with -icanon and
+-echo etc. If the terminal incorrectly set at half-duplex (HDX), then
+one set of the characters you see when you type are coming from the
+terminal itself. If the characters are doubled, then the echos from the
+computer are OK and you may switch to full-duplex to fix this. But if
+half-duplex is set and you only see what looks like normal "echos", then
+they are not coming from the computer as they should be.
If you get a message saying something like "login failed" then if
there is no error in typing or in the password, there may be some
@@ -6352,16 +6404,17 @@ section.
Measure voltages
If you have a voltmeter handy check for a negative voltage (-4v to
--15v) at pin 3 (receive data) at the terminal side of the
+-15v) at pin 3 or 2 (receive data) at the terminal side of the
file-transfer cable. The positive lead of the meter should be
-connected to a good ground (the metal connectors on the ends of cables
-are often not grounded). If there is no such negative voltage then
+connected to a good ground (a metal connector on the end of the cable
+may not be grounded). If there is no such negative voltage then
check for it at the transmit pin (TxD) on the computer (see [ for the pin-out). If it's present
there but not at the receive pin (RxD) at the terminal, then the cable
is bad (loose connection, broken wire, or not a file-transfer aka
-null-modem). If voltage is absent at the computer, then its serial
-port is dead. Test it with a software diagnostic test or replace it.
+null-modem). If this voltage is absent at the computer, then its
+serial port is dead. Test it with a software diagnostic test or
+replace it.
If the serial port is alive, you may want to send a file to it (with
modem controls disabled) and watch the signal on a voltmeter (or other
@@ -6609,10 +6662,6 @@ Monitors". Much of this information is applicable to terminals as are
the sections: "Testing Capacitors", "Testing Flyback Transformers",
etc. Perhaps in the future, the "info" on repair in this HOWTO will
consist mainly of links to the above FAQ (or the like).
-] of newsgroup postings on terminal
-repair is another source of info.
Safety
CRT's use high voltage of up to 30,000 volts for color (less for
@@ -7084,24 +7133,37 @@ entries
The Internet and Books
Terminal Info on the Internet
-
--
at the University of Tennessee has a great
-deal of useful information about text terminals.
--
2009: Serious errors re history
-- VT terminal information and history
+ In the first decade of the 20th century,
+http://www.cs.utk.edu/~shuford/terminal_index.html was Shuford's Website
+at the University of Tennessee. It was the major sit for information
+about text terminals but is now (2013) defunct. Perhaps one can find it
+archived on the "Wayback" machine.
+http://www.cs.utk.edu/~shuford/terminal/repair_hints_news.txt was
+Shuford's repair archive of newsgroup postings on terminal repair. See
+below for the vt100 part of this website which is still on the internet.
+
+
+-
+-
+-
+-
part of "GNU C Library Reference
+Manual" (in libc (or glibc) docs package). It covers the detailed
+meaning of "stty" commands, etc.
-
purchased the VT and Dorio terminal business from
DEC. Boundless used to have online Specs of their ADDS, VT, and
DORIO terminals but that link (in previous versions of this HOWTO) is
now dead.
-- Wyse has detailed info (such as escape sequences) in it's
+
- Wyse had detailed info (such as escape sequences) in it's
knowledge base. It's not as complete as a real manual since it mainly
-cover "native" personality.
For current models see .
+cover "native" personality. It was Wyse text-terminals database" at
+http://www.wyse.com/service/support/kbase/wyseterm.aspi but it's defunct.
+You may still access their knowledge base (does it still cover
+text-terminals) by registering. Start at .
-
- comp.terminals is the newsgroup for
terminals
@@ -7243,12 +7305,8 @@ escape sequences options will not be repeated here.
See url url= "http://www.neoware.com/docs/teemtalk/t2k17pro.pdf"
name="TeemTalk.2000 Programmer's Guide v 1.7"> in pdf format. But
there are some sites that have info for certain terminals. For VT
-terminals see . A
-list for VT (not maintained) may be found in Appendix B of . For Wyse see: and select the terminal model.
+terminals see .
+Other lists have disappeared from the internet.
8-bit Control Codes
Table of 8-bit DEC control codes (in hexadecimal). Work on VT2xx or
@@ -7673,8 +7731,8 @@ nice if for each terminal model, there were a set of links linking to
most of the documentation relevant to that model (including escape
codes). But it hasn't been done. Note that some VT (DEC) manuals are
now available on the Internet. See and [. Wyse has put the information from its manuals on the
-Internet. See ][.
+(DEC)">. Wyse put the information from its manuals on the
+Internet but it can't be readily found now (2013).
] Adds
The Adds terminal menu incorrectly used "Xon/Xoff" to mean any kind
@@ -7761,10 +7819,7 @@ url="http://www.boundless.com/terminals.html" name="Boundless"> name
and url have been retained.
Detailed VT terminal information, some manuals, and
-history is at . Other information is
-available at .
+history is at .
VT220: Some have a BNC connector for video output (not for input).
Sometimes people erroneously think this is for an ethernet connection.
@@ -7784,7 +7839,7 @@ The "sco unix console" is claimed to be a powerful emulation using the
Qume was taken over by Wyse in the early 1990s.
Wyse Terminals
- For detailed manual-like information on old terminals see detailed manual-like information on old terminals see . This
information includes specs, lists of escape sequences, part lists,
FAQs, setup info, etc. Thanks to Wyse for providing this even though
@@ -7796,6 +7851,8 @@ these terminals, especially the Wyse 50. But the large number of
failure reports (other than Wyse 50) may be due in part to the large
number of Wyse terminals in use.
+See for a history of Wyse.
+
Wyse 50
Reported not to last very long.
@@ -7804,7 +7861,7 @@ number of Wyse terminals in use.
VR302, Width VR101 (also affects height). If you want to use it in
Native Personality, then the arrow-key codes will conflict with the
codes used in vi (such as ^L). To fix this set "Application key mode"
-with ESC ˜ 3. This results in the arrow keys sending 0xd1 - 0xd4.
+with ESC ˜ 3. This results in the arrow keys sending 0xd0 - 0xd3.
Due to a bug in the readline interface of the Bash shell, you need to
edit /etc/inputrc so that the arrow keys will work in Bash. See [
]