I have not worked with callout drivers, but your comment that the INF does
not have a SourceDisksName section and yet you get a file not found error
implies that the Class setup application processing the INF file is trying
to do a file copy. In looking on msdn at "INF Files for Callout Drivers" i
While I am not doing what you are doing, and I have a lot to learn about
wix/msi, when I tried to install several different pnp printer drivers, each
of which install using non-msi setup by calling the Difx API (or by using my
SetupAPI app), I could not get them to install using DifxApp in wix. I
Thanks Phill.
You're right; WFP drivers are non-PNP drivers. I did try to use the legacy
flag, but then the installer was complaining that the .sys file was missing
even though it was copied properly to the target folder. I'll give it
another try. Otherwise, I'll have to make a custom app that ins
I do not have experience with WFP callout drivers, however I observe that
msdn indicates that they are non-PNP drivers. The DifxApp by default
installs PNP drivers. I assume that the basic process of installing the
driver by right-clicking the INF is successful. If setting the legacy flag
for Di
I'm attempting to install a WFP (Windows Filtering Platform) callout driver
via WiX. All the driver's .inf file does during installation is to copy the
.sys file to the Drivers folder and that's that.
The driver isn't a "typical" driver in the sense that its .inf file doesn't
have a SourceDisksN
5 matches
Mail list logo
