Re: NDIS IM Layering
- From: Anton Bassov <AntonBassov@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 02:10:02 -0700
Thomas,
Agreed that the doc isn't crystal clear, but sometimes you have to
experiment a little to find what they really meant.
This is EXACTLY what the problem is all about - sometimes, in order to
understand what the doc *wants* to say, you have to experiment with your
code and/or disassemble the OS, and sometimes you may discover that
something the doc *wants* to say is somehow different from what it
*actually* says. However, at this point the practical usefullness of the doc
becomes questionable - after all, the very idea of documentation is to help
you with the development and to spare you all the trouble of doing your own
investigations.....
I think the problem lies with misunderstanding between those who write docs
and those who write the actual code. Unfortunately, in a company as large as
MSFT it is just inevitable, so that MSDN bugs are, apparently, not going
anywhere anytime soon (if ever).....
Anton Bassov
"Thomas F. Divine" wrote:
.
"Anton Bassov" <AntonBassov@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6D79BA59-382C-4918-B738-2B808429CC22@xxxxxxxxxxxxxxxx
In practice, I was able to install the WDK sample PassThru and our own
driver which is based on PassThru with no observable problems. Both
drivers
have their FilterClass specified as failover in their respective INF
files.
Am I misunderstanding something here? Is the documentation making a
recommendation instead of stating policy?
As you have experimentally established, this is just one more MSDN claim
that proved to be false, at least in respect of failover drivers. Another
similar claim can be found in NDIS 6 documentation - MSDN claims that you
cannot have more than one modifying LWF in the same stack, and this claim
is
false as well.....
I believe that you can read this claim a little differently.
In particular, you can only have one instance of your own modifying LWF on
the same stack. For example, if you have a LWF that can bind to 802.3 and
WLAN, then it will bind to one or the other but not both. In this case, the
modifying driver will probably bind as 802.3 above the Microsoft Native
Wi-Fi driver but will not bind a second time below the Native Wi-Fi filter.
A modifying filter setup to bind to 802.3 and WLAN will behave differently
and will, in fact, bind itself twice on the same stack.
Agreed that the doc isn't crystal clear, but sometimes you have to
experiment a little to find what they really meant.
Thomas F. Divine
Anton Bassov
"tnili" wrote:
According to the WDK documentation, you cannot have more than one NDIS IM
driver of a particular FilterClass (scheduler, loadbalance, failover) in
a
stack. This is found under the topic "Filter Intermediate Driver
Installation (NDIS 5.1)".
In practice, I was able to install the WDK sample PassThru and our own
driver which is based on PassThru with no observable problems. Both
drivers
have their FilterClass specified as failover in their respective INF
files.
Am I misunderstanding something here? Is the documentation making a
recommendation instead of stating policy?
- References:
- NDIS IM Layering
- From: tnili
- Re: NDIS IM Layering
- From: Thomas F. Divine
- NDIS IM Layering
- Prev by Date: PCIe 64b addressing under Vista.
- Next by Date: Re: NDIS IM Layering
- Previous by thread: Re: NDIS IM Layering
- Next by thread: NDIS IM, ethernet loopback
- Index(es):
Relevant Pages
|
