Using WDK on XP x64: Build.exe fails

NTDEV
1

I have successfully been using the WDK for some time on 32bit machines, but I recently installed it on a 64 bit machine, and every I attempt to run build.exe either against my own drivers, or even against the WDK samples I get the error

‘nmake.exe’ is not a recognized internal or external command.

Nmake is definitely in my path. I’ve tried setting a number of different environment variables is various ways, but nothing seems to work.

I am using WDK 6001.18002.

Has anyone had success with this? Are there any known tricks that I am missing?

Thanks,
Bob

2

Is there a space in the path?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@egenera.com
Sent: Tuesday, October 27, 2009 3:05 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Using WDK on XP x64: Build.exe fails

I have successfully been using the WDK for some time on 32bit machines, but I recently installed it on a 64 bit machine, and every I attempt to run build.exe either against my own drivers, or even against the WDK samples I get the error

‘nmake.exe’ is not a recognized internal or external command.

Nmake is definitely in my path. I’ve tried setting a number of different environment variables is various ways, but nothing seems to work.

I am using WDK 6001.18002.

Has anyone had success with this? Are there any known tricks that I am missing?

Thanks,
Bob

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

Doron Holan wrote:

Is there a space in the path?

Yeah, funny how this is STILL an issue …

Pete

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@egenera.com
Sent: Tuesday, October 27, 2009 3:05 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Using WDK on XP x64: Build.exe fails

I have successfully been using the WDK for some time on 32bit machines, but I recently installed it on a 64 bit machine, and every I attempt to run build.exe either against my own drivers, or even against the WDK samples I get the error

‘nmake.exe’ is not a recognized internal or external command.

Nmake is definitely in my path. I’ve tried setting a number of different environment variables is various ways, but nothing seems to work.

I am using WDK 6001.18002.

Has anyone had success with this? Are there any known tricks that I am missing?

Thanks,
Bob

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

–
Kernel Drivers
Windows File System and Device Driver Consulting
www.KernelDrivers.com
866.263.9295

4

No, there is no space in the path for any of the WDK directories. There are other elements with a space in the path, but they are for non-related items and the appear later in the path than the WDK items. My 32bit machine has almost exactly the same path settings and is working fine.

5

This seems to be more of a generic 32bit app not inheriting the path issue. If I run nmake directly against a makefile, I get the error ‘cl.exe’ is not a recognized internal or external command. I’ll comb some of the more generic x64 forums.

Thanks.