Copyright: Copyright © 1996, Attachmate Corporation. All Rights Reserved.


Release Notes

You can run this version of KEA! under:

•	Windows 95

•	Windows NT version 3.51 or greater.

Some important information and changes in KEA! Version 4.23 are noted in this file. Except where otherwise noted, please refer to the online help for more detailed information.

Installing KEA!

Installing KEA!

Using an LK450 Keyboard with Windows 95

A Note About Protecting Files on a Server

New Features in Version 4.23

OLE Automation

ANSI Locator Mode

Host Connections

Tektronix Overwrite Option

New Registry Options

Using KEA! with the Enterprise Access Library

Enterprise Access Library

Cautions

Restriction on Macro Naming

Printing in Printer Controller Mode

Errors and Omissions in the Manuals

KEA! User's Guide

Installing KEA!

Installing KEA!

In a multi-user environment, there are several methods for installing KEA!; each one might have advantages in your organization. In addition, the System Administrator can customize KEA!'s SETUP program to suit specific requirements. The Installation Guide included in your KEA! package describes the methods for installing KEA! in both single- and multi-user environments.

Using an LK450 Keyboard with Windows 95

If you use an LK450 keyboard with Windows 95 and KEA!, you can use the KEA!-supplied LK450 keyboard driver. This option is not available if you are using Windows NT.

To install the LK450 Keyboard driver

1	In the Windows Control Panel, double-click the Keyboard icon.

2	Select the General tab, then click Change.

3	Select Show All Devices, then click Have Disk.

4	Type the path to the KEYBOARD\LK450 directory on your KEA! disk.

5	In the WIN95\KEYBOARD\LK450 directory, select KEYBOARD.INF.

Note  You can use the macro file LK450DRV.KTM (located in the same directory) to automatically map VT terminal functions to LK450 keyboard keys. From the KEA! Macro menu, choose Run. This macro replaces existing mapping for the specified keys. The new keyboard mapping is saved when you save your session.

Protecting Files on a Server

If you are preparing KEA! files on a file server for installation by multiple users, the Installation Guide tells you to make the files shareable and read-only. The following notes describe how to do this for some particular networks.

DOS-based networks

All files in the shared directory must be read-only. Set the DOS file attributes to READ-ONLY as follows:

attrib +r *.*

Digital Pathworks

KEA! supports Version 4.0 and above, and PCSA. All files in the shared directory must be read-only. Place files on a read-only device, or set the DOS file attributes to READ-ONLY as follows:

attrib +r *.*

Sometimes VMS attributes are not set at the same time. Use the DCL command SET PROT as follows:

set protection=(o:re,g:re,w:re)  *.*

Novell NetWare

All the files in the shared directory must be shareable and read-only. Change the current directory to the shared directory and issue the command:

flag  *.*  sro

-or-

flag  *.*  shro  /fo

New Features in version 4.23

OLE Automation

KEA! now provides an OLE Automation interface, a Microsoft Windows standard for inter-program communications. As an OLE Automation server, KEA! exposes programmable objects like Session, Screen, Connectivity, FileTransferScheme, and Wait, whose built-in functionality can be accessed by user-written applications. For example, you could write an Excel program that uses functions in KEA! to obtain changing host data and applies Excel's analysis functions to the data.

To access automation-enabled objects, you must use a macro or programming language that supports OLE Automation, such as C++, Microsoft's Visual Basic 3.0 or later, and Visual Basic for Applications (as used by Word, Access, and Excel).

Multiple Applications Waiting on One KEA! Session.

There is a known anomaly when multiple client applications access a single KEA! session. If two clients call a wait-type object's Wait method on the same session, the wait period of the second call must be satisfied before the first call returns a value.

ANSI Locator Mode

This version of KEA! supports ANSI Locator Mode. When the host enables ANSI Locator mode, you can specify screen locations and send locator position reports back to the host.

Host Connections

KEAlink LAT

KEA! supports KEAlink LAT for Windows 95 and KEAlink LAT for Windows NT, which use DIGITAL's Local Area Transport network protocol for terminal access over Ethernet. If you want to use a LAT connection, you must install LAT network software on your personal computer.

KEAlink MSU

This version of KEA! supports KEAlink MSU  version 1.10 or later. KEA! no longer supports earlier versions of KEAlink MSU.

In order to use KEAlink MSU, you must install it after you install KEA!

Note  When installing KEAlink MSU with Windows 95, you must run Setup from the Windows subdirectory of the distribution disk. Do not run Setup from either the NT subdirectory or the root directory of the MSU installation disk.

NetWare for DEC Access

When making a NetWare for DEC Access network connection, in the Communications dialog box under Port Type, select NetWare for LAT.

Proxies

As a component of network security, a proxy acts as an intermediary and limits access to servers outside your internal network. This version of KEA! supports the use of FTP, Telnet, and SOCKS version 4.0 proxies.

Tektronix Overwrite Option

A new Tektronix Overwrite option has been added in the Graphics Dialog box. If, under Overwrite, you select Destructive, existing characters (including spaces) are erased before the area is overwritten.

New Registry Options

UseSystemCursor

You can override KEA!'s default cursors and use the Windows cursors you have selected by adding a value to the Windows Registry database.

NewScrollBars

If you are using Windows NT 3.51 without the New Shell, you can change the appearance of your KEA! scrollbars to the newer Windows 95 scrollbars by adding a value to the Windows Registry database.

Enterprise Access Library

Programs written in Visual Basic, PowerBuilder, Delphi, C, or any language that can access a .DLL can use the Attachmate Enterprise Access Library (EAL) functions to communicate with KEA! 4.23. The EAL functionality has been updated to use the OLE2 support now available in KEA!. It is now easier to install and much faster in execution than the previous version.

When you install KEA!, the files KHLLAPI2.DLL and ATMAPI32.DLL are copied to the Windows\System directory where they are accessible to any program that uses the EAL. If you do not want to leave them in Windows\System directory, you can copy these .DLLs to the current directory of the running program, or any directory where the program can find them.

Installation

You should run KEA! once before first using it with the EAL. This completes some required registry entries.

The XTOOLS.KTM macro is no longer needed and no startup macro needs to be specified on your EAL sessions.

Note  The KHLLAPI2.DLL supports the WinHLLAPI interface and the Attachmate WinHLLAPI (HLL_xxx functions) in addition to EAL functions.

Function Changes

Field Functions:

Some field functions that previously returned ATM_UNSUPPORTED (-10) now return a value. This is based on a default assumption that a 24 row-80 column screen contains 24-80 column fields. These functions are:

ATMGetFieldLength

ATMGetFieldInfo

ATMGetStringFromField

ATMGetFieldPosition

In prior versions of EAL, the function ATMGetKeyStroke returned a minimum value of 6; if there were fewer characters in the key stroke buffer, the buffer was padded with spaces to a length of six bytes. In this version, the buffer is not padded and the returned value can be as low as 2. For example, if the "x" key is pressed without Shift or Ctrl, the buffer contains the string "Ax" and the function returns the value 2. (The "A" code in the string indicates ASCII.)

ATMGetATMAPIVersion returns 1 and a string of "6.10" instead of 4 and a string of "6.11".

ATMGetEmulatorPath now returns the complete path for the KEA\USER\ directory, including the drive letter and final back slash.

Cautions

Restriction on Macro Naming

If you write a macro and give it a name that happens to match a command on the KEA! menus, you cannot directly assign that macro to a SmartPad button, keyboard key, or mouse button. Unfortunately, not all the commands "on the KEA! menus" are evident by looking at the menus; there are additional hidden command names which exist to provide compatibility with earlier KEA! versions.

To get around this restriction, instead of assigning the macro name directly to a key or button, you can assign a macro Run statement in the Value box of the Keyboard Mapping, SmartPad, or Mouse dialog box. For example, when either of the following strings is used in the Value box, the macro file MYMACRO.KTM is assigned to the key or button:

mymacro.ktm

Run("mymacro")

Two of the macros supplied with KEA! cannot be directly assigned for this reason: KERMIT.KTM, a sample macro and SHUTTLE.KTM, a system macro which implements part of the Shuttle command. If you have a need to assign these, do so using the macro Run statement.

Printing in Printer Controller Mode

If you encounter problems when printing in Printer Controller mode (Printer dialog box), it might be because the host does not generate output in a form the printer can accept (for example, a PostScript printer). In the Printer dialog box if you also select Emulate ANSI Printer KEA! assumes the host sends LA210 ANSI printer sequences and translates them to equivalent Windows printer functions. Otherwise, KEA! assumes the host is configured for the printer you are using, and sends all data to the printer without translation.

Errors and Omissions in the Manuals Printed April 1996

KEA! User's Guide

Chapter 4, Transferring Files does not describe the New Host Type dialog box. You can use the options in this box to define new Host Types to be displayed in the drop-down list in the FTP Host Options dialog box.

p 105  FTP Options dialog box, Passive Mode Transfers option states that the default is selected, which is incorrect. The default is not selected (Active Mode). If you transfer files using an FTP Proxy, you should select Passive Mode Transfers.

p.157-159  The notes state that in order to compose a character, the character must be in the currently selected User-Preferred Character Set. That is not exactly correct; the character must be in the currently selected character set (either Multinational or National). For more information, refer to the Terminal General dialog box option descriptions in the online help.

p.252-253 under Editing the Windows Registry, the User's Guide provides separate procedures for Windows 95 and Windows NT if you want to add a new value to the Registry. The first procedure should be for Windows 95 and Windows NT 4.0, and the second for Windows NT 3.51 only. In addition, the equivalent online help topic provides examples. You should use these procedures only if you are familiar with the Windows Registry Database.


Definition of PRODNAME bookmark:KEA!

Definition of SHORTNAME bookmark:KEA!

Definition of EDITNAME bookmark:KEA! Edit