Environment for developing and debugging drivers

NTFSD
1

Hello!

I am learning to write file system drivers for some time, and so far I was writing my

code in notepad, and then compile it by going to the folder of the driver, and typing

“build” in the console of WDK. I am sure that’s not the way people write drivers…

So maybe someone could tell me in which environment (like Visual Studio, eclipse,…)

I can write drivers, and compile them in the same environment? Also, is it possible to

debug drivers in runtime? Maybe not step by step, but at least to see what is happening…

Thanks in advance!

2

A number of us use Visual Studio with DDKBUILD (from either OSR or
http://www.hollistech.com/) this gives you the advantages of Visual Studio,
but keeps the BUILD environment which is the only safe way to build a
windows driver. For debugging you need WinDBG
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx, this requires
two machines (or two virtual machines) but is the way to go.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntfsd…
> Hello!
>
> I am learning to write file system drivers for some time, and so far I was
> writing my
>
> code in notepad, and then compile it by going to the folder of the driver,
> and typing
>
> “build” in the console of WDK. I am sure that’s not the way people write
> drivers…
>
> So maybe someone could tell me in which environment (like Visual Studio,
> eclipse,…)
>
> I can write drivers, and compile them in the same environment? Also, is it
> possible to
>
> debug drivers in runtime? Maybe not step by step, but at least to see what
> is happening…
>
> Thanks in advance!
>

3

That is the way most people develop drivers, other than notepad, but
that’s just a matter of preference. If you want to use Visual Studio,
check out DDKBuild from hollistech.com
(http://www.hollistech.com/Resources/ddkbuild/ddkbuild.htm).

I’m not really sure what you mean by ‘debug drivers in runtime.’ For
all practical purposes, these days, the only option for debugging
drivers (if one defines debugging to mean more than just trace
information) is WinDbg.

Good luck,

mm

xxxxx@gmail.com wrote:

Hello!

I am learning to write file system drivers for some time, and so far I was writing my

code in notepad, and then compile it by going to the folder of the driver, and typing

“build” in the console of WDK. I am sure that’s not the way people write drivers…

So maybe someone could tell me in which environment (like Visual Studio, eclipse,…)

I can write drivers, and compile them in the same environment? Also, is it possible to

debug drivers in runtime? Maybe not step by step, but at least to see what is happening…

Thanks in advance!

4

I downloaded DDKBUILD from OSR. Now, if I execute it, what should it do? It will change

permanently the compiler and linker settings in visual studio? If so, for which projects?

5

No,see http://www.osronline.com/article.cfm?id=104

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntfsd…
>I downloaded DDKBUILD from OSR. Now, if I execute it, what should it do? It
>will change
>
> permanently the compiler and linker settings in visual studio? If so, for
> which projects?
>

6

Thank you!

7

If you don’t already own or don’t want to buy Visual Studio to code in,
it’s completely feasible to develop with a text editor and command line
build environment. Gvim is my editor of choice, but there are a lot of
people who like emacs too. Both have steep learning curves, but they
will do indentation sanely and automatically and do syntax highlighting
like Visual Studio. Either of these will be worlds better than notepad.
I believe nano and pico (if they’re available for Windows) are also more
targetted towards programmers, and are a bit less user-hostile if you
don’t know what you’re doing.

What they won’t do is give you the little hints about function arguments
that VS gives you. I usually have a dozen or so tabs open in Firefox
pointed at the MSDN docs as I code. I don’t view this as a hindrance.
The idea is that I can eventually code without having the documentation
open, and that I’ll learn the details of what the functions do, not just
the order of the arguments.

~Eric

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, November 19, 2007 8:53 AM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Environment for developing and debugging drivers

Hello!

I am learning to write file system drivers for some time, and so far I
was writing my

code in notepad, and then compile it by going to the folder of the
driver, and typing

“build” in the console of WDK. I am sure that’s not the way people write
drivers…

So maybe someone could tell me in which environment (like Visual Studio,
eclipse,…)

I can write drivers, and compile them in the same environment? Also, is
it possible to

debug drivers in runtime? Maybe not step by step, but at least to see
what is happening…

Thanks in advance!

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars (including our new
fs mini-filter seminar) visit:
http://www.osr.com/seminars

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

8

To be frank, I would like to configure visual studio to work with WDK. But, I have a problem

with that… Can someone of you help me?

9

You can use Visual Studio environment to build kernel mode driver. All you
need to do is appropriately set up driver project properties. You can’t use
Visual Studios default libraries (use /NODEFAULTLIB linker option), instead
use DDK libraries (in Additional Include Directories compiler option &
Additional Dependencies linker option). For other compiler and linker
options (like Preprocessor definitions) refer to DDK sample projects and
their makefile options in DDK build environment. Even though kernel mode
projects are usually written in C, you can also use C++, but limited to
basic features (see http://www.microsoft.com/whdc/driver/kernel/KMcode.mspx).

To debug a kernel mode driver you need a kernel mode debugger (like
WinDbg). I would advise against local debugging unless you’re fond of
system crashes. Personally I’m using VMware with it’s bundled Virtual
Debugger to debug user mode projects & WinDbg to debug a kernel mode
project running in a virtual machine. When step by step debugging is not
necessary I just use DbgView to check DbgPrint’s from my driver
(http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx).
For more info see http://www.catch22.net/tuts/vmware.asp and WinDbg help.

Hope it helps…
Robert

Hello!

I am learning to write file system drivers for some time, and so far I was writing my
code in notepad, and then compile it by going to the folder of the driver, and typing
“build” in the console of WDK. I am sure that’s not the way people write drivers…
So maybe someone could tell me in which environment (like Visual Studio, eclipse,…)
I can write drivers, and compile them in the same environment? Also, is it possible to
debug drivers in runtime? Maybe not step by step, but at least to see what is happening…

Thanks in advance!

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@imis.si
To unsubscribe send a blank email to xxxxx@lists.osr.com

10

And if you get it even slightly wrong you can be like one of my customers
who wasted over a man-year and sufferred a bunch of non-perfomrance fines
because their driver was screwed up. Also, of course this wonderul
technique blocks you from using PreFasr for Drivers, and if your driver is a
WDM or KMDF driver using Static Driver Verifier. Of course, using the
tools can take all the fun of weeks of debugging out of the project since
they can find those hard to locate bugs, but who cares right?

Finally, of course it will be impossible to get your driver signed if you
need to without going back to the build environment, so why not use it in
the first place?

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntfsd…
> You can use Visual Studio environment to build kernel mode driver. All you
> need to do is appropriately set up driver project properties. You can’t
> use
> Visual Studios default libraries (use /NODEFAULTLIB linker option),
> instead
> use DDK libraries (in Additional Include Directories compiler option &
> Additional Dependencies linker option). For other compiler and linker
> options (like Preprocessor definitions) refer to DDK sample projects and
> their makefile options in DDK build environment. Even though kernel mode
> projects are usually written in C, you can also use C++, but limited to
> basic features (see
> http://www.microsoft.com/whdc/driver/kernel/KMcode.mspx).
>
> To debug a kernel mode driver you need a kernel mode debugger (like
> WinDbg). I would advise against local debugging unless you’re fond of
> system crashes. Personally I’m using VMware with it’s bundled Virtual
> Debugger to debug user mode projects & WinDbg to debug a kernel mode
> project running in a virtual machine. When step by step debugging is not
> necessary I just use DbgView to check DbgPrint’s from my driver
> (http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx).
> For more info see http://www.catch22.net/tuts/vmware.asp and WinDbg help.
>
> Hope it helps…
> Robert
>
>
>>Hello!
>>
>>I am learning to write file system drivers for some time, and so far I was
>>writing my
>>code in notepad, and then compile it by going to the folder of the driver,
>>and typing
>>“build” in the console of WDK. I am sure that’s not the way people write
>>drivers…
>>So maybe someone could tell me in which environment (like Visual Studio,
>>eclipse,…)
>>I can write drivers, and compile them in the same environment? Also, is it
>>possible to
>>debug drivers in runtime? Maybe not step by step, but at least to see what
>>is happening…
>>
>>Thanks in advance!
>>
>>—
>>NTFSD is sponsored by OSR
>>
>>For our schedule debugging and file system seminars
>>(including our new fs mini-filter seminar) visit:
>>http://www.osr.com/seminars
>>
>>You are currently subscribed to ntfsd as: xxxxx@imis.si
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>

11

You could also look at this
http://www.hollistech.com/

Basically —

You create a Makefile workspace.

And follow the detail discussion (help ) from the website.

-pro

----- Original Message -----
From:
To: “Windows File Systems Devs Interest List”
Sent: Monday, November 19, 2007 7:25 AM
Subject: RE:[ntfsd] Environment for developing and debugging drivers

> To be frank, I would like to configure visual studio to work with WDK.
> But, I have a problem
>
> with that… Can someone of you help me?
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

12

So, how can I develop drivers conveniently?

13

Use DDKBuild that lets you use the build environment and still have the
friendly Visual Studio environment. It is the idiots who advocate messing
with Visual Studio withouth somehting like DDKbuild in the middel that get
people in trouble.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntfsd…
> So, how can I develop drivers conveniently?
>

14

Don,
you’re often threatening with that customer of yours.
I took my driver thru operating system changes (NT4 to W2K to XP to Vista)
and
our products architecture changes, all the time using the latest Visual
Studio and DDK.
I think that if one takes care of the issues that Robert mentioned below, a
driver built this
way is not less reliable than a driver build that way. If there are doubts
about the compilation,
there’s the assembly to look at too.
And it really does not block you from using PreFast, it just does not
invite you to do so.
So instead of leaving us frightened, why don’t you just explain what
problems your customer
had ? Why was their driver screwed up ?

Regards
Else

|---------±-------------------------------->
| | “Don Burn” |
| | |
| | Sent by: |
| | bounce-306417-18867@li|
| | sts.osr.com |
| | |
| | |
| | 11/19/2007 04:42 PM |
| | Please respond to |
| | “Windows File Systems |
| | Devs Interest List” |
|---------±-------------------------------->
>-----------------------------------------------------------------------------------------------------------|
| |
| To: “Windows File Systems Devs Interest List” |
| cc: |
| Subject: Re:[ntfsd] Environment for developing and debugging drivers |
>-----------------------------------------------------------------------------------------------------------|

And if you get it even slightly wrong you can be like one of my customers
who wasted over a man-year and sufferred a bunch of non-perfomrance fines
because their driver was screwed up. Also, of course this wonderul
technique blocks you from using PreFasr for Drivers, and if your driver is
a
WDM or KMDF driver using Static Driver Verifier. Of course, using the
tools can take all the fun of weeks of debugging out of the project since
they can find those hard to locate bugs, but who cares right?

Finally, of course it will be impossible to get your driver signed if you
need to without going back to the build environment, so why not use it in
the first place?

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntfsd…
> You can use Visual Studio environment to build kernel mode driver. All
you
> need to do is appropriately set up driver project properties. You can’t
> use
> Visual Studios default libraries (use /NODEFAULTLIB linker option),
> instead
> use DDK libraries (in Additional Include Directories compiler option &
> Additional Dependencies linker option). For other compiler and linker
> options (like Preprocessor definitions) refer to DDK sample projects and
> their makefile options in DDK build environment. Even though kernel mode
> projects are usually written in C, you can also use C++, but limited to
> basic features (see
> http://www.microsoft.com/whdc/driver/kernel/KMcode.mspx).
>
> To debug a kernel mode driver you need a kernel mode debugger (like
> WinDbg). I would advise against local debugging unless you’re fond of
> system crashes. Personally I’m using VMware with it’s bundled Virtual
> Debugger to debug user mode projects & WinDbg to debug a kernel mode
> project running in a virtual machine. When step by step debugging is not
> necessary I just use DbgView to check DbgPrint’s from my driver
> (http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx).
> For more info see http://www.catch22.net/tuts/vmware.asp and WinDbg help.
>
> Hope it helps…
> Robert
>
>
>>Hello!
>>
>>I am learning to write file system drivers for some time, and so far I
was
>>writing my
>>code in notepad, and then compile it by going to the folder of the
driver,
>>and typing
>>“build” in the console of WDK. I am sure that’s not the way people write
>>drivers…
>>So maybe someone could tell me in which environment (like Visual Studio,
>>eclipse,…)
>>I can write drivers, and compile them in the same environment? Also, is
it
>>possible to
>>debug drivers in runtime? Maybe not step by step, but at least to see
what
>>is happening…
>>
>>Thanks in advance!
>>
>>—
>>NTFSD is sponsored by OSR
>>
>>For our schedule debugging and file system seminars
>>(including our new fs mini-filter seminar) visit:
>>http://www.osr.com/seminars
>>
>>You are currently subscribed to ntfsd as: xxxxx@imis.si
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@utimaco.de
To unsubscribe send a blank email to xxxxx@lists.osr.com

15

Just like the others doing !!!

-pro
----- Original Message -----
From:
To: “Windows File Systems Devs Interest List”
Sent: Monday, November 19, 2007 8:33 AM
Subject: RE:[ntfsd] Environment for developing and debugging drivers

> So, how can I develop drivers conveniently?
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

16

Else,

I never found them all, because bottom line the driver built correctly
with BUILD. I know some of them were that they were using the latest DDK
but had not kept the Visual Studio settings up to date. But even when we
fixed those the results were different.

Some of there developers wanted me to figure out what the problem was
in detail so they could continue using the crap. I was willing but quoted
$20k to do the work for management. If you want to me to do give you the
details, send me the check and I will schedule it for a few months from now.

I stand by my statement THE PEOPLE WHO BUILD DRIVERS WITHOUT BUILD
ARE STUPID, AND SHOULD GO BACK TO JAVA OR SIMILAR THINGS.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Else Kluger” wrote in message news:xxxxx@ntfsd…
> Don,
> you’re often threatening with that customer of yours.
> I took my driver thru operating system changes (NT4 to W2K to XP to Vista)
> and
> our products architecture changes, all the time using the latest Visual
> Studio and DDK.
> I think that if one takes care of the issues that Robert mentioned below,
> a
> driver built this
> way is not less reliable than a driver build that way. If there are doubts
> about the compilation,
> there’s the assembly to look at too.
> And it really does not block you from using PreFast, it just does not
> invite you to do so.
> So instead of leaving us frightened, why don’t you just explain what
> problems your customer
> had ? Why was their driver screwed up ?
>
> Regards
> Else
>
>
>
> |---------±-------------------------------->
> | | “Don Burn” |
> | | |
> | | Sent by: |
> | | bounce-306417-18867@li|
> | | sts.osr.com |
> | | |
> | | |
> | | 11/19/2007 04:42 PM |
> | | Please respond to |
> | | “Windows File Systems |
> | | Devs Interest List” |
> |---------±-------------------------------->
>
> >-----------------------------------------------------------------------------------------------------------|
> |
> |
> | To: “Windows File Systems Devs Interest List”
> |
> | cc:
> |
> | Subject: Re:[ntfsd] Environment for developing and debugging
> drivers |
>
> >-----------------------------------------------------------------------------------------------------------|
>
>
>
>
> And if you get it even slightly wrong you can be like one of my customers
> who wasted over a man-year and sufferred a bunch of non-perfomrance fines
> because their driver was screwed up. Also, of course this wonderul
> technique blocks you from using PreFasr for Drivers, and if your driver is
> a
> WDM or KMDF driver using Static Driver Verifier. Of course, using the
> tools can take all the fun of weeks of debugging out of the project since
> they can find those hard to locate bugs, but who cares right?
>
> Finally, of course it will be impossible to get your driver signed if you
> need to without going back to the build environment, so why not use it in
> the first place?
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
> wrote in message news:xxxxx@ntfsd…
>> You can use Visual Studio environment to build kernel mode driver. All
> you
>> need to do is appropriately set up driver project properties. You can’t
>> use
>> Visual Studios default libraries (use /NODEFAULTLIB linker option),
>> instead
>> use DDK libraries (in Additional Include Directories compiler option &
>> Additional Dependencies linker option). For other compiler and linker
>> options (like Preprocessor definitions) refer to DDK sample projects and
>> their makefile options in DDK build environment. Even though kernel mode
>> projects are usually written in C, you can also use C++, but limited to
>> basic features (see
>> http://www.microsoft.com/whdc/driver/kernel/KMcode.mspx).
>>
>> To debug a kernel mode driver you need a kernel mode debugger (like
>> WinDbg). I would advise against local debugging unless you’re fond of
>> system crashes. Personally I’m using VMware with it’s bundled Virtual
>> Debugger to debug user mode projects & WinDbg to debug a kernel mode
>> project running in a virtual machine. When step by step debugging is not
>> necessary I just use DbgView to check DbgPrint’s from my driver
>> (http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx).
>> For more info see http://www.catch22.net/tuts/vmware.asp and WinDbg help.
>>
>> Hope it helps…
>> Robert
>>
>>
>>>Hello!
>>>
>>>I am learning to write file system drivers for some time, and so far I
> was
>>>writing my
>>>code in notepad, and then compile it by going to the folder of the
> driver,
>>>and typing
>>>“build” in the console of WDK. I am sure that’s not the way people write
>>>drivers…
>>>So maybe someone could tell me in which environment (like Visual Studio,
>>>eclipse,…)
>>>I can write drivers, and compile them in the same environment? Also, is
> it
>>>possible to
>>>debug drivers in runtime? Maybe not step by step, but at least to see
> what
>>>is happening…
>>>
>>>Thanks in advance!
>>>
>>>—
>>>NTFSD is sponsored by OSR
>>>
>>>For our schedule debugging and file system seminars
>>>(including our new fs mini-filter seminar) visit:
>>>http://www.osr.com/seminars
>>>
>>>You are currently subscribed to ntfsd as: xxxxx@imis.si
>>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule debugging and file system seminars
> (including our new fs mini-filter seminar) visit:
> http://www.osr.com/seminars
>
> You are currently subscribed to ntfsd as: xxxxx@utimaco.de
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

17

VS 2005 lets you set up a Makefile based build, but it really just runs
command line commands of your choice. Substitute the commands to run
ddkbuild for those you’d use to run make, and you’re off. You can code
in VS, browse error messages in VS, and have a kosher build.

By the way, having a command line based build is, in my opinion, far
simpler than having a gui based build. All the configuration
information is defined in text files and environment variables. If
you’re developing with other people, you don’t run into issues with
somebody having a checkbox checked 5 dialogs deep in a configuration
screen that screws their build up. It’s usually a little harder to set
up initially, but the payoff is that it usually keeps working as
multiple people start using the build system. The trade off is (like a
good text editor) a steep learning curve for long term usefulness and
usability. Make, it’s worth noting, is especially arcane (though it is
pretty powerful). Ddkbuild seems a little more straightforward, but I
haven’t had to set up a build from scratch.

~Eric

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, November 19, 2007 11:33 AM
To: Windows File Systems Devs Interest List
Subject: RE:[ntfsd] Environment for developing and debugging drivers

So, how can I develop drivers conveniently?

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars (including our new
fs mini-filter seminar) visit:
http://www.osr.com/seminars

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

18

Use VS2005 editor and BUILD in the command line.

You cannot use VS’s debugger from kernel mode drivers anyway, so, the loss
of VS2005’s build facility is not a major loss.

BTW - can VS2005 build script (“project” or “solution”) support
#include-style feature? BUILD can support this, and this is a major advantage
of BUILD.

–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntfsd…
> So, how can I develop drivers conveniently?
>

19

If you use Mark’s current DDKBUILD, he has a nice simple setup described in
the help pages. Every time I create a ddkbuild project, I follow it. It
always works and you don’t forget a step and find yourself missing a
capability. I also use SlickEdit to invoke ddkbuild via a batch file local
to the project.

“Eric Diven” wrote in message news:xxxxx@ntfsd…
VS 2005 lets you set up a Makefile based build, but it really just runs
command line commands of your choice. Substitute the commands to run
ddkbuild for those you’d use to run make, and you’re off. You can code
in VS, browse error messages in VS, and have a kosher build.

By the way, having a command line based build is, in my opinion, far
simpler than having a gui based build. All the configuration
information is defined in text files and environment variables. If
you’re developing with other people, you don’t run into issues with
somebody having a checkbox checked 5 dialogs deep in a configuration
screen that screws their build up. It’s usually a little harder to set
up initially, but the payoff is that it usually keeps working as
multiple people start using the build system. The trade off is (like a
good text editor) a steep learning curve for long term usefulness and
usability. Make, it’s worth noting, is especially arcane (though it is
pretty powerful). Ddkbuild seems a little more straightforward, but I
haven’t had to set up a build from scratch.

~Eric

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, November 19, 2007 11:33 AM
To: Windows File Systems Devs Interest List
Subject: RE:[ntfsd] Environment for developing and debugging drivers

So, how can I develop drivers conveniently?

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars (including our new
fs mini-filter seminar) visit:
http://www.osr.com/seminars

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

20

Alright, maybe it will sound even more stupid than all my questions till this, but can someone help me

starting a project in visual studio 2005 with ddkbuild?