Thomas,
As you noticed in my previous questions, I'm analyzing the passthru example
you provided at your site...
therefore I just want to double check my understanding of the Passthru
layered structure with you...
in whole, Passthru is an intermediate (IM) driver type reside bellow the IP
layer and above a miniport driver.
therefore the MINIPORT.C provides the functionality necessary for the lower
edge (bellow) of the IM and PROTOCOL.C provides the functionality for the
upper edge (above) support.
Is this a correct ?

thankx

Re: PASSTHRU by Thomas/MS by Maxim

Maxim
Tue Oct 12 17:25:31 CDT 2004

> therefore the MINIPORT.C provides the functionality necessary for the lower
> edge (bellow) of the IM and PROTOCOL.C provides the functionality for the

Protocol.C is the lower egde of the IM, which talks to adapter below.
Miniport.C is the upper edge of the IM, which talks to protocols above.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com



Re: PASSTHRU by Thomas/MS by Harry

Harry
Tue Oct 12 17:29:06 CDT 2004

, I had it completely reverse...
thanks for the clarificatio
"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:uLSx4nKsEHA.1988@TK2MSFTNGP11.phx.gbl...
> > therefore the MINIPORT.C provides the functionality necessary for the
lower
> > edge (bellow) of the IM and PROTOCOL.C provides the functionality for
the
>
> Protocol.C is the lower egde of the IM, which talks to adapter below.
> Miniport.C is the upper edge of the IM, which talks to protocols above.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
>



Re: PASSTHRU by Thomas/MS by Thomas

Thomas
Tue Oct 12 17:28:25 CDT 2004


"Harry Potter" <hpotter@azkabar.com> wrote in message
news:uEnMEWKsEHA.3460@TK2MSFTNGP15.phx.gbl...
> Thomas,
> As you noticed in my previous questions, I'm analyzing the passthru
> example
> you provided at your site...
> therefore I just want to double check my understanding of the Passthru
> layered structure with you...
> in whole, Passthru is an intermediate (IM) driver type reside bellow the
> IP
> layer and above a miniport driver.
> therefore the MINIPORT.C provides the functionality necessary for the
> lower
> edge (bellow) of the IM and PROTOCOL.C provides the functionality for the
> upper edge (above) support.
> Is this a correct ?
>

I think it's backwards.

Lookup the DDK topic "NDIS Filter Intermediate Drivers".

Thomas F. Divine, Windows DDK MVP
http://www.rawether.net

> thankx
>
>



Re: PASSTHRU by Thomas/MS by Harry

Harry
Tue Oct 12 17:30:37 CDT 2004

I had it completely reverse, thankx for the clarification...
but the IM resides bellow the IP layer, right?

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:uLSx4nKsEHA.1988@TK2MSFTNGP11.phx.gbl...
> > therefore the MINIPORT.C provides the functionality necessary for the
lower
> > edge (bellow) of the IM and PROTOCOL.C provides the functionality for
the
>
> Protocol.C is the lower egde of the IM, which talks to adapter below.
> Miniport.C is the upper edge of the IM, which talks to protocols above.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
>



Re: PASSTHRU by Thomas/MS by Maxim

Maxim
Tue Oct 12 17:37:35 CDT 2004

> but the IM resides bellow the IP layer, right?

Yes.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com



Re: PASSTHRU by Thomas/MS by Harry

Harry
Tue Oct 12 17:40:09 CDT 2004

Thank you...
"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:uH0QquKsEHA.224@TK2MSFTNGP15.phx.gbl...
> > but the IM resides bellow the IP layer, right?
>
> Yes.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
>



Re: PASSTHRU by Thomas/MS by Michael

Michael
Wed Oct 13 04:44:35 CDT 2004

Harry,

When I've needed IM finctionality in one driver, I started from Mcrosoft's
MUX.
Really MUX is not working. As example, if you set up MUX, your comp can't
reboot...:(((

After some time I built the dirver is based on Netvmini and Ndisprot
examples.
I mix the code inside one driver and going forward.
Works fine.

I glad, if my experience helps you...

Regards,
Michael.


"Harry Potter" <hpotter@azkabar.com> wrote in message
news:uEnMEWKsEHA.3460@TK2MSFTNGP15.phx.gbl...
> Thomas,
> As you noticed in my previous questions, I'm analyzing the passthru
example
> you provided at your site...
> therefore I just want to double check my understanding of the Passthru
> layered structure with you...
> in whole, Passthru is an intermediate (IM) driver type reside bellow the
IP
> layer and above a miniport driver.
> therefore the MINIPORT.C provides the functionality necessary for the
lower
> edge (bellow) of the IM and PROTOCOL.C provides the functionality for the
> upper edge (above) support.
> Is this a correct ?
>
> thankx
>
>



Re: PASSTHRU by Thomas/MS by Harry

Harry
Wed Oct 13 11:27:14 CDT 2004

sure, thanks for the note.

"Michael Grobelkovsky" <michaelg@milcse.cig.mot.com> wrote in message
news:ckitl9$k7c$1@newshost.mot.com...
> Harry,
>
> When I've needed IM finctionality in one driver, I started from Mcrosoft's
> MUX.
> Really MUX is not working. As example, if you set up MUX, your comp can't
> reboot...:(((
>
> After some time I built the dirver is based on Netvmini and Ndisprot
> examples.
> I mix the code inside one driver and going forward.
> Works fine.
>
> I glad, if my experience helps you...
>
> Regards,
> Michael.
>
>
> "Harry Potter" <hpotter@azkabar.com> wrote in message
> news:uEnMEWKsEHA.3460@TK2MSFTNGP15.phx.gbl...
> > Thomas,
> > As you noticed in my previous questions, I'm analyzing the passthru
> example
> > you provided at your site...
> > therefore I just want to double check my understanding of the Passthru
> > layered structure with you...
> > in whole, Passthru is an intermediate (IM) driver type reside bellow the
> IP
> > layer and above a miniport driver.
> > therefore the MINIPORT.C provides the functionality necessary for the
> lower
> > edge (bellow) of the IM and PROTOCOL.C provides the functionality for
the
> > upper edge (above) support.
> > Is this a correct ?
> >
> > thankx
> >
> >
>
>



Re: PASSTHRU by Thomas/MS by Thomas

Thomas
Wed Oct 13 11:40:14 CDT 2004


"Michael Grobelkovsky" <michaelg@milcse.cig.mot.com> wrote in message
news:ckitl9$k7c$1@newshost.mot.com...
> Harry,
>
> When I've needed IM finctionality in one driver, I started from Mcrosoft's
> MUX.
> Really MUX is not working. As example, if you set up MUX, your comp can't
> reboot...:(((
>

Humm... Really?

Although the behavior of MUX is a little confusing, it certainly isn't that
bad. The Windows Server 2003 DDK MUX sample can be installed OK and doesn't
prevent machines at PCAUSA from re-booting.

The connections that are left in the Network Control Panel are bewildering,
however.

Good luck,

Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com

> After some time I built the dirver is based on Netvmini and Ndisprot
> examples.
> I mix the code inside one driver and going forward.
> Works fine.
>
> I glad, if my experience helps you...
>
> Regards,
> Michael.
>
>
> "Harry Potter" <hpotter@azkabar.com> wrote in message
> news:uEnMEWKsEHA.3460@TK2MSFTNGP15.phx.gbl...
>> Thomas,
>> As you noticed in my previous questions, I'm analyzing the passthru
> example
>> you provided at your site...
>> therefore I just want to double check my understanding of the Passthru
>> layered structure with you...
>> in whole, Passthru is an intermediate (IM) driver type reside bellow the
> IP
>> layer and above a miniport driver.
>> therefore the MINIPORT.C provides the functionality necessary for the
> lower
>> edge (bellow) of the IM and PROTOCOL.C provides the functionality for the
>> upper edge (above) support.
>> Is this a correct ?
>>
>> thankx
>>
>>
>
>



Re: PASSTHRU by Thomas/MS by yianghan

yianghan
Tue Nov 16 16:25:04 CST 2004

hi Thomas,

do you know where can I find some sample code of NDIS 1-to-n (1 upper
virtual device interface vs. multi lower protocol interfaces) MUX
intermediate driver.
Thanks in advance.

Yiang Han

NET.COM


"Thomas F. Divine [DDK MVP]" wrote:

>
> "Michael Grobelkovsky" <michaelg@milcse.cig.mot.com> wrote in message
> news:ckitl9$k7c$1@newshost.mot.com...
> > Harry,
> >
> > When I've needed IM finctionality in one driver, I started from Mcrosoft's
> > MUX.
> > Really MUX is not working. As example, if you set up MUX, your comp can't
> > reboot...:(((
> >
>
> Humm... Really?
>
> Although the behavior of MUX is a little confusing, it certainly isn't that
> bad. The Windows Server 2003 DDK MUX sample can be installed OK and doesn't
> prevent machines at PCAUSA from re-booting.
>
> The connections that are left in the Network Control Panel are bewildering,
> however.
>
> Good luck,
>
> Thomas F. Divine, Windows DDK MVP
> http://www.pcausa.com
>
> > After some time I built the dirver is based on Netvmini and Ndisprot
> > examples.
> > I mix the code inside one driver and going forward.
> > Works fine.
> >
> > I glad, if my experience helps you...
> >
> > Regards,
> > Michael.
> >
> >
> > "Harry Potter" <hpotter@azkabar.com> wrote in message
> > news:uEnMEWKsEHA.3460@TK2MSFTNGP15.phx.gbl...
> >> Thomas,
> >> As you noticed in my previous questions, I'm analyzing the passthru
> > example
> >> you provided at your site...
> >> therefore I just want to double check my understanding of the Passthru
> >> layered structure with you...
> >> in whole, Passthru is an intermediate (IM) driver type reside bellow the
> > IP
> >> layer and above a miniport driver.
> >> therefore the MINIPORT.C provides the functionality necessary for the
> > lower
> >> edge (bellow) of the IM and PROTOCOL.C provides the functionality for the
> >> upper edge (above) support.
> >> Is this a correct ?
> >>
> >> thankx
> >>
> >>
> >
> >
>
>
>