Facebook

Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.


E1081: GlinkW, forced TEXT mode for telnet 'VIP7800' termtype

Product: Glink Professional
Platform: All
Status: Fixed for 8.0.3, 7.2.6
Last updated: 2005-10-12 08:38:10

Glink forces TEXT mode if the telnet terminal type response indicates
that the terminal is SYNC or capable of SYNC operation. Glink was
incorrectly interpreting Telnet terminal type responses containing the
string '7800' as being such a terminal type. In fact VIP7800 is not a
known VIP model either ASYNC or SYNC, and should have caused no
interpretation by Glink. The interpretation as SYNC overrides the
configured setting:

  Settings->Emulation->VIP mode setup->Init mode: CHAR

Making the configuration unsuitable for use with UNIX/Linux
applications.

This problem was seen where a customer was using 'VIP7800-VI' as the
Telnet terminal type response.

Work-around is to configure the telnet terminal type response as a valid
asynchronous VIP model such as 'VIP7801'. If this is not possible due to
the string being the name of the desired UNIX terminfo, then
echo/character mode can be set after the connection by using the "SET
MODE VIP CHAR" script command or typing ' k' from the keyboard,
macro or script.
(c) Copyright 1982-2017 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors
 
PARTNERS