Re: unresolved symbol - 'KeSetTargetProcessorDpc'

From: Don Burn (burn_at_stopspam.acm.org)
Date: 08/24/04 

Date: Tue, 24 Aug 2004 12:55:04 -0400

DON'T EVER DO THIS PIECE OF CRAP. Taking stuff from NTDDK.H to it's own
file just causes a maintainence headache, doing this produces a mess. I
have as a consultant reviewing products shot down a major hardware purchase,
becuase the idiots who did the driver, did this type of ***, the last I
know the OEM hardware company was suing the consultants who pull this.

In this case the persons problem is obvious. He is trying to build a WDM
driver which doesn't support the call. Change the include to only include
ntddk.h which is a superset of wdm. And change the DRIVERTYPE in the souces
file to DRIVER instead of WDM. 

-- 
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"Spiro Trikaliotis" <news+200406@trikaliotis.net> wrote in message
news:slrncimj7p.gru.news+200406@news.trikaliotis.net...
> Hello,
>
> Puneet Jain <pjain@datatekcorp.com> wrote:
>
> > I am including both wdm.h and ntddk.h and I am getting the following
> > error:
> [...]
>
> From times where it was not even possible to include ntddk.h and ndis.h
> in one source file, I found it to be good practice to "encapsulate"
> everything from ntddk.h that is needed in an own file, and let every
> file only include one of the headers.
>
> It might be that this would solve the problem with ntddk.h and wdm.h,
> too?
>
> HTH,
>    Spiro.
>
> -- 
> Spiro R. Trikaliotis
> http://www.trikaliotis.net/