Re: OOB Information
- From: "Rodel Miguel" <rodel_miguel@xxxxxxxxx>
- Date: Mon, 14 Apr 2008 10:36:59 +0800
Thanks Pavel! There is a real need to talk to the driver... :-) Ok, I'll
post on device drivers. Thanks again.
"Pavel A." <pavel_a@xxxxxxxxxxxxxxx> wrote in message
news:uO9uMOCnIHA.5704@xxxxxxxxxxxxxxxxxxxxxxx
Applications don't talk directly to NDIS layer (except of few pervert
cases)
so they don't pass any OOB information to the drivers.
The OOB info is created and consumed by kernel-mode clients of NDIS,
such as TDI layer, various protocol drivers etc.
If you're still looking for more details, please ask in
microsoft.public.development.device.drivers.
Regards,
--PA
"Rodel Miguel" <rodel_miguel@xxxxxxxxx> wrote in message
news:OneLNQ8mIHA.944@xxxxxxxxxxxxxxxxxxxxxxx
Hi Gurus,
Can you help me give some information to my NDIS driver whenever I send a
specific packet? MSDN tells me to use OOB Information which is attached
to every packet descriptor whenever MiniportSend is being called. How
can an application supply some OOB information to the driver? How can
the driver access the OOB information? Can you point me to proper
tutorials on this?
Thank you very much!
Best Regards,
Rodel
.
- References:
- OOB Information
- From: Rodel Miguel
- Re: OOB Information
- From: Pavel A.
- OOB Information
- Prev by Date: LSALogonUser and smart cards....
- Next by Date: Re: Changing MAC address of physical adapters from Intermediate driver
- Previous by thread: Re: OOB Information
- Next by thread: dhcpsapi.h
- Index(es):
Relevant Pages
|