I would like to get something clarified:
Can XP drivers be used in 2K or should/must they be built using the 2K build environment? I believe that they are to be built using the 2K env. however I have received information saying that building a driver using the XP env. is good enough for both.
Or:
Is it simply a per case scenario in which, if you have no technical issues/problems with using the XP driver in 2K, go for it.
There are devices out there which use the same drivers for 2K and XP so either they are using the 2K driver in XP or the XP driver in 2K, which supports this case.
Thanks, Chris
The XP DDK has extensions that are not in the 2K DDK. I know you can test 2K drivers under XP, but you need care in going the other way.
–
Gary G. Little
xxxxx@broadstor.com
xxxxx@inland.net
“Chris Dore” wrote in message news:xxxxx@ntdev…
I would like to get something clarified:
Can XP drivers be used in 2K or should/must they be built using the 2K build environment? I believe that they are to be built using the 2K env. however I have received information saying that building a driver using the XP env. is good enough for both.
Or:
Is it simply a per case scenario in which, if you have no technical issues/problems with using the XP driver in 2K, go for it.
There are devices out there which use the same drivers for 2K and XP so either they are using the 2K driver in XP or the XP driver in 2K, which supports this case.
Thanks, Chris
>> Can XP drivers be
No. It might work for some drivers , while for other resolving imports will fail.
----- Original Message -----
From: Chris Dore
To: NT Developers Interest List
Sent: Tuesday, July 16, 2002 7:57 PM
Subject: [ntdev] Build Environments
I would like to get something clarified:
Can XP drivers be used in 2K or should/must they be built using the 2K build environment? I believe that they are to be built using the 2K env. however I have received information saying that building a driver using the XP env. is good enough for both.
Or:
Is it simply a per case scenario in which, if you have no technical issues/problems with using the XP driver in 2K, go for it.
There are devices out there which use the same drivers for 2K and XP so either they are using the 2K driver in XP or the XP driver in 2K, which supports this case.
Thanks, Chris
You are currently subscribed to ntdev as: xxxxx@rdsor.ro
To unsubscribe send a blank email to %%email.unsub%%
Right - you need to use the address lookup function
MmGetSystemRoutineAddress for any functionality that your XP driver might be
using that is not in W2K - which is why if the goal is to have a single
binary the path of least resistance is to use the W2K build environment as
suggested by the DDK. That way you can’t stray off the reservation
unintentionally.
The problem of course is that if you require a single binary *AND* you have
functional issues with XP that can only be resolved using XP-specifc api’s
then you have to go the MmGetSystemRoutineAddress route. At least they
published that interface and managed to get it into both W2K and XP. On the
projects that I have worked on where this issue did come up we continue to
build using W2K but import XP-specific APIs using MmGetSystemRoutineAddress.
I think that is the right way to go.
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@broadstor.com]
Sent: Tuesday, July 16, 2002 1:17 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Build Environments
The XP DDK has extensions that are not in the 2K DDK. I know you can test 2K
drivers under XP, but you need care in going the other way.
–
Gary G. Little
xxxxx@broadstor.com
xxxxx@inland.net
“Chris Dore” wrote in message news:xxxxx@ntdev…
I would like to get something clarified:
Can XP drivers be used in 2K or should/must they be built using the 2K build
environment? I believe that they are to be built using the 2K env. however I
have received information saying that building a driver using the XP env. is
good enough for both.
Or:
Is it simply a per case scenario in which, if you have no technical
issues/problems with using the XP driver in 2K, go for it.
There are devices out there which use the same drivers for 2K and XP so
either they are using the 2K driver in XP or the XP driver in 2K, which
supports this case.
Thanks, Chris
—
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to %%email.unsub%%
Donno how right Im here, but im really the adept of #ifdef #endif
Dan
----- Original Message -----
From: “Roddy, Mark”
To: “NT Developers Interest List”
Sent: Tuesday, July 16, 2002 10:17 PM
Subject: [ntdev] Re: Build Environments
> Right - you need to use the address lookup function
> MmGetSystemRoutineAddress for any functionality that your XP driver might
be
> using that is not in W2K - which is why if the goal is to have a single
> binary the path of least resistance is to use the W2K build environment as
> suggested by the DDK. That way you can’t stray off the reservation
> unintentionally.
>
> The problem of course is that if you require a single binary AND you
have
> functional issues with XP that can only be resolved using XP-specifc api’s
> then you have to go the MmGetSystemRoutineAddress route. At least they
> published that interface and managed to get it into both W2K and XP. On
the
> projects that I have worked on where this issue did come up we continue to
> build using W2K but import XP-specific APIs using
MmGetSystemRoutineAddress.
> I think that is the right way to go.
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@broadstor.com]
> Sent: Tuesday, July 16, 2002 1:17 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Build Environments
>
>
> The XP DDK has extensions that are not in the 2K DDK. I know you can test
2K
> drivers under XP, but you need care in going the other way.
>
> –
> Gary G. Little
> xxxxx@broadstor.com
> xxxxx@inland.net
> “Chris Dore” wrote in message news:xxxxx@ntdev…
> I would like to get something clarified:
>
> Can XP drivers be used in 2K or should/must they be built using the 2K
build
> environment? I believe that they are to be built using the 2K env. however
I
> have received information saying that building a driver using the XP env.
is
> good enough for both.
>
> Or:
>
> Is it simply a per case scenario in which, if you have no technical
> issues/problems with using the XP driver in 2K, go for it.
> There are devices out there which use the same drivers for 2K and XP so
> either they are using the 2K driver in XP or the XP driver in 2K, which
> supports this case.
>
> Thanks, Chris
>
> —
> You are currently subscribed to ntdev as: xxxxx@stratus.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>
Not if you want a single *binary*, right?
-----Original Message-----
From: Dan Partelly [mailto:xxxxx@rdsor.ro]
Sent: Tuesday, July 16, 2002 3:52 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Build Environments
Donno how right Im here, but im really the adept of #ifdef #endif
Dan
----- Original Message -----
From: “Roddy, Mark”
> To: “NT Developers Interest List”
> Sent: Tuesday, July 16, 2002 10:17 PM
> Subject: [ntdev] Re: Build Environments
>
>
> > Right - you need to use the address lookup function
> > MmGetSystemRoutineAddress for any functionality that your XP driver
> > might
> be
> > using that is not in W2K - which is why if the goal is to have a
> > single binary the path of least resistance is to use the W2K build
> > environment as suggested by the DDK. That way you can’t
> stray off the
> > reservation unintentionally.
> >
> > The problem of course is that if you require a single
> binary AND you
> have
> > functional issues with XP that can only be resolved using
> XP-specifc
> > api’s then you have to go the MmGetSystemRoutineAddress route. At
> > least they published that interface and managed to get it into both
> > W2K and XP. On
> the
> > projects that I have worked on where this issue did come up we
> > continue to build using W2K but import XP-specific APIs using
> MmGetSystemRoutineAddress.
> > I think that is the right way to go.
> >
> > -----Original Message-----
> > From: Gary G. Little [mailto:xxxxx@broadstor.com]
> > Sent: Tuesday, July 16, 2002 1:17 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Build Environments
> >
> >
> > The XP DDK has extensions that are not in the 2K DDK. I
> know you can
> > test
> 2K
> > drivers under XP, but you need care in going the other way.
> >
> > –
> > Gary G. Little
> > xxxxx@broadstor.com
> > xxxxx@inland.net
> > “Chris Dore” wrote in message
> > news:xxxxx@ntdev… I would like to get something clarified:
> >
> > Can XP drivers be used in 2K or should/must they be built
> using the 2K
> build
> > environment? I believe that they are to be built using the 2K env.
> > however
> I
> > have received information saying that building a driver
> using the XP
> > env.
> is
> > good enough for both.
> >
> > Or:
> >
> > Is it simply a per case scenario in which, if you have no technical
> > issues/problems with using the XP driver in 2K, go for it.
> There are
> > devices out there which use the same drivers for 2K and XP
> so either
> > they are using the 2K driver in XP or the XP driver in 2K, which
> > supports this case.
> >
> > Thanks, Chris
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@stratus.com To
> > unsubscribe send a blank email to %%email.unsub%%
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@rdsor.ro To
> > unsubscribe send a blank email to %%email.unsub%%
> >
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@stratus.com To unsubscribe send a blank email to
> %%email.unsub%%
>
>> Not if you want a single *binary*, right?
Obivioulsy no. Im the adept of multiple binaryes, in most of the cases.
Ppl who need binary compatibility should not only do what you said, but as
well read the headers step by step , because
they offer some defines which can alter binary compatibility, an example is
the single list case , and associated _WIN2K_COMPAT_SLIST_USAGE . This is
just an example , and if missed, some lookaside functions and single list
manipulation functions can break compatibility.
----- Original Message -----
From: “Roddy, Mark”
To: “NT Developers Interest List”
Sent: Tuesday, July 16, 2002 11:05 PM
Subject: [ntdev] Re: Build Environments
> Not if you want a single binary, right?
>
> > -----Original Message-----
> > From: Dan Partelly [mailto:xxxxx@rdsor.ro]
> > Sent: Tuesday, July 16, 2002 3:52 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Build Environments
> >
> >
> > Donno how right Im here, but im really the adept of #ifdef #endif
> >
> > Dan
> > ----- Original Message -----
> > From: “Roddy, Mark”
> > To: “NT Developers Interest List”
> > Sent: Tuesday, July 16, 2002 10:17 PM
> > Subject: [ntdev] Re: Build Environments
> >
> >
> > > Right - you need to use the address lookup function
> > > MmGetSystemRoutineAddress for any functionality that your XP driver
> > > might
> > be
> > > using that is not in W2K - which is why if the goal is to have a
> > > single binary the path of least resistance is to use the W2K build
> > > environment as suggested by the DDK. That way you can’t
> > stray off the
> > > reservation unintentionally.
> > >
> > > The problem of course is that if you require a single
> > binary AND you
> > have
> > > functional issues with XP that can only be resolved using
> > XP-specifc
> > > api’s then you have to go the MmGetSystemRoutineAddress route. At
> > > least they published that interface and managed to get it into both
> > > W2K and XP. On
> > the
> > > projects that I have worked on where this issue did come up we
> > > continue to build using W2K but import XP-specific APIs using
> > MmGetSystemRoutineAddress.
> > > I think that is the right way to go.
> > >
> > > -----Original Message-----
> > > From: Gary G. Little [mailto:xxxxx@broadstor.com]
> > > Sent: Tuesday, July 16, 2002 1:17 PM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Build Environments
> > >
> > >
> > > The XP DDK has extensions that are not in the 2K DDK. I
> > know you can
> > > test
> > 2K
> > > drivers under XP, but you need care in going the other way.
> > >
> > > –
> > > Gary G. Little
> > > xxxxx@broadstor.com
> > > xxxxx@inland.net
> > > “Chris Dore” wrote in message
> > > news:xxxxx@ntdev… I would like to get something clarified:
> > >
> > > Can XP drivers be used in 2K or should/must they be built
> > using the 2K
> > build
> > > environment? I believe that they are to be built using the 2K env.
> > > however
> > I
> > > have received information saying that building a driver
> > using the XP
> > > env.
> > is
> > > good enough for both.
> > >
> > > Or:
> > >
> > > Is it simply a per case scenario in which, if you have no technical
> > > issues/problems with using the XP driver in 2K, go for it.
> > There are
> > > devices out there which use the same drivers for 2K and XP
> > so either
> > > they are using the 2K driver in XP or the XP driver in 2K, which
> > > supports this case.
> > >
> > > Thanks, Chris
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@stratus.com To
> > > unsubscribe send a blank email to %%email.unsub%%
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@rdsor.ro To
> > > unsubscribe send a blank email to %%email.unsub%%
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@stratus.com To unsubscribe send a blank email to
> > %%email.unsub%%
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>