In message <[email protected]>, Tony Gravagno
<[email protected]> writes
It does. ViaDuct was my favorite emulator in the early 90's
until I found wIntegrate, and that was my favorite until the
later 90's when I found AccuTerm. :) All support scripting.
The problem is that they're all different. So if you send
ESC:"FOO" to any one of the emulators, it might do something nice
or it might lock it up. That's the chance you take and
fine-tuning the scripts to play nice if they hit the wrong
emulator is what I call "the hard way". You may get it right
with some experimenting but it could be time consuming to get it
just right.
So you configure all the emulators to respond to the same sequence. The
problem is if you've got different real terminals that you can't
program. But it looks like some variant of <ctrl>E might well be a
common factor.
Below is the code I used to tell whether the user was using a pt250, a
wyse85, or wintegrate/pt250. As you can tell, it was written long, long
ago.
* Select Terminal Type Here
* *************************
* Use the answerback mechanism so the terminal is selected correctly.
PRINT "Requesting answerback" ; * This message is necessary
to clear the buffer
CLEAR INPUT
PRINT CHAR(27):CHAR(5)
SLEEP 1
TTY = ""
HUSH ON
LOOP
INPUT KEYSTAT,-1
WHILE KEYSTAT
INPUT JUNK,1: ; TTY := JUNK
REPEAT
HUSH OFF
* Now try again - the above code doesn't work with the new winterm. awy
21/09/01
IF TTY ELSE
CLEAR INPUT
PRINT "XX":CHAR(5)
SLEEP 1
TTY = ""
HUSH ON
LOOP
INPUT KEYSTAT,-1
WHILE KEYSTAT
INPUT JUNK,1: ; TTY := JUNK
REPEAT
HUSH OFF
END
SKIP = 0
IF TTY ELSE
LOOP
CRT ; CRT @SYS.BELL : "Which terminal type 1 (VT100) 2
(PT200/wIntegrate) 3 (ignore) ? : " :
INPUT TTY :
BEGIN CASE
CASE TTY = 1 ; TTY = "VT100"
CASE TTY = 2 ; TTY = "PT200"
CASE TTY = 3 ; SKIP = 1
CASE 1 ; CONTINUE
END CASE
EXIT
REPEAT
END
EXECUTE "SET.TERM.TYPE " : TTY : " WIDTH 80 LENGTH 24 HUSH"
If I remember correctly, the wyse/vt answerback sequence was <ctrl>E,
while for the pt250 it was <esc><ctrl>E.
The winterm thingy was a wyse thin terminal running WinCE or something
like that. We played with them but ended up not using them.
The "requesting answerback" tipped the user off that something was
happening, and the 1-second sleep gave the terminal/emulator time to
respond and fill the buffer. The program then checked what response it
got and carried on ... as you can see, we'd programmed it to respond
with the terminal type. So occasionally, when we got a new real
terminal, things fell over until we remembered to program the terminal
response :-)
Cheers,
Wol
--
Anthony W. Youngman <[email protected]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
