This MSKB article discusses how to do it:
http://support.microsoft.com/kb/259697
> -Original Message-
> From: Shane Corbin [mailto:shane_cor...@selinc.com]
> Sent: Friday, January 11, 2013 22:49
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxA
I'm still curious how you are calling CM_Reenumerate_DevNode on the root
devnode in your custom
action.
Would you mind sharing this snippet?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/DIFxApp-and-upgrades-tp5786223p7582858.html
Sent from the
the DIFxApp team would fix these issues... Or
> at
> least document the limitations so that at least people who read the docs
> don't get trapped by this.
>
> > -Original Message-
> > From: Rob Hamflett [mailto:rob_hamfl...@sn.scee.net]
> > Sent: Wedn
mfl...@sn.scee.net]
> Sent: Wednesday, January 09, 2013 14:14
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxApp and upgrades
>
> We've recently been seeing issue 1 where an upgrade doesn't work due to a
> missing registry entry. We're current
We've recently been seeing issue 1 where an upgrade doesn't work due to
a missing registry entry. We're currently telling customers how to do a
full repair on a case by case basis as this occurs. Did anyone ever
find a fix for this?
Thanks,
Rob
On 29/11/2010 21:23, James Johnston wrote:
> Hi
Would you mind sharing your custom action so myself and others can see how
you accomplished this?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/DIFxApp-and-upgrades-tp5786223p7582650.html
Sent from the wix-users mailing list archive at Nabble.com
ar at some inopportune moment.
--
Message: 5
Date: Fri, 16 Nov 2012 15:51:08 -
From: "James Johnston"
Subject: Re: [WiX-users] DIFxApp
To: "'General discussion for Windows Installer XML toolset.'"
Message-ID: <026b01cdc412$32
Maybe the driver is not WHQL signed?
I'm not sure why you wouldn't have the same issue with DPInst, however. I
was under the impression that the various DIFX methods (DPInst, DIFxApp,
DIFxAPI) would all call the same underlying code to perform the driver
install. Seems like anything else would b
> -Original Message-
> From: Shane Corbin [mailto:shane_cor...@selinc.com]
> Sent: Friday, October 05, 2012 18:07
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DIFxApp and upgrades
>
> Hey James,
>
> Did you ever get any resolution to your
Hey James,
Did you ever get any resolution to your problem regarding scanning for new
hardware when your installation must first uninstall an older version?
I'm in the same boat, and was curious if you made any progress since your
last post. If you are continuing with your workaround, I'd really
> -Original Message-
> From: Frank Jenner [mailto:frank8...@gmail.com]
> Sent: Friday, June 22, 2012 19:29
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] DIFxApp driver files in multiple directories
>
> I'm attempting to use the WixDifxAppExtension to in
Ran into the same problem and couldn't figure it out either. In our case I was
modifying the inf file with our branding anyways so at same time I just created
two inf files: one for 32bit and one for 64bit and a separate MSI for each one.
I then have burn detect the OS "bitness" and run the ap
e the
dedicated ARP entry.
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Wednesday, December 07, 2011 16:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxAPP and Properties question
Personally I tend to set AddRemoveProgram
Thanks. I did exactly that and the ARP* properties are working just fine.
I love this thing ;-)
On Wed, Dec 7, 2011 at 10:00 AM, Tobias S wrote:
> Personally I tend to set AddRemovePrograms="no" to prevent drivers
> from showing up in ARP. Mean otherwise the user could uninstall the
> drivers w
Personally I tend to set AddRemovePrograms="no" to prevent drivers
from showing up in ARP. Mean otherwise the user could uninstall the
drivers while leaving back the application which IMHO makes no sense.
Back to your question AFAIK configuring the ARP entries is done inside
the DifX driver.
Rega
On 01-Jul-11 15:27, jjbean wrote:
> In many cases, I've found that even when using the win32 api directly, it's
> not possible to rollback uninstalled drivers, the exact behavior is very
> platform dependent. In many cases, the api returns "reboot required", at
> which point there is no chance of r
users@lists.sourceforge.net
Subject: Re: [WiX-users] DIFxApp does not properly rollback to the old driver
when doing a major upgrade
I don't think there's much the DIFXApp team can do to make the lib
foolproof/robust.
I'm pretty sure that DIFXApp is simply a wrapper around the win32 set
I don't think there's much the DIFXApp team can do to make the lib
foolproof/robust.
I'm pretty sure that DIFXApp is simply a wrapper around the win32 setupapi
API.
I've used both for the last few years.
In many cases, I've found that even when using the win32 api directly, it's
not possible to r
o anything about it when
customers try to point this out. It's very frustrating to deal with.
(Heck... if one of those two products was open source, I would have
seriously considered fixing it and submitting a patch...)
James
-Original Message-
From: Rob Hamflett [mailto:r...@snsys.co
taller but have proprietary, non-DIFxApp
>> custom actions for installing drivers.
>>
>> Logitech webcam driver, Dell V310 printer driver, NVIDIA graphics drivers,
>> ATI Radeon graphics driver, Intel HD graphics driver, Intel DH55HC drivers,
>> Intel HD Audio drivers: t
Hi Tobias,
In relation to a separate issue, a colleague asked all the developers at his
site to install our
driver and reports that about 1 in 10 fail, but a second attempt works fine.
Thanks for the link,
I'll check it out.
Rob
On 24/03/2011 21:03, Tobias S wrote:
> Hi Rob,
>
> Just some t
Hi Rob,
Just some thoughts to it (even I never had the issue). Maybe they help:
On http://errordecoder.com/system-error-codes/3/code-1021.html I found
some points which could be from interest:
* Device Driver Conflicts
* Hardware Malfunction
Is it only one system where it occurs ? Hardwar
l HD Audio drivers: these products did not appear to use Windows
> Installer for installing the drivers. (Some drivers had MSI files for
> helper/utility programs but did not have the MsiDriverPackages table so I
> conclude they do something else).
>
> Best regards,
>
> James Joh
ML toolset.'
Subject: Re: [WiX-users] DIFXAPP: ERROR: Failed to calculate strong name.
If it's only one PC and it works fine on other computers of similar
configuration (same version of Windows, etc.) then maybe also check some
registry entries:
HKLM\SOFTWARE\Microsoft\Windows\Current
might want to review the topics
> in this section in MSDN for any potential gotchas:
> http://msdn.microsoft.com/en-us/library/ff543645(VS.85).aspx
>
> -Original Message-
> From: Jury BURA [mailto:jury.b...@visutechsystem.by]
> Sent: Thursday, February 10, 2011 16:40
&g
gotchas:
> http://msdn.microsoft.com/en-us/library/ff543645(VS.85).aspx
>
> -Original Message-
> From: Jury BURA [mailto:jury.b...@visutechsystem.by]
> Sent: Thursday, February 10, 2011 16:40
> To: General discussion for Windows Installer XML toolset.
> Subject: Re:
l gotchas:
http://msdn.microsoft.com/en-us/library/ff543645(VS.85).aspx
-Original Message-
From: Jury BURA [mailto:jury.b...@visutechsystem.by]
Sent: Thursday, February 10, 2011 16:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFXAPP: ERROR: Failed to c
Wix code for my driver:
Driver isn't WHQL signed.
And... typical error message for missed cat file is:
DIFXAPP: ERROR: Failed to calculate strong name from 'file-path'.
This error message doesn't contain file path.
Thanks!
10.02.2011 17:39, James Johnston пишет:
> http://www.advancedinst
http://www.advancedinstaller.com/forums/viewtopic.php?f=2&t=2820
Maybe there are some issues with the driver package itself? i.e.
bad/missing catalog file. Be sure that the driver files is completely
installed & that all required files are in the appropriate locations.
If the driver isn't WHQL
able so I
conclude they do something else).
Best regards,
James Johnston
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com]
Sent: Friday, December 10, 2010 17:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp does not prop
Thanks for digging into this further. The support e-mail for DIFx Tools
is difxt...@microsoft.com. I have received responses over the years from
different people, but never any resolution to my problems. If that
e-mail address is no longer valid, then I can give you the addresses of
the specific pe
.
James
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com]
Sent: Tuesday, November 30, 2010 21:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp and upgrades
We use the FT245BM. We use our own PID and have a resold drive
, November 30, 2010 8:43 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] DIFxApp and upgrades
In response to #2: It looks like you are using the same / similar
hardware
that we do. We also use an FTDI product (FT232R). However, there are
some
ds,
James Johnston
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltamotion.com]
Sent: Monday, November 29, 2010 22:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp and upgrades
2. I do not see the second problem at all with our drive
1. We see the exact same problems with DIFxApp on major upgrades (which
is the only type of upgrade we do). I would love to be able to track
down the cause and have a better solution. If anyone has anything
approaching a solution, please let us know! I realize that this issue is
probably DIFxApp-sp
Thanks for the reply Bob. It appears that neither DIFx or DPInst support
the Sensor driver type. SetupAPI appears to work just fine, installing
the sensor as a "legacy" driver -- funny yet sad.
/rafael
On 2/26/2010 11:32 AM, Bob Arnson wrote:
> On 2/24/2010 10:33 AM, Rivera, Rafael wrote:
>
On 2/24/2010 10:33 AM, Rivera, Rafael wrote:
> I put together a WiX 3.0 package, utilizing the DIFx extensions, to
> install a Windows 7 Sensor (UMDF driver). During installation, DIFXAPP
> logged "No matching devices found in INF" and simply threw the driver
> into storage. I read I'm to populate
Алексей Далекин wrote:
> I'm using WIX v3 to install my filter driver. The driver is installed
> correctly but DeleteFiles option doesn't work.
>
You'd have to take that up with the DifxApp folks; WiX just wraps their
custom actions.
> I need to remove *.inf, *.sys files from my InstallFolder
Lian Jiang wrote:
> DIFXAPP: ERROR: InstallDriverPackages failed with error 0xE24A
>
0xE24a translates to ERROR_WRONG_INF_TYPE so you likely have an .inf
file that's malformed for the OS you're trying to install on.
--
sig://boB
http://joyofsetup.com/
-
Notice that WiX v3.0.5217.0 includes DIFxApp 2.1. I see that a later
build (v3.0.5301.0) includes a fix by BobArnso that upgrades to DIFxApp
2.1.1 from WDK v6001.18002, and I understand that this version of
DIFxApp includes Win2K8 support.
So, you can probably update to the latest weekly build of
might try that and see if
it helps.
-Ari
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Thursday, June 25, 2009 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFXAPP: ERROR - The operating system you are running
WiX supports all operating systems. It sounds like DIFXApp does not.
DIFXApp was written by the DIFXApp team. You need to follow up with them
to get it fixed. Kinda' funny that it refers to "codenamed Longhorn" as
well. Someone at MSFT should probably be bopped for that.
June Bell wrote:
> Hi,
Unfortunately, we don't own the DifxApp code. It seems like the
Condition on the Component should work but the DIFXApp team would have
to tell you if/why it does not.
Kalev Lember wrote:
> Hello,
>
> Is it possible to conditionally install drivers with DIFxApp extension?
>
> If I put a Condition
Yeah, the DifxApp team was kind enough to ignore our requests for WiX v3
updates. So we eventually had to do it ourself.
-Original Message-
From: Rob Hamflett [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 01:31
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users
Ah, I see that there are now versions of the DifxApp wixlib shipped with WiX.
I was previously
using v2 and using the wixlibs from the Driver Installation Tools 2.01
installation. I'll try the
ones in the v3 bin folder.
Rob
Bob Arnson wrote:
> Rob Hamflett wrote:
>> Can I get WiX v3 to inst
Rob Hamflett wrote:
> Can I get WiX v3 to install drivers?
>
Yes. Supporting all three platforms required the .wixlibs to be external
to WixDifxAppExtension, however:
To use this element, you need to reference the WixDifxAppExtension
extension and add the .wixlib appropriate for the t
Sigh...
The following recipient(s) could not be reached:
'[EMAIL PROTECTED]' on 2006 11 22 5:04 PM
The e-mail account does not exist at the organization this
message was sent to. Check the e-mail address, or contact the recipient
directly to find out the correct address.
On 11
The best approach is to email the DIFx team: [EMAIL PROTECTED] Address
found at http://www.microsoft.com/whdc/driver/install/difxtools.mspx#EHE.
--
Mike Dimmick
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: 21 November 2006 20:52
To: wix-user
PROTECTED] on behalf of Mike DimmickSent: Sat 23/09/2006 16:03To: Dennis Roy; wix-users@lists.sourceforge.netSubject: Re: [WiX-users] DifxApp
The only suggestion I can make at the moment is simply to use an older version of WiX. The supported version of DIFxApp seems to be the WiX 2.0 versio
ourceForge.
--
Mike Dimmick
From: Dennis Roy [mailto:[EMAIL PROTECTED]Sent: Fri 22/09/2006 18:25To: Mike Dimmick; wix-users@lists.sourceforge.netSubject: RE: [WiX-users] DifxApp
Linking in the DifXApp.wixlib got me beyond that point. The caps on the MSI was just me.
I can build it with no w
?
Thanks
Dennis
From: Mike Dimmick
[mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006
5:00 PM
To: Dennis Roy;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] DifxApp
I think you need to include
difxapp.wixlib in the command line to light.exe. I believe
I think you need to include difxapp.wixlib in the command line to light.exe. I believe difxapp.wixlib is in the WDK.
If this doesn't work (the DIFxApp documentation on MSDN seems to refer to WiX 2.0) then my next question is around case-sensitivity: the documentation refers to MsiProcessDriver
52 matches
Mail list logo
