I am currently revising the drivers for a device that uses an EZ-USB chip,
so they can be signed. I have completed the Microsoft HCT tests and have
test signed the drivers.
The drivers now install without any of the usual user interaction, add
hardware wizard etc… (with the microsft testroot certificate installed).
This seems to cause a problem with the EZ-USB way of doing things.
On first installation, the device is found and the firmware driver is
loaded… The device then re-numerates and the firmware driver unloads. The
main driver then loads… This all happens as expected, without any user
interaction and you see the usual XP bubbles appear telling you what is
happening. At the end of the installation a one of two possible bubbles are
displayed. “A problem occurred during installation, your hardware might not
work properly” or “Your new hardware is installed but might not work
properly until you reboot”.
Looking into the setupapi.log, does not lead us to any real conclusions, as
there are no errors indicated. The only thing you do see is :
@ 11:32:28.222 #W165 Device “USB\VID_0ADA&PID_8000\6&2C3B5705&24&1” required
reboot: Device not started (unknown reason).
But this is only seen when the “might need a reboot” bubble is shown. They
seem to alternate, clean the machine of install USB devices and the other
message is shown, do it again and the first message comes back…
Does anyone have any clues why this is? It seems to have something to do
with windows xp checking that the drivers it has just installed are loaded,
the firmware driver is no longer.
Thanks
Duncan
Data Encryption Systems Ltd
Hard to say, but it sounds like your driver is perhaps loading and failing
StartDevice. Have you debugged the driver during this process?
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
wrote in message news:xxxxx@ntdev…
>
>
> I am currently revising the drivers for a device that uses an EZ-USB chip,
> so they can be signed. I have completed the Microsoft HCT tests and have
> test signed the drivers.
>
> The drivers now install without any of the usual user interaction, add
> hardware wizard etc… (with the microsft testroot certificate installed).
> This seems to cause a problem with the EZ-USB way of doing things.
>
> On first installation, the device is found and the firmware driver is
> loaded… The device then re-numerates and the firmware driver unloads. The
> main driver then loads… This all happens as expected, without any user
> interaction and you see the usual XP bubbles appear telling you what is
> happening. At the end of the installation a one of two possible bubbles
are
> displayed. “A problem occurred during installation, your hardware might
not
> work properly” or “Your new hardware is installed but might not work
> properly until you reboot”.
>
> Looking into the setupapi.log, does not lead us to any real conclusions,
as
> there are no errors indicated. The only thing you do see is :
>
> @ 11:32:28.222 #W165 Device “USB\VID_0ADA&PID_8000\6&2C3B5705&24&1”
required
> reboot: Device not started (unknown reason).
>
> But this is only seen when the “might need a reboot” bubble is shown. They
> seem to alternate, clean the machine of install USB devices and the other
> message is shown, do it again and the first message comes back…
>
>
> Does anyone have any clues why this is? It seems to have something to do
> with windows xp checking that the drivers it has just installed are
loaded,
> the firmware driver is no longer.
>
> Thanks
>
> Duncan
>
> Data Encryption Systems Ltd
>
>