I’m trying to install an NT4.0 development environment for some
legacy work I need to do, but I’m having trouble. I’ve installed
the VisualStudio 6 (w/ sp5) and IE6.0, which is the latest in the
subscription pack I have, but the Platform SDK installer crashes
with a JavaScript error. None of the text entry dialog boxes work
and I can’t install any of the Platform SDK from the November 2001
disk.
I don’t really want it, I just want the MSTOOLS environment variable
set for the sake of the DDK. Can I get what I need without the
platform SDK?
Steve Williams “The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
steve at picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep.”
abuse@xo.com
xxxxx@ftc.gov
I think you can. I think MSTOOLS originally points to the root of platform
SDK. Try to register this environment variable to point to root folder of
Visual C.
Dan
----- Original Message -----
From: “Stephen Williams”
To: “NT Developers Interest List”
Sent: Wednesday, June 26, 2002 6:21 PM
Subject: [ntdev] Installing NT4 DDK
>
> I’m trying to install an NT4.0 development environment for some
> legacy work I need to do, but I’m having trouble. I’ve installed
> the VisualStudio 6 (w/ sp5) and IE6.0, which is the latest in the
> subscription pack I have, but the Platform SDK installer crashes
> with a JavaScript error. None of the text entry dialog boxes work
> and I can’t install any of the Platform SDK from the November 2001
> disk.
>
> I don’t really want it, I just want the MSTOOLS environment variable
> set for the sake of the DDK. Can I get what I need without the
> platform SDK?
> –
> Steve Williams “The woods are lovely, dark and deep.
> steve at icarus.com But I have promises to keep,
> steve at picturel.com and lines to code before I sleep,
> http://www.picturel.com And lines to code before I sleep.”
>
> abuse@xo.com
> xxxxx@ftc.gov
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>
I thought you could get away without formally installing the platform sdk,
but I may be wrong ? I’m running without it, in fact, I don’t even have an
MSTOOLS environment variable defined, and things seem fine. And I don’t
remember having installed it in my NT4 systems either, but it’s been some
time now. What do we get with the platform sdk that we don’t already have
with vc6 ?
Alberto.
-----Original Message-----
From: Dan Partelly [mailto:xxxxx@rdsor.ro]
Sent: Wednesday, June 26, 2002 11:31 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Installing NT4 DDK
I think you can. I think MSTOOLS originally points to the root of platform
SDK. Try to register this environment variable to point to root folder of
Visual C.
Dan
----- Original Message -----
From: “Stephen Williams”
To: “NT Developers Interest List”
Sent: Wednesday, June 26, 2002 6:21 PM
Subject: [ntdev] Installing NT4 DDK
>
> I’m trying to install an NT4.0 development environment for some
> legacy work I need to do, but I’m having trouble. I’ve installed
> the VisualStudio 6 (w/ sp5) and IE6.0, which is the latest in the
> subscription pack I have, but the Platform SDK installer crashes
> with a JavaScript error. None of the text entry dialog boxes work
> and I can’t install any of the Platform SDK from the November 2001
> disk.
>
> I don’t really want it, I just want the MSTOOLS environment variable
> set for the sake of the DDK. Can I get what I need without the
> platform SDK?
> –
> Steve Williams “The woods are lovely, dark and deep.
> steve at icarus.com But I have promises to keep,
> steve at picturel.com and lines to code before I sleep,
> http://www.picturel.com And lines to code before I sleep.”
>
> abuse@xo.com
> xxxxx@ftc.gov
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> 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.
“Stephen Williams” wrote in message news:xxxxx@ntdev…
>
> I’m trying to install an NT4.0 development environment for some
> legacy work I need to do, but I’m having trouble. I’ve installed
>
Just to remind you: The NT V4 DDK really prefers to work with the Platform
SDK and compiler package that was shipping concurrently with it.
While I’ve seen other arrangements work, I’ve also seen all sorts of
problems: Linking, symbols, loading, you name it. Here at OSR we do our NT
V4 work with the NT V4 DDK, MSVC V4.2 and a platform SDK from 1997 (I
think – Can’t seem to find the disk right now). Is this a royal pain in
the butt? Yes, it certainly is. But it’s the only way we’ve managed to get
100% consistent working results, and no hassles. Good thing we get the
compiler, etc, with the DDK now, huh?
Of course, YMMV…
Peter
OSR
xxxxx@osr.com said:
Just to remind you: The NT V4 DDK really prefers to work with the
Platform SDK and compiler package that was shipping concurrently with
it.
The thing is, what I have is the set of tools from the MSDN Professional
subscription. I naively presumed that that would form a consistent set,
and since I’m doing a fresh DDK environment install for NT4 (it’s been
a while since I needed to work on my NT4 driver) these are the tools I
have.
Oh well, it doesn’t seem to matter what MSTOOLS is set to, so long
as it is set; and I’m able to build drivers now.
xxxxx@osr.com said:
Good thing we get the compiler, etc, with the DDK now, huh?
Amen, brother.
Steve Williams “The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
steve at picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep.”
abuse@xo.com
xxxxx@ftc.gov
Peter’s advice regarding using NT4DDK with VC4.2 and j-random sdk circa 1997
might be a bit of an overstatement, a little bit paranoid, and fairly
useless to any organization that was not doing NT development circa 1997 
In my experience NT4 drivers can be built correctly using VC6 and the most
recent platform sdk. You will get error messages from the platform sdk
setenv.bat file, but they can be ignored. FYI, the most recent platform sdk
does insist that it is compatible with NT4, and there is most likely some
way to fix up the setenv.bat file so that it does not complain.
As others have pointed out, there isn’t a whole lot that is being taken from
the SDK anyway.
-----Original Message-----
From: Stephen Williams [mailto:xxxxx@icarus.com]
Sent: Wednesday, June 26, 2002 1:25 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Installing NT4 DDK
xxxxx@osr.com said:
> Just to remind you: The NT V4 DDK really prefers to work with the
> Platform SDK and compiler package that was shipping
concurrently with
> it.
The thing is, what I have is the set of tools from the MSDN
Professional subscription. I naively presumed that that would
form a consistent set, and since I’m doing a fresh DDK
environment install for NT4 (it’s been a while since I needed
to work on my NT4 driver) these are the tools I have.
Oh well, it doesn’t seem to matter what MSTOOLS is set to, so
long as it is set; and I’m able to build drivers now.
xxxxx@osr.com said:
> Good thing we get the compiler, etc, with the DDK now, huh?
Amen, brother.
Steve Williams “The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
steve at picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep.”
abuse@xo.com
xxxxx@ftc.gov
You are currently subscribed to ntdev as:
xxxxx@stratus.com To unsubscribe send a blank email to
%%email.unsub%%
You get current headers. The VC6 SDK/DDK headers are not updated. MSTOOLS
must point to a SETENV.BAT which is all that is needed. You could go into
the batch file in the DDK that is run and modify it to eliminate the checks
for the SDK.
----- Original Message -----
From: “Moreira, Alberto”
To: “NT Developers Interest List”
Sent: Wednesday, June 26, 2002 11:38 AM
Subject: [ntdev] Re: Installing NT4 DDK
> I thought you could get away without formally installing the platform sdk,
> but I may be wrong ? I’m running without it, in fact, I don’t even have an
> MSTOOLS environment variable defined, and things seem fine. And I don’t
> remember having installed it in my NT4 systems either, but it’s been some
> time now. What do we get with the platform sdk that we don’t already have
> with vc6 ?
>
> Alberto.
>
>
> -----Original Message-----
> From: Dan Partelly [mailto:xxxxx@rdsor.ro]
> Sent: Wednesday, June 26, 2002 11:31 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Installing NT4 DDK
>
>
> I think you can. I think MSTOOLS originally points to the root of platform
> SDK. Try to register this environment variable to point to root folder of
> Visual C.
>
> Dan
>
> ----- Original Message -----
> From: “Stephen Williams”
> To: “NT Developers Interest List”
> Sent: Wednesday, June 26, 2002 6:21 PM
> Subject: [ntdev] Installing NT4 DDK
>
>
> >
> > I’m trying to install an NT4.0 development environment for some
> > legacy work I need to do, but I’m having trouble. I’ve installed
> > the VisualStudio 6 (w/ sp5) and IE6.0, which is the latest in the
> > subscription pack I have, but the Platform SDK installer crashes
> > with a JavaScript error. None of the text entry dialog boxes work
> > and I can’t install any of the Platform SDK from the November 2001
> > disk.
> >
> > I don’t really want it, I just want the MSTOOLS environment variable
> > set for the sake of the DDK. Can I get what I need without the
> > platform SDK?
> > –
> > Steve Williams “The woods are lovely, dark and deep.
> > steve at icarus.com But I have promises to keep,
> > steve at picturel.com and lines to code before I sleep,
> > http://www.picturel.com And lines to code before I sleep.”
> >
> > abuse@xo.com
> > xxxxx@ftc.gov
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> > 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@yoshimuni.com
> To unsubscribe send a blank email to %%email.unsub%%
> In my experience NT4 drivers can be built correctly using VC6 and
the most
recent platform sdk.
NT4 DDK does not use SDK except setenv.bat. So, not having SDK must
not spoil the driver binary.
I never saw any problems with NT4 drivers built by VC5 and VC6,
though, according to sources from MS, their decision to provide the
compiler in XP DDK is to ensure that all drivers will be built by the
same tools as the kernel and MS’s binaries themselves.
w2k and XP DDK does not use SDK at all.
As about SDK - IIRC it just provides some additional LIBs and header
files to OS components not included in MSVC, and also some more recent
headers, newer then ones provided in MSVC (the OS develops faster then
the compiler suite).
So, if one does not program to these components (LSA auth package, for
instance) - MSVC is well enough.
Max