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

Installer Version 6.25

Package Version 6.25

May 2012

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 2008 R2

Notes

• Windows XP Embedded is not supported with this installer. To install the Run-time environment under Windows XP Embedded, use the SLD file.



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

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 environment, overwrite the haspdinst.exe file in
  ...\Program Files\SafeNet Sentinel\Sentinel LDK\Redistribute\Runtime Environment\cmd Install\ with the file in this package.

• By default, Windows Vista, Windows Server 2008, and Windows 7 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.

Compatibility Issues

• Run-time Environment may be incorrectly reported as a virus by Control Guard Agent version 4.0.0.27. If this occurs, update to a later version of Control Guard Agent.



• Run-time Environment may be incorrectly reported as a virus by SkyRecon StormShield Agent version 5.6. If this occurs, contact SkyRecon support to determine if a fix is available.

Known Issues

• MKS159048: A user who converts an MBR disk to dynamic or vice-versa must reboot the computer before installing the Run-time Environment.

Issues Resolved

• US147632: Admin Control Center would display HASP keys that were not provided by SafeNet.



• US157306: Known compatibility issues are now listed in the Run-time Environment readme file.



• US126998, CASE1335: When the end user applied an update for one Product, multiple unexpected Products were added in the
Admin Control Center. In addition, when the ISV checked in a C2V file from the end user, duplicate Features relating to the Product were added in Business Studio.


• US150843, MKS132920: Expired detached licenses would continue to be displayed in Admin Control Center for 7 days. You can now customize Admin Control Center to display these licenses for 0 to 9999 days. In the hasplm.ini file, add or locate the parameter commuter_delete_days = and assign it the number of days to display expired licenses. If you specify 0, an expired detachable license entry is deleted within a few minutes after it expires.



• US148372, MKS142453:When a computer with an active protected application and attached HL was set to hibernate, and the HL key was then detached, the computer would freeze upon being restarted.



• US153304, MKS152843: An error would occur when running an RTE installer that includes a Provisional Product.



• MKS154755, 154375, 153944, 152449, US158710: hasplms.exe would fail, sometimes showing an Access Violation error in the system log.



• MKS147694: When a modification is applied to decrease the concurrency count, it was still possible to extend the duration of detached licenses even though the number of detached licenses exceeded the maximum allowed.



• MKS147644: The License Manager would lose track of the number of detached licenses for a given Product when a modification is applied to add a new detachable Feature.



• US144668: Under Windows XP, a protected application that is linked with Runtime API v.5.0, and is running in Run-time Environment v.5.95 or later would fail with "Communication Error 33" after several hours of activity.



• Ref #8033: If you attempted to update the Sentinel HASP Run-time, and your protected application uses DataHASP, it was necessary to close the protected application before running the update. (Resolved in version 6.22)



• MKS146944, 147038: The License Manager would eventually lose track of the number of detached licenses for a given Product if the number of available licenses for that Product was changed to a value lower than the number of licenses currently detached. (Resolved in version 6.23)

Copyright © 2012 SafeNet, Inc. All rights reserved.