I've packaged several hardware driver packages using this procedure and it's worked a treat.

This time is different. Why?

The problem, I think, is that the driver files are in separate subfolders from the INF/CAT files. As the author of the aforementioned article states, the drivers and INF file must be in the same folder. However, i was told by the vendor and confirmed by experimentation, that altering the INF file as suggested in the article BREAKS the signature, and you get the unsigned driver warning.

So what I need is a way to script the driver install after the the files are on the machine. (manually pointing to the folder where the INF files are works fine). I've tried dpinst.exe and devcon.exe without any luck, devcon.exe says failed and dpinst.exe just sits there and does nothing as far as I can tell. rudll32?

thanks!
Owen
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

Answer this question or Comment on this question for clarity