problem with InterlockedDecrement

im getting error saying that: ‘InterlockedDecrement’: identifier not found, even with argument-dependent lookup

though this function is defined as intrinsic function is wdm.h

pls help me out

PeterGV wrote:
muhammed waseem wrote:

>
> kindly help me out of this situation.
>

Read the Getting Started FAQ on OSR Online. Read the back issues of The
NT Insider that have to do with getting started writing drivers (use the
search facility).

The Most Important Thing (pay attention now) to learn if you need to
write Windows drivers is to LEARN THE OPERATING SYSTEM ARCHITECTURE. Do
not take shortcuts with this, or you’ll be doomed to asking dumb
questions on this list for the rest of your life and/or project
(whichever ends first).

Unlike most application programming topics, you absolutely, positively
cannot simply hack and whack your way through driver development by
grabbing a sample that’s “close” to what you need, and trying to modify
it without knowing what you’re doing. It won’t work, but you won’t find
this out until you’ve invested several months/weeks in the effort or
you’ve released some shite that crashes your customer’s systems.

So, read Inside Windows whatever-it-is, read some/all of the
architectural articles on OSR Online, and for goodness sakes at the very
least read ALL of the “Getting Started Writing Windows Drivers” section
and as much of the Kernel-Mode Driver Architecture section of the DDK
that you can stomach. Understand the threading model, IRQLs,
serialization mechanisms, and the flow of data through the I/O system.
THIS is what you need to know to write a driver – NOT the list of
approved APIs and assorted trivia (that’ll become interesting/useful later).

With a good fundamental understanding of the operating system under your
belt, read a book or two on Windows driver development. The only book
that’s close to up to date on this topic is Oney’s, and that book leaves
a lot to be desired. Oh well, better than nothing.

As to your specific problem (“target architecture not defined”)…
After installing the DDK, you need to start the appropriate command
prompt window from Start->Programs->Development Kits->Windows DDK->Build
Environments->[choose one]->[choose one] – Build your driver in this
command window, which has the environment variables set appropriately.

Peter
OSR


Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@yahoo.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com