How can i change the settings in developer studio so that i can build
drivers without using the BUILD utility?
Thanks in advance
Ramakrishnan J
Get src2dsp (its free) from numega.com.
It takes a sources file and produces a project for vc5 and vc6.
The only thing so far I’ve found it can’t convert are sources for KMDLLs.
-----Original Message-----
From: Ramakrishnan Jayaraman [mailto:xxxxx@yahoo.com]
Sent: 28 September 2000 11:07
To: NT Developers Interest List
Subject: [ntdev] Building drivers in developer studio???How can i change the settings in developer studio so that i can build
drivers without using the BUILD utility?Thanks in advance
Ramakrishnan J
You are currently subscribed to ntdev as: xxxxx@des.co.uk
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
I was not able to locate src2dsp on the numega.com site can you post the
URL or category ?
Thanks
Sanford Hayes
Livingston & Co. Inc.
xxxxx@livco.com
www.livco.com
you posted :
Get src2dsp (its free) from numega.com.
It takes a sources file and produces a project for vc5 and vc6.
The only thing so far I’ve found it can’t convert are sources for
KMDLLs.
On the main page go to ‘Driverstudio’ then ‘Free Downloads’ and its under
Utilities.
The URL for the file is
http://numega.com/drivercentral/utilfiles/srctodsp.zip
Rob Linegar
Software Engineer
Data Encryption Systems Limited
-----Original Message-----
From: Hayes, Sanford [mailto:xxxxx@livco.com]
Sent: 28 September 2000 16:24
To: NT Developers Interest List
Subject: [ntdev] RE: Building drivers in developer studio???I was not able to locate src2dsp on the numega.com site can
you post the
URL or category ?
Thanks
Sanford Hayes
Livingston & Co. Inc.
xxxxx@livco.com
www.livco.comyou posted :
Get src2dsp (its free) from numega.com.
It takes a sources file and produces a project for vc5 and vc6.
The only thing so far I’ve found it can’t convert are sources for
KMDLLs.
You are currently subscribed to ntdev as: xxxxx@des.co.uk
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
Numega’s site is a little cluttered, but I found it without any problems:
http://www.numega.com/drivercentral/utilfiles/util.shtml
-------------------------±------------------------------------------------
Regards, | Texas Instruments Standard Linear & Logic
Joe Turner | Wire/Die Bond Group
Voice: 903 868-6182 | 6412 Hwy 75 South, M/S 812
fax: 903 868-6460 | Sherman, TX 75090-0084
> -----Original Message-----
> From: Hayes, Sanford [mailto:xxxxx@livco.com]
> Sent: Thursday, September 28, 2000 10:24 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Building drivers in developer studio???
>
>
> I was not able to locate src2dsp on the numega.com site can
> you post the
> URL or category ?
> Thanks
> Sanford Hayes
> Livingston & Co. Inc.
> xxxxx@livco.com
> www.livco.com
>
> you posted :
>
> Get src2dsp (its free) from numega.com.
>
> It takes a sources file and produces a project for vc5 and vc6.
>
> The only thing so far I’ve found it can’t convert are sources for
> KMDLLs.
>
>
> —
> You are currently subscribed to ntdev as: Zeus@ti.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
http://www.numega.com/drivercentral/utilfiles/srctodsp.zip
Min
-----Original Message-----
From: Hayes, Sanford [mailto:xxxxx@livco.com]
Sent: Thursday, September 28, 2000 11:24 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Building drivers in developer studio???
I was not able to locate src2dsp on the numega.com site can you post the
URL or category ?
Thanks
Sanford Hayes
Livingston & Co. Inc.
xxxxx@livco.com
www.livco.com
you posted :
Get src2dsp (its free) from numega.com.
It takes a sources file and produces a project for vc5 and vc6.
The only thing so far I’ve found it can’t convert are sources for
KMDLLs.
You are currently subscribed to ntdev as: xxxxx@ati.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
The utility can be found at
http://www.numega.com/drivercentral/utilfiles/util.shtml
The direct link to file is
http://www.numega.com/drivercentral/utilfiles/srctodsp.zip
-----Original Message-----
From: Hayes, Sanford [mailto:xxxxx@livco.com]
Sent: Thursday, September 28, 2000 5:24 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Building drivers in developer studio???I was not able to locate src2dsp on the numega.com site can
you post the
URL or category ?
Thanks
Sanford Hayes
Livingston & Co. Inc.
xxxxx@livco.com
www.livco.comyou posted :
Get src2dsp (its free) from numega.com.
It takes a sources file and produces a project for vc5 and vc6.
The only thing so far I’ve found it can’t convert are sources for
KMDLLs.
You are currently subscribed to ntdev as: xxxxx@baslerweb.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
download src2dsp.exe from www.numega.com
It will convert you SOURCES file to a DSP/DSW file and the build become 100%
native in the IDE.
Jamey
----- Original Message -----
From: Ramakrishnan Jayaraman
To: NT Developers Interest List
Sent: Thursday, September 28, 2000 3:07 AM
Subject: [ntdev] Building drivers in developer studio???
> How can i change the settings in developer studio so that i can build
> drivers without using the BUILD utility?
>
> Thanks in advance
> Ramakrishnan J
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
Of course there is the other view that not using build is adding needless
additional risk to your driver development effort. A compromise is to build
driver projects as “External Makefile” projects in Visual Studio, and invoke
build indirectly. For details on how to do this, see the resources section
of my web site (www.hollistech.com).
-----Original Message-----
From: Jamey kirby [mailto:xxxxx@storagecraft.com]
Sent: Saturday, September 30, 2000 12:49 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Building drivers in developer studio???download src2dsp.exe from www.numega.com
It will convert you SOURCES file to a DSP/DSW file and the
build become 100%
native in the IDE.Jamey
Mark Roddy
xxxxx@hollistech.com
www.hollistech.com
WindowsNT Windows 2000 Consulting Services
What risk?
Dave Cox
Hewlett-Packard Co.
HPSO/SMSO (Santa Barbara)
https://ecardfile.com/id/Dave+Cox
-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]
Sent: Monday, October 02, 2000 10:41 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Building drivers in developer studio???Of course there is the other view that not using build is adding needless
additional risk to your driver development effort. A compromise is to
build
driver projects as “External Makefile” projects in Visual Studio, and
invoke
build indirectly. For details on how to do this, see the resources section
of my web site (www.hollistech.com).> -----Original Message-----
> From: Jamey kirby [mailto:xxxxx@storagecraft.com]
> Sent: Saturday, September 30, 2000 12:49 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Building drivers in developer studio???
>
>
> download src2dsp.exe from www.numega.com
>
> It will convert you SOURCES file to a DSP/DSW file and the
> build become 100%
> native in the IDE.
>
> Jamey
>
>
Mark Roddy
xxxxx@hollistech.com
www.hollistech.com
WindowsNT Windows 2000 Consulting Services
You are currently subscribed to ntdev as: david_cox2@hp.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
The risk that whatever compiler/linker/preprocessor settings you get from
the visual-studio-only version is not correct for building drivers in the
target ddk version for your driver. Unless I am mistaken, driver wizards and
src2dsp all essentially use snapshots of these settings from some point in
time based on some version of the ddk.
Now I will agree that the risk is small, but it is there.
In addition there is no automatic way to go back to a straight build version
of the same driver. So if you do run in to what appear to be compiler or
linker problems you are SOL and have to go re-create a DDK project by hand.
-----Original Message-----
From: COX,DAVID (HP-Roseville,ex1) [mailto:david_cox2@hp.com]
Sent: Monday, October 02, 2000 3:36 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Building drivers in developer studio???What risk?
Dave Cox
Hewlett-Packard Co.
HPSO/SMSO (Santa Barbara)
https://ecardfile.com/id/Dave+Cox> -----Original Message-----
> From: Roddy, Mark [mailto:xxxxx@stratus.com]
> Sent: Monday, October 02, 2000 10:41 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Building drivers in developer studio???
>
>
> Of course there is the other view that not using build is
adding needless
> additional risk to your driver development effort. A
compromise is to
build
> driver projects as “External Makefile” projects in Visual
Studio, and
invoke
> build indirectly. For details on how to do this, see the
resources section
> of my web site (www.hollistech.com).
>
> > -----Original Message-----
> > From: Jamey kirby [mailto:xxxxx@storagecraft.com]
> > Sent: Saturday, September 30, 2000 12:49 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Building drivers in developer studio???
> >
> >
> > download src2dsp.exe from www.numega.com
> >
> > It will convert you SOURCES file to a DSP/DSW file and the
> > build become 100%
> > native in the IDE.
> >
> > Jamey
> >
> >Mark Roddy
xxxxx@hollistech.com
www.hollistech.com
WindowsNT Windows 2000 Consulting Services
You are currently subscribed to ntdev as: david_cox2@hp.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
Just as an aside…REAL kernel level programmers don’t use IDEs…
Thomas “Rick” Tewell
Sequoia Advanced Technologies, Inc.
Marin County, California
tel: 415-459-7978 x104
----- Original Message -----
From: Roddy, Mark
To: NT Developers Interest List
Sent: Monday, October 02, 2000 12:52 PM
Subject: [ntdev] Re: Building drivers in developer studio???
> The risk that whatever compiler/linker/preprocessor settings you get from
> the visual-studio-only version is not correct for building drivers in the
> target ddk version for your driver. Unless I am mistaken, driver wizards
and
> src2dsp all essentially use snapshots of these settings from some point in
> time based on some version of the ddk.
>
> Now I will agree that the risk is small, but it is there.
>
> In addition there is no automatic way to go back to a straight build
version
> of the same driver. So if you do run in to what appear to be compiler or
> linker problems you are SOL and have to go re-create a DDK project by
hand.
>
>
>
> > -----Original Message-----
> > From: COX,DAVID (HP-Roseville,ex1) [mailto:david_cox2@hp.com]
> > Sent: Monday, October 02, 2000 3:36 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Building drivers in developer studio???
> >
> >
> > What risk?
> >
> > --------------------------------------------------------------
> > ---------
> > Dave Cox
> > Hewlett-Packard Co.
> > HPSO/SMSO (Santa Barbara)
> > https://ecardfile.com/id/Dave+Cox
> >
> > > -----Original Message-----
> > > From: Roddy, Mark [mailto:xxxxx@stratus.com]
> > > Sent: Monday, October 02, 2000 10:41 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Building drivers in developer studio???
> > >
> > >
> > > Of course there is the other view that not using build is
> > adding needless
> > > additional risk to your driver development effort. A
> > compromise is to
> > build
> > > driver projects as “External Makefile” projects in Visual
> > Studio, and
> > invoke
> > > build indirectly. For details on how to do this, see the
> > resources section
> > > of my web site (www.hollistech.com).
> > >
> > > > -----Original Message-----
> > > > From: Jamey kirby [mailto:xxxxx@storagecraft.com]
> > > > Sent: Saturday, September 30, 2000 12:49 PM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Re: Building drivers in developer studio???
> > > >
> > > >
> > > > download src2dsp.exe from www.numega.com
> > > >
> > > > It will convert you SOURCES file to a DSP/DSW file and the
> > > > build become 100%
> > > > native in the IDE.
> > > >
> > > > Jamey
> > > >
> > > >
> >
> > Mark Roddy
> > xxxxx@hollistech.com
> > www.hollistech.com
> > WindowsNT Windows 2000 Consulting Services
> >
> >
> > —
> > You are currently subscribed to ntdev as: david_cox2@hp.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@stratus.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
>
> —
> You are currently subscribed to ntdev as: rick@1394.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>
Agree completely.
IDE is OK as a text editor - by why typing “build” in the command line is
more boring than pressing the Shift-F8 in the IDE?
I think that possible problems while using a .DSP for driver can be worse
than typing 6 keys + (also minor) problem of pressing Ctrl-G + entering the
error line number in the IDE.
Max
----- Original Message -----
From: “Thomas “Rick” Tewell”
To: “NT Developers Interest List”
Sent: Monday, October 02, 2000 12:06 AM
Subject: [ntdev] Re: Building drivers in developer studio???
> Just as an aside…REAL kernel level programmers don’t use IDEs…
>
>
>
> Thomas “Rick” Tewell
> Sequoia Advanced Technologies, Inc.
> Marin County, California
> tel: 415-459-7978 x104
>
> ----- Original Message -----
> From: Roddy, Mark
> To: NT Developers Interest List
> Sent: Monday, October 02, 2000 12:52 PM
> Subject: [ntdev] Re: Building drivers in developer studio???
>
>
> > The risk that whatever compiler/linker/preprocessor settings you get
from
> > the visual-studio-only version is not correct for building drivers in
the
> > target ddk version for your driver. Unless I am mistaken, driver wizards
> and
> > src2dsp all essentially use snapshots of these settings from some point
in
> > time based on some version of the ddk.
> >
> > Now I will agree that the risk is small, but it is there.
> >
> > In addition there is no automatic way to go back to a straight build
> version
> > of the same driver. So if you do run in to what appear to be compiler or
> > linker problems you are SOL and have to go re-create a DDK project by
> hand.
> >
> >
> >
> > > -----Original Message-----
> > > From: COX,DAVID (HP-Roseville,ex1) [mailto:david_cox2@hp.com]
> > > Sent: Monday, October 02, 2000 3:36 PM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Building drivers in developer studio???
> > >
> > >
> > > What risk?
> > >
> > > --------------------------------------------------------------
> > > ---------
> > > Dave Cox
> > > Hewlett-Packard Co.
> > > HPSO/SMSO (Santa Barbara)
> > > https://ecardfile.com/id/Dave+Cox
> > >
> > > > -----Original Message-----
> > > > From: Roddy, Mark [mailto:xxxxx@stratus.com]
> > > > Sent: Monday, October 02, 2000 10:41 AM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Re: Building drivers in developer studio???
> > > >
> > > >
> > > > Of course there is the other view that not using build is
> > > adding needless
> > > > additional risk to your driver development effort. A
> > > compromise is to
> > > build
> > > > driver projects as “External Makefile” projects in Visual
> > > Studio, and
> > > invoke
> > > > build indirectly. For details on how to do this, see the
> > > resources section
> > > > of my web site (www.hollistech.com).
> > > >
> > > > > -----Original Message-----
> > > > > From: Jamey kirby [mailto:xxxxx@storagecraft.com]
> > > > > Sent: Saturday, September 30, 2000 12:49 PM
> > > > > To: NT Developers Interest List
> > > > > Subject: [ntdev] Re: Building drivers in developer studio???
> > > > >
> > > > >
> > > > > download src2dsp.exe from www.numega.com
> > > > >
> > > > > It will convert you SOURCES file to a DSP/DSW file and the
> > > > > build become 100%
> > > > > native in the IDE.
> > > > >
> > > > > Jamey
> > > > >
> > > > >
> > >
> > > Mark Roddy
> > > xxxxx@hollistech.com
> > > www.hollistech.com
> > > WindowsNT Windows 2000 Consulting Services
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: david_cox2@hp.com
> > > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@stratus.com
> > > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> > >
> >
> > —
> > You are currently subscribed to ntdev as: rick@1394.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
Bull shit.
-----Original Message-----
From: Thomas “Rick” Tewell [mailto:rick@1394.com]
Sent: Sunday, October 01, 2000 1:06 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Building drivers in developer
studio???
Just as an aside…REAL kernel level programmers don’t use
IDEs…
Thomas “Rick” Tewell
Sequoia Advanced Technologies, Inc.
Marin County, California
tel: 415-459-7978 x104
Well the command line does not have a source browser or other standard
software engineering tools for grokking software. From that perspective, and
from a simple perspective of efficiency/productivity visual studio (or
emacs, or any other set of integrated programming tools,) is a huge win over
the ‘real kernel programmer’ methods. IMHO the reason why ‘real kernel
programmers’ use command shells is that they all learned to program on dec
writers etc. in the late 70’s and think that a 24x80 video display is state
of the art, and are too fossilized to learn new technologies.
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Monday, October 02, 2000 4:08 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Building drivers in developer studio???Agree completely.
IDE is OK as a text editor - by why typing “build” in the
command line is
more boring than pressing the Shift-F8 in the IDE?
I think that possible problems while using a .DSP for driver
can be worse
than typing 6 keys + (also minor) problem of pressing Ctrl-G
- entering the
error line number in the IDE.Max
----- Original Message -----
From: “Thomas “Rick” Tewell”
> To: “NT Developers Interest List”
> Sent: Monday, October 02, 2000 12:06 AM
> Subject: [ntdev] Re: Building drivers in developer studio???
>
>
> > Just as an aside…REAL kernel level programmers don’t use IDEs…
> >
> >
> >
> > Thomas “Rick” Tewell
> > Sequoia Advanced Technologies, Inc.
> > Marin County, California
> > tel: 415-459-7978 x104
> >
> > ----- Original Message -----
> > From: Roddy, Mark
> > To: NT Developers Interest List
> > Sent: Monday, October 02, 2000 12:52 PM
> > Subject: [ntdev] Re: Building drivers in developer studio???
> >
> >
> > > The risk that whatever compiler/linker/preprocessor
> settings you get
> from
> > > the visual-studio-only version is not correct for
> building drivers in
> the
> > > target ddk version for your driver. Unless I am mistaken,
> driver wizards
> > and
> > > src2dsp all essentially use snapshots of these settings
> from some point
> in
> > > time based on some version of the ddk.
> > >
> > > Now I will agree that the risk is small, but it is there.
> > >
> > > In addition there is no automatic way to go back to a
> straight build
> > version
> > > of the same driver. So if you do run in to what appear to
> be compiler or
> > > linker problems you are SOL and have to go re-create a
> DDK project by
> > hand.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: COX,DAVID (HP-Roseville,ex1) [mailto:david_cox2@hp.com]
> > > > Sent: Monday, October 02, 2000 3:36 PM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Re: Building drivers in developer studio???
> > > >
> > > >
> > > > What risk?
> > > >
> > > > --------------------------------------------------------------
> > > > ---------
> > > > Dave Cox
> > > > Hewlett-Packard Co.
> > > > HPSO/SMSO (Santa Barbara)
> > > > https://ecardfile.com/id/Dave+Cox
> > > >
> > > > > -----Original Message-----
> > > > > From: Roddy, Mark [mailto:xxxxx@stratus.com]
> > > > > Sent: Monday, October 02, 2000 10:41 AM
> > > > > To: NT Developers Interest List
> > > > > Subject: [ntdev] Re: Building drivers in developer studio???
> > > > >
> > > > >
> > > > > Of course there is the other view that not using build is
> > > > adding needless
> > > > > additional risk to your driver development effort. A
> > > > compromise is to
> > > > build
> > > > > driver projects as “External Makefile” projects in Visual
> > > > Studio, and
> > > > invoke
> > > > > build indirectly. For details on how to do this, see the
> > > > resources section
> > > > > of my web site (www.hollistech.com).
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Jamey kirby [mailto:xxxxx@storagecraft.com]
> > > > > > Sent: Saturday, September 30, 2000 12:49 PM
> > > > > > To: NT Developers Interest List
> > > > > > Subject: [ntdev] Re: Building drivers in developer
> studio???
> > > > > >
> > > > > >
> > > > > > download src2dsp.exe from www.numega.com
> > > > > >
> > > > > > It will convert you SOURCES file to a DSP/DSW file and the
> > > > > > build become 100%
> > > > > > native in the IDE.
> > > > > >
> > > > > > Jamey
> > > > > >
> > > > > >
> > > >
> > > > Mark Roddy
> > > > xxxxx@hollistech.com
> > > > www.hollistech.com
> > > > WindowsNT Windows 2000 Consulting Services
> > > >
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as: david_cox2@hp.com
> > > > To unsubscribe send a blank email to
> $subst(‘Email.Unsub’)
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as: xxxxx@stratus.com
> > > > To unsubscribe send a blank email to
> $subst(‘Email.Unsub’)
> > > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: rick@1394.com
> > > To unsubscribe send a blank email to
> $subst(‘Email.Unsub’)
> > >
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@stratus.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
Haven’t met anyone working on the kernel at any OS development company yet
(including Microsoft) that endorses using an IDE as a suitable development
environment… That may change…but I’m not sure when… This is why the
DDKs are set up the way they are.
Anyway my comment was intended as just a little “humor” not a raging debate
issue…
Thomas “Rick” Tewell
Sequoia Advanced Technologies, Inc.
Marin County, California
----- Original Message -----
From: Gary Little
To: NT Developers Interest List
Sent: Monday, October 02, 2000 1:09 PM
Subject: [ntdev] Re: Building drivers in developer studio???
> Bull shit.
>
> -----Original Message-----
> From: Thomas “Rick” Tewell [mailto:rick@1394.com]
> Sent: Sunday, October 01, 2000 1:06 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Building drivers in developer
> studio???
>
> Just as an aside…REAL kernel level programmers don’t use
> IDEs…
>
>
>
> Thomas “Rick” Tewell
> Sequoia Advanced Technologies, Inc.
> Marin County, California
> tel: 415-459-7978 x104
>
>
>
> —
> You are currently subscribed to ntdev as: rick@1394.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>
Well, children, REAL programmers don’t need debuggers either … they use
the light panel and switches to find and fix bugs. But then anyone born
after 1975 has no idea of that which I speak.
Thank you … I like the IDE, I use the IDE, and I’m an old geezer that’s
been writing code longer than many here are old.
It boils down to personal preference.
Gary
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Monday, October 02, 2000 1:08 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Building drivers in developer
studio???
Agree completely.
IDE is OK as a text editor - by why typing “build” in the
command line is
more boring than pressing the Shift-F8 in the IDE?
I think that possible problems while using a .DSP for driver
can be worse
than typing 6 keys + (also minor) problem of pressing Ctrl-G
- entering the
error line number in the IDE.
Max
----- Original Message -----
From: “Thomas “Rick” Tewell”
To: “NT Developers Interest List”
Sent: Monday, October 02, 2000 12:06 AM
Subject: [ntdev] Re: Building drivers in developer
studio???
> Just as an aside…REAL kernel level programmers don’t use
IDEs…
>
>
>
> Thomas “Rick” Tewell
> Sequoia Advanced Technologies, Inc.
> Marin County, California
> tel: 415-459-7978 x104
>
> ----- Original Message -----
> From: Roddy, Mark
> To: NT Developers Interest List
> Sent: Monday, October 02, 2000 12:52 PM
> Subject: [ntdev] Re: Building drivers in developer
studio???
>
>
> > The risk that whatever compiler/linker/preprocessor
settings you get
from
> > the visual-studio-only version is not correct for
building drivers in
the
> > target ddk version for your driver. Unless I am
mistaken, driver wizards
> and
> > src2dsp all essentially use snapshots of these settings
from some point
in
> > time based on some version of the ddk.
> >
> > Now I will agree that the risk is small, but it is
there.
> >
> > In addition there is no automatic way to go back to a
straight build
> version
> > of the same driver. So if you do run in to what appear
to be compiler or
> > linker problems you are SOL and have to go re-create a
DDK project by
> hand.
> >
> >
> >
> > > -----Original Message-----
> > > From: COX,DAVID (HP-Roseville,ex1)
[mailto:david_cox2@hp.com]
> > > Sent: Monday, October 02, 2000 3:36 PM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Building drivers in developer
studio???
> > >
> > >
> > > What risk?
> > >
> > >
--------------------------------------------------------------
> > > ---------
> > > Dave Cox
> > > Hewlett-Packard Co.
> > > HPSO/SMSO (Santa Barbara)
> > > https://ecardfile.com/id/Dave+Cox
> > >
> > > > -----Original Message-----
> > > > From: Roddy, Mark [mailto:xxxxx@stratus.com]
> > > > Sent: Monday, October 02, 2000 10:41 AM
> > > > To: NT Developers Interest List
> > > > Subject: [ntdev] Re: Building drivers in developer
studio???
> > > >
> > > >
> > > > Of course there is the other view that not using
build is
> > > adding needless
> > > > additional risk to your driver development effort. A
> > > compromise is to
> > > build
> > > > driver projects as “External Makefile” projects in
Visual
> > > Studio, and
> > > invoke
> > > > build indirectly. For details on how to do this, see
the
> > > resources section
> > > > of my web site (www.hollistech.com).
> > > >
> > > > > -----Original Message-----
> > > > > From: Jamey kirby [mailto:xxxxx@storagecraft.com]
> > > > > Sent: Saturday, September 30, 2000 12:49 PM
> > > > > To: NT Developers Interest List
> > > > > Subject: [ntdev] Re: Building drivers in developer
studio???
> > > > >
> > > > >
> > > > > download src2dsp.exe from www.numega.com
> > > > >
> > > > > It will convert you SOURCES file to a DSP/DSW file
and the
> > > > > build become 100%
> > > > > native in the IDE.
> > > > >
> > > > > Jamey
> > > > >
> > > > >
> > >
> > > Mark Roddy
> > > xxxxx@hollistech.com
> > > www.hollistech.com
> > > WindowsNT Windows 2000 Consulting Services
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
david_cox2@hp.com
> > > To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
> > >
> > > —
> > > You are currently subscribed to ntdev as:
xxxxx@stratus.com
> > > To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
> > >
> >
> > —
> > You are currently subscribed to ntdev as: rick@1394.com
> > To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
> >
> >
>
>
> —
> You are currently subscribed to ntdev as:
xxxxx@storagecraft.com
> To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
>
—
You are currently subscribed to ntdev as:
xxxxx@broadstor.com
To unsubscribe send a blank email to
$subst(‘Email.Unsub’)
> the ‘real kernel programmer’ methods. IMHO the reason why 'real kernel
programmers’ use command shells is that they all learned to program on dec
writers etc. in the late 70’s and think that a 24x80 video display is
state
of the art, and are too fossilized to learn new technologies.
You know, your “tongue in cheek” comment is probably pretty accurate. I
learned to write MS-DOS device drivers using Brief and command line
makefiles. I still do. I always install Brief on my development system
(including W2k DDK) and rock and roll. I’m resistant to the IDE because I
never had to learn to use it. I simply edit SOURCES files manually and/or
makefiles and I always work in the “console” 80x?? (usually 80x50 with
Brief!!). I even drop to a console when I have to trigger SoftICE because I
find the “window” too distracting.
Someday, maybe I’ll sit down and take the time to look at SlickEdit or maybe
even (gasp!!) VisualStudio…but until then, when I need to bang out a
driver, I fire up my old trusty friend Brief and type “BUILD”…
Thomas “Rick” Tewell
Sequoia Advanced Technologies, Inc.
Marin County, California
> Well, children, REAL programmers don’t need debuggers either … they use
the light panel and switches to find and fix bugs. But then anyone born
after 1975 has no idea of that which I speak.
I like debuggers…just COMMAND LINE debuggers!! (of which I think SoftIce
fits in this category)
Actually, come to think of it, I like the DEBUG.EXE interface pretty well
too.
You get a “-”. If you don’t know what to do from there…you shouldn’t have
run DEBUG.EXE!!
HA HA…Couldn’t resist…
Thomas “Rick” Tewell
Sequoia Advanced Technologies, Inc.
Marin County, California
Hi Guys,
Wow! Good topic. I must say that I have seen “REAL Kernel mode programmers”
use the build environment to build the driver, discover that they have a
compiler error with a variable, so they run “grep” or “find” to locate all
places this variable occurs in their source files, open these files in age
old editors (some go to the extent of using ‘vi’ emulators under windows),
by then they forget how the variable was spelt so they jump back to the grep
window memorize the spelling and jump back to the editor fix the problem,
jump back to the build environment and run build again.
Then there are the ‘non-REAL kernel mode programmers’ who use the IDE, run
build from within it, double click on the error and the source file is
ready, press F11 and the variable definition/declaration is ready,
thankfully he can use copy paste instead of memorizing the variable names,
when done, build just a key or clicks away.
Lucky for me, I discovered the batch utility Mark Roddy is talking about a
couple of years ago and life has been better for me being a non-REAL
programmer. I agree that learning new stuff does require some time but it
DOES pays off when it make you comfortable when you are developing/debugging
and you can concentrate on the things you want to do rather than HOW to do
the thing you want to do.
----- Original Message -----
From: “Thomas “Rick” Tewell”
To: “NT Developers Interest List”
Sent: Sunday, October 01, 2000 1:28 PM
Subject: [ntdev] Re: Building drivers in developer studio???
> Haven’t met anyone working on the kernel at any OS development company yet
> (including Microsoft) that endorses using an IDE as a suitable development
> environment… That may change…but I’m not sure when… This is why the
> DDKs are set up the way they are.
>
> Anyway my comment was intended as just a little “humor” not a raging
debate
> issue…
>
> Thomas “Rick” Tewell
> Sequoia Advanced Technologies, Inc.
> Marin County, California
>
> ----- Original Message -----
> From: Gary Little
> To: NT Developers Interest List
> Sent: Monday, October 02, 2000 1:09 PM
> Subject: [ntdev] Re: Building drivers in developer studio???
>
>
> > Bull shit.
> >
> > -----Original Message-----
> > From: Thomas “Rick” Tewell [mailto:rick@1394.com]
> > Sent: Sunday, October 01, 2000 1:06 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Building drivers in developer
> > studio???
> >
> > Just as an aside…REAL kernel level programmers don’t use
> > IDEs…
> >
> >
> >
> > Thomas “Rick” Tewell
> > Sequoia Advanced Technologies, Inc.
> > Marin County, California
> > tel: 415-459-7978 x104
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: rick@1394.com
> > To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@hotmail.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>