Which version of the Platform SDK should you install in order for the NT4 DDK to be happy. I’ve installed the November 2001 Platform SDK and it’s obvious that the NT4 DDK won’t work with it. A look at the NT4 DDK’s setenv.bat file shows that it calls the SDK’s setenv.bat like so:
rem This will put the SDK headers & libs first in the search path.
if “%MSTOOLS%”==“” goto no_mstools
call %MSTOOLS%\setenv %MSTOOLS%
However, the November 2001 Platform SDK’s setenv.bat file doesn’t take a directory as a parameter and complains when it is called with the above. Here’s its complaint (it just tells you the PROPER way to call it and then exits):
Attempting to detect a Visual Studio 6 installation
Setting environment for using Microsoft Visual C++ tools.
“Usage Setenv [/2000 | /me | /XP32 | /XP64 | /pre32 | /pre64] [/DEBUG | /RETAIL]”
/2000 (default) - target Windows 2000 and IE 5.0
/me - target Windows Millennium
/pre32 - target all 32bit pre-release content
/pre64 - target Windows 64bit pre-release content not available on 9x or Me platforms
/DEBUG - set the environment to DEBUG
/RETAIL - set the environment to RETAIL
So… the question is, which version of the Platform SDK DOES work with the NT4 DDK? Or, is there a workaround to this?
Oh, by the way, I had to define MSTOOLS myself, as the November 2001 Platform SDK Setup didn’t define it. I also ran into the “spaces in the directory name” problem and ended up installing the platform SDK in C:\SDK\ rather than C:\Program Files\Microsoft SDK\
Nate
You need the very old MSTOOLS SDK. You have to have a very old version of
the NT SDK to get this. You really don’t need it. Just fix the batch file
since the SDK is not used much or change the call to match the newer SDK’s
needs. I keep the old MsTools directory around just to keep the NT4 DDK
working.
----- Original Message -----
From: “Nate Bushman”
To: “NT Developers Interest List”
Sent: Tuesday, September 10, 2002 10:01 PM
Subject: [ntdev] NT4 DDK and November 2001 Platform SDK don’t work
together…
Which version of the Platform SDK should you install in order for the NT4
DDK to be happy. I’ve installed the November 2001 Platform SDK and it’s
obvious that the NT4 DDK won’t work with it. A look at the NT4 DDK’s
setenv.bat file shows that it calls the SDK’s setenv.bat like so:
rem This will put the SDK headers & libs first in the search path.
if “%MSTOOLS%”==“” goto no_mstools
call %MSTOOLS%\setenv %MSTOOLS%
However, the November 2001 Platform SDK’s setenv.bat file doesn’t take a
directory as a parameter and complains when it is called with the above.
Here’s its complaint (it just tells you the PROPER way to call it and then
exits):
Attempting to detect a Visual Studio 6 installation
Setting environment for using Microsoft Visual C++ tools.
“Usage Setenv [/2000 | /me | /XP32 | /XP64 | /pre32 | /pre64] [/DEBUG |
/RETAIL]”
/2000 (default) - target Windows 2000 and IE 5.0
/me - target Windows Millennium
/pre32 - target all 32bit pre-release content
/pre64 - target Windows 64bit pre-release content not
available on 9x or Me platforms
/DEBUG - set the environment to DEBUG
/RETAIL - set the environment to RETAIL
So… the question is, which version of the Platform SDK DOES work with the
NT4 DDK? Or, is there a workaround to this?
Oh, by the way, I had to define MSTOOLS myself, as the November 2001
Platform SDK Setup didn’t define it. I also ran into the “spaces in the
directory name” problem and ended up installing the platform SDK in C:\SDK<br>rather than C:\Program Files\Microsoft SDK<br>
Nate
—
You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
To unsubscribe send a blank email to %%email.unsub%%