List of HASP4 and Hardlock MSI driver install sample since Version 4.96 (Dec 2004)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The following list includes improvements, bug fixes, and other relevant
information regarding the HASP HL installer. It is arranged in descending
chronological order.
Supported environments:
-----------------------
Wise for Windows Installer Versions 4.21 and 5.21.
InstallShield Professional Version 10 and newer.
Operating systems: Windows 98SE, Windows ME, Windows 2000, Windows XP,
Windows Server 2003, Windows XP x64, Windows Server 2003 x64.
Version 4.99.5.20 (October 2005)
================================
Problems Solved
---------------
TD#820: Sporadic installer failures returned the following error message:
"Failed to start Aladdin Device Driver. Failed to start a service in the Service Control Manager Database"
TD#2330: Driver installation failed when run directly from an installation CD.
TD#2337: PC Card drivers failed to update on Windows Server 2003.
TD#2366: PC Card drivers failed to update or install on Windows 2000.
Version 4.98 (September 2005)
=============================
New Features
-------------
Enhanced to support Windows x64 operation systems.
Known Issues
------------
TD#2224: Protected Programs with either the Envelope's overlay support or data file protection enabled,
cannot open encrypted data when Symantec AntiVirus Corporate Edition version 10.0.1.1000
(Scan engine version 51.1.0.15) runs in the background. This pertains to the Windows 32-bit
platform.
Workaround - Download and install the following file from Aladdin's FTP site
ftp://ftp.ealaddin.com/pub/hasp/support/kb_files/SAV_10.zip
All items listed below pertain to Windows 64-bit platforms.
Does not support HASP4 API versions older than version 8.0.
Data files cannot be protected using the Envelope program.
No overlay support for applications protected with the Envelope program.
No support for PC-CardHASP (PCMCIA-based HASP) and Hardlock PCMCIA.
Problems solved
----------------
All items listed below pertain to Windows 32-bit platforms.
TD#2063: Blue screen displays when using 64-bit Hardware on
Windows XP SP2 (32Bit) with McAfee 8.0 Enterprise running in the background.
TD#2052: When the size of the aksdrvsetup.log file was too big, the driver installer suspended.
TD#1994: Redundant copy of aksusb.sys created in the %windows%\system32\setup\aladdin directory.
TD#1968: Java programs converted to executables with exe4j once protected with Envelope could not
run with recent HASP drivers.
TD#1948: Blue screen displayed on Windows 2003 SP1 when running .NET applications Enveloped with
IMAGE_EMULATION enabled.
TD#1928: Data encryption/decryption failed on Windows Server 2003 SP1 with McAfee Anti Virus v8
installed.
TD#1925: Message "Can not install automatic data protection" displayed when application was restarted
immediately after termination.
TD#1833: Data protection error - "Unknown error" - displayed on Windows Server 2003.
TD#1008: When remotely logging to parallel HASP4 Net key, the API returns a hardware mismatch.
TD#1607: Data files cannot be protected when AVG 7.0 Anti Virus is installed.
TD#1708: Driver crashes when running encrypted data files for protected programs on
Win64 or Sempron machines with Win XP SP2 installed.
TD#1842: When running encrypted data files for protected programs, the program sometimes suspends when
key is unplugged.
TD#1856: Protected programs with encrypted data files crash due to a threading error.
TD#1796: Protected programs with encrypted data files do not work with McAfee Enterprise 8.0 when the
overrun McAfee protection buffer is enabled.
TD#1047: Incorrect termination message when installing on Win 2000 platforms.
TD#1756: Cannot install drivers when another running windows setup is detected.
TD#1870: Reboot request even no update performed on Win9x platforms.
Version 4.96 (Dec 2004)
=========================
New Features
-------------
Drivers signed for Windows 2000 platforms.
Problems Solved
---------------
TD#1557: System crash when Norton Antivirus 2005 is installed and running.
TD#303: Double generation of log files during installation.
TD#405: Incorrect 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" appears instead of "Aladdin Knowledge Systems Key"
in Device Manager.
TD#826: Error messages lacking error strings.
TD#895: User not prompted to insert key during installation.
TD#993: Repeated logins on Win9X to (legacy)parallel keys failed.
Known Issues
------------
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
pertinent to 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.