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. snapshpt and then using my knowledge of packaging device drivers to ensure the relevant. I am contemplating packaging the Device Driver i.e. I have downloaded the latest driver hdinst.exe from the Aladdin website and know that the switches for installing and uninstalling are -install and. Visit this link to learn how to install these Aladdin. 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? While these USB drivers are basic, they support the primary hardware functions. 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. To login via the Aladdin Connect app, you must have first signed up for your Aladdin Connect account via an internet browser. 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 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. I am packaging an application at present that has a requirement for a dongle - hence the Hardlock Device Drivers.
0 kommentar(er)
