Re: Errors while building samples of DriverStudio in Windows XP

> Wrong, Max. DriverWorks gives you a lot less gotchas,

But if the developer will have one - nearly nobody on all 5 forums I
know will help, only Numega will, not the community.

and moves you one
notch above this rat’s nest of a zillion APIs to contend with.

…by replacing them with a rat’s nest of zillion C++ classes.

gives you C++, which is a world of a difference from programming in
plain
vanilla C.

OK, let’s stop this debate about whether or not C++ gives advantages
in system-level development.

Max

> Second, Max, exactly what are the ‘gotchas’ with the 'external
makefile

project using a shell script to invoke build’ (i.e. ddkbuild)
approach to
integrating visual studio with the ddk ‘development process’?

With this - maybe no gotchas, but the amount of problems people on
this list have with all kinds of SRC2DSP tools is large enough to
un-recommend any of them.

Why not use BUILD? We got the knowledge that .BSC can be created from
BUILD. Any more reasons against BUILD?

Max

I’ve shipped three commercial drivers built with Visual Studio .dsp
projects that were created with Numega’s Src2Dsp tool (with minor
variations). Having the freedom to compile and link outside of the
current directory tree has simplified and speeded up development
immensely, and I haven’t encountered a single bug that cropped up solely
as a result of this.

Unforunately, Numega hasn’t updated the tool in years, so the resulting
.dsp requires some tweaking to work with the XP DDK, but it’s not a big
deal (Numega, public-source the project or give it to one of us and
we’ll fix it up).

  • Nicholas Ryan

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim
S. Shatskih
Sent: Friday, October 18, 2002 5:13 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Errors while building samples of
DriverStudio in Windows XP

> Second, Max, exactly what are the ‘gotchas’ with the ‘external
makefile
> project using a shell script to invoke build’ (i.e. ddkbuild)
approach to
> integrating visual studio with the ddk ‘development process’?

With this - maybe no gotchas, but the amount of problems
people on this list have with all kinds of SRC2DSP tools is
large enough to un-recommend any of them.

Why not use BUILD? We got the knowledge that .BSC can be
created from BUILD. Any more reasons against BUILD?

Max


You are currently subscribed to ntdev as: xxxxx@nryan.com
To unsubscribe send a blank email to %%email.unsub%%

Nicholas,

Try Walter Oney’s wizard that he provides with his WDM book. I believe his
updates will set things up for XP and VS .NET (???).


Gary G. Little
Have Computer, Will Travel …
909-698-3191
909-551-2105

“Gary G. Little” wrote:

Try Walter Oney’s wizard that he provides with his WDM book. I believe his
updates will set things up for XP and VS .NET (???).

The current service pack for the 1st edition sample uses the XP kit. The
2d edition will use the .net DDK.


Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Now teaming with John Hyde for USB Device Engineering Seminars
Check out our schedule at http://www.oneysoft.com