HASP SRM Run-time GUI Installer: Readme

The list below includes new HASP SRM Run-time features, improvements, issues addressed, and other relevant information.

Note:

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

Upgrade Note

When upgrading the HASP SRM Run-time Environment Installer, ensure that it is not currently being used by any Run-time components. 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 Installer.

Version 5.70 (May 2009)

Supported Platforms

Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 (32-bit and 64-bit)

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 HASP SRM Run-time environment on Windows XP Embedded, use the SLD file.

Note:

By default, 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.

Known Issues

HASP SRM Run-time

Ref #5561: When you apply an update to a HASP SRM 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 HASP SRM 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 HASP SRM Envelope, after clicking on the displayed error message, HASP SRM Envelope will automatically log in again and the protected software will continue to run correctly.

HASP SRM 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 HASP SRM 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 HASP SRM protection key was reformatted following clone detection, not when the key has been cleared.)

HASP SRM 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.

0509_1