Installing a new FLEXid USB keylock and drivers

If your Active-HDL, Riviera-PRO, ALINT, HES/DVM or Netlist Converter license is issued for a USB FLEXid keylock or dongle (license file contains reference to "flexid=9" or "flexid=10" in the server line), installing the drivers may be necessary. Read Verifying Driver Installation below to check if you need to install the driver.

NOTE: USB FLEXid keylocks are labeled with a FLEXid number, in the format FLEXid=9/10-xxxxxxxx, where x is a hexadecimal number. The FLEXid=9 (HASP) keylock is green, and the FLEXid=10 (WIBU) is blue, as shown below:

Figure 1. USB keylocks

Drivers

Drivers can be obtained from the following locations:

Platform

FLEXid

Download Location

Red Hat® and SUSE® Linux 32/64-bit

9

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/aksusbd-redhat-suse-2.5.1.tar.gz

Debian, Ubuntu, and CentOS Linux 32/64-bit

9

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/Sentinel_LDK_Linux_Run-time_Installer_script.tar.gz

Red Hat®, CentOS, and SUSE® Linux 32-bit

10

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/Sentinel_LDK_Linux_Run-time_Installer_script.tar.gz

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/libhasp_linux_i686.so

Red Hat®, CentOS, and SUSE® Linux 64-bit

10

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/WkRt-Lin-6.30.1454-500.x86_64.rpm

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/libhasp_linux_x86_64.so

Microsoft® Windows® 32 bit

9

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/FLEXID9_Windows_v6_65_i686.zip

Microsoft® Windows® 64 bit

9

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/FLEXID9_Windows_v6_65_x64.zip

Microsoft® Windows® 32 bit

10

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/FLEXID10_Windows_v6_30_i686.zip

Microsoft® Windows® 64 bit

10

ftp://reguser:reguser@ftp.aldec.com/drivers/11.13.1/FLEXID10_Windows_v6_30_x64.zip

NOTE: Please refer to fnpdig.pdf for installation instructions.

Windows

FLEXID10 (Blue)

  1. Simply double-click "Setup.exe" and complete the wizard. All default settings and options are acceptable.

FLEXID9 (Green)

Windows 10

  1. Open a command prompt (cmd.exe) and navigate to the extracted flexid driver folder

    64-bit

    • Copy "haspsrm_win64.dll" to %windir%/System32

    • Copy "haspsrm_win32.dll" to %windir%/SysWOW64

    32-bit

    • Copy "haspsrm_win32.dll" to %windir%/System32

  2. Execute command: haspdinst -i

Windows 7

  1. Right-click the install script (Install.bat) and select "Run as administrator"

  2. If the dongle is still not recognized

    64-bit

    • Copy "haspsrm_win64.dll" to %windir%/System32

    • Copy "haspsrm_win32.dll" to %windir%/SysWOW64

    32-bit

    • Copy "haspsrm_win32.dll" to %windir%/System32

Linux

(64-bit) - Place libhasp_linux_x86_64.so into /usr/lib

(32-bit) - Place libhasp_linux_i686.so into /usr/lib

FLEXID10 (Blue)

Debian, Ubuntu

64-bit

  1. sudo alien WkRt-Lin-6.30.1454-500.x86_64.rpm

  2. sudo dpkg -i wkrt-lin_6.30.1454-501_amd64.deb

32-bit

  1. tar -xzvf Sentinel_LDK_Run-time_Installer_script.tar.gz

  2. tar -xzvf aksusbd-2.2.1-i386.tar.gz

  3. ./dinst

RedHat, SUSE, CentOS

64-bit

  1. rpm -i WkRt-Lin-6.30.1454-500.x86_64.rpm

32-bit

  1. rpm -i WkRt-Lin-6.30.1454-500.i386.rpm

FLEXID9 (Green)

Debian, Ubuntu, CentOS

64-bit and 32-bit

  1. tar -xzvf Sentinel_LDK_Linux_Run-time_Installer_script.tar.gz

  2. tar -xzvf aksusbd-2.2.1-i386.tar.gz

  3. ./dinst

RedHat, SUSE

64-bit and 32-bit

  1. tar -xzvf aksusbd-redhat-suse-2.5.1.tar.gz

  2. rpm -i aksusbd-2.5.1.i386.rpm

Verifying Driver Installation

To verify the driver installation on Linux or Windows, invoke the lmutil program with the following parameters:

./lmutil lmhostid -flexid

If the driver is installed correctly you should see the message as shown below: The FLEXlm host ID of this machine is "FLEXID=9-a2b2c845" or "FLEXid=10-0bebc48a".

The lmutil tool can be downloaded from this location: ftp://reguser:reguser@ftp.aldec.com/drivers/lmutil.zip

Ask Us a Question
x

Ask Us a Question

x
Captcha ImageReload Captcha
Incorrect data entered.
Thank you! Your question has been submitted. Please allow 1-3 business days for someone to respond to your question.
Internal error occurred. Your question was not submitted. Please contact us using Feedback form.