Re: Disable Device is persisted, but where?
- From: jeffm@xxxxxxxxxxxxxxxxxxxx ("[MSFT] Jeff McCashland")
- Date: Tue, 30 Oct 2007 16:34:58 GMT
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Gerry,
\par
\par Microsoft Customer Support Services is the group that includes DDK Support. If a case is required for in-depth debuggig, it would come to us.
\par
\par The verbose logging is mostly useful to troubleshoot install issues. However, it does log the results of loading the driver and starting the device. If the device is failing to start properly when installed or enabled, that will show up in the log. The third party driver is probably failing the Start IRP. What we want to know first, is what error code the IRP was failed with.
\par
\par Look in Device Manager while the software device is in the failed state, and see if there is an error code displayed in the Properties dialog. You can also use the DevCon tool from the WDK, and use 'devcon status' to get the problem code. Unfortunately, it's likely something generic, such as Code 10 CM_PROB_FAILED_START.
\par
\par There is not a delayed start available for PnP drivers. In fact, all PnP drivers should have a Start Type of SERVICE_DEMAND_START, and be able to load whenever Setup configures it's device. Apparently this particular driver isn't succeeding at this on Vista.
\par
\par You've suggested 2 theories of why the driver isn't starting: 1) something changes in the disable/enable code that allows the driver to start the second time, and 2) the driver has a dependancy that requires a delay in it starting up (something else needs to complete). To isolate between these two, you could try tweaking (or renaming) the INF file so that the driver for the software device is not found (the PnP ID doesn't resolve). This will cause the software device not to install right away, but display the New Hardware Found dialog instead. From there, you can go 2 ways: You can leave the New Hardware Found dialog up for awhile before completing it (by directing it to a good INF), or you can dismiss the dialog without installing the driver, then update with the correct driver.
\par
\par The problem with the first strategy is that the process the device depends on could be serialized with the wizard, so it might have no effect. The second strategy could be misleading if it ends up having the same effect as disabling and enabling a failed install.
\par
\par Best Regards,
\par Jeff McCashland [Microsoft]
\par Escalation Engineer, DDK/DTM Support
\par This posting is provided "AS IS" with no warranties, and confers no rights
\par }
- Follow-Ups:
- Re: Disable Device is persisted, but where?
- From: Gerry Hickman
- Re: Disable Device is persisted, but where?
- References:
- Disable Device is persisted, but where?
- From: Gerry Hickman
- Re: Disable Device is persisted, but where?
- From: Eliyas Yakub [MSFT]
- Re: Disable Device is persisted, but where?
- From: Gerry Hickman
- Re: Disable Device is persisted, but where?
- From: Don Burn
- Re: Disable Device is persisted, but where?
- From: Eliyas Yakub [MSFT]
- Re: Disable Device is persisted, but where?
- From: Gerry Hickman
- Re: Disable Device is persisted, but where?
- From: "[MSFT] Jeff McCashland"
- Re: Disable Device is persisted, but where?
- From: Gerry Hickman
- Re: Disable Device is persisted, but where?
- From: "[MSFT] Jeff McCashland"
- Re: Disable Device is persisted, but where?
- From: Gerry Hickman
- Disable Device is persisted, but where?
- Prev by Date: Halsetbusdata for PCI/PCI express bridges
- Next by Date: Unable to upload a Hardware Logo Submission to Winqual
- Previous by thread: Re: Disable Device is persisted, but where?
- Next by thread: Re: Disable Device is persisted, but where?
- Index(es):
Relevant Pages
|
Loading