old terminals...

Bill Pechter pechter at gmail.com
Wed Mar 14 15:16:15 CDT 2007


On 3/14/07, Jay West <jwest at ezwind.net> wrote:
>
> Ya know... this recent talk of terminals got me thinking.....
>
> It would be a good idea IMHO to preserve the functionality of all these
> classic old terminals. After all, sooner or later the real ones will
> disappear or at least stop working. After all, some systems are picky
> about
> only working with certain terminals (or some only work WELL with certain
> terminals)...
>
> Then I started thinking... most modernish "good" terminal emulation
> packages
> don't support all the old venerable classics. Sure, many do VT100 (sort
> of).
> But when was the last time you saw a terminal emulation package that
> faithfully reproduced a beehive minibee? Or a Heath H19? I think it might
> be
> helpful for the future if there was a "collectors" terminal emulation
> program that really did strive to get emulations for all the old
> terminals,
> and get it dead right. I know it'd be nice to have one emulator for my
> systems that "did the right thing(tm)" on my HP mini's, my DECs, DGs, and
> my
> Heathkits, GA Zebras, TI990's, etc. etc. all with one program. Instead I
> have to have many different terminal emulation programs (because one that
> does HP2624 emulation wont do my TI terminal emulation...)... or the real
> thing (which of course I'd prefer).
>
> So then my unix-centric brain said... Oh, well, there's always
> termcap/terminfo. Surely that will document old terminals for posterity
> and
> future emulation. So I just popped in to my local copy of terminfo and
> sure
> enough, there's even an entry for the beehive minibee and superbee. BUT...
> I
> then noted the comments that say "hey, this termcap entry is pretty wrong
> and doesn't work right". So relying on terminfo for preservation is
> probably
> not a great idea. But it's a start.
>
> Just thinking out loud... would be nice to have a terminal emulation
> program
> that was easily extensible for any terminal, already had all the ones
> defined that we here are familiar with... and ran on everything from
> MS/DOS
> to Vista to *nix. A classiccmp'ers terminal emulator :) Maybe a good start
> would be those of us that have particular terminals at least going in and
> correcting the terminfo entries that are incorrect.
>
> Perhaps this is a silly idea and I just need my morning coffee!
>
> Jay West
>
>
>
>
If you get something that does that... let me know.
Kermit-95 is the closest thing.

I purchased it and like the emulation for the DEC stuff.  Don't know how
good the DG is... also used the SCO-Ansi... pretty good there.

Kermit 95 Terminal Types

*As of:* Kermit 95 2.0 <http://www.columbia.edu/kermit/k95.html>
*Date:* 7 June 2002

 Kermit 95 2.0 supports 40 terminal emulations:

*ADM3A* The Lear-Siegler ADM-3A terminal. No F-keys.

*AIXTERM* For accessing IBM AIX systems. Compatible with the AIXTERM window
on AIX workstations, and the AIXTERM termcap / terminfo entry. Has F1-F12
keys, also Shift-F1-F12.

*ANSI-BBS (*) <http://www.columbia.edu/kermit/termtype.html#ansi>* For
accessing most BBSs. 8 bits, color, line- and box-drawing, "ANSI graphics".
As defined in the DOS 5.0 manual. Function keys F1-F4 send what VT100 sends,
F5-F12 undefined.

*AT386 (*) <http://www.columbia.edu/kermit/termtype.html#ansi>* For
accessing (SCO) Unixware and (Sunsoft) Interactive UNIX systems. Has 60
Function keys F1-F12 plus various versions with Shift, Ctrl, Ctrl-Shift,
etc.

*Avatar/0+ (*) <http://www.columbia.edu/kermit/termtype.html#ansi>* For
accessing BBSs that support certain advanced features. If a BBS supports
Avatar/0+, this is normally negotiated automatically when you log in to it.
F1-F4, like ANSI-BBS.

*BA80* The Nixdorf BA80 terminal (Germany), used for accessing Nixdorf
computers. Has PA (function) keys 1-12.

*BETERM (*) <http://www.columbia.edu/kermit/termtype.html#ansi>* BeBox
console, the preferred terminal type for accessing the BeBox and BeOS.

*DG200* Data General DASHER 200, for accessing AOS/VS, DG/UX, and other Data
General platforms. Has function keys F1-F12, which can be modified by Shift,
Ctrl, or Ctrl-Shift, plus some others (e.g. Alt-F1-F5, Alt-Shift-F1-F5,
Ctrl-Alt-F1-F5).

*DG210* Data General DASHER 210, for accessing AOS/VS, DG/UX, and other Data
General platforms. F-keys as for DG200.

*DG217* Data General DASHER 217, for accessing AOS/VS, DG/UX, and other Data
General platforms. Includes both DG and UNIX modes, as well as alternate
character sets -- Math/Symbol, Line Drawing, Word Processing. F-keys as for
DG200.

*HEATH19* The Heath-19 or Zenith-19 terminal. Has PF1-4 like VT100.

*HFT* IBM's High Function Terminal type, used for accessing AIX and other
IBM platforms that support it. Has F1-F12, Shift-F1-F12, Ctrl-F1-F12.

*HP2621A* The Hewlett Packard 2621A terminal. Has F1-F16. F9-F16 are entered
by Shift-F1-F8.

*HPTERM (*) <http://www.columbia.edu/kermit/termtype.html#hpterm>* Hewlett
Packard's generic HPTERM specification, used on HP-UX in HPTERM windows, and
compatible with various specific HP terminals such as those in the 700
series. F keys as for HP2621A.

*HZ1500* The Hazeltine 1500 terminal. Has F1-F12.

*IBM3151* The IBM 3151 terminal. This emulation is just enough to support
termcap and terminfo driven applications on Unix. A complete keyboard
mapping is provided as well as the IBM 3151 graphics character set. None of
the special forms modes are (yet) implemented. Has F1-F12, Alt-F1-F12,
Shift-Alt-F1-F12.

*LINUX* The Linux console. Has 60+ function keys, produced by F-keys (and
some others) in various combinations with Shift, Ctrl, and Alt.

*QANSI (*) <http://www.columbia.edu/kermit/termtype.html#ansi>* The QNX ANSI
terminal. F1-F10.

*QNX* The QNX console. F1-F12, Shift F1-F12.

*SCOANSI (*) <http://www.columbia.edu/kermit/termtype.html#ansi>* The SCO
version of ANSI, used by SCO UNIX, ODT, and OpenServer, and Caldera Open
UNIX. Has 60 function keys, like AT386. WARNING: The host name is ANSI, but
Kermit's name is SCOANSI, to distinguish it from ANSI-BBS, which is
different. When making Telnet connections, set Kermit's terminal type to
SCOANSI and its Telnet terminal-type to ANSI:

  set terminal type scoansi
  set telnet terminal-type ansi

 *SNI-97801* The Siemens Nixdorf Bildschirmeinheit 97801-5xx (Germany), for
use with SINIX. Downloadable character-sets, fonts, and compose tables are
not supported. Has tons of function keys produced by various combinations of
F-keys with Shift, Ctrl, and Alt.

*TTY* Teletypewriter. This is equivalent to no terminal emulation at all.

*TVI910+* The Televideo 910+ terminal. F1-F12, Shift-F1-F12, Alt-F1-F6,
Alt-Shift-F1-F6.

*TVI925* The Televideo 925 terminal. F1-F12, Shift-F1-F12, Alt-F1-F6,
Alt-Shift-F1-F6.

*TVI950* The Televideo 950 terminal. F1-F12, Shift-F1-F12, Alt-F1-F6,
Alt-Shift-F1-F6.

*VC404* The Volker Craig 404 terminal. F1-F12.

*VIP7809* Partial emulation of the Honeywell VIP-7809 terminal. In fact,
this is VT-102 emulation with minor modifications sufficient to allow access
to Honeywell DPS-6 systems.

*VT52* The Digital Equipment Corporation VT52 terminal. Has PF keys 1-4 on
F1-F4 but no F keys.

*VT100* The industry-standard 7-bit Digital Equipment Corporation VT100
terminal, with color extensions. Has PF keys 1-4 on F1-F4, but no F keys.

*VT102* Like VT100, but with character insertion and deletion capabilities
and several other functions added, and with color extensions.

*VT220* The industry-standard 8-bit Digital Equipment Corporation VT220
terminal with color extensions. Has PF keys 1-4 on F1-F4, plus 20 F-keys,
1-20, of which only F5-F20 are usable, on F5-F12 and Shift-F1-F10.

*VT220PC* VT220 with a PC keyboard.

*VT320* The industry-standard 8-bit Digital Equipment Corporation VT320
terminal with color extensions, plus many features of the VT420, VT520, and
DECterm. F-keys as for VT220.

*VT320PC* VT320 with a PC keyboard.

*VTNT* VTNT is a proprietary Microsoft terminal definition used by the
Telnet Server distributed with Windows 2000/XP and NT Services for Unix.

*WY30* The Wyse model 30 terminal, plus most of the capaibilities of the
Wyse 30+ and 35 models. Multiple Windows, display controls, and certain
other features are not currently supported.

*WY50* The Wyse model 50 terminal. Multiple Windows, display controls, and
certain other features are not currently supported. F1-F12, Shift-F1-F12,
Alt-Shift-F1-F6, and others.

*WY60* The Wyse model 60 terminal, plus most of the features of the Wyse
120, 160, and 350 models. Multiple Windows, display controls, and certain
other features are not currently supported. F keys as for WY50.

*WY160* The Wyse model 160 terminal, plus most of the features of the Wyse
120 and 350 models. Multiple Windows, display controls, and certain other
features are not currently supported.

*WY370* The Wyse model 370 terminal, similar to VT320 but with additional
color capabilities. F-keys as for WY60, plus some more.

The names in the list are those used in the Terminal Type box on the
Terminal page of the Dialer entry notebook, and by the SET TERMINAL TYPE
command. These names are also sent to the host in Telnet terminal type
negotiations unless you have specified a TELNET terminal-type name to
override it.
------------------------------
ANSI Terminal Types Whenever a (PC)
ANSI<http://www.columbia.edu/kermit/gloss.htm#g_ansi>terminal type is
chosen, the following actions are executed automatically:


   - SET TERMINAL BYTESIZE 8
   - SET PARITY NONE
   - SET TERMINAL CHARACTER-SET CP437
   - SET TERMINAL COLOR TERMINAL LGRAY BLACK
   - Your PC code page (right half) is designated to G1, G2, and G3.

 The normal mode of operation for any ANSI terminal type is to converse with
a host application that uses a PC code page as its character set, and whose
code page is the same as your code page. This is because ANSI terminal
emulation is generally used for applications where there is a lot of line
and box drawing -- "graphics" simulated by colored character cells.

In some environments, however, the host sends Latin-1 or other codes for
accented or special characters. In such cases, you can set your terminal
character set to Latin-1 (or other set) AFTER selecting an ANSI terminal
type, for example:

  set terminal type scoansi                 ; Sets CP437
  set terminal remote character-set latin1  ; Set it to Latin-1

 But Latin-1 (and Latin-2, Cyrillic, Hebrew, etc) do not include the many
box-drawing characters needed for ANSI emulation, and the simple form of the
SET TERMINAL CHARACTER-SET command shown above assigns Latin-1 to all of G1,
G2, and G3. Thus you must also ensure that your PC code page remains
available as an alternate character set by using the more specific form of
the command, which is:

  SET TERMINAL REMOTE-CHARACTER-SET *name [ *G*n ]*

 This lets you change your remote character set without having to respecify
(or even know) your local PC character set (or code page). The
optional G*n*field designates the named set to the specified terminal
graphics table, G0,
G1, G2, or G3 (you can specify more than one) according to ISO 4873 and 2022
rules.
------------------------------
HPTERM Emulation This is a functional HPTERM (Hewlett Packard Xterm)
emulation, but lacking color and multiple pages. When function keys are
programmed and/or labeled, you can view the labels on a popup help screen
using the new \Kfnkeys verb, which is assigned by default to Alt-f.

When the HPTERM emulation is selected, character sets are assigned as
follows:

   Remote: GL->G0: US ASCII (94 chars)
           GR->G1: Hewlett Packard Roman 8 (96 chars)
               G2: HP Line Drawing Graphics (96 chars)
               G3: HP Line Drawing Graphics (96 chars)

------------------------------
SNI-97801 Emulation The SNI-97801 is an advanced terminal designed
specificly with the multiple language market in mind. Kermit 95 does not
support the following features of the terminal:


   - downloadable soft character sets
   - downloadable compose key settings

 The SNI-97801 has a keyboard with more than 42 function and editing keys
which cannot be mapped directly to a PC keyboard. K95 provides keyboard
verbs <http://www.columbia.edu/kermit/kverbs.htm> for all of the SNI-97801
keys although most are not assigned to the PC keyboard due to lack of space.


Kermit 95 does support all of the 7-bit and 8-bit CH.CODE modes which are
controlled by the following commands:


   - SET TERMINAL SNI-CH.CODE {ON, OFF} or the \Ksni_ch_code keyboard
   verb
   - SET TERMINAL BYTESIZE { 7, 8 }

 The CH.CODE mode determines whether the terminal communicates using
International character sets such U.S. ASCII and ISO Latin 1; or whether it
uses a National character set such as German. The SET TERMINAL LANGUAGE
command is used to specify the default language.

The Firmware Versions numbers can be customized using the SET TERMINAL
SNI-FIRWARE-VERSIONS  command. The default keyboard version number is 920031
and the default terminal version number is 830851.
------------------------------
Automatic Actions on Switching Terminal Types Terminal types can be switched
by user command ("set terminal type"), hot key (\Ktermtype, normally
assigned to Alt-t), Telnet negotiations, or (in some cases) by host escape
sequence. Whenever the terminal type is set or switched:


   - The screen is cleared.

   - The corresponding terminal-specific keymap is activated.

   - A macro named TT_*XXX*, where *xxx* is the same as the terminal type
   name, is executed if such a macro is defined; e.g. tt_vt320, tt_scoansi,
   etc. Such a macro definition might include SET TERM HEIGHT or WIDTHcommands.

------------------------------
Terminal Send Data modes Many terminals including the Wyse and Televideo
terminals support a SEND DATA feature which allows the host application to
query the terminal and request that a copy of all of the data on the screen
be sent to the host. This feature is very useful with applications that
process a complete form of data at a time; or that allow a single terminal
to be used with multiple sessions. However, this feature is also a security
hole which can be exploited to steal data. Therefore, Kermit 95 disables the
SEND DATA feature by default. If you need to use SEND DATA with your
application, you must add a SET TERMINAL SEND-DATA ON command to your
K95CUSTOM.INI file.

------------------------------

*Click Back on your Browser's Toolbar to return.*

 ------------------------------


--
  d|i|g|i|t|a|l had it THEN.  Don't you wish you could still buy it now!
pechter-at-gmail.com



More information about the cctalk mailing list