hello folks,
I have an NDIS miniport driver for windows XP and one for winvista. How do I
ensure (from INFs) that the XP one doesnt load on vista and vice versa?
thanks
AP
By creating a separate decorated sections which specify NT. (NT.5,
NT.6) to filter the results that the device installer will select based on
platform version. I am pretty sure there is an example of this in the WDK.
Read the section in the WDK titled “INF Manufacturer Section”
and do something akin to:
[Manufacturer]
FooCo=FooNic5
[Manufacturer.NT]
FooCo=FooNic5,NT5
FooCo=FooNic6,NT6
[FooNic5]
; NDIS5
[FooNic6]
; NDIS6
It is all spelled out in the docs.
dave
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, March 04, 2008 11:57 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] INFs
hello folks,
I have an NDIS miniport driver for windows XP and one for winvista. How do I
ensure (from INFs) that the XP one doesnt load on vista and vice versa?
thanks
AP
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
david,
thanks for the pointer. But we already have this in the XP installer INF
[Manufacturer]
%Foo% = Foo,NTx86.5.1
this INF is meant for XP and I see that when Vista is pointed to it, it
gladly installs the XP drivers. *this is something I want to prevent*.
Please note, we have a totally different INF for vista, the point here is
preventing user from accidentally installing the wrong driver by clicking
the wrong INF.
So is there a way?
AP
On Wed, Mar 5, 2008 at 12:18 AM, David R. Cattley wrote:
> By creating a separate decorated sections which specify NT. (NT.5,
> NT.6) to filter the results that the device installer will select based on
> platform version. I am pretty sure there is an example of this in the WDK.
>
>
>
> Read the section in the WDK titled “INF Manufacturer Section”
>
>
>
> and do something akin to:
>
>
>
> [Manufacturer]
>
> FooCo=FooNic5
>
>
>
> [Manufacturer.NT]
>
> FooCo=FooNic5,NT5
>
> FooCo=FooNic6,NT6
>
>
>
> [FooNic5]
>
> ; NDIS5
>
>
>
> [FooNic6]
>
> ; NDIS6
>
>
>
> It is all spelled out in the docs.
>
>
>
> dave
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, March 04, 2008 11:57 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] INFs
>
>
>
> hello folks,
>
>
>
> I have an NDIS miniport driver for windows XP and one for winvista. How do
> I ensure (from INFs) that the XP one doesnt load on vista and vice versa?
>
>
>
> thanks
>
>
>
> AP
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
I do not think there is a way to do this with two separate inf files. The
mechanism works for one inf file that installs two different binaries.
On Wed, Mar 5, 2008 at 9:34 AM, A P wrote:
> david,
>
> thanks for the pointer. But we already have this in the XP installer INF
>
> [Manufacturer]
> %Foo% = Foo,NTx86.5.1
>
> this INF is meant for XP and I see that when Vista is pointed to it, it
> gladly installs the XP drivers. this is something I want to prevent.
>
> Please note, we have a totally different INF for vista, the point here is
> preventing user from accidentally installing the wrong driver by clicking
> the wrong INF.
>
> So is there a way?
>
> AP
>
>
>
>
>
> On Wed, Mar 5, 2008 at 12:18 AM, David R. Cattley
> wrote:
>
> > By creating a separate decorated sections which specify NT. (NT.5,
> > NT.6) to filter the results that the device installer will select based
> > on platform version. I am pretty sure there is an example of this in the
> > WDK.
> >
> >
> >
> > Read the section in the WDK titled “INF Manufacturer Section”
> >
> >
> >
> > and do something akin to:
> >
> >
> >
> > [Manufacturer]
> >
> > FooCo=FooNic5
> >
> >
> >
> > [Manufacturer.NT]
> >
> > FooCo=FooNic5,NT5
> >
> > FooCo=FooNic6,NT6
> >
> >
> >
> > [FooNic5]
> >
> > ; NDIS5
> >
> >
> >
> > [FooNic6]
> >
> > ; NDIS6
> >
> >
> >
> > It is all spelled out in the docs.
> >
> >
> >
> > dave
> >
> >
> >
> > From: xxxxx@lists.osr.com [mailto:
> > xxxxx@lists.osr.com] *On Behalf Of *A P
> > Sent: Tuesday, March 04, 2008 11:57 AM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] INFs
> >
> >
> >
> > hello folks,
> >
> >
> >
> > I have an NDIS miniport driver for windows XP and one for winvista. How
> > do I ensure (from INFs) that the XP one doesnt load on vista and vice versa?
> >
> >
> >
> > thanks
> >
> >
> >
> > AP
> >
> > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging
> > and other seminars visit: http://www.osr.com/seminars To unsubscribe,
> > visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
–
Mark Roddy
(Mark: I think that it is possible, even with multiple INFs. I recall
having done it to block a driver from installing on NT6 that would only work
on NT5. The trick was to have *empty* sections for the platform you don’t
want to install.)
I think that it goes something like this:
[Manufacturer]
%Foo% = Foo5 ; Win2K - Omit to prevent Win2K
[Manufacturer.NT.5]
%Foo% = Foo5, NT.5 ; WinXP - Omit to prevent WinXP
[Manufacturer.NT.6]
%Foo%=Foo6, NT.6 ; LH - Omit to prevent LH
But I am only working from memory and I cannot put my hands on a real
example at this point.
Read all of the sections on platform decoration. There are a dozen (ok,
that is an exaggeration but not much of one) platform, version, and section
decoration ‘tweaks’ that have been added to INFs to handle different aspects
of this problem. If you look at the different places and methods setupdi
attempts to ‘decorate’ a section with OS, architecture, or version, you will
figure it out.
-dave
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Wednesday, March 05, 2008 9:49 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] INFs
I do not think there is a way to do this with two separate inf files. The
mechanism works for one inf file that installs two different binaries.
On Wed, Mar 5, 2008 at 9:34 AM, A P wrote:
david,
thanks for the pointer. But we already have this in the XP installer INF
[Manufacturer]
%Foo% = Foo,NTx86.5.1
this INF is meant for XP and I see that when Vista is pointed to it, it
gladly installs the XP drivers. this is something I want to prevent.
Please note, we have a totally different INF for vista, the point here is
preventing user from accidentally installing the wrong driver by clicking
the wrong INF.
So is there a way?
AP
On Wed, Mar 5, 2008 at 12:18 AM, David R. Cattley wrote:
By creating a separate decorated sections which specify NT. (NT.5,
NT.6) to filter the results that the device installer will select based on
platform version. I am pretty sure there is an example of this in the WDK.
Read the section in the WDK titled “INF Manufacturer Section”
and do something akin to:
[Manufacturer]
FooCo=FooNic5
[Manufacturer.NT]
FooCo=FooNic5,NT5
FooCo=FooNic6,NT6
[FooNic5]
; NDIS5
[FooNic6]
; NDIS6
It is all spelled out in the docs.
dave
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Tuesday, March 04, 2008 11:57 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] INFs
hello folks,
I have an NDIS miniport driver for windows XP and one for winvista. How do I
ensure (from INFs) that the XP one doesnt load on vista and vice versa?
thanks
AP
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
–
Mark Roddy — NTDEV is sponsored by OSR For our schedule of WDF, WDM,
debugging and other seminars visit: http://www.osr.com/seminars To
unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Ok - I was thinking the OP did not want to change his existing XP package.
But as I think about that, it doesn’t seem to make much sense. If an end
user has the XP package, and if that package does not restrict installation
on Vista, it will install on Vista. Instead the OP is going to have to
change the XP package or combine it with the Vista package.
On Wed, Mar 5, 2008 at 12:50 PM, David R. Cattley wrote:
> (Mark: I think that it is possible, even with multiple INFs. I recall
> having done it to block a driver from installing on NT6 that would only work
> on NT5. The trick was to have empty sections for the platform you
> don’t want to install.)
>
>
>
> I think that it goes something like this:
>
>
>
> [Manufacturer]
>
> %Foo% = Foo5 ; Win2K ? Omit to prevent Win2K
>
>
>
> [Manufacturer.NT.5]
>
> %Foo% = Foo5, NT.5 ; WinXP ? Omit to prevent WinXP
>
>
>
> [Manufacturer.NT.6]
>
> %Foo%=Foo6, NT.6 ; LH ? Omit to prevent LH
>
>
>
>
>
> But I am only working from memory and I cannot put my hands on a real
> example at this point.
>
>
>
> Read all of the sections on platform decoration. There are a dozen (ok,
> that is an exaggeration but not much of one) platform, version, and section
> decoration ‘tweaks’ that have been added to INFs to handle different aspects
> of this problem. If you look at the different places and methods setupdi
> attempts to ‘decorate’ a section with OS, architecture, or version, you will
> figure it out.
>
>
>
> -dave
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Mark Roddy
> Sent: Wednesday, March 05, 2008 9:49 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] INFs
>
>
>
> I do not think there is a way to do this with two separate inf files. The
> mechanism works for one inf file that installs two different binaries.
>
> On Wed, Mar 5, 2008 at 9:34 AM, A P wrote:
>
> david,
>
>
>
> thanks for the pointer. But we already have this in the XP installer INF
>
>
>
> [Manufacturer]
> %Foo% = Foo,NTx86.5.1
>
>
>
> this INF is meant for XP and I see that when Vista is pointed to it, it
> gladly installs the XP drivers. this is something I want to prevent.
>
>
>
> Please note, we have a totally different INF for vista, the point here is
> preventing user from accidentally installing the wrong driver by clicking
> the wrong INF.
>
>
>
> So is there a way?
>
>
>
> AP
>
>
>
>
>
>
>
>
>
> On Wed, Mar 5, 2008 at 12:18 AM, David R. Cattley
> wrote:
>
> By creating a separate decorated sections which specify NT. (NT.5,
> NT.6) to filter the results that the device installer will select based on
> platform version. I am pretty sure there is an example of this in the WDK.
>
>
>
> Read the section in the WDK titled “INF Manufacturer Section”
>
>
>
> and do something akin to:
>
>
>
> [Manufacturer]
>
> FooCo=FooNic5
>
>
>
> [Manufacturer.NT]
>
> FooCo=FooNic5,NT5
>
> FooCo=FooNic6,NT6
>
>
>
> [FooNic5]
>
> ; NDIS5
>
>
>
> [FooNic6]
>
> ; NDIS6
>
>
>
> It is all spelled out in the docs.
>
>
>
> dave
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *A P
> Sent: Tuesday, March 04, 2008 11:57 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] INFs
>
>
>
> hello folks,
>
>
>
> I have an NDIS miniport driver for windows XP and one for winvista. How do
> I ensure (from INFs) that the XP one doesnt load on vista and vice versa?
>
>
>
> thanks
>
>
>
> AP
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
> –
> Mark Roddy — NTDEV is sponsored by OSR For our schedule of WDF, WDM,
> debugging and other seminars visit: http://www.osr.com/seminars To
> unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Mark Roddy