In my driver, the load fails due to the
above entry point being not found. I suppose this one is being internally
used by LookAsideList related function!!!.
I’m using windows 2k build environment that comes with the ifs kit
(2600.1106).
Am I missing something?
TIA
-prokash
You need to add the _WIN2K_COMPAT_SLIST_USAGE define to your sources file
like so:
C_DEFINES = $(C_DEFINES) -D_WIN2K_COMPAT_SLIST_USAGE
It appears MS figured out that they could get away without using the
spinlock required for the single linked-list functions (ex.
ExInterlockedPushEntrySList). So, they optimized these functions on XP and
later. But, to maintain back compatibility they provided the define above.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Prokash Sinha” wrote in message news:xxxxx@ntdev…
>
> In my driver, the load fails due to the
> above entry point being not found. I suppose this one is being internally
> used by LookAsideList related function!!!.
>
> I’m using windows 2k build environment that comes with the ifs kit
> (2600.1106).
>
> Am I missing something?
>
> TIA
> -prokash
>
>
>
>
Prokash Sinha wrote:
In my driver, the load fails due to the
above entry point being not found. I suppose this one is being internally
used by LookAsideList related function!!!.I’m using windows 2k build environment that comes with the ifs kit
(2600.1106).
There may be a mistake in the IFS kit headers. The Win2K version of
wdm.h in the regular DDK (I’m looking at 2615 here) declares an external
function named ExInterlockedPushEntrySList. The XP version will do that
too *if* you define _WIN2K_COMPAT_SLIT_USAGE. Otherwise, the XP version
macros to InterlockedPopEntrySList. So perhaps they just didn’t create
the 2K environment header carefully enough.
–
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com
Ooh, I didn’t notice you said a 2K build environment, ouch that does appear
to be a bug.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Walter Oney” wrote in message news:xxxxx@ntdev…
>
> Prokash Sinha wrote:
> > In my driver, the load fails due to the
> > above entry point being not found. I suppose this one is being
internally
> > used by LookAsideList related function!!!.
> >
> > I’m using windows 2k build environment that comes with the ifs kit
> > (2600.1106).
>
> There may be a mistake in the IFS kit headers. The Win2K version of
> wdm.h in the regular DDK (I’m looking at 2615 here) declares an external
> function named ExInterlockedPushEntrySList. The XP version will do that
> too if you define _WIN2K_COMPAT_SLIT_USAGE. Otherwise, the XP version
> macros to InterlockedPopEntrySList. So perhaps they just didn’t create
> the 2K environment header carefully enough.
>
> –
> Walter Oney, Consulting and Training
> Basic and Advanced Driver Programming Seminars
> Check out our schedule at http://www.oneysoft.com
>
>
I just tried this with the IFS kit 2600.1106 and the 2K environment was fine
with no defines added, and the XP environment required the compatibility
define. Are you sure you used the 2K build environment?
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Bill McKenzie” wrote in message
news:xxxxx@ntdev…
>
> Ooh, I didn’t notice you said a 2K build environment, ouch that does
appear
> to be a bug.
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Walter Oney” wrote in message news:xxxxx@ntdev…
> >
> > Prokash Sinha wrote:
> > > In my driver, the load fails due to the
> > > above entry point being not found. I suppose this one is being
> internally
> > > used by LookAsideList related function!!!.
> > >
> > > I’m using windows 2k build environment that comes with the ifs kit
> > > (2600.1106).
> >
> > There may be a mistake in the IFS kit headers. The Win2K version of
> > wdm.h in the regular DDK (I’m looking at 2615 here) declares an external
> > function named ExInterlockedPushEntrySList. The XP version will do that
> > too if you define _WIN2K_COMPAT_SLIT_USAGE. Otherwise, the XP version
> > macros to InterlockedPopEntrySList. So perhaps they just didn’t create
> > the 2K environment header carefully enough.
> >
> > –
> > Walter Oney, Consulting and Training
> > Basic and Advanced Driver Programming Seminars
> > Check out our schedule at http://www.oneysoft.com
> >
> >
>
>
>
>
Yes I’m using the Win2k cmd line build env from that ifs kit…
But I think I’ve some build problem too, when using the ddkbuild.bat under
vc 6.0 ide.
Thanx for all those pointers though. I’ve to see the suggestion from Walter
too.
Thanx Walter and Bill.
-prokash
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
Sent: Wednesday, June 04, 2003 10:35 AM
To: NT Developers Interest List
Subject: [ntdev] Re: InterLockedPopEntrySList()
Ooh, I didn’t notice you said a 2K build environment, ouch that does appear
to be a bug.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Walter Oney” wrote in message news:xxxxx@ntdev…
>
> Prokash Sinha wrote:
> > In my driver, the load fails due to the
> > above entry point being not found. I suppose this one is being
internally
> > used by LookAsideList related function!!!.
> >
> > I’m using windows 2k build environment that comes with the ifs kit
> > (2600.1106).
>
> There may be a mistake in the IFS kit headers. The Win2K version of
> wdm.h in the regular DDK (I’m looking at 2615 here) declares an external
> function named ExInterlockedPushEntrySList. The XP version will do that
> too if you define _WIN2K_COMPAT_SLIT_USAGE. Otherwise, the XP version
> macros to InterlockedPopEntrySList. So perhaps they just didn’t create
> the 2K environment header carefully enough.
>
> –
> Walter Oney, Consulting and Training
> Basic and Advanced Driver Programming Seminars
> Check out our schedule at http://www.oneysoft.com
>
>
—
You are currently subscribed to ntdev as: xxxxx@vormetric.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I also tried, and sent you an earlier email that win2k build of ifs works
fine, no need to define the flag.
It is I am goofing somewhere in the ddkbuild.bat as I told U earler.
-prokash
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Bill McKenzie
Sent: Wednesday, June 04, 2003 10:45 AM
To: NT Developers Interest List
Subject: [ntdev] Re: InterLockedPopEntrySList()
I just tried this with the IFS kit 2600.1106 and the 2K environment was fine
with no defines added, and the XP environment required the compatibility
define. Are you sure you used the 2K build environment?
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Bill McKenzie” wrote in message
news:xxxxx@ntdev…
>
> Ooh, I didn’t notice you said a 2K build environment, ouch that does
appear
> to be a bug.
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Walter Oney” wrote in message news:xxxxx@ntdev…
> >
> > Prokash Sinha wrote:
> > > In my driver, the load fails due to the
> > > above entry point being not found. I suppose this one is being
> internally
> > > used by LookAsideList related function!!!.
> > >
> > > I’m using windows 2k build environment that comes with the ifs kit
> > > (2600.1106).
> >
> > There may be a mistake in the IFS kit headers. The Win2K version of
> > wdm.h in the regular DDK (I’m looking at 2615 here) declares an external
> > function named ExInterlockedPushEntrySList. The XP version will do that
> > too if you define _WIN2K_COMPAT_SLIT_USAGE. Otherwise, the XP version
> > macros to InterlockedPopEntrySList. So perhaps they just didn’t create
> > the 2K environment header carefully enough.
> >
> > –
> > Walter Oney, Consulting and Training
> > Basic and Advanced Driver Programming Seminars
> > Check out our schedule at http://www.oneysoft.com
> >
> >
>
>
>
>
—
You are currently subscribed to ntdev as: xxxxx@vormetric.com
To unsubscribe send a blank email to xxxxx@lists.osr.com