Installing the Run-time Environment
This section describes how to install or upgrade the Run-time Environment.
NOTE Given the following circumstances:
>You are installing or upgrading the Run-time Environment on the customer's machine.
> You want a placeholder for new SL keys for the relevant Batch Code to appear at the top of the Sentinel Keys page in Admin Control Center.
Distribute your current custom Vendor library along with the Run-time Environment installer.
CAUTION! If you downgrade the Run-time Environment to a previous version, license storage may become inaccessible. Licenses may be missing, and commands will fail with the HASP_DEVICE_ERR error. To recover, reinstall the latest Run-time Environment, although this may cause some licenses to be marked as "cloned".
To install or upgrade the Run-time Environment for Sentinel LDK or Sentinel HASP:
1.To support your application on both 32-bit and 64-bit architectures, ensure that you provide both 32-bit and 64-bit customized Vendor libraries with the Run-time Environment installer. These libraries are contained in the following files:
•haspvlib_<vendorID>.so
•haspvlib_x86_64_<vendorID>.so
•haspvlib_armhf_<vendorID>.so
•haspvlib_arm64_<vendorID>.so
2.Disconnect your Sentinel HL key (if any) from the computer.
3.Open a terminal window and navigate to the directory containing the downloaded installation file.
4.As root, enter the following command:
•For 32-bit ARM systems:
dpkg -i aksusbd_10.13-1_armhf.deb
•For 64-bit ARM systems:
dpkg -i aksusbd_10.13-1_arm64.deb
•For 64-bit Intel systems:
dpkg -i aksusbd_10.13-1_amd64.deb
5.Reconnect the Sentinel HL key (if any).
NOTE At this point, for older HASP HL keys, the firmware on the HL key may be automatically upgraded. During the upgrade process, the key will blink continuously. Do not remove the key while it is blinking. If you remove the key too soon, the key may no longer be visible in Admin Control Center. If the key is not visible, or if the upgrade does not occur, refer to Upgrading HASP HL Key Firmware.