When you use our DriverWorks or DriverNetworks wizard, we state upfront,
loud and clear, which versions of the IDE, Compiler, Tools and DDK we
support. When a new version of any of those comes out, we jump at it, and
sooner or later we will come up with an upgrade to our product that will
support that new whatever. As far as i can tell, our wizards to the job, and
if they don’t, that’s a bug and we’re going to fix it.
Developing drivers from and IDE is not a risky thing and is not the “wrong”
way. Like anything else, one must know what one’s doing !
And by the way, it’s a jolly bad idea to depend on specific versions of
anything to be able to build a driver. Or any piece of software for that
matter. One golden rule that every compiler, linker, IDE or DDK developer
should abide to is, backward compatibility - whatever you do to your
product, just make sure you don’t break what your customers have already
done. If I build something with V6 today and tomorrow V7 or V6 SPumpteen
breaks it, you bet I’m not going to be happy with my tools supplier.
Alberto.
-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]
Sent: Friday, November 01, 2002 12:53 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Newbie Question
I’m sorry, but ‘Undocumented Whatever’ is the wrong place to start. I have
no idea if that is a good book or a bad book (the NT4 version of similar
title was hideously bad,) but if you are ‘new to driver development’ why not
start with what is documented and with the excellent set of books that
describe how to do things the ‘right way’?
Building drivers using project wizards has ‘issues’, mostly dealing with
tracking changes to both visual studio and the ddk. I’m not saying don’t do
it this way, I’m just saying BE VERY CAREFUL.
-----Original Message-----
From: Dan Morales [mailto:xxxxx@MoralesDirect.com]
Sent: Friday, November 01, 2002 12:11 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Newbie Question
Alberto,
Here is the book info:
Title: Undocumented Windows 2000 Secrets
ISBN: 0-201-72187-2
Author: Sven B. Schreiber
This book dives into some undocumented APIs as well as shows
the basics of driver development (driver entry , dispatcher
routines, IRPs). It’s well-written. The CD that comes with
it contains the driver skeleton builder that I was talking about.
Dan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
Moreira, Alberto
Sent: Friday, November 01, 2002 11:01 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Newbie Question
Hi, Dan,
Which book are you talking about ? Can you share more info with us ?
Alberto.
-----Original Message-----
From: Dan Morales [mailto:xxxxx@MoralesDirect.com]
Sent: Friday, November 01, 2002 11:53 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Newbie Question
I have not read the ntdev list archive (just signed up this
week). However, Sven Schreiber’s book comes with a neat
utility that will build a device driver project that can be
compiled in Visual Studio. It comes with template source
files that you can customize to build initial driver
skeletons. It was a helpful and welcome start for me as a
driver newbie also.
Dan Morales
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Phil Barila
Sent: Friday, November 01, 2002 10:38 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Newbie Question
MessageThis is the most irresponsible post I’ve seen all
week. If you only do just what is described in this post,
you will very likely have subtle (and probably some unsubtle
ones as well) runtime bugs, if you get a successful compile at all.
Please visit the archives and study the interminable threads
which describe, in exhaustive detail, why this isn’t a good
idea, and how to get it right if you insist on doing it
anyway. There are a couple of well implemented and
documented means of using the VC6 or VS.NET IDE’s for driver
development, and they are obvious if you read the archive.
Phil
–
Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
“Devendra Singh” wrote in message
news:xxxxx@ntdev… you can use VC6 to build the driver… what all you have
to do is -Open a workspace in VC6, add code files to it -in settings, add
path to the ddk header files and libraries… now you can compile it
normally
hope it will help you
Dev
—
You are currently subscribed to ntdev as: xxxxx@moralesdirect.com To
unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@compuware.com To
unsubscribe send a blank email to %%email.unsub%%
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
—
You are currently subscribed to ntdev as: xxxxx@moralesdirect.com To
unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to %%email.unsub%%
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
