Is it possible to handle IOCTLs in NDIS miniport
drivers? Do I have to write a protocol driver to bind
with the miniport driver for having this
functionality? Can somebody please explain?
Thanks,
N.T. Dev
Do You Yahoo!?
Send a newsletter, share photos & files, conduct polls, organize chat events. Visit http://in.groups.yahoo.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Yes, you can handle IOCTLs in a NDIS miniport but you don’t generally want
to do this. Well, it really depends. If you want a solution that will
work across all WDM platforms with one set of binaries, then you will want
to create a custom protocol driver which creates a symbolic link and thus
can be opened via CreateFile from your app. The protocol will also have
IOCTLs which are accessible via DeviceIoControl. Have the protocol bind
over your miniport and talk to your miniport using custom OIDs. Seem like
a royal pain in the old keester just to do something simple like talk to
your miniport?? Well, if you don’t do this, then there is no way to create
one binary to work on 98 through XP that will pass WHQL. There is an NDIS
function in 2000/XP called NdisMRegisterDevice which will let you create a
symbolic link for a miniport. Problem is, this call doesn’t work on Win9x,
actually I can’t remember about Me. So, on Win9x platforms you could call
IoCreateDevice and IoCreateSymbolicLink to create your own device object
and symbolic link, and then you can take over the dispatch function
pointers in the Driver Object and filter your IOCTL calls, but if you call
either of the aforementtioned IoXxx functions in a 2000 or XP miniport you
will fail WHQL and they will not give you a pass on this. So, you cannot
make one binary to work under both platforms in this way. So, the protocol
solution is the best if you care about cross-platform compatibility. If
not, then I already explained the alternatives. Good luck.
Bill McKenzie
Software Engineer
bSquare Corporation
On 10/08/01, “=?iso-8859-1?q?NT=20Dev?= ” wrote:
> Is it possible to handle IOCTLs in NDIS miniport
> drivers? Do I have to write a protocol driver to bind
> with the miniport driver for having this
> functionality? Can somebody please explain?
>
> Thanks,
> N.T. Dev
>
>
> ____________________________________________________________
> Do You Yahoo!?
> Send a newsletter, share photos & files, conduct polls, organize chat events. Visit http://in.groups.yahoo.com
>
> —
> You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Can the “query global stats” IOCTL + custom OIDs help in this case?
----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Tuesday, October 09, 2001 6:00 PM
Subject: [ntdev] Re: IOCTLs in NDIS miniport driver ???
> Yes, you can handle IOCTLs in a NDIS miniport but you don’t generally want
> to do this. Well, it really depends. If you want a solution that will
> work across all WDM platforms with one set of binaries, then you will want
> to create a custom protocol driver which creates a symbolic link and thus
> can be opened via CreateFile from your app. The protocol will also have
> IOCTLs which are accessible via DeviceIoControl. Have the protocol bind
> over your miniport and talk to your miniport using custom OIDs. Seem like
> a royal pain in the old keester just to do something simple like talk to
> your miniport?? Well, if you don’t do this, then there is no way to create
> one binary to work on 98 through XP that will pass WHQL. There is an NDIS
> function in 2000/XP called NdisMRegisterDevice which will let you create a
> symbolic link for a miniport. Problem is, this call doesn’t work on Win9x,
> actually I can’t remember about Me. So, on Win9x platforms you could call
> IoCreateDevice and IoCreateSymbolicLink to create your own device object
> and symbolic link, and then you can take over the dispatch function
> pointers in the Driver Object and filter your IOCTL calls, but if you call
> either of the aforementtioned IoXxx functions in a 2000 or XP miniport you
> will fail WHQL and they will not give you a pass on this. So, you cannot
> make one binary to work under both platforms in this way. So, the protocol
> solution is the best if you care about cross-platform compatibility. If
> not, then I already explained the alternatives. Good luck.
>
> Bill McKenzie
> Software Engineer
> bSquare Corporation
>
>
> On 10/08/01, “=?iso-8859-1?q?NT=20Dev?= ” wrote:
> > Is it possible to handle IOCTLs in NDIS miniport
> > drivers? Do I have to write a protocol driver to bind
> > with the miniport driver for having this
> > functionality? Can somebody please explain?
> >
> > Thanks,
> > N.T. Dev
> >
> >
> > ____________________________________________________________
> > Do You Yahoo!?
> > Send a newsletter, share photos & files, conduct polls, organize chat events. Visit http://in.groups.yahoo.com
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Doesn’t work on Win9x platforms.
Bill M.
On 10/10/01, ““Maxim S. Shatskih” ” wrote:
> Can the “query global stats” IOCTL + custom OIDs help in this case?
>
> ----- Original Message -----
> From:
> To: “NT Developers Interest List”
> Sent: Tuesday, October 09, 2001 6:00 PM
> Subject: [ntdev] Re: IOCTLs in NDIS miniport driver ???
>
>
> > Yes, you can handle IOCTLs in a NDIS miniport but you don’t generally want
> > to do this. Well, it really depends. If you want a solution that will
> > work across all WDM platforms with one set of binaries, then you will want
> > to create a custom protocol driver which creates a symbolic link and thus
> > can be opened via CreateFile from your app. The protocol will also have
> > IOCTLs which are accessible via DeviceIoControl. Have the protocol bind
> > over your miniport and talk to your miniport using custom OIDs. Seem like
> > a royal pain in the old keester just to do something simple like talk to
> > your miniport?? Well, if you don’t do this, then there is no way to create
> > one binary to work on 98 through XP that will pass WHQL. There is an NDIS
> > function in 2000/XP called NdisMRegisterDevice which will let you create a
> > symbolic link for a miniport. Problem is, this call doesn’t work on Win9x,
> > actually I can’t remember about Me. So, on Win9x platforms you could call
> > IoCreateDevice and IoCreateSymbolicLink to create your own device object
> > and symbolic link, and then you can take over the dispatch function
> > pointers in the Driver Object and filter your IOCTL calls, but if you call
> > either of the aforementtioned IoXxx functions in a 2000 or XP miniport you
> > will fail WHQL and they will not give you a pass on this. So, you cannot
> > make one binary to work under both platforms in this way. So, the protocol
> > solution is the best if you care about cross-platform compatibility. If
> > not, then I already explained the alternatives. Good luck.
> >
> > Bill McKenzie
> > Software Engineer
> > bSquare Corporation
> >
> >
> > On 10/08/01, “=?iso-8859-1?q?NT=20Dev?= ” wrote:
> > > Is it possible to handle IOCTLs in NDIS miniport
> > > drivers? Do I have to write a protocol driver to bind
> > > with the miniport driver for having this
> > > functionality? Can somebody please explain?
> > >
> > > Thanks,
> > > N.T. Dev
> > >
> > >
> > > ____________________________________________________________
> > > Do You Yahoo!?
> > > Send a newsletter, share photos & files, conduct polls, organize chat events. Visit http://in.groups.yahoo.com
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com