On the machine where the HL key is connected: Requires Run-time Environment from Sentinel LDK v.6.4 or later On the machine where the HL key is connected: Requires Run-time Environment from Sentinel LDK v.6.3 or later On the machine where the HL key is connected: Requires Run-time Environment from same (or later) version that was used to protect the application Net and NetTime HL Keys Version of Licensing API or Envelope used to protect the application (lower of the two) Under Windows, use of Run‑time Environment (from Sentinel LDK v.7.0 or later) is optional. Requires Run-time Environment from Sentinel LDK v.7.0 or later Requires Run-time Environment from Sentinel LDK v.6.4 or later Requires Run-time Environment from Sentinel LDK v.6.3 or later
Requires Run-time Environment from same (or later) version that was used to protect the application HASP SRM, Sentinel HASP, or Sentinel LDK v.6.0 or v.6.1 HASP HL key or Sentinel HL (HASP configuration) key Standalone HL Keys Version of Licensing API or Envelope used to protect the application (lower of the two) The tables that follow summarize the requirements for working with HL keys. However, the requirement for the presence of the Run-time Environment does not change. The application will work correctly after the upgrade. >The Sentinel HL (HASP configuration) key that licenses the application is upgraded to the Driverless configuration. >An application is protected with version 6.3 or 6.4 of Sentinel Licensing API libraries and/or Envelope. >The key may no longer require the presence of Sentinel LDK Run-time Environment.Īll of the licenses and key memory that existed in the Sentinel HL (HASP configuration) key will continue to exist in the key after the upgrade. >The key is less subject to issues related to operating system upgrades.
Sentinel hl max drivers#
(HID drivers are an integral part of the operating system.) As a result:
In Driverless configuration, this key will employ HID drivers instead of HASP key drivers. Upgrading a Sentinel HL Key to Driverless ConfigurationĪ Sentinel HL (HASP configuration) key that was previously delivered to a customer can be upgraded to a Sentinel HL (Driverless configuration) key in the field. >Sentinel HL (Driverless configuration) standalone (non-Net) keys can be converted to Sentinel HL (Driverless configuration) network keys.Įach of these upgrades is described below. >Sentinel HL (HASP configuration) keys can be upgraded to Sentinel HL (Driverless configuration) keys. The configuration of Sentinel HL keys can be upgraded before or after delivery to customers as follows: