The only problem with this solution is that it REQUIRES BOTH Wintegrate
and Accuterm to be installed on every client. Otherwise it will fall
over on one of the CALL statements.

Joe provided a link earlier in this thread which gave an escape sequence
that would return a Wintegrate response. There is an equivalent Accuterm
escape sequence too. So a better general purpose routine would use these
escape sequences.

Cheers,

Brian


pickd3 (AT) mchsi (DOT) com wrote:

Brian, I agree. There could be anything including a DOS command window
connecting to the system. We've found that the best overall solution is
to throw the escape sequence at the emulator and see what comes back.
If it's the expected result for that given emulator, then everything's
wonderful. If not, then we have logic that disables emulator-specific
functionality for unexpected emulators.

Regards,
Joe


Brian Speirs <bss59 (AT) REMOVETHISparadise (DOT) net.nz> wrote in news:45e8fc0b$1
@clear.net.nz:

First, the two calls in the solution from pickd3 are calls to
subroutines on the host, not on the client, therefore you do not need
to have both AccuTerm and Wintegrate installed on each PC. I cannot
speak for the WIN.COMSUB routine, but AccuTerm's FTVSINF subroutine
returns a status that indicates whether AccuTerm is present, and a
variety of information about the version and capabilities of the
connected AccuTerm. It will work with a dumb terminal, and other
emulators (as far as I know). It has a timed INPUT statement so if
something other than AccuTerm is connected, it will simply return with
a "AccuTerm not found" status.

It uses the same approach recommended by Brian, but the details are
already written for you.

Thanks,

Peter Schellenbach

Yes - If I'd thought about that for a moment longer, I would have
realised that the subroutines are on the host!

So this approach works in the specific instance where the organisation
uses both Wintegrate and Accuterm, but wouldn't work in a program that
had to work across a number of organisations.

Brian

Peter Schellenbach wrote:

Based on this thread, the linked one, and some digging in code and
manuals, I put together the following code snippet that determines
whether a user is logged in via wIntegrate or AccuTerm (the two most
common terminal emulators in use here).

WINTEG = ""
PRINT CHAR(27):CHAR(1):"Enter stx:Version":CHAR(13)
INPUT WINTEG FOR 1 ELSE END
IF WINTEG <> "" THEN
PRINT "Terminal emulator is wIntegrate: ":WINTEG
END
PRINT CHAR(27):CHAR(2):"I"
ACCUTERM = ""
INPUT ACCUTERM FOR 1 ELSE END
IF ACCUTERM <> "" THEN
PRINT "Terminal emulator is AccuTerm: ":ACCUTERM
END

Simple and it works.