BUG: DDK Build Fails Due to Spaces in the Install Directory of SDK
ID: Q241909
|
The information in this article applies to:
-
Microsoft Windows NT 4.0 Driver Development Kit (DDK)
on the following platforms: x86
SYMPTOMS
When the free or checked build environment of Microsoft Windows NT DDK is opened, the following error is displayed in the MS-DOS window:
The name specified is not recognized as an
internal or external command, operable program or batch file.
CAUSE
The Platform SDK is installed in a directory that has spaces in its pathname; for instance: \program files\mssdk.
RESOLUTION
- If the Platform SDK is already installed on the system then follow these steps:
- Open the batch file Setenv.bat in a text editor such as Notepad. The file resides in the bin subdirectory where you have installed the DDK.
- Look for the following line in the batch file. It should be the eight line in the file.
call %MSTOOLS%\setenv %MSTOOLS%
- Modify the line so that %MSTOOLS%\setenv is in quotes.
call "%MSTOOLS%\setenv" %MSTOOLS%
- Save the batch file.
- If the Platform SDK has not been installed, do this:
- Install the Platform SDK in a directory that does not contain spaces in its pathname.
You do not need to modify the Setenv.bat batch file in the DDK as outlined in the first case.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
Additional query words:
Keywords : kbDDK kbKMode kbNTOS400 kbWinOS2000 kbDSupport kbGrpNTDDK
Version : winnt:
Platform : winnt
Issue type : kbbug