intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the intermediate
driver installation.

This is on 2K/XP for now.

Sunil


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 could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. But, what would be in your IM driver that you can’t
push down into your miniport in the first place? Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.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

Bryan -

What do you suggest if you only own the IM driver? not the miniport. Its
been my observation that new hardware does not bind automatically to the
DDK sample passthru.sys (at least on XP). Thanks.

PJ KIrner

“Bryan Burgin”
Sent by: xxxxx@lists.osr.com
02/21/02 05:10 PM
Please respond to “NT Developers Interest List”

To: “NT Developers Interest List”
cc:
Subject: [ntdev] RE: intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. But, what would be in your IM driver that you can’t
push down into your miniport in the first place? Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@funk.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

Yes, you’re right; if you don’t own the miniport then you need the extra IM layer – I was keying on the phrase ‘I have…’. But, then, you probably can’t do a CoInstaller either, because you don’t own the miniport’s INF.

I’ve seen some new hardware where their lower edge was defined as “none” instead of “Ethernet”. PASSTHRU will bind so long as the list of media types listed in PASSTHRU’s FilterMediaType (HKR,Ndi\Interfaces,FilterMediaTypes,“ethernet, tokenring, fddi, wan”) matches an entry in the hardware’s LowerRange (HKR,Ndi\Interfaces,LowerRange,ethernet).

I’ve seen this in cases where the device was sitting out on the USB hub. But ultimately, the device was exposing Ethernet as its lower edge and should have declared this in their .Inf.

I would be interested if you’ve seen examples of PASSTHRU not binding on 2K or XP to a miniport that isn’t due to this.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@funk.com [mailto:xxxxx@funk.com]
Sent: Thursday, February 21, 2002 2:24 PM
To: NT Developers Interest List
Cc: Bryan Burgin
Subject: Re: [ntdev] RE: intermediate driver installation

Bryan -

What do you suggest if you only own the IM driver? not the miniport. ?Its been my observation that new hardware does not bind automatically to the DDK sample passthru.sys (at least on XP). ?Thanks.

PJ KIrner

“Bryan Burgin”
Sent by: xxxxx@lists.osr.com
02/21/02 05:10 PM
Please respond to “NT Developers Interest List”
? ? ? ?
? ? ? ? To: ? ? ? ?“NT Developers Interest List”
? ? ? ? cc: ? ? ? ?
? ? ? ? Subject: ? ? ? ?[ntdev] RE: intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. ?But, what would be in your IM driver that you can’t
push down into your miniport in the first place? ?Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@funk.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

Hi Bryan,

I have got a similar problem (maybe 50% similar) with the passthru example
in the XP DDK, which is not installed properly, when trying to install it by
SNETCFG.EXE app from XP DDK!!! It is possible to install it when I use the
GUI installation (Network Property Dialog). Any Idea what the problem could
be ?

regards

johnny

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bryan Burgin
Sent: Freitag, 22. Februar 2002 01:33
To: NT Developers Interest List
Subject: [ntdev] RE: intermediate driver installation

Yes, you’re right; if you don’t own the miniport then you need the extra IM
layer – I was keying on the phrase ‘I have…’. But, then, you probably
can’t do a CoInstaller either, because you don’t own the miniport’s INF.

I’ve seen some new hardware where their lower edge was defined as “none”
instead of “Ethernet”. PASSTHRU will bind so long as the list of media
types listed in PASSTHRU’s FilterMediaType
(HKR,Ndi\Interfaces,FilterMediaTypes,“ethernet, tokenring, fddi, wan”)
matches an entry in the hardware’s LowerRange
(HKR,Ndi\Interfaces,LowerRange,ethernet).

I’ve seen this in cases where the device was sitting out on the USB hub.
But ultimately, the device was exposing Ethernet as its lower edge and
should have declared this in their .Inf.

I would be interested if you’ve seen examples of PASSTHRU not binding on 2K
or XP to a miniport that isn’t due to this.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights
(c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@funk.com [mailto:xxxxx@funk.com]
Sent: Thursday, February 21, 2002 2:24 PM
To: NT Developers Interest List
Cc: Bryan Burgin
Subject: Re: [ntdev] RE: intermediate driver installation

Bryan -

What do you suggest if you only own the IM driver? not the miniport.  Its
been my observation that new hardware does not bind automatically to the DDK
sample passthru.sys (at least on XP).  Thanks.

PJ KIrner

“Bryan Burgin”
Sent by: xxxxx@lists.osr.com
02/21/02 05:10 PM
Please respond to “NT Developers Interest List”

To: “NT Developers Interest List”
cc:
Subject: [ntdev] RE: intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. But, what would be in your IM driver that you can’t
push down into your miniport in the first place? Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@funk.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@yahoo.de
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

_________________________________________________________

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.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

Johnny,

The issue with the original poster was that PASSTHRU was already installed and bound to other miniports, but is not getting bound to a new miniport when the hardware for that miniport was installed.

This seems different from your situation, I think, where PASSTHRU will install through the Network Property Dialog but not through SNETCFG. There may be several reasons for this, but I’d like to know a little more detail. If it works in 2000 but not XP, it might be because of a security or a signed/unsigned driver issue. Before speculating further, please describe the symptoms you’re seeing (dialogs, error messages, logs, etc), the platforms (2000, XP or both), …, …, … .

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights
(c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: Johnny [mailto:xxxxx@yahoo.de]
Sent: Thursday, February 21, 2002 4:53 PM
To: NT Developers Interest List
Subject: [ntdev] RE: intermediate driver installation

Hi Bryan,

I have got a similar problem (maybe 50% similar) with the passthru example
in the XP DDK, which is not installed properly, when trying to install it by
SNETCFG.EXE app from XP DDK!!! It is possible to install it when I use the
GUI installation (Network Property Dialog). Any Idea what the problem could
be ?

regards

johnny

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bryan Burgin
Sent: Freitag, 22. Februar 2002 01:33
To: NT Developers Interest List
Subject: [ntdev] RE: intermediate driver installation

Yes, you’re right; if you don’t own the miniport then you need the extra IM
layer – I was keying on the phrase ‘I have…’. But, then, you probably
can’t do a CoInstaller either, because you don’t own the miniport’s INF.

I’ve seen some new hardware where their lower edge was defined as “none”
instead of “Ethernet”. PASSTHRU will bind so long as the list of media
types listed in PASSTHRU’s FilterMediaType
(HKR,Ndi\Interfaces,FilterMediaTypes,“ethernet, tokenring, fddi, wan”)
matches an entry in the hardware’s LowerRange
(HKR,Ndi\Interfaces,LowerRange,ethernet).

I’ve seen this in cases where the device was sitting out on the USB hub.
But ultimately, the device was exposing Ethernet as its lower edge and
should have declared this in their .Inf.

I would be interested if you’ve seen examples of PASSTHRU not binding on 2K
or XP to a miniport that isn’t due to this.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights
(c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@funk.com [mailto:xxxxx@funk.com]
Sent: Thursday, February 21, 2002 2:24 PM
To: NT Developers Interest List
Cc: Bryan Burgin
Subject: Re: [ntdev] RE: intermediate driver installation

Bryan -

What do you suggest if you only own the IM driver? not the miniport. ?Its
been my observation that new hardware does not bind automatically to the DDK
sample passthru.sys (at least on XP). ?Thanks.

PJ KIrner

“Bryan Burgin”
Sent by: xxxxx@lists.osr.com
02/21/02 05:10 PM
Please respond to “NT Developers Interest List”
? ? ? ?
? ? ? ? To: ? ? ? ?“NT Developers Interest List”
? ? ? ? cc: ? ? ? ?
? ? ? ? Subject: ? ? ? ?[ntdev] RE: intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. ?But, what would be in your IM driver that you can’t
push down into your miniport in the first place? ?Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@funk.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@yahoo.de
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

_________________________________________________________

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com


You are currently subscribed to ntdev as: xxxxx@microsoft.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

Yes, we use a CoInstaller for exactly this purpose.

Stephan

On Thu, 21 Feb 2002 14:10:24 -0800, “Bryan Burgin”
wrote:

>You could write a CoInstaller for your miniport, reference it in the
>miniport’s INF and within the CoInstaller DLL fire off the installation
>of your IM driver. But, what would be in your IM driver that you can’t
>push down into your miniport in the first place? Why have the extra
>layers?
>
>Bryan S. Burgin
>xxxxx@microsoft.com
>
>This posting is provided “AS IS” with no warranties, and confers no
>rights (c) 2002 Microsoft Corporation. All rights reserved.
>
>-----Original Message-----
>From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]=20
>Sent: Thursday, February 21, 2002 7:45 AM
>To: NT Developers Interest List
>Subject: [ntdev] intermediate driver installation
>
>Hi,
>
>This might be a FAQ, but here goes anyways.=20
>
>How do I get a intermediate driver to automatically get installed=20
>when my ndis driver is installed.=20
>
>Here’s the scenario.=20
>
>I have a NDIS driver and inf.=20
>I have an intermediate driver and its two infs.=20
>
>When the user plugs in the hardware and points at my netcard inf, I want
>the adapter driver installed and then automatically start the
>intermediate
>driver installation.=20
>
>This is on 2K/XP for now.=20
>
>Sunil


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

Thanks for the reply.

We do own both the netcard driver and the intermediate driver.

The intermediate driver is not a straight passthru (1:1),
it is more of a mux(N:1) driver.

I had thought of the coinstaller and will look further into it.
I was wondering if there was a way just via the inf file. i.e. to
launch the intermediate drivers inf file from the netcard inf file?

Also with the coinstaller would the be portable to 9X/ME?
Or would the process be completly different.

Thanks again,

Sunil Sanwalka
Neesus Datacom

-----Original Message-----
From: xxxxx@www.neesus.com [mailto:xxxxx@www.neesus.com]On
Behalf Of Bryan Burgin
Sent: Thursday, February 21, 2002 5:10 PM
To: NT Developers Interest List
Cc: xxxxx@neesus.com
Subject: RE: [ntdev] intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. But, what would be in your IM driver that you can’t
push down into your miniport in the first place? Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.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

Bryan,

Is there a solution to the USB miniport problem?

Thanks
Qiang

-----Original Message-----
From: Bryan Burgin [mailto:xxxxx@microsoft.com]
Sent: Thursday, February 21, 2002 6:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: intermediate driver installation

Yes, you’re right; if you don’t own the miniport then you need the extra IM layer – I was keying on the phrase ‘I have…’. But, then, you probably can’t do a CoInstaller either, because you don’t own the miniport’s INF.

I’ve seen some new hardware where their lower edge was defined as “none” instead of “Ethernet”. PASSTHRU will bind so long as the list of media types listed in PASSTHRU’s FilterMediaType (HKR,Ndi\Interfaces,FilterMediaTypes,“ethernet, tokenring, fddi, wan”) matches an entry in the hardware’s LowerRange (HKR,Ndi\Interfaces,LowerRange,ethernet).

I’ve seen this in cases where the device was sitting out on the USB hub. But ultimately, the device was exposing Ethernet as its lower edge and should have declared this in their .Inf.

I would be interested if you’ve seen examples of PASSTHRU not binding on 2K or XP to a miniport that isn’t due to this.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@funk.com [mailto:xxxxx@funk.com]
Sent: Thursday, February 21, 2002 2:24 PM
To: NT Developers Interest List
Cc: Bryan Burgin
Subject: Re: [ntdev] RE: intermediate driver installation

Bryan -

What do you suggest if you only own the IM driver? not the miniport. ?Its been my observation that new hardware does not bind automatically to the DDK sample passthru.sys (at least on XP). ?Thanks.

PJ KIrner

“Bryan Burgin”
Sent by: xxxxx@lists.osr.com
02/21/02 05:10 PM
Please respond to “NT Developers Interest List”
? ? ? ?
? ? ? ? To: ? ? ? ?“NT Developers Interest List”
? ? ? ? cc: ? ? ? ?
? ? ? ? Subject: ? ? ? ?[ntdev] RE: intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. ?But, what would be in your IM driver that you can’t
push down into your miniport in the first place? ?Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@funk.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@ecutel.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

Bryan,

Is there a solution to the USB miniport problem? I actually has a USB miniport which does the lower edge declaration as “ethernet” in the INF, but still my IM can’t bind to it. It is Win2k

Thanks
Qiang

-----Original Message-----
From: Bryan Burgin [mailto:xxxxx@microsoft.com]
Sent: Thursday, February 21, 2002 6:33 PM
To: NT Developers Interest List
Subject: [ntdev] RE: intermediate driver installation

Yes, you’re right; if you don’t own the miniport then you need the extra IM layer – I was keying on the phrase ‘I have…’. But, then, you probably can’t do a CoInstaller either, because you don’t own the miniport’s INF.

I’ve seen some new hardware where their lower edge was defined as “none” instead of “Ethernet”. PASSTHRU will bind so long as the list of media types listed in PASSTHRU’s FilterMediaType (HKR,Ndi\Interfaces,FilterMediaTypes,“ethernet, tokenring, fddi, wan”) matches an entry in the hardware’s LowerRange (HKR,Ndi\Interfaces,LowerRange,ethernet).

I’ve seen this in cases where the device was sitting out on the USB hub. But ultimately, the device was exposing Ethernet as its lower edge and should have declared this in their .Inf.

I would be interested if you’ve seen examples of PASSTHRU not binding on 2K or XP to a miniport that isn’t due to this.

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@funk.com [mailto:xxxxx@funk.com]
Sent: Thursday, February 21, 2002 2:24 PM
To: NT Developers Interest List
Cc: Bryan Burgin
Subject: Re: [ntdev] RE: intermediate driver installation

Bryan -

What do you suggest if you only own the IM driver? not the miniport. ?Its been my observation that new hardware does not bind automatically to the DDK sample passthru.sys (at least on XP). ?Thanks.

PJ KIrner

“Bryan Burgin”
Sent by: xxxxx@lists.osr.com
02/21/02 05:10 PM
Please respond to “NT Developers Interest List”
? ? ? ?
? ? ? ? To: ? ? ? ?“NT Developers Interest List”
? ? ? ? cc: ? ? ? ?
? ? ? ? Subject: ? ? ? ?[ntdev] RE: intermediate driver installation

You could write a CoInstaller for your miniport, reference it in the
miniport’s INF and within the CoInstaller DLL fire off the installation
of your IM driver. ?But, what would be in your IM driver that you can’t
push down into your miniport in the first place? ?Why have the extra
layers?

Bryan S. Burgin
xxxxx@microsoft.com

This posting is provided “AS IS” with no warranties, and confers no
rights (c) 2002 Microsoft Corporation. All rights reserved.

-----Original Message-----
From: xxxxx@neesus.com [mailto:xxxxx@neesus.com]
Sent: Thursday, February 21, 2002 7:45 AM
To: NT Developers Interest List
Subject: [ntdev] intermediate driver installation

Hi,

This might be a FAQ, but here goes anyways.

How do I get a intermediate driver to automatically get installed
when my ndis driver is installed.

Here’s the scenario.

I have a NDIS driver and inf.
I have an intermediate driver and its two infs.

When the user plugs in the hardware and points at my netcard inf, I want
the adapter driver installed and then automatically start the
intermediate
driver installation.

This is on 2K/XP for now.

Sunil


You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@funk.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: xxxxx@ecutel.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