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.

E1196: GlinkW, non-destructive backspace on AIX using SSH

Product: Glink 8.1
Platform: Win32
Status: Fixed in 8.1.4
Last updated: 2008-10-13 14:05:40

AIX defaults to stty -echoe. This means that the backspace (regardless
of the erase character) is not destructive. Generally the administrator
of a UNIX system will have fixed the login scripts so that:

   STTY echoe

is executed during login, both for Telnet logins and for SSH logins. If
this is not done correctly, then

   STTY -a

will show 'echoe' for a Telnet session (where destructive backspace
works), but '-echoe' for the SSH session.

Please note that at the SSH command line level the destructive backspace
might continue to work, even though '-echoe' is set. This is because
many of the shells (for example bash) disregard '-echoe' and give you a
destructive backspace anyway. The incorrect setting of -echoe will only
take effect when you start a script or utility that respects the STTY
settings (ftp was the problem for the customer in question).

Glink's PuTTY SSHD interface has now been enhanced to set echoe as a
default. This works regardless of the erase character you have
configured on UNIX/Linux. Today (^H, Backspace) is the preferred erase,
but users with a DEC terminal background might have the erase
configured as (^?, DEL). Either way, with the enhancement in Glink the
UNIX scripts/utilities will echo 'BS space BS' to give you a destructive
backspace on reception of the erase character from the client.

Work-around for earlier Glink releases is to add the REG_SZ entry to
the PuTTY registry.


(c) Copyright 1982-2019 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

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