Re: [802.11] Windows NDIS questions by James
James
Fri Feb 27 16:47:38 CST 2004
1) NDIS is the overall "traffic cop" and nagging mommy. It is what actually
sees IRPs related to network packets. When it sees a packet, it invokes --
as callbacks, essentially -- whatever protocol or miniport drivers have
registered with it for the concerned device (which may be only a logical
device). I believe NDISIUO and NDISPROT are basically the same thing;
NDISPROT is more recent. They both act as callbacks vis-a-vis NDIS.
2) Yes, almost certainly you'll need to develop a protocol driver like
NDISPROT. NDIS will call you and, sometimes, you'll call NDIS back.
3) Dunno.
--
James Antognini
Windows DDK Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Claudio Takahasi" <claudiotakahasi@yahoo.com.br> wrote in message
news:3a74d3cc.0402270916.27ae03c6@posting.google.com...
> Hello,
>
> I am beginner at this subject. Sorry I if ask some bullshits.
> I need develop an application that detect the available access points and
> establish a connection. The target O.S. are Windows 2000 and Windows XP.
> My questions are:
>
> 1. What are the diferences among NDIS, NDISUIO and NDISPROT?
>
> 2. Must I develop a Protocol driver(like NDISPROT or NDISUIO) or
> it's better call directly the NDIS library functions(like NdisRequest)?
>
> 3. How can I disable Wireless Zero Configuration (WZC) service inside
> my application?
>
>
> Thanks,
> Claudio.