RE: DIFxApp update problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

I setup the system with setup api logging options 0x4800FFFF, I then
seperately logged the upgrade and the initial install. While the full results
are too long to post here I noticed the following:

---(from upgrade_setupapi.log)----
[2007/11/20 09:10:45 2404.3]: @ 09:10:45.812 #V132 File
"C:\WINDOWS\system32\DRVSTORE\dxpci_D2E51AF8BFD3DA4DBCCF519F319B53147846E709\dxpci.inf"
(key "dxpci.inf") is signed in catalog
"C:\WINDOWS\system32\DRVSTORE\dxpci_D2E51AF8BFD3DA4DBCCF519F319B53147846E709\dxpci.cat".
[2007/11/20 09:10:46 2404.6]: #-198 Command line processed:
C:\WINDOWS\system32\MsiExec.exe -Embedding A5D0C02029763811DB5F5F5C81472971
[2007/11/20 09:10:46 2404.6]: @ 09:10:46.187 #V132 File
"C:\WINDOWS\INF\oem12.inf" (key "dxpci.inf") is signed in catalog
"C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem12.CAT".
[2007/11/20 09:10:45 2404.3]: @ 09:10:46.203 #V042 Opened INF
"C:\WINDOWS\INF\oem12.inf", PNF created (Languge = 0409).
[2007/11/20 09:10:46 2404.7]: #-198 Command line processed:
C:\WINDOWS\system32\MsiExec.exe -Embedding A5D0C02029763811DB5F5F5C81472971
[2007/11/20 09:10:46 2404.7]: @ 09:10:46.234 #V039 Opened INF
"C:\WINDOWS\system32\DRVSTORE\dxpci_D2E51AF8BFD3DA4DBCCF519F319B53147846E709\dxpci.inf", PNF not created (Languge = 0409).
[2007/11/20 09:10:46 2404.8]: #-198 Command line processed:
C:\WINDOWS\system32\MsiExec.exe -Embedding A5D0C02029763811DB5F5F5C81472971
[2007/11/20 09:10:46 2404.8]: @ 09:10:46.265 #V039 Opened INF
"C:\WINDOWS\system32\DRVSTORE\dxpci_D2E51AF8BFD3DA4DBCCF519F319B53147846E709\dxpci.inf", PNF not created (Languge = 0409).
[2007/11/20 09:10:46 2404.7]: @ 09:10:46.296 #V132 File
"C:\WINDOWS\system32\DRVSTORE\dxpci_D2E51AF8BFD3DA4DBCCF519F319B53147846E709\dxpci.inf"
(key "dxpci.inf") is signed in catalog
"C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem12.CAT".
[2007/11/20 09:10:46 2404.9]: #-198 Command line processed:
C:\WINDOWS\system32\MsiExec.exe -Embedding A5D0C02029763811DB5F5F5C81472971
[2007/11/20 09:10:46 2404.9]: @ 09:10:46.328 #V132 File
"C:\WINDOWS\INF\oem12.inf" (key "dxpci.inf") is signed in catalog
"C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem12.CAT".
[2007/11/20 09:10:46 2404.7]: @ 09:10:46.359 #V042 Opened INF
"C:\WINDOWS\INF\oem12.inf", PNF created (Languge = 0409).


this appears to indicate that the newer driver was recognised as signed and
the inf and catalog info are saved under the name oem12. (The previous old
install was found as oem6). At this time, both the old and the new driver
have copies present in the drvstore.

later on in the upgrade...

[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.593 #V005 Opened
the PNF file of "C:\WINDOWS\inf\oem12.inf" (Language = 0409).
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.593 #I022 Found
"PCI\VEN_11EE&DEV_4D78&SUBSYS_00A011EE" in C:\WINDOWS\inf\oem12.inf; Device:
"DOME DX2/PCI"; Driver: "DOME DX2/PCI"; Provider: "Planar Systems, Inc.";
Mfg: "Planar Systems, Inc."; Section name: "dxpcixp".
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.625 #I023 Actual
install section: [dxpcixp]. Rank: 0x00000001. Effective driver date:
05/17/2007.
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.640 #T076
Enumerating files: Cache pass completed.
[2007/11/20 09:10:47 2404.351 Driver Install]: #-147 Loading class installer
module for "DOME DX2/PCI".
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.796 #V132 File
"C:\WINDOWS\system32\Desk.Cpl" (key "Desk.Cpl") is signed in catalog
"C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\NT5.CAT".
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.812 #V146 Using
exported function "DisplayClassInstaller" in module
"C:\WINDOWS\system32\Desk.Cpl".
[2007/11/20 09:10:47 2404.351 Driver Install]: #-148 Loading coinstaller
modules for "DOME DX2/PCI".
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.843 #I180
Verifying file "C:\WINDOWS\system32\dxpcicls.dll" (key "dxpcicls.dll")
against catalog "" failed. Error 1168: Element not found.
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.875 #V330
Verifying file "C:\WINDOWS\system32\dxpcicls.dll" (key "dxpcicls.dll") as
self-signed failed. Error 0x800b0100: No signature was present in the subject.
[2007/11/20 09:10:47 2404.351 Driver Install]: @ 09:10:50.890 #E360 An
unsigned or incorrectly signed file "C:\WINDOWS\system32\dxpcicls.dll" for
driver "DOME DX2/PCI" will be installed (Policy=Ignore). Error 0x800b0100: No
signature was present in the subject.


Somewhere the signature information has been lost. The setup is again trying
to use oem12 (the new signed driver).



Finally, after the device has been installed setup seems to find the
signature:

[2007/11/20 09:10:51 2404.470]: @ 09:10:53.687 #T201 Install Device: End.
[2007/11/20 09:10:51 2404.470]: @ 09:10:53.703 #V156 Completed default
installer.
[2007/11/20 09:10:51 2404.470]: @ 09:10:53.718 #T185 Pruning Files:
Verifying catalogs/INFs.
[2007/11/20 09:10:51 2404.470]: @ 09:10:53.750 #V132 File
"c:\windows\inf\oem12.inf" (key "dxpci.inf") is signed in catalog
"C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem12.CAT".
[2007/11/20 09:10:51 2404.470]: @ 09:10:53.765 #T186 Pruning Files:
Verifying catalogs/INFs completed.



"Mr Hat" wrote:

Sorry I wasn't clear. This is on XP pro sp2 with a WHQL signed driver. In
both cases the legacy flag is set (both initial unsigned, and signed update).
If I do a fresh install of the signed driver everything behaves as I would
expect, it is only when upgrading from an unsigned driver to a signed driver
that the behavior is unexpected. I'll enable setupapi logging and see if that
can give me more information.

""[MSFT] Jeff McCashland"" wrote:

What is the target OS/SP? Verify that your CAT file is signed for that
target.

I would start by enabling verbose setupapi logging (instructions in the WDK
documentation), repro, then examine the log for clues.

I'm not sure it makes a difference, but I assume you were using the Legacy
flag to install the unsigned driver with DIFxApp. Did you turn the flag
off when you upgraded to the signed driver? What type of signature does
the driver have?

Best Regards,
Jeff McCashland [Microsoft]
Escalation Engineer, DDK/DTM Support
This posting is provided "AS IS" with no warranties, and confers no rights
.

Relevant Pages

  • Re: 0x0000007B
    ... I got past the Windows setup infinite loop by copying NTLDR and NTDETECT.COM ... to an empty USB memory stick. ... There is an autorun Intel installation program that can be used to install ... Warning:Could not find a driver for Video Controller ...
    (microsoft.public.windowsxp.embedded)
  • Re: Harddisc cant be found on Windowx XP pro install on Amilo Pi1536
    ... To do a clean install, boot the Windows XP install CD-Rom. ... your computer's hardware configuration and then begins to install the Setup ... prompted to insert the manufacturer supplied Windows XP driver for your ...
    (microsoft.public.windowsxp.general)
  • Re: ACPI.SYS file corrupt
    ... If your drive controller driver isn't included on the Windows 2000 install ... text-mode setup. ...
    (microsoft.public.win2000.advanced_server)
  • Re: Installing Windows XP with IDE RAID controller
    ... --> Using setup disks I ran the install process again and hit F2 to specify ... the setup displayed. ... Sorry for the confusion - i pressed F6 to specify a third party raid driver. ... > installed in this computer" error message when i try to install windows xp ...
    (microsoft.public.windowsxp.setup_deployment)
  • RE: Help! I cant install catalog on XP and Vista
    ... I have problems in installing catalog file. ... Then I right clicked the INF file and click on "Install", my driver was ...
    (microsoft.public.win32.programmer.kernel)