Re: Can I install and use both the NT4 and W2K DDKs on the same machine?

NTDEV
1

Max is right.

The BUILD tool that comes with DDK seems to work with DOS-like
(!? I wonder why!?..) pathnames (limited to 64-characters): after
installing DDK, I realized that when compiling and building my first
few projects/experiments. I found up two useful workarounds:

  1. NEVER include spaces in directory names (well, this is good practice
    and common sense and I usually avoid spaces, but you’ll be laughing to
    know I spend almost half an hour to find that my driver would compile
    OK after I renamed “C:\My Projects” to “C:\MyProjects”);

  2. To avoid using extremely long pathnames (>64 characters) you may
    assign your working project directory to a drive letter (mapped), e.g.
    you could be using the following directory:

C:\Program Files\Microsoft Visual
Studio\VC98\MyProjects\ProjectX\VersionY\DriverZ

In addition to the above path, using the DDK BUILD tool would add
a lot of sub-directories (Debug, i386, obj, objchk, etc.); you may
imagine how easy it is for you to get more than 64 characters on a
pathname to your project… So, a possible workaround would be to
use a mapped network drive (e.g. P:\ for “Projects”) and assign it to:

C:\Program Files\Microsoft Visual Studio\VC98\MyProjects

you would come up with:

P:\ProjectX\VersionY\DriverZ

referring to your driver project (and DDK won’t complain).

(Before you ask, the above example is not real: it’s not very smart to
mix your project directory with program files; this is intended to be an
example of how pathnames might grow easily)

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

«Humour and love are God’s answers
to Human weaknesses»

On Saturday, May 12, 2001 12:35 AM “Maxim S. Shatskih” wrote:

Surely they can. Just install to different directories.
Also - do not install VC++ in the directory with spaces in the name
like “Program Files”.
BUILD has bugs with it.

On Saturday, May 12, 2001 1:43 AM “Nate Bushman” wrote:

I’d like to be able to build both NT4 and W2K drivers using the same
machine and I’m just wondering if these two DDKs can coexist on the
same machine without causing any problems.

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

> assign your working project directory to a drive letter (mapped), e.g.

you could be using the following directory:

C:\Program Files\Microsoft Visual
Studio\VC98\MyProjects\ProjectX\VersionY\DriverZ

I always hated such pathnames for a project directories.
I prefer d:\MyProject1, d:\MyProject2 etc.
The shorter the pathname is - the better.

Max

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

On Wednesday, May 16, 2001 9:20 AM “Maxim S. Shatskih” wrote:

> assign your working project directory to a drive letter (mapped),
e.g.
> you could be using the following directory:
>
> C:\Program Files\Microsoft Visual
> Studio\VC98\MyProjects\ProjectX\VersionY\DriverZ

I always hated such pathnames for a project directories.
I prefer d:\MyProject1, d:\MyProject2 etc.
The shorter the pathname is - the better.

Max

Sure. :slight_smile: That’s why I said that was NOT a “real” example (I just meant
to prove
how easily pathnames could grow and become a lot longer than 64
characters).
Personally, I take your approach: however, I’m limited to a single (but
large) C:
drive, so you could consider a slightly different variation and from the
“C:\MyProjects” «parent» directory consider each project lying on
sub-directories
(C:\MyProjects\MyProject1, C:\MyProjects\MyProject2, etc.). Then I could
map a D: drive to C:\MyProjects and I would come up (like you) with
d:\MyProject1, d:\MyProject2 etc… as you say, the shorter the
pathname, the
better.

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

«Humour and love are God’s answers
to Human weaknesses»

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com