If running DPInstall.exe on the command line fails, then those issues should
be resolved first. Have you enabled verbose driver setupAPI logging?
https://msdn.microsoft.com/en-us/library/windows/hardware/ff550808%28v=vs.85%29.aspx
I think it is recommended that you use the Wix DifxAppExtension to
Hi,
I have used the Driver installation tutorial here:
http://www.codeproject.com/Articles/44191/Drivers-Installation-With-WiX
My driver is signed. When I try to install it, I get no errors but the
process does not start. When I manually try to use the dpinst tool on the
command line, all I recei
t; Thanks for the info Garth.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Garth
> Sent: 23 June 2008 11:56
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Driver installation
>
>
Thanks for the info Garth.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Garth
Sent: 23 June 2008 11:56
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Driver installation
The difxapp stuff works fine for me in 3.0
The difxapp stuff works fine for me in 3.0 installing a filter driver
The only thing to check is to see if your package meets the requirements
http://msdn.microsoft.com/en-us/library/ms790263.aspx
Also you need to set "Legacy" option if your driver is unsigned for
testing or test sign it which
Hi all,
I have a vbscript Custom Action that installs a port monitor, printer
driver, printer and also sets the default printer. I'd like to migrate this
to something more sturdy.
I've seen notes about difxapp but not much mention of it lately, is it
working OK under 3.0 and would it do all
Thanks a lot - it works for me too.
Bo
Ben Greenberg-3 wrote:
>
> I got this to work in WiX3 by linking to WixDifxAppEntension and adding
> the Custom Actions manually:
>
>
> DllEntry="ProcessDriverPackages" HideTarget="no" Impersonate="no"
> Execute="immediate" Return="check"/>
>
I got it working by adding the following
Can't remeber where I got this from...
Think I extraced it from somewhere...
Seems to work for me...
You'll also need the set the var DIFxAppPath
I got this to work in WiX3 by linking to WixDifxAppEntension and adding the
Custom Actions manually:
Those DLLs are from Difx distribution.
bg
On Tue, 02 Oct 2007 09:08:10 -0700, Bob Arnson <[EMAIL PROTECTED]> wrote:
> bcs wrote:
>> I am trying to install
bcs wrote:
> I am trying to install a driver using Wix 3.0 and DifxAppExtension.
> When I build my installer I get this linker error:
>
> Unresolved reference to symbol 'CustomAction:MsiProcessDrivers'
>
Difx doesn't currently support WiX v3. The Difx extension exists for
when they support it.
I am trying to install a driver using Wix 3.0 and DifxAppExtension.
When I build my installer I get this linker error:
Unresolved reference to symbol 'CustomAction:MsiProcessDrivers'
My Wix source code is shown below.
Can anyone help me find out how to avoid this linker error?
Thanks
Bo
http:
I am trying to install a driver using Wix 3.0 and DifxAppExtension.
When I build my installer I get this linker error:
Unresolved reference to symbol 'CustomAction:MsiProcessDrivers'
My Wix source code is shown below.
Can anyone help me find out how to avoid this linker error?
Thanks
Bo
http:
Christoph von Wittich wrote:
I have to install a kernel driver using WiX v3 but Type="kernelDriver"
(in ) isn't supported.
With linking fails with "error LGHT0094 : Unresolved
reference to symbol 'CustomAction:MsiProcessDrivers'"
Any suggestions?
Stick with WiX v2 -- it includes DifxApp sup
Hi!
I have to install a kernel driver using WiX v3 but Type="kernelDriver"
(in ) isn't supported.
With linking fails with "error LGHT0094 : Unresolved
reference to symbol 'CustomAction:MsiProcessDrivers'"
Any suggestions?
Regards,
Christoph von Wittich
__
14 matches
Mail list logo
