1
From: sherwin@royalt.enet.dec.com (Jim Sherwin)
2
Newsgroups: comp.terminals
3
Subject: Re: VT100 (DEC) Setup Problem (online/offline)
4
Message-ID: <29245@nntpd.lkg.dec.com>
5
Date: 25 Oct 91 02:02:07 GMT
6
Organization: DEC -- Video, Image and Printer Systems Group
10
Striking the SET-UP key places you into SET-UP A mode. SET-UP A is
11
basically your tab stops. Use the space bar to move along the ruler
12
and strike the T key at the desired tab stop location.
14
SET-UP B may only be entered from SET-UP A and is done be striking
15
the 5 on the main keyboard (i.e. top-row).
17
To exit SET-UP B strike the SET-UP key.
19
The SET-UP parameters are as follows:
22
Bank Position Parameters
24
1 1 Scroll; 0=jump; 1=smooth
25
1 2 Autorepeat; 0=off; 1=on
26
1 3 Screen; 0=dark; 1=light
27
1 4 Cursor; 0=underline; 1=block
29
2 1 Margin Bell; 0=off; 1=on
30
2 2 Keyclick; 0=off; 1=on
31
2 3 ANSI/VT52; 0=VT52; 1=ANSI
32
2 4 Auto XON/XOFF; 0=off; 1=on
34
3 1 Pound Sign; 0=octothorpe; 1=British Pound
35
3 2 Wrap Around; 0=off; 1=on
36
3 3 New Line; 0=off; 1=on
37
3 4 Interlace; 0=off; 1=on
39
4 1 Parity Sense; 0=odd; 1=even
40
4 2 Parity; 0=off; 1=on
41
4 3 Bits per Char; 0=7 bits; 1=8 bits
42
4 4 Power; 0=60 Hz; 1=50 Hz
44
While in SET-UP B mode, these features are set by positioning the
45
cursor above the feature switch, using the spacebar, and striking
46
the 6 key on the main keyboard.
48
To set the ANSWERBACK MESSAGE, enter SET-UP B and strike the SHIFT
49
and A keys simultaneously. The terminal will respond with A = on
50
the screen. Type a message delimiter character which may be any
51
chaacter not used in the actual message. Type the ANSWERBACK
52
MESSAGE, up to 20 characters. Type the message delimiter
53
character. The message will disappear from the screen. You may
54
not edit an ANSWERBACK MESSAGE. You may only supercede it with a
55
new ANSWERBACK MESSAGE.
57
To save the SET-UP, strike the SHIFT and S keys simultaneously,
65
<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>
66
<> "When things are going well, \ Jim Sherwin a.k.a. <>
67
<> someone will inevitably \ sherwin@royalt.enet.dec.com <>
68
<> experiment detrimentally." \ !decwrl!royalt.enet.dec.com!sherwin <>
69
<> Boyle's Second Law \ sherwin%royalt.enet@decwrl.dec.com <>
70
<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>-<>
73
Article 20936 of comp.dcom.modems:
74
Path: utkcs2!darwin.sura.net!jvnc.net!yale.edu!think.com!news.bbn.com!news.bbn.com!news
75
From: Paul Placeway <pplacewa@bbn.com>
76
Newsgroups: comp.dcom.modems,alt.bbs
77
Subject: Re: Detecting ANSI on a remote system
78
Date: 11 Jul 1992 00:04:09 GMT
80
Message-ID: <l5s9bpINNqdt@news.bbn.com>
81
References: <1992Jul8.204233.13120@csusac.csus.edu> <1992Jul9.053233.11670@f109f.mil.se>
82
NNTP-Posting-Host: bbn.com
83
Xref: utkcs2 comp.dcom.modems:20936 alt.bbs:11447
85
nils@f109f.mil.se (Nils Hammar) writes:
87
< emamid@athena.ecs.csus.edu (David Emami) writes:
90
< >I am currently writing a communications app using TurboVision; I've got a
91
< >view that can display ANSI, but how do I let the system that I hook up with
92
< >that I can use ANSI codes. Most BBS's that I've tried respond with "ANSI
93
< >detected" or "ANSI not detected" when I login using a commercial term
94
< >program, based on the emulation I'm using. I presume that the BBS sends a
95
< >string which I need to respond to in a certain way; what should my program
96
< >be looking for, and how should it answer? Any help would be appreciated.
98
< What I have been using is the function that reports the cursor position.
99
< If you get an answer on that request that is correct, it's ANSI, or a VT100
100
< compatible terminal. To determine if it's a VT100 or similar, you will have
101
< to send a second request that's only recognized by the VT100 or
102
< similar terminals. That request will result in an answer that tells you
103
< almost everything that you need to know about the terminal.
104
< If this secondary request doesn't give you any response, then it's only
105
< ANSI. This is a really nice way to find out if you can send high resolution
106
< graphics to the caller too. What a surprise to get a hig resolution
107
< picture on the screen when you are calling an ordinary BBS!
109
The ANSI Device Status Report (DSR) is
113
where <n> is 5 for a status report (OK reply is "ESC [ 0 n"), and 6
114
for report cursor position (reply is "ESC [ <row> ; <col> R").
116
ANSI (and DEC) Send Device Attributes is
120
where <n> is a number, in ASCII 0-9, and usually is 0 for the request.
122
Here are a (small) selection of replies:
125
---- ----- -----------
126
xterm ESC[?1;2c VT100 w/AVO
129
VT320 ESC[63;1;2;8;9c
131
(These are from vttest, by Per Lindberg)
133
vanilla VT100 ESC[?1;0c no options
134
VT100 with STP ESC[?1;1c
135
VT100 with AVO ESC[?1;2c could be a VT102
136
VT100 with STP and AVO ESC[?1;3c
137
VT100 with GPO ESC[?1;4c
138
VT100 with STP and GPO ESC[?1;5c
139
VT100 with AVO and GPO ESC[?1;6c
140
VT100 with STP, AVO and GPO ESC[?1;7c
141
VT100 with PP and AVO ESC[?1;11c
142
VT100 with PP, GPO and AVO ESC[?1;15c
143
VT132 with AVO ESC[?4;2c
144
VT132 with AVO and STP ESC[?4;3c
145
VT132 with GPO and AVO ESC[?4;6c
146
VT132 with GPO, AVO, and STP ESC[?4;7c
147
VT132 with PP and AVO ESC[?4;11c
148
VT132 with PP, GPO and AVO ESC[?4;15c
150
VT125 ESC[?12;5c VT125 also has ROM version
151
VT125 with AVO ESC[?12;7c number, so this won't work
152
VK100 (GIGI) ESC[?5;0c
155
DXterm (DEC's version of xterm) ESC[?63;1;3;4;6;8;9;15;16;29c
157
< For this reason, I once wrote a program that convert PCX pictures
158
< to DEC Sixel Graphics. It was interesting to view those pictures
159
< on the screen with MS-KERMIT (which supports Sixel Graphics in colour.)
160
< The only disadvantage was that Sixel graphics is bitmapped and slow.
162
This is cute, but one needs to be careful about assuming what a
163
terminal emulator will do based on what it claims to be. There are a
164
lot of mediocre "emulations" out there. This is partially because the
165
ANSI spec allows the terminal to do a lot of weird and unexpected
166
things, like embedding simple control characters in the middle of an
167
escape sequence. ("foo ^H^[^H[^H4^HCbar" should render as "foo bar".
170
-- Paul Placeway <pplacewa@bbn.com>