Re: A journey from NT-Device Driver to WDM
- From: "David J. Craig" <SeniorDriversWriter@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 13 Jun 2005 21:19:29 -0700
If you don't understand that code first, how will you ever develop a working
driver? I will admit it is fairly complex, but build each piece and install
them one by one running windbg on them. Add a breakpoint into DriverEntry
and watch every request until you understand what is happening. The first
pieces will not exercise much of their code until later pieces get
installed, but you need to understand the driver model before you can create
a design that will work.
"Ali" <abdulrazaq@xxxxxxxxx> wrote in message
news:1118695148.624728.221820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Don Burn has given me good starting points from DDK
[src\general\toaster\func\featured2] as starting points but sir its
really hard to extract and understand all that code by Eliyas Yakub.
havn't started coding yet still stuck in design phase:)
.
- Follow-Ups:
- References:
- A journey from NT-Device Driver to WDM
- From: Ali
- Re: A journey from NT-Device Driver to WDM
- From: Maxim S. Shatskih
- Re: A journey from NT-Device Driver to WDM
- From: Ali
- Re: A journey from NT-Device Driver to WDM
- From: Ali
- A journey from NT-Device Driver to WDM
- Prev by Date: Re: Using the DDK.
- Next by Date: Re: Usb detection
- Previous by thread: Re: A journey from NT-Device Driver to WDM
- Next by thread: Re: A journey from NT-Device Driver to WDM
- Index(es):
Relevant Pages
|