Prev: HidD_GetFeature() working, HidD_SetFeature() not working
Next: USB RNDIS
From: oz_malkocoglu on 2 Dec 2009 05:50
I load the RNDIS (Microsoft supplied) drivers on WinXP. The INF file was
previously (and automatically) copied to Windows\INF directory as
"oem14.inf". When I plug-in the device, in the Device Manager, I see 2
devices like "RNDIS Gadget" & "RNDIS Gadget #2". Both of them give "The
device can not start. (Code 10)". The USB device never gets the
RNDIS_INITIALIZE_MSG message. In fact, after lots of GetDesc , SetAddr and
more GetDesc, the last control message it receives is GetDescriptor (String
type) which was successfull. What to do next to debug it ?

Thanks In Advance...
From: Mike [MSFT] on 3 Dec 2009 22:38
Code 10 means the AddDevice call into the driver failed.

-Mike

"oz_malkocoglu" <oz_malkocoglu(a)discussions.microsoft.com> wrote in message
news:1831FEF7-B890-4053-A4A6-26183A1B6ED4(a)microsoft.com...
> I load the RNDIS (Microsoft supplied) drivers on WinXP. The INF file was
> previously (and automatically) copied to Windows\INF directory as
> "oem14.inf". When I plug-in the device, in the Device Manager, I see 2
> devices like "RNDIS Gadget" & "RNDIS Gadget #2". Both of them give "The
> device can not start. (Code 10)". The USB device never gets the
> RNDIS_INITIALIZE_MSG message. In fact, after lots of GetDesc , SetAddr and
> more GetDesc, the last control message it receives is GetDescriptor
> (String
> type) which was successfull. What to do next to debug it ?
>
> Thanks In Advance...

 | 
Pages: 1
Prev: HidD_GetFeature() working, HidD_SetFeature() not working
Next: USB RNDIS