Dear all
Does anyone have experience on multi-interface USB device driver installation?
Our USB device has 2 interface. Every interface has an driver (one sys file and one inf file), also they need a USB hub driver (we can use usb.inf in Windows).
So I should install driver 3 times for my USB device.
In order to simplify the installation. I write a dll to call SDK API SetupCopyOEMInf to copy all inf files to Windows inf directory and copy all sys files to sytem32\drivers dir. Then I connect my USB device to PC. Then Windows will search its driver in Windows inf dir, and will not appear the “find new hardware” dialogue.
but it is work well in Windows 2000, and can work in Windwos xp later version. Because our driver haven’t passed WHQL certification.
can anyone tell me how to solve this problem?
thank you very much
Denny
huaping jiang wrote:
Our USB device has 2 interface. Every interface has an driver
(one sys file and one inf file), also they need a USB hub driver
(we can use usb.inf in Windows). So I should install driver 3
times for my USB device.
This wasn’t part of your question, but if you tweak your device’s descriptors appropriately, you can obviate the need for an INF which manually references the generic parent driver.
If you aren’t going to get your driver signed, that’s one less hardware wizard for your customers to whack away…
but it is work well in Windows 2000, and can work in Windwos
xp later version. Because our driver haven’t passed WHQL
certification.
If this is actually a typo and means “can’t work in XP later version”, this is by design. Unsigned drivers cannot be installed silently – period.
Sorry dear,
there is no idea about it.
On 7/3/07, xxxxx@gmail.com wrote:
>
> huaping jiang wrote:
>
> > Our USB device has 2 interface. Every interface has an driver
> > (one sys file and one inf file), also they need a USB hub driver
> > (we can use usb.inf in Windows). So I should install driver 3
> > times for my USB device.
>
> This wasn’t part of your question, but if you tweak your device’s
> descriptors appropriately, you can obviate the need for an INF which
> manually references the generic parent driver.
>
> If you aren’t going to get your driver signed, that’s one less hardware
> wizard for your customers to whack away…
>
> > but it is work well in Windows 2000, and can work in Windwos
> > xp later version. Because our driver haven’t passed WHQL
> > certification.
>
> If this is actually a typo and means “can’t work in XP later version”,
> this is by design. Unsigned drivers cannot be installed silently – period.
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
thank Chris Aseltine very much! But…
This wasn’t part of your question, but if you tweak your device’s descriptors
appropriately, you can obviate the need for an INF which manually references the
generic parent driver.
Can you tell me more information about your idea? My USB device have 1 configufation and 2 BULk interfaces.
How can I do?
Denny