# Sentinel® LDK and Sentinel HASP® Run-time Environment Command-line Installer: Readme

## Installer Version 6.60

## Package Version 6.60

### August 2013

This document provides information regarding the Run-time Environment Command-line Installer for Sentinel HASP and Sentinel LDK, including enhancements and limitations. Using this installer, you can test HASP4, Hardlock, Sentinel HL, Sentinel HASP, and Sentinel LDK under any of the supported operating systems. ("Sentinel LDK" is the next generation of the Sentinel HASP system.)

## Operating Systems Supported

- Windows XP (32-bit and 64-bit)
- Windows Server 2003 (32-bit and 64-bit)
- Windows Vista (32-bit and 64-bit)
- Windows 2008 (32-bit and 64-bit)
- Windows 7 (32-bit and 64-bit)
- Windows 8 (32-bit and 64-bit)
- Windows 2008 R2
- Windows Server 2012
- Windows XP Embedded standard (x86 only)
- Windows 7 Embedded standard SP1 (x86 only)

The latest service packs and security updates must be installed.

Note: The installer detects the version of the operating system at run-time, before installing the relevant drivers.

## What's New in This Release?

Support has been added for Windows XP Embedded and Window 7 Embedded.

## Changes in Terminology

Sentinel Admin Control Center user interface and help files incorporate changes in terminology as follows:

- The Sentinel HASP product is now referred to as Sentinel LDK.
- SL keys that were created with Sentinel HASP Business Studio now appear in the user interface as "SL-Legacy" keys.
- References to Sentinel EMS in the help files are also valid for Sentinel HASP Business Studio.

## Installation

- Type `haspdinst.exe -?` for command-line help.
- To use Sentinel EMS to produce Run-time Environment installers in the Sentinel LDK v.6.0 or later environment, overwrite the `haspdinst.exe` file in
  %SystemDrive%\Program Files (x86)\SafeNet Sentinel\Sentinel EMS\EMSServer\webapps\ems\haspTools\ with the file in this package. (For Win32 systems, go to \Program Files\...)
- A log file of the installation process is written to aksdrvsetup.log in the Windows directory.

Note

- By default, Windows Vista (and later) operating systems display a User Account Control message during driver installation. Users must click Continue to continue the installation. Alternatively, users can change the default setting from the Control Panel of their operating system.

## Upgrade Notes

- When upgrading the Run-time Environment, ensure that it is not currently being accessed. Although the installation program can terminate applications that are accessing the Run-time, it cannot terminate running services.
- If you are running HASP License Manager (HASP4 and HASP HL legacy License Manager) as a service, you must stop the License Manager before proceeding with the installation.

## Accessing Admin Control Center in Internet Explorer Metro Mode

Under Windows 8, Internet Explorer 10 can be operated in "desktop" style or "Metro" style. When users attempt to access Admin Control Center for the local License Manager in the Metro style browser, they get the message "This page can't be displayed". (This problem does not occur when a user attempt to access Admin Control Center for a remote License Manager.)

To access Admin Control Center for the local License Manager under Windows 8 with Internet Explorer 10, the user must do either of the following:

- Operate Internet Explorer in desktop style:
  1. After you receive the message "This page can't be displayed" in Metro style, click the wrench icon at the bottom right of the browser window.
  2. Click View on the desktop. Admin Control Center is displayed.
- Enable Internet Explorer to access Admin Control Center in Metro style:
  1. After you receive the message "This page can't be displayed" in Metro style, click the wrench icon at the bottom right of the browser window.
  2. Click View on the desktop. Admin Control Center is displayed.
  3. Click the cogwheel ("Tools") icon at the top right of the browser window. From the menu, select Internet options > Security. Select the Trusted sites zone. Click the Sites button.
  4. "http://localhost" is already filled in. Click Add. Close the screen.

## Compatibility Issues

- When Control Guard Agent version 4.0.0.27 is present on a computer, installation of the Run-time Environment will cause the operating system to crash. If this occurs, update to a later version of Control Guard Agent.
- When SkyRecon StormShield Agent version 5.6 is present on a computer, installation of the Run-time Environment will cause the operating system to crash. If this occurs, contact SkyRecon support to determine if a fix is available.

## Issues Resolved in This Release

Reference | Description
--- | ---
LDK-2119 | After cancellation of an SL AdminMode license on a machine, Features would disappear from other Products and become unusable.
189473 | Under certain circumstances, the License Manager would fail with HTTP scanners.
LDK-1892 | For a "6to4" IPv6 address, network licenses would not be available (disconnect from the NetKey) after a short period. Now the License Manager scans the network interfaces to detect local IP addresses, similar to the RuntimelessAPI. The License Manager no longer asks for the DNS.
LDK-1683 | Product names displayed in Admin Control Center were different from the names specified at creation time. Product names are now handles as follows:

- Names provided within a license container (for example, a V2C file) are valid just for that container.
- Names provided manually in a vendorid.xml file always override those container names, retaining backward compatibility (for examples, for translations)
- vendorid.xml files are never overwritten by the License Manager, so different names for licenses on different machines are no longer mixed up

LDK-2052 | When the login to a Feature would fail, the log file would not contain the username, hostname, FeatureID (and haspid, if specified in scope) .
LDK-2718 | Under certain circumstances, Sentinel HL (Driverless configuration) keys did not appear in Admin Control Center.
LDK-1965 | Under certain circumstances, a protected application under Windows 7 would cause a "Key not found" error.
LDK-2235 | False positive VM detection would occur on a physical machine that had a Hyper-V virtual machine.
LDK-2107 | A reference finger print would not contain the NIC_UID value when the NIC address has an OUI (Organizational Unique Identifier) value of “00:50:56:XX:YY:ZZ” OR “00:05:69:XX:YY:ZZ”. These OUIs (“00:50:56” OR “00:05:69”) are assigned to VMWare, and are used by VMWare when the NIC address for a VM guest m/c is manually generated.
LDK-1175 | Intermittent H0043 errors would occur when a USB camera was connected to the machine.
LDK-2564 | Under certain circumstances, the bundled RTE installer created using Sentinel EMS would fail.
LDK-1194 | Under certain circumstances, termination of a protected application would cause a Stop error.
LDK-2502 | When using RTE version 6.56: After logging off and then logging on to the machine, a HASP 4 key was not detected.
LDK-2240 | Under Windows XP, when installing haspdinst v.6.51 or 6.55 on an HP 8200 ELITE SFF machine, a stop error would occur.
LDK-2074 | The RTE installer would not add the registry entry “HKLM\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers" if it was not present. As a result, end users would received Error 16 (Inconsistent Filesystem Structure) errors during RTE installation.
LDK-2034 | Licenses that were installed with a bundled RTE were not visible in Admin Control Center if a branded RTE had been first uninstalled and then uninstalled.
LDK-2428 | When a proxy server is used, Admin Control Center was not able to obtain language packs automatically.
LDK-3014 | When no HL key is connected to a machine, the driver package version was shown as as 0.0.

## Issues Resolved in Version 6.56

- 170463: When the user attempted to install MicroSoft Office 2010 on a computer that contains the Run-time Environment, the installation would fail and display an "Error 1046" message.
- 185897: Run-time Environment v6.55 would not recognize a HASP HL key with Firmware v2.16. The key would not be displayed in Sentinel Admin Control Center.
- 186197: When an application is protected with "Enable data file encryption" selected in Sentinel LDK Envelope, and file extensions are added in the filter, it was not possible to save the encrypted files to a network location.

## Issues Resolved in Version 6.55

- MKS177499: Under Windows 7 64-bit, protected application process would not exit from the Task Manager after closing.
- MKS180520: A Stop message (BSoD) would occur while running a DataHASP protected application when Norton Internet Security is installed.
- MSK79112: A delay would occur in obtaining the current remaining executions count when using the Licensing API hasp_get_sessioninfo() call soon after the hasp_login() call.
- MKS177029: The NX flag for hasplms.exe was not enabled.
- MKS178460: LM ID content of the LM Server whose information has not been refreshed for a long time would not be shown when more than 512 LM servers exist.
- MKS168507: If the HL key was changed while a machine was sleeping, then afterwards the License Manager would show that the original HL key is still present. The new HL key would not be recognized and would not work.
- MKS175770: hasplms.exe would crash and record an Access Violation error in the system log.

## Issues Resolved in Version 6.50

- MKS160209: When installing the Run-time Environment under Windows Server 2008 x32 JP, the system would crash.
- MKS170889: Irrelevant "func_0" entries have been removed from the Admiin Control Center access log.
- MKS167561: When using "Aggressive Search" in Admin Control Center, if you enter the machine's own name in the search parameters, the License Manager fails to detect the local keys.

## Known Issues - Runtime Environment Installer

Reference | Description
--- | ---
Ref#8475 (LDK-2196) | When you attempt to integrate the Sentinel LDK Run-time Environment Installer MSM module in your Windows Vista installation package, a warning may be displayed. This is a known issue for the Installer, and the message can be ignored. For more information about this issue, go to this URL.

## Known Issues - Run-time Environment

Reference | Description
--- | ---
12506 | Sentinel LDK communicates via TCP and UDP on port 1947. This port is IANA-registered exclusively for this purpose. At the end user site, the firewall must be configured so that communication via this port is not blocked.
180256 | When a computer names contains UTF-16 characters, Admin Control Center displays the short name for the computer (similar to Windows Explorer). Similarly, the sntl_admin_get function in Admin API returns the short name.
182646 | After Windows 7 is upgraded to Windows 8, the user is not able to use existing SL licenses or to install new SL licenses. Workaround: After you upgrade from Windows 7 to Windows 8, reinstall the Run-time Environment.
LDK-2471 | Sentinel Licensing API: On a computer with the Nvidia chip set GeForce 7025/nForce 630a, and where the CPU is AMD Athlon 64 X2, the hasp_read and hasp_encrypt functions may fail with error 39, HASP_BROKEN_SESSION. This problem only exists with Sentinel HL keys with Firmware version 3.25.
Workaround 1: On the computer described above, when error 39 is returned, call the hasp_read or hasp_encrypt function again. It is not necessary to call hasp_login again.
Workaround 2: Use Sentinel HL keys with Firmware version 4.2x.

Copyright © 2013 SafeNet, Inc. All rights reserved.

DocID 129j Revision 1308-1