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

Read more
Follow us
Facebook    Twitter    LinkedIn

G&R » About G&R » News » Glink for Java R6.8 beta is available  

Glink for Java R6.8 beta is available

The first beta release of Glink for Java R6.8.0 is available, and can be downloaded from the G&R web site for test and evaluation.


This beta release, R6.8.0a, is the first release of Glink for Java using activation keys for downloading and licensing. Downloading is a two stage operation: first registration, which delivers an activation key to your e-mail address; followed by the download itself, using the activation key.

Customers who have purchased the software and been delivered an activation key can go directly to the download page:


For Glink for Java clients that obtain their license from the Glink for Java license server there is no change. You simply modify glink.ini in the installation directory to point at your license server.

For stand-alone clients the procedure is improved. When you start Glink for Java it brings up a dialog box that allows you to select whether you have a license file delivered by a distributor or an activation key. If you have a file you can browse and select it. If you have an activation key you are asked to enter it, and Glink for Java then connects to our web site for activation.


Configuration has been greatly simplified to make it possible for administrators (all users with administrative privileges) to generate, modify and delete configurations directly from Glink for Java, without using the administration program. In the connection dialog box showing available sessions there is now a button for 'New' (and a button for 'Remove'). New configurations are stored in the global configuration group, available to all users.

Note that new or modified configurations are not stored until the administrator connects to a different session or closes Glink; both cause a prompt asking if the changes should be saved. Disconnecting does not cause the prompt, and a reconnect to the same session continues with the modified configuration without saving it.

Besides giving the administrator an easier way of managing configurations, this makes it far easier for stand-alone users to get started, particularly users who have downloaded Glink for Java from our web site for evaluation. After installation they can simply start Glink for Java with user ADMIN, password ADMIN, and use Glink itself to add their own configurations.

User-specific modifications are deprecated

Note that the concept of user-specific modifications to configurations has been removed (it can be restored with a configuration option). A user without administrative privileges can only use existing configurations, as before. A user with administrative privileges can modify any configuration visible to him or her, and the changes in the configuration are visible to all users in groups where the configuration is visible. New configurations are added to the global group, so if the administrator wants to make a new configuration visible only to specific user groups then he or she must use the administration program to copy/paste the configuration (then delete it from the global group). The administrator can still create configurations in the old way, directly in the desired group, using the administration program.

New configurations are complete and unique

Configurations created directly from Glink are given their own complete set of sub-configurations (Hosts, Emulation, Keyboard, Screen, Printer and Toolbars), with the same name as the configuration. Deleting the configuration deletes all the sub-configurations with the same name.



This release of Glink for Java has new icons. These are graphical copies of the Glink for Windows icons, but are in a different colour (green).

(c) Copyright 1982-2019 Gallagher & Robertson AS. Webmaster: