+1
Also (pardon my amending THE OSR MASTER), it’s about knowing where to start,
both in terms of the actual coding, but also and equally importantly, the
docs and tools. Knowing that takes a HUGE bite out of the learning curve,
especially for something like, say, WinDbg. Not exactly hard to spend one
week in the windbg docs and get, you know, nowhere, whereas MVP Snoone will
set you straight, at least as far as getting going.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Saturday, July 10, 2010 12:21 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Re: need advice learning driver development
I think that is EXCEPTIONALLY BAD advice. Epic bad. And obviously from
somebody who has no clue what we teach in our seminars.
What’s ALL IMPORTANT is understanding the architecture… what the role of
your driver is in the overall system, how it gets requests and how it
services them. Everything else is trivia. You can look up the names of the
functions, get sample INF files… but if you don’t know that you can’t
touch pageable memory at IRQL DISPATCH_LEVEL, you’re screwed plain and
simple. If you don’t understand the concept of execution context (specific
and arbitrary) you are totally fucked.
The fact that you call IoCompleteRequest or WdfRequestComplete or NdisMXxxxx
doesn’t matter. What matters is that you understand the environment in
which your solution is operating, and the constraints within which that
solution must be crafted.
Peter
OSR
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