List of HASPDINST.EXE (HASP HL Installer) Versions since 5.10 (July 2004) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This device driver installer supports the Win32 and Windows x64 platforms. The following list includes improvements, bug fixes, and other relevant information. It is arranged in descending chronological order. version 5.20 (October 2005) =========================== Problems Solved --------------- TD #2330: Driver installation failed when directly run from an installation CD. TD #2335: The haspdinst -r -cm command displays a message box after an uninstall is executed. TD #2224: DataHASP protected applications cannot open encrypted data if Symantec AntiVirus Corporate addition version 10.0.1.1000 (Scan engine version 220.127.116.11) is installed and running. -av and -noav switches have been added to workaround this issue: To install use haspdinst.exe -i -av. To uninstall use haspdinst.exe -r -noav. version 5.19 (August 2005) ========================== Enhanced to support Windows x64 operation systems. List of restrictions of the Windows x64 support: ------------------------------------------------ - Doesn't support HASP4 API of version lower than 8.0 - Enveloped files with DataHASP are not supported. - Enveloped files with Overlay are not supported. - PC-CardHASP (PCMCIA-based HASP) and Hardlock PCMCIA are not supported. Problems Solved (Windows 32bit): -------------------------------- TD#2063: Blue-screen under 64Bit Hardware and Windows XP SP2 32Bit with McAfee 8.0 Enterprise. TD#2052: When file size of aksdrvsetup.log was too big, the driver installer could hang due to heavy file access. TD#1994: Redundant copy of aksusb.sys was created in the %windows%\system32\setup\aladdin directory. TD#1968: Enveloped executables created by exe4j could't run with recent HASP drivers. TD#1948: Blue-screen on Windows 2003 SP1 when .NET applications Enveloped with IMAGE_EMULATION enabled attempted to run. TD#1928: On Windows Server 2003 SP1 with McAfee Anti Virus v8 installed, data encryption/decryption failed. TD#1925: Sporadic message "Can not install automatic data protection" when application was quickly restarted after termination. TD#1833: Sporadic DataHASP error 1025 "Unknown error" on Windows Server 2003. version 5.15 (April 2005) ========================= Problems Solved --------------- TD#1008: when logging in to parallel HASP4 NetHASP remotely,The API returns <keycaps>hardlock</keycaps> for this key. TD#1607: DataHASP does not work when AVG 7.0 Anti Virus is installed TD#1708: Driver crashes when running DataHASP protected programs on Win64 or Sempron machines with Win XP SP2 installed. TD#1842: When running DataHASP protected programs the protected program sometimes hangs when no HASP Key is plugged out during running. TD#1856: Programs protected with DataHASP may generate Blue Screens when an unexpected error occurs in the program. Wi#1796: DataHASP protected programs do not work in conjunction with McAfee Enterprise 8.0 when the buffer overrun McAfee protection is enabled. TD#1047: Wrong termination message when installing on Win 2000 operating systems. TD#1756: Add "-fi" switch to force installations when another running windows setup is detected. TD#1870: Avoid reboot requests on Win9x operation systems when no update is made. version 5.12 (Dec 2004) ========================= Drivers are also signed for Win2000 operating systems. Problems Solved --------------- TD #1557: solves Blue Screens when Norton Antivirus 2005 is installed Version 5.11 (Sept 2004) ======================== The drivers included support the HASP API version 8.0 onwards and all Hardlock API versions. In order to run HASP Applications with API versions before 8.0, you must also install the corresponding HASP driver for each API version. Problems Solved --------------- TD#303: Double generation of log files during installation. TD#405: Wrong copyright string. TD#503: Older device driver installations overwrote the newly installed HASP HL drivers. TD#524: Applications protected with overlay support crashed. TD#710: Obsolete dialog displayed during installation. TD#742: "Aladdin Knowledge Systems Key 00" instead of "Aladdin Knowledge Systems Key" in Device Manager. TD#826: Errors lacked error strings. TD#895: User not prompted to insert key during installation. TD#993: Win9X consecutive (legacy) logins to parallel keys failed. Version 5.10 (July 2004) ======================== Known Issues ------------ The driver installer, haspdinst.exe, does not install drivers on Windows NT 4.0 and Windows 95 platforms. HASP HL drivers are not available for DOS applications. To run protected DOS applications you must install the corresponding HASP driver. Under Windows XP, a HASP HL key must have been previously connected to the computer to enable haspdinst.exe to display the correct HASP HL drivers version. Under Windows 9x/ME, HL-Server won't detect Hardlock Server USB keys. You should install the required Hardlock drivers. When running the HASP HL driver installer in a Terminal Server environment, the aksdrvsetup.log file is generated in the current userís directory. Older device driver installations sometimes overwrite the HASP HL drivers. You should run the haspdinst installer (haspdinst.exe -i) to fix the HASP HL installation. This scenario is only relevant for Windows XP/2003 platforms. The current version of the drivers does not support applications wrapped with HASP HL Envelope with overlay encryption enabled. Should you attempt to start these applications, your system will crash and display a Blue Screen. If you use USB hubs which do not comply with all specifications of the USB standard, your Aladdin USB keys might occasionally lose their enumeration. If you plan to use USB keys on Microsoft platforms, refer to the Hardware Compatibility Lists at http://www.microsoft.com/whdc/hcl/default.mspx Some USB controllers cause Microsoft platforms to hang or display a Blue Screen. This problem is not related to Aladdin drivers. There are known limitations with various PCMCIA card reader brands used on AMD64 platforms. Check for chipset compatibility in the hardware specifications provided by the manufacturer the of card reader. Due to a problem with the hardware of the PCI crypto programmer card, in some cases a Hardlock key will be recognized on the CPC address, however, encryption and read/write memory functions will fail. To avoid this problem, you should explicitly set the address where to search for the Hardlock key. Trademarks ---------- Aladdin Knowledge Systems Ltd. (c) 1985 - 2005. All rights reserved.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.