Hi all, I am packaging an application at present that has a requirement for a dongle - hence the Hardlock Device Drivers. I have downloaded the latest driver hdinst.exe from the Aladdin website and know that the switches for installing and uninstalling are '-install' and '-remove' respectively. However, it has come to my attention that there are other applications in the company that use these same drivers, therfore I see a problem. I was going to just include the exe as a Custom Action with the relevant command line but when i remove my msi it will remove the drivers which could potentially break any other applications that are using the hardlock device drivers.

Has anyone ever had to deal with this same scenario, and if so, what did you do? Or has anyone any information on what to do with Hardlock Device drivers? I am contemplating packaging the Device Driver i.e. Snapshpt and then using my knowledge of packaging device drivers to ensure the relevant.inf and.sys files are copied to the correect locations but i am hesitant to do this as i have heard of issues with this in the past. Thanks in advance! Hi all again, I've been onto Aladdin, the company that provides the driver and they have supplied me with a sample msi that inlcudes an msm that they have created that installs the hardlock device drivers.

Repair Matroska File Structure. Download the latest driver installer. How to install HASP driver. (You might need to wait till the 'found new hardware' pop-up will approve using the device).

My only worry is that the user may have to have administrative rights to install the drivers. I will do some investigating but hopefully this merge module will answer all my questions. P. Aiv Editor Stronghold Crusader 3 more. S This is the location of the latest Device Driver in zip format and the MSI version in zip file.

Ftp://ftp.aladdin.com/pub/aladdin.de/hardlock/hldinst.zip ftp://ftp.aladdin.com/pub/aladdin.de/hardlock/Hardlock_driver_MSI.zip Cheers.