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.

E0144: Glink, scripts no longer execute after failed connect

Product: Glink
Platform: DOS, Win, MAC
Status: Closed, fixed in 5.4.2
Last updated: 1996-09-30 14:08:25

When you start up a TCP/IP interface from a script (either directly
with a NETCONNECT or indirectly by loading a config file that points
to a TCP/IP interface) and the startup fails catastrophically (for
example because the interface simply is not there) then Glink is
left in a 'half connected' state, and code in the emulator that
was designed to stop the script executing more commands from your
script until the connect was complete is left enabled. So we never
execute another script command until the connect status is cleaned
up. You can do this by manually loading a configuration file that
uses a communications setup that's startable, or by manually
changing the communications interface.

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

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