The symptoms that you have shared, (installs on a clean system, but when the
"old" driver is present, the "new" driver is added to the driver store, but
the class installer is not invoked by the PNP manager) are commonly due to
the fact that the "new" driver has a lower driver rank than the "old"
d
e
> driverstore just not copied over to the C:\Windows\inf folder as a
> OEM*.INF
>
> Thank you,
> Michael Ogilvie
>
>
> -Original Message-
> From: Carter Young [mailto:ecyo...@grandecom.net]
> Sent: Wednesday, June 11, 2014 10:57 AM
> To: wix-users@list
t copied over to the C:\Windows\inf folder as a
OEM*.INF
Thank you,
Michael Ogilvie
-Original Message-
From: Carter Young [mailto:ecyo...@grandecom.net]
Sent: Wednesday, June 11, 2014 10:57 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Driver Issue
See Al
See Also:
http://stackoverflow.com/questions/13345788/propertyref-to-require-combobox
Quoting Carter Young :
> Note 1: Error 2205:
> 2205
> Database: [2]. Table does not exist: [3].
>
> [2] = Install Database Name
> [3] = Table Name
>
> See http://msdn.microsoft.com/en-us/library/aa372835.aspx
>
Note 1: Error 2205:
2205
Database: [2]. Table does not exist: [3].
[2] = Install Database Name
[3] = Table Name
See http://msdn.microsoft.com/en-us/library/aa372835.aspx
If an Upgrade/Repair option always works, my hunch is that Table [3]
is created during the Repair, but not during a fresh in
et=InstallDriverPackages,CustomActionData=2.12{1464D187-09
88-457A-91EE-36945AFD9347}C:\Program Files
(x86)\PixeLINK\Install\FWx64\312Camera DriversPixeLINK)
MSI (s) (FC:DC) [07:02:22:917]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIBFF1.tmp, Entrypoint: InstallDriverPackages
---
>>>DIFXAPP: INFO: No matching devices found in INF
"C:\Windows\System32\DriverStore\FileRepository\pxlgevndis6.inf_amd64_ne
utral_fe3715a4af78ac12\PxLGevNdis6.inf" on the Machine.
I would configure the target system to generate a verbose setupapi log, and
study both (msi and setupapi.dev.log)
7 matches
Mail list logo
