Re: New bee to Device Driver Development

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"Ali" <abdulrazaq@xxxxxxxxx> wrote in message >
Sooner or later one has to switch to DDK tool set but I do support
Pavel's suggestion to start. Especially if you have a BOSS to
report;-)For example using sofIce is far more easier as compare to
legend kd (though any developer will certainly endup with this
excellent debugger ) but for newbie its not that convenient unless he
knows the right places (osr windbg list).


The problem is that I know of three companies who used Jungo to get a jump
start. Now all three of them are contacting experts to help them over "a
few bugs and performance issues". Well bottom line, between the problems
in Jungo, the errors in the samples, and the lack of performance by Jungo,
we are talking a total rewrite. Even worse some of the Jungo examples have
directed them to interface models that will never be stable and fast, so
not only are they looking at rewriting the driver, they are looking at
throwing out multiple man-years of work.

I reviewed one startups efforts and explained in simple terms to a board
member that the decision to use Jungo had cost the firm a year in time, and
over $1M. The boards first step was fire the boss. Convience is not
usesful if it takes you to a deadend, which is certainly what the crap
Jungo sells is.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



.

Quantcast