NDIS - USB IoCallDriver returns 0xC000000E - Device does not exist while configuring USB - Regd.

Eliyas Yakub [MSFT]

The usbnwifi is an NDIS6.0 driver. It will not work on XP. Everything you
need is in these two samples. You just have to understand how they work and
transfer the code from one to the other. You have to do this part yourself.
I don't have any ready made sample for you. Since you are planning to write
an NDIS 5.0 driver, take the 5.0 version of NDISEDGE driver and move all the
code that is required to interface with USB stack from the usbnwifi sample
to this one and customize it to your hardware. The hardware interaction
piece is already separated out nicely in its own module in the wifi sample.
So transferring this code should be easy. Remember both ndis 5.0 and 6.0
models are conceptually similar when it comes to initialization, cleanup. So
for every callback in usbwifi sample, find out what the corresponding
callback is in ndis 5.0 and then transfer the code. This article might help
in understanding the differences between these two models.



-Eliyas

sudheer

Hi Eliyas

Thanks for your kind support.

I have already started doing that part of transferring USB code to
NDISEDGE sample (of version NDIS 5.1) and replacing NDIS 6.0 APIs with
NDIS 5.1 that is supported for windows XP. The link provided by you is
very helpful.

Thanks once again and will be back with a new issue (if any)

Thanks & Regards
Sudheer



On Aug 15, 8:14 pm, "Eliyas Yakub [MSFT]"
<eliyasy@online.discussion.microsoft.com> wrote:
> The usbnwifi is an NDIS6.0 driver. It will not work on XP. Everything you
> need is in these two samples. You just have to understand how they work and
> transfer the code from one to the other. You have to do this part yourself.
> I don't have any ready made sample for you. Since you are planning to write
> an NDIS 5.0 driver, take the 5.0 version of NDISEDGE driver and move all the
> code that is required to interface with USB stack from the usbnwifi sample
> to this one and customize it to your hardware. The hardware interaction
> piece is already separated out nicely in its own module in the wifi sample.
> So transferring this code should be easy. Remember both ndis 5.0 and 6.0
> models are conceptually similar when it comes to initialization, cleanup. So
> for every callback in usbwifi sample, find out what the corresponding
> callback is in ndis 5.0 and then transfer the code. This article might help
> in understanding the differences between these two models.
>
>
>
> -Eliyas

sudheer

Hi Guys

Thanks very much for your support.

Now i am using NdisEdge sample with USB stack attached to it.
The device has at present 2 endpoints (Bulk) for read and write.
The read and write request of the device is failing with NTSTATUS
error code as C0000010 - STATUS_INVALID_DEVICE_REQUEST.
Can you please tell me what would be the underlying request that the
device is sending when calling NICPostReadRequest from NDIS Driver. Is
the request is same as that of Bulk_Read request of BulkUsb? Which
endpoints are used for sending this requests.

Thanks & Regards
Sudheer


On Aug 6, 12:44 am, "Eliyas Yakub [MSFT]"
<> wrote:
> NDISminiports that interface withUSBstack should be written using KMDF.
> AFAIK, it's a WHQL requirement now. By usingUSBIoTarget and
> ContinuousReader interface of KMDF, you can write a much more simple and
> robustndisminiport driver. The realtek sample for wifiUSBdevice in the
> Server2003 WDK is a good sample to base your driver. This sample is derived
> from ndisedge sample.
>
> -Eliyas

sudheer

Hi Eliyas

I have looked in to usbnwifi sample and compiled that sample for XP
x86 processor, but it is giving warning as the sample is invalid for
the specified OS and also i am not working on 802.11 and dont want any
hardware code to be present.

I just want to read the IP Packets from my USB device and pump the
same to Ndis layer for further processing.

As the development time is very less, I thought of modifying ndisedge
sample.

I dont think any change is required in ndisedge sample expect the
configuration of the device (i.e., in ndiswdm.h and Inf file).
(correct me if i am wrong) and I would like to know where the USB
device should be registered (like the registering the usb device in
sample usbnwifi in hardware initialize) in NICInitAdapterWorker.

Can you please let me know the steps to attach USB stack to ndisedge
sample.

Thanks in advance
Regards
Sudheer

Eliyas Yakub [MSFT]

The usbnwifi is an NDIS6.0 driver. It will not work on XP. Everything you
need is in these two samples. You just have to understand how they work and
transfer the code from one to the other. You have to do this part yourself.
I don't have any ready made sample for you. Since you are planning to write
an NDIS 5.0 driver, take the 5.0 version of NDISEDGE driver and move all the
code that is required to interface with USB stack from the usbnwifi sample
to this one and customize it to your hardware. The hardware interaction
piece is already separated out nicely in its own module in the wifi sample.
So transferring this code should be easy. Remember both ndis 5.0 and 6.0
models are conceptually similar when it comes to initialization, cleanup. So
for every callback in usbwifi sample, find out what the corresponding
callback is in ndis 5.0 and then transfer the code. This article might help
in understanding the differences between these two models.



-Eliyas

sudheer

Hi Eliyas

Thanks for your kind support.

I have already started doing that part of transferring USB code to
NDISEDGE sample (of version NDIS 5.1) and replacing NDIS 6.0 APIs with
NDIS 5.1 that is supported for windows XP. The link provided by you is
very helpful.

Thanks once again and will be back with a new issue (if any)

Thanks & Regards
Sudheer



On Aug 15, 8:14 pm, "Eliyas Yakub [MSFT]"
<eliyasy@online.discussion.microsoft.com> wrote:
> The usbnwifi is an NDIS6.0 driver. It will not work on XP. Everything you
> need is in these two samples. You just have to understand how they work and
> transfer the code from one to the other. You have to do this part yourself.
> I don't have any ready made sample for you. Since you are planning to write
> an NDIS 5.0 driver, take the 5.0 version of NDISEDGE driver and move all the
> code that is required to interface with USB stack from the usbnwifi sample
> to this one and customize it to your hardware. The hardware interaction
> piece is already separated out nicely in its own module in the wifi sample.
> So transferring this code should be easy. Remember both ndis 5.0 and 6.0
> models are conceptually similar when it comes to initialization, cleanup. So
> for every callback in usbwifi sample, find out what the corresponding
> callback is in ndis 5.0 and then transfer the code. This article might help
> in understanding the differences between these two models.
>
>
>
> -Eliyas

moeloek132