How to develop and build a driver under vc6.0

Hi All!
how can I develop and build a driver under vc6.0? what I’m doing now
is just the editing on vc, and then run build from a ddk-set command line.
What are the settings to make the compiler build a driver?

Thanks,
Aaron Elberg mailto:xxxxx@mysticom.com
Mysticom Ltd. www.mysticom.com
Tel (972) 9 8636441 Fax: (972) 9 8636466

You can either check out www.osr.com for the white paper on building drivers
with the IDE, or look at the Numega site (which has some program which reads
your sources file and sets up the IDE.

–Mark
Mark J. Cariddi
Consulting Associate
xxxxx@osr.com

OSR Open Systems Resources, Inc.
105 Route 101A, Suite 19
Amherst, New Hampshire 03031
603/595-6500
603/595-6503 Fax
http://www.osr.com

****************************************
The definitive book on writing Windows NT
device drivers, “Windows NT Device Driver
Development” by OSR consulting partners
Peter Viscarola and Tony Mason, is now
available for ordering.
****************************************

-----Original Message-----
From: Aaron Elberg [mailto:xxxxx@mysticom.com]
Sent: Wednesday, March 08, 2000 7:06 AM
To: NT Developers Interest List
Subject: [ntdev] How to develop and build a driver under vc6.0

Hi All!
how can I develop and build a driver under vc6.0? what I’m doing now
is just the editing on vc, and then run build from a ddk-set command line.
What are the settings to make the compiler build a driver?

Thanks,
Aaron Elberg mailto:xxxxx@mysticom.com
Mysticom Ltd. www.mysticom.com
Tel (972) 9 8636441 Fax: (972) 9 8636466


You are currently subscribed to ntdev as: xxxxx@osr.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

Hi,

There is utility which will convert your DDK Sources
file into VC 6.0 workspace .dsw file and then u can
build ur driver from vc editor. but i don’t know
whether that utility is propeitry … search on the
net…the utility has some limitations…like it
cannot work for … drivers of type EXPORT…

may be some one can put some more light…
but it is possible to build from vc 6.0

Girish

— Aaron Elberg wrote:
> Hi All!
> how can I develop and build a driver under vc6.0?
> what I’m doing now
> is just the editing on vc, and then run build from a
> ddk-set command line.
> What are the settings to make the compiler build a
> driver?
>
> Thanks,
> Aaron Elberg mailto:xxxxx@mysticom.com
> Mysticom Ltd. www.mysticom.com
> Tel (972) 9 8636441 Fax: (972) 9 8636466
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> $subst(‘Email.Unsub’)
>
>
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

There are two methods.

The first is to create ‘external makefile’ projects for your drivers. I
wrote an article for OSR’s NtInsider a few years ago describing this
process. An updated on-line description of this process is available on my
website www.hollistech.com along with an associated shell script called
ddkbuild.bat.

The second method is to use one of the various driver wizards or converters.
There are links in my article to these utilities and my brief explanation of
why I won’t use them.

=
Mark Roddy

Windows 2000/Windows NT Consulting:

xxxxx@hollistech.com
www.hollistech.com

=

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Aaron Elberg
Sent: Wednesday, March 08, 2000 7:06 AM
To: NT Developers Interest List
Subject: [ntdev] How to develop and build a driver under vc6.0

Hi All!
how can I develop and build a driver under vc6.0? what I’m doing now
is just the editing on vc, and then run build from a ddk-set command line.
What are the settings to make the compiler build a driver?

Thanks,
Aaron Elberg mailto:xxxxx@mysticom.com
Mysticom Ltd. www.mysticom.com
Tel (972) 9 8636441 Fax: (972) 9 8636466


You are currently subscribed to ntdev as: xxxxx@wattanuck.mv.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

Mark,

reading your web page I found following paragraph about bscmake -n:

The second line sets the name of the .bsc file to our project
target name. We also sneak in the ‘-n’ option to
BscMake here so that Bscmake does NOT truncate .sbr files. This is
just the opposite behavior from the default
VisualStudio behavior, but unless you have a very slow processor
and a very small hard drive I strongly suggest
you follow what I’m doing up above. You will be much happier.

I always want to be happier but don’t understant why it better to use -n.
Could you explain it? I’m using BSC information created using BROWSER_INFO=1
only for years and never had any problem.

Thanks.

Best regards,

Michal Vodicka
RKK Informationssysteme s.r.o.
:We support your Future
[WWW: http://www.rkk.cz , http://www.skytale.com]


From: Mark Roddy[SMTP:xxxxx@wattanuck.mv.com]
Reply To: NT Developers Interest List
Sent: Wednesday, March 08, 2000 14:18
To: NT Developers Interest List
Subject: [ntdev] RE: How to develop and build a driver under vc6.0

There are two methods.

The first is to create ‘external makefile’ projects for your drivers. I
wrote an article for OSR’s NtInsider a few years ago describing this
process. An updated on-line description of this process is available on my
website www.hollistech.com along with an associated shell script called
ddkbuild.bat.

The second method is to use one of the various driver wizards or
converters.
There are links in my article to these utilities and my brief explanation
of
why I won’t use them.

=
Mark Roddy

Windows 2000/Windows NT Consulting:

xxxxx@hollistech.com
www.hollistech.com

=

Hmm… good point, what the heck did I mean?

Ah, yes now I remember. Here’s the thing: what I tend to do a lot with big
projects is to have bsc files for each component, and then parent bsc files
for groups of components. I can then ‘change my focus’ in visual studio by
picking a higher-level project, and pick up an associated bsc file that
covers all the subcomponents. There are hooks in ddkbuild for generating
these high level bsc files.

Truncating the sbr files makes this impossible. The default model for
bscmake is a simple small project. Once the sbr file is truncated it cannot
be re-used.

I do have on my list of things to do a much longer article on the
development process. Unfortunately I have to go out raise cash. When I do
get it done it will cover this stuff in more detail.

=
Mark Roddy

Windows 2000/Windows NT Consulting:

xxxxx@hollistech.com
www.hollistech.com

=

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Vodicka, Michal
Sent: Thursday, March 09, 2000 3:47 PM
To: NT Developers Interest List
Subject: [ntdev] RE: How to develop and build a driver under vc6.0

Mark,

reading your web page I found following paragraph about bscmake -n:

The second line sets the name of the .bsc file to our project
target name. We also sneak in the ‘-n’ option to
BscMake here so that Bscmake does NOT truncate .sbr
files. This is
just the opposite behavior from the default
VisualStudio behavior, but unless you have a very slow processor
and a very small hard drive I strongly suggest
you follow what I’m doing up above. You will be much happier.

I always want to be happier but don’t understant why it better to use -n.
Could you explain it? I’m using BSC information created using
BROWSER_INFO=1
only for years and never had any problem.

Thanks.

Best regards,

Michal Vodicka
RKK Informationssysteme s.r.o.
:We support your Future
[WWW: http://www.rkk.cz , http://www.skytale.com]

> ----------
> From: Mark Roddy[SMTP:xxxxx@wattanuck.mv.com]
> Reply To: NT Developers Interest List
> Sent: Wednesday, March 08, 2000 14:18
> To: NT Developers Interest List
> Subject: [ntdev] RE: How to develop and build a driver under vc6.0
>
> There are two methods.
>
> The first is to create ‘external makefile’ projects for your drivers. I
> wrote an article for OSR’s NtInsider a few years ago describing this
> process. An updated on-line description of this process is
available on my
> website www.hollistech.com along with an associated shell script called
> ddkbuild.bat.
>
> The second method is to use one of the various driver wizards or
> converters.
> There are links in my article to these utilities and my brief
explanation
> of
> why I won’t use them.
>
>
> =
> Mark Roddy
>
> Windows 2000/Windows NT Consulting:
>
> xxxxx@hollistech.com
> www.hollistech.com
>
> =
>


You are currently subscribed to ntdev as: xxxxx@wattanuck.mv.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

Go to OSR’s web site, www.osr.com, they have an article about how to do
this.

Jim

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Aaron Elberg
Sent: Wednesday, March 08, 2000 4:06 AM
To: NT Developers Interest List
Subject: [ntdev] How to develop and build a driver under vc6.0

Hi All!
how can I develop and build a driver under vc6.0? what I’m doing now
is just the editing on vc, and then run build from a ddk-set command line.
What are the settings to make the compiler build a driver?

Thanks,
Aaron Elberg mailto:xxxxx@mysticom.com
Mysticom Ltd. www.mysticom.com
Tel (972) 9 8636441 Fax: (972) 9 8636466


You are currently subscribed to ntdev as: xxxxx@youngendeavors.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

>

Go to OSR’s web site, www.osr.com, they have an article
about how to do
this.

Jim

An updated version of ddkbuild.bat and documentation on how to use it is
available at www.hollistech.com

ddkbuild.bat now supports W2K features, and the documentation uses VC6.