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!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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.

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.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.
Mark
Answered 11/30/2006 by: mark_holland21
Fourth Degree Green Belt

Please log in to comment
0
Merge module or MSI you will have to be an administrator to install the device driver or have the MSI elevate its permissions. I think you can change the security policy on a PC to allow end users to install device drivers but that part of my memory is a little cloudy.
Answered 11/30/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Thanks kkaminsk,

I know that users must have administrator or evelated permissions to install a Device Driver but I've just had a thought..........

What if I was to install these Device drivers as an admin lets say. And then a user logs in under another (User) account and plugs in their hardware. Will the Device Drivers want to install again? Are they per user?

I don't have the luxury of having the hardware at hand so I can't answer those questions myself.

Any ideas?
Answered 11/30/2006 by: mark_holland21
Fourth Degree Green Belt

Please log in to comment
0
If it is USB / Firewire then you will have an admin present each time a device is plugged into a different USB port. Other than lowering the security to install a device driver you can have a desktop person show up and plug the device into each possible port before letting the user use the app. If the device will not be changing USB / Firewire ports then you should be able to install the device once.
Answered 11/30/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
What I meant by install once is that the administrator can install the driver and the user wont have to.
Answered 11/30/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity