Re: NdisMIndicateReceivePacket for large packets
- From: Anton Bassov <AntonBassov@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Feb 2007 19:51:00 -0800
Please be assured that miniport driver developers don't break rules
just of fun. They have reasons.
....... which is not going to make your life any easier if, as NDIS IM
developer, you have a misfortune to come across such miniport driver - out of
1000 clients 999 will be happy about your NDIS IM, and 1 (i.e. the one that
has this "masterpiece" on his machine) will complain. Therefore, it may take
you quite a while to figure out what is going on, and, after you do, I don't
really think that you will readily accept an argument like "I just had a
reason to do things this way" from the developer who wrote this
"masterpiece"....
In general, I believe that drivers should always expose a "proper" interface
on both upper and lower edges, no matter how they do things internally. If
you take this approach, you will never ever come into any conflict either
with the system or with the third-party software - even if internally your
driver is written "improperly". Unfortunately, most of AV/PF writers seem to
have a different opinion on the subject......
Anton Bassov
"Pavel A." wrote:
"Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx> wrote in message news:eTzbFBaQHHA.4404@xxxxxxxxxxxxxxxxxxxxxxx.
<soviet_bloke@xxxxxxxxxxx> wrote in message news:1169851453.832988.179860@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Eric,
Don't count on anything - even if your test show that everything works
fine......
Tricks like that are the main reason why the same NDIS IM may work
perfectly well with adapter X and fail with adapter Y for no obvious
reason. In other words, please don't do it - you will do a huge favour
to any NDIS-level developer who comes across your driver...
<rant>I'd really like to tell this to a lot of the Wi-Fi miniport driver developers...</rant>
Please be assured that miniport driver developers don't break rules just of fun. They have reasons.
And these reasons often are specific needs of customers, partners
and others we *must* appeace.
In the specific case of indicating up large packets - this may occur with some
drivers that have "wi-fi sniffer mode" - when they indicate raw .11 PDUs.
Regards,
--PA
- Prev by Date: Re: How to remove default Layer 2 multicast addresses in miniport
- Next by Date: Re: newbie for searching a usbaudio.sys lower filter sample code!!
- Previous by thread: RE: Help! Print Processor Clipping Path
- Next by thread: Re: NdisMIndicateReceivePacket for large packets
- Index(es):
Relevant Pages
|
