Sentinel HASP^® (Formerly HASP SRM) Run-time Environment Installer GUI: Readme

This document provides information regarding the Sentinel HASP Run-time Environment Installer GUI, including supported operating systems and known issues.

Version 5.75 (November 2009)

Operating Systems Supported

• Windows Server 2008 R2
• 32-bit and 64-bit versions of the following:
• Windows 7
• Windows XP
• Windows Server 2003
• Windows Vista
• Windows Server 2008


• Windows 2000 (32-bit)


• Windows 98SE and Windows ME (for backward compatibility only)

Note: Windows XP Embedded is not supported with this installer. To install the Sentinel HASP Run-time environment on Windows XP Embedded, use the SLD file.

Installing the Run-time Environment

• The Installer GUI detects the version of the operating system during Run-time Environment installation, before installing the relevant drivers.



• By default, Windows 7, Windows Vista, and Windows Server 2008 operating systems display a User Account Control message during driver installation. The user must click Continue to continue the installation. Alternatively, the user can change the default setting from the Control Panel of their operating system.

Upgrading the Run-time Environment

When using the Installer GUI to upgrade the Sentinel HASP Run-time Environment, ensure that:

• No other Run-time Environment Installer is active.



• No other Run-time Environment components are active. Although the installation program terminates applications that are accessing the Run-time, it does not terminate running services. For example, if the HASP License Manager is running as a service, you must stop the service before upgrading the Run-time Environment.

Known Issues

Sentinel HASP Run-time

• Ref #5561: When you apply an update to a Sentinel HASP protection key, all currently opened sessions in HASP License Manager are disconnected. If you are using the Run-time Environment API, you need to log in again.
• Ref #3193: If the connection to a Sentinel HASP protection key is broken (for example, if a HASP HL key is disconnected), the login session is terminated. An error message is returned during subsequent API calls that use the previous handle. In your application code, you need to specify how the application should behave when the system detects a session has been disconnected. (For example, whether the application should continue running, stop running, require a new log in, and so on.)
  
  If you use Sentinel HASP Envelope, after clicking on the displayed error message, Sentinel HASP Envelope will automatically log in again and the protected software will continue to run correctly.

Sentinel HASP Admin Control Center

• Ref # 10168: In the event that cloning has been detected on an end-user machine and the user chooses to reformat the Sentinel HASP protection key in order to delete the disabled Products, Admin Control Center will continue to show the key as disabled. (Note: This occurs only when a Sentinel HASP protection key was reformatted following clone detection, not when the key has been cleared.)

Sentinel HASP Protection Keys

• Ref #5404: On computers with NVIDIA nForce4 chipsets the following may occur:
  • The driver is not loaded
  • The data read out of the key contains incorrect data
  Workaround: Connect a USB hub, and connect the HASP HL key to the hub.

Copyright:
© 2009 SafeNet, Inc., and/or Aladdin Knowledge Systems Ltd. All rights reserved.