nmake error DDK 3790.1830

[dave]

Hello,

I installed DDK 3790.1830 on W2K.
To verify installation i run "build –cZ".

In each source directory this command created
folder "objchk_w2k_x86" which contains
empty folder "i386" and file "_objects.mac".

I run "build -w" to build my driver.
This command created empty folder "i386", and
folder "objchk_w2k_x86" which contains
empty folder "i386" and file "_objects.mac".

This command also generated
file "buildchk_w2K_x86.log" which contains the following:

BUILD: Computing Include file dependencies:
BUILD: Examining e:\devel\src\dist_01\rwdrv directory for files to compile.
Compiling (NoSync) e:\devel\src\dist_01\rwdrv directory ********************
'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 NOPASS0=1 386=1'
Bad command or file name
Linking e:\devel\src\dist_01\rwdrv directory ********************
'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
386=1'
Bad command or file name

thank you,
dave

[Gary G. Little]

And did you open a checked or free build environment from the Development
Kits folder?

--
The personal opinion of
Gary G. Litte

"dave" <da...@discussions.microsoft.com> wrote in message
news:EEF878EC-9E51-4831...@microsoft.com...

>
> Hello,
>
> I installed DDK 3790.1830 on W2K.

> To verify installation i run "build -cZ".

[dave]

I opened checked build environment .

dave

[Mark Roddy]

On Sat, 31 Dec 2005 14:38:02 -0800, "dave"
<da...@discussions.microsoft.com> wrote:

>I opened checked build environment .
>

What is the path to your ddk installation? More specifically, are
there any spaces in the path?

Do a build -cZ of your driver and copy the entire build log file here,
not just the parts you find interesting.

=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP/2000 Consulting
Device and Filesystem Drivers
Hollis Technology Solutions 603-321-1032
www.hollistech.com

[dave]

Mark,

1. Path to ddk installation:
C:\Winddk

2. Here the entire "buildchk_w2K_x86.log":

BUILD: Examining e:\devel\src\dist_01\rwdrv directory for files to compile.
Compiling (NoSync) e:\devel\src\dist_01\rwdrv directory ********************

'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 386=1'

Bad command or file name
Linking e:\devel\src\dist_01\rwdrv directory ********************
'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
386=1'
Bad command or file name

3. Here the output in concole window when running "build -cZ"

e:\devel\src\dist_01\rwdrv> build -cZ

BUILD: Adding /Y to COPYCMD so xcopy ops won't hang.
BUILD: Object root set to: ==> objchk_w2k_x86
BUILD: Compile and Link for i386

BUILD: Examining e:\devel\src\dist_01\rwdrv directory for files to compile.

BUILD: Compiling <NoSync> e:\devel\src\dist_01\rwdrv directory
BUILD: Linking e:\devel\src\dist_01\rwdrv directory
BUILD: Done

thank you,
dave.

[Ali]

Dave can you put your SOURCES file ?
Cann't see any C or CPP file that you want to compile.

[dave]

Ali:

Here the "Sources" file:

TARGETNAME=rwdrv
TARGETPATH=.
TARGETTYPE=DRIVER

SOURCES=rwdrv.c rwdrv.rc

thank you,
dave

[dave]

After i install DDK to verify instllation i run "build -cZ".

And here the contents of
"C:\WINDDK\3790.1830\buildchk_w2K_x86.log"

BUILD: Examining c:\winddk\3790~1.183 directory tree for files to compile.
Building generated files in c:\winddk\3790~1.183\src\general\pcidrv\sys\hw
********************
'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 PASS0ONLY=1

386=1'
Bad command or file name

Building generated files in c:\winddk\3790~1.183\src\general\toaster\bus
********************
'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 PASS0ONLY=1

386=1'
Bad command or file name

Linking c:\winddk\3790~1.183\src\wdm\wmi\wmifilt directory

********************
'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
386=1'

Bad command or file name.

[Beverly Brown]

When you open the checked build environment window, can you post the output
from the "set" command in that window to show how your environment variables
are set?

Beverly

"dave" <da...@discussions.microsoft.com> wrote in message

news:0F72B31F-9841-49B2...@microsoft.com...

[dave]

Beverly:

Here the output of "set":

ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\dave\Application Data
ATL_INC_PATH=C:\WINDDK\3790~1.183\inc
ATL_INC_ROOT=C:\WINDDK\3790~1.183\inc
ATL_LIB_PATH=C:\WINDDK\3790~1.183\lib\atl\*
BASEDIR=C:\WINDDK\3790~1.183
BUFFER_OVERFLOW_CHECKS=1
BUILD_ALT_DIR=chk_w2K_x86
BUILD_DEFAULT=-ei -nmake -i
BUILD_DEFAULT_TARGETS=-386
BUILD_MAKE_PROGRAM=nmake.exe
BUILD_MULTIPROCESSOR=1
COFFBASE_TXT_FILE=C:\WINDDK\3790~1.183\bin\coffbase.txt
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=84JSN01
ComSpec=C:\WINDOWS\system32\COMMAND.COM
CPU=x86
CRT_INC_PATH=C:\WINDDK\3790~1.183\inc\crt
CRT_LIB_PATH=C:\WINDDK\3790~1.183\lib\crt\*
DDKBUILDENV=chk
DDK_INC_PATH=C:\WINDDK\3790~1.183\inc\ddk\w2K
DDK_LIB_DEST=C:\WINDDK\3790~1.183\lib\w2K
DDK_LIB_PATH=C:\WINDDK\3790~1.183\lib\w2K\*
DDK_TARGET_OS=Win2K
DRIVER_INC_PATH=C:\WINDDK\3790~1.183\inc\ddk\w2K
HALKIT_INC_PATH=C:\WINDDK\3790~1.183\inc\hal\w2K
HALKIT_LIB_PATH=C:\WINDDK\3790~1.183\lib\w2K\*
HOMEDRIVE=C:
HOMEPATH=\
IFSKIT_INC_PATH=C:\WINDDK\3790~1.183\inc\ifs\w2K
IFSKIT_LIB_DEST=C:\WINDDK\3790~1.183\lib\w2K
IFSKIT_LIB_PATH=C:\WINDDK\3790~1.183\lib\w2K\*
INCLUDE=C:\WINDDK\3790~1.183\inc\w2K
LIB=C:\WINDDK\3790~1.183\lib
LINK_LIB_IGNORE=4198
LOGONSERVER=\\84JSN01
MFC_INCLUDES=C:\WINDDK\3790~1.183\inc\mfc42
MFC_LIB_PATH=C:\WINDDK\3790~1.183\lib\mfc\*
MSC_OPTIMIZATION=/Od /Oi
NetSamplePath=C:\PROGRA~1\MICROS~3.NET\FRAMEW~1\Samples
NEW_CRTS=1
NO_BINPLACE=TRUE
NO_BROWSER_FILE=TRUE
NO_SAFESEH=1
NTDBGFILES=1
NTDEBUG=ntsd
NTDEBUGTYPE=both
NTMAKEENV=C:\WINDDK\3790~1.183\bin
NT_UP=0
NUMBER_OF_PROCESSORS=1
OAK_INC_PATH=C:\WINDDK\3790~1.183\inc\w2K
OS=Windows_NT
Os2LibPath=C:\WINDOWS\system32\os2\dll;
Path=C:\WINDDK\3790~1.183\bin\x86;C:\WINDDK\3790~1.183\bin;C:\WINDDK\3790~1.183\bin\x86\drvfast\scripts;e:\appser4.5\bin;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\PROGRA~1\COMMON~1\3COMSH~1;"C:\Program
Files\Dell\Resolution
Assistant\Common\bin";C:\WINDOWS\system32;C:\WINDOWS\system32\WBEM;C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\;E:\JDK1.3.1\BIN;E:\JUNIT\JUNIT3.7\JUNIT\TESTS;e:\mms\lib\win32;E:\BES\bin;C:\PROGRA~1\COMMON~1\AUTODE~1;C:\PROGRA~1\MI0041~1\Office;C:\Program
Files\Microsoft Visual Studio
.Net\FrameworkSDK\Bin;C:\Windows\microsoft.net\framework\v1.0.3705;C:\Program
Files\Microsoft Visual Studio .Net\Vc7\bin;C:\Program Files\Common
Files\Microsoft Shared\VSA\7.0\VsaEnv
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PREFAST_ROOT=C:\WINDDK\3790~1.183\bin\x86\drvfast
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 0 Stepping 10, GenuineIntel
PROCESSOR_INC_PATH=C:\WINDDK\3790~1.183\inc\processor
PROCESSOR_LEVEL=15
PROCESSOR_LIB_PATH=C:\WINDDK\3790~1.183\lib\w2K\*
PROCESSOR_REVISION=000a
ProgramFiles=C:\Program Files
PROJECT_ROOT=C:\WINDDK\3790~1.183\src
PROMPT=$p$g
PUBLISH_CMD=@echo Publish not available...
SDK_INC_PATH=C:\WINDDK\3790~1.183\inc\w2K
SDK_LIB_DEST=C:\WINDDK\3790~1.183\lib\w2K
SDK_LIB_PATH=C:\WINDDK\3790~1.183\lib\w2K\*
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\dave\LOCALS~1\Temp
TMP=C:\DOCUME~1\dave\LOCALS~1\Temp
USERDOMAIN=84JSN01
USERNAME=WinDDK
USERPROFILE=C:\Documents and Settings\dave
VSCOMNTOOLS="C:\Program Files\Microsoft Visual Studio .NET\Common7\Tools\"
W2K=_w2k
WDM_INC_PATH=C:\WINDDK\3790~1.183\inc\ddk\wdm\w2K
WIN2K_DDKBUILD=1
winbootdir=C:\WINDOWS
windir=C:\WINDOWS
WPP_CONFIG_PATH=C:\WINDDK\3790~1.183\bin\wppconfig
_BUILDARCH=x86
_NT_TARGET_VERSION=0x500
_NT_TOOLS_VERSION=0x700

Thank you,
dave

[Pavel A.]

Please try following:

1. Make a copy of the checked build shortcut
2. open it's properties.
3. In the command line, insert between cmd /k and setenv.bat :
path %windir%\system32;%windir% &

( the & is command separator!)

4. Use this shortcut.

Regards
--PA

[Ali]

I also hope that it is deu to environment settings, hope avobe steps
would help you.
Are you able to invoke the ( cl )compiler from command line or from
.Net?

Try Follwing from command line :
1) Setting the environment variables as above or Open Free Buil
Environment:

2)
Switch to your driver directory and type:
cl -nologo -Ii386\ -I. -IG:\WINDDK\3790\inc\mfc42
-Iobjfre_wnet_x86\i386 -IG:\WINDDK\3790\inc\wnet
-IG:\WINDDK\3790\inc\wnet -IG:\WINDDK\3790\inc\ddk\wnet
-IG:\WINDDK\3790\inc\ddk\wdm\wnet -IG:\WINDDK\3790\inc\crt -D_X86_=1
-Di386=1 -DSTD_CALL -DCONDITION_HANDLING=1 -DNT_INST=0 -DWIN32=100
-D_NT1X_=100 -DWINNT=1 -D_WIN32_WINNT=0x0502 /DWINVER=0x0502
-D_WIN32_IE=0x0600 -DWIN32_LEAN_AND_MEAN=1 -DDEVL=1
-D__BUILDMACHINE__=WinDDK -DFPO=1 -DNDEBUG -D_DLL=1 /c /Zel /Zp8
/Gy /Gi- /Gm- -cbstring /W3 /WX /Gz /QIfdiv- /G6 /GX- /GR- /GF /GS
-Z7 /Oxs /Oy -FIG:\WINDDK\3790\inc\wnet\warning.h .\yourFile.cpp

yourFile.cpp

3) Above should produce object file for further linking. Don't forget
to replace paths according to your installation;-)

Regards

[Mark Roddy]

On Sun, 1 Jan 2006 18:45:02 -0800, "dave"
<da...@discussions.microsoft.com> wrote:

>After i install DDK to verify instllation i run "build -cZ".
>
>And here the contents of
>"C:\WINDDK\3790.1830\buildchk_w2K_x86.log"
>
>BUILD: Examining c:\winddk\3790~1.183 directory tree for files to compile.
>Building generated files in c:\winddk\3790~1.183\src\general\pcidrv\sys\hw
>********************
>'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 PASS0ONLY=1
>386=1'
>Bad command or file name
>Building generated files in c:\winddk\3790~1.183\src\general\toaster\bus
>********************
>'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 PASS0ONLY=1
>386=1'
>Bad command or file name
>
>Linking c:\winddk\3790~1.183\src\wdm\wmi\wmifilt directory
>********************
>'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
>386=1'
>Bad command or file name.
>
>
>

I'm coming to the conclusion that your installation did not install
the build toolset. Is there actually an nmake.exe, or anything else
located at c:\winddk\3790.1830\bin\x86 ?

If not then you want to do a re-install and this time you need to
install everything.

[Beverly Brown]

Hmmm, those setting looks OK. Did you install all the build tools? Does
nmake.exe exist in the %BASEDIR%\bin\x86 directory?

Beverly

"dave" <da...@discussions.microsoft.com> wrote in message

news:8553A087-F06A-41A5...@microsoft.com...

[dave]

Hello:

I used "Process Explorer" to analize "build -cZ" and
it detects that "build -cZ" invokes "ntvdm.exe".

thank you,
dave

[dave]

I tried it right away yestarday and
when it didn't work i looked more closely
and found that "build.exe" invokes "ntvdm".

It's very strange because only win16 appl are
executed through "ntvdm".

thank you,
dave

"Pavel A." wrote:

> "dave" wrote:
> > Hello:
> >
> > I used "Process Explorer" to analize "build -cZ" and
> > it detects that "build -cZ" invokes "ntvdm.exe".
>

> Too bad. it attempts to run some DOS command.
> Please try to fix the path as in my previous reply.
>
> --PA

[dave]

OK, i found the error and the fix.

Error was caused by system wide variable
ComSpec=C:\WINDOWS\system32\Command.Com
and fix:
ComSpec=C:\WINDOWS\system32\cmd.exe

thank you,
dave.

P.S.
1. "Command.Com" is win16 appl and it why "ntvdm.exe" got invoked

2. This PC at some point was updated from W98 to W2K.
Doesn't this update change all system wide variables ?

[Mark Roddy]

I personally would copy all my data somewhere and re-ipl that system.
Who knows what other crap you are dragging around.