Re: [libwdi-devel] WinUSB device installation failed on Win7 x86

[Pete B. <pb...@gm...>]

On 2012.11.02 22:07, Liam Staskawicz wrote:
> Please excuse me - I think I misread my logs, I think the logs above can
> largely be ignored.
>
> I'm actually installing drivers for 2 devices - my normal device, and
> its bootloader. In this case, the preinstallation of the first driver
> appears to have succeeded (I see a block in the logs that starts
> with [SetupCopyOEMInf - C:\Program
> Files\Sifteo\Sync\drivers\sifteo_base.inf] and finishes successfully.
>
> However, it also appears to trigger installation attempts for other
> pre-existing devices on the system under test that look like they were
> never installed successfully (who knows why).
>
> Perhaps relatedly, I don't see any corresponding SetupCopyOEMInf block
> for my second device, making me think that its preinstallation did not
> occur, possibly because the other installation attempts were still in
> progress, and libwdi doesn't wait for any installations in progress to
> complete before exiting. For my second device, I only see blocks in the
> logs starting with "Device Install (Hardware initiated)", which appear
> to correspond to a driver installation prompted by a device being connected.
>
> Does this sound like a feasible explanation? If so, would it make sense
> to add an optional parameter to wdi-simple to specify a timeout to wait
> for any installations in progress?

That seems to make sense. libwdi does not expect multiple driver 
installations to be occurring at once, and will only wait for the 
completion of the one it initiated, so anything that occurs after that 
will not be reported.

I'm not sure I want to add a timeout for other installations in 
wdi-simple, as, apart from lack of time to do so and the need to add 
changes in the libwdi installer, this would only apply for very specific 
cases like yours and, well, wdi-simple is supposed to be kept simple, as 
it is there as a sample.

In your case, I think it would be better if you monitored the 
C:\Windows\inf\setupapi.dev.log device installation log on your own, as 
this is really what libwdi forwards, to confirm whether your 
installation succeeded or not.

Regards,

/Pete