HI
I am writing a NDIS miniport driver for NIC card. I want a user mode
applications to communicate with NDIS Miniport driver via IOCTL. I have
used NdisMRegisterDevice API to expose a symbolic link to user mode. Is it
a preferred way to do? Is there any alternative approach?
Also I have to give a set of dispatch routines (Major function array) along
with the call to NdisMRegisterDevice API. I am just interested in
IRP_MJ_DEVICE_CONTROL messages. But in NDIS, I cannot access the IRP
structure and IRP related functions. In order to access the IRP related
structure, I have to include ntddk.h. Is it recommended to include ntddk.h
in NDIS drivers?
Thanks in advance
Ravindra
You could use NdisMRegisterDevice but the best approach would be to use WMI
interfaces in Miniports. You can follow the E100BEX sample from the DDK to
learn that. There is also an user-mode WMICLI sample in the DDK that shows
how set/get the information from a driver using WMI. There was lot
discussion in the newsgroup on how to use NdisMRegisterDevice, please search
the archive.
-Eliyas
-----Original Message-----
From: xxxxx@intel.com [mailto:xxxxx@intel.com]
Sent: Tuesday, July 11, 2000 6:00 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS and IOCTL
HI
I am writing a NDIS miniport driver for NIC card. I want a user mode
applications to communicate with NDIS Miniport driver via IOCTL. I have
used NdisMRegisterDevice API to expose a symbolic link to user mode. Is it
a preferred way to do? Is there any alternative approach?
Also I have to give a set of dispatch routines (Major function array) along
with the call to NdisMRegisterDevice API. I am just interested in
IRP_MJ_DEVICE_CONTROL messages. But in NDIS, I cannot access the IRP
structure and IRP related functions. In order to access the IRP related
structure, I have to include ntddk.h. Is it recommended to include ntddk.h
in NDIS drivers?
Thanks in advance
Ravindra
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
Hello
…
used NdisMRegisterDevice API to expose a symbolic link to user mode. Is it
a preferred way to do? Is there any alternative approach?
The NDIS function is only avail for Windows 2000. When you support
more OS for you driver the best way is a protocol driver on top on
your ndis driver. The same protocol driver binaries can work for
Windows NT 4.0, Windows 98 and Windows 2000, Windows ME. The
protocol driver offer a standard DeviceControl Interface to user mode
and can call NdisRequest to talk with the NDIS driver. Here you can
use special OID codes for your protocol driver - NDIS driver
communication.
elli
This is a recurring question. The only generic way that I know is the use of
the IOCTL_NDIS_QUERY_GLOBAL_STATS parameter to DeviceIoControl(). A sample
is demonstrated in macaddr.c on DDK. This is for NT 4, I’m fairly sure it
can be done in Win 2000 as well, but it does not work for Win 98/95. This
call will make a call to your Query routine so you will not have to add “non
NDIS” code or headers.
-----Original Message-----
From: xxxxx@intel.com [mailto:xxxxx@intel.com]
Sent: Tuesday, July 11, 2000 9:00 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS and IOCTL
HI
I am writing a NDIS miniport driver for NIC card. I want a user mode
applications to communicate with NDIS Miniport driver via IOCTL. I have
used NdisMRegisterDevice API to expose a symbolic link to user mode. Is it
a preferred way to do? Is there any alternative approach?
Also I have to give a set of dispatch routines (Major function array) along
with the call to NdisMRegisterDevice API. I am just interested in
IRP_MJ_DEVICE_CONTROL messages. But in NDIS, I cannot access the IRP
structure and IRP related functions. In order to access the IRP related
structure, I have to include ntddk.h. Is it recommended to include ntddk.h
in NDIS drivers?
Thanks in advance
Ravindra
You are currently subscribed to ntdev as: xxxxx@moore-solutions.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)