problems building WDK 5600 WDF samples

NTDEV
1

I try to build the WDF samples using build.exe -ceZ in a Windows 2000 checked (or free for that matter) environment under the WDK RC1 (5600). I get the following message in a modal error box:

C:WinDDK\5600\bin\x86\build.exe not a valid Win32 Application

I can’t go further after that error.

All I want out of this is to use KMDF 1.5. could I copy the library files over to the WDF 1.1 stuff that does work and link with those and make sure I use the 1.5 co-installer from the 5600 subdirectory?

I also noticed there are no symbols for 1.5 under the 5600 directory. Is this coming off of the symbol server now since it is a release candidate or are they not yet available? This
machine is a dual P3 running Windows 2K SP4.

2

MARKLOSANGELES:

I just built all the KMDF samples in a 2K environment and had no
trouble. Do other WDK samples build correctly?

That dialog box usually means that you are either trying to execute an
x64 image on an x86, trying to execute something that is not a Win32
executable but has an extension that Windows considers that of an
executable (.BAT, .COM, .EXE…), or the file itself is corrupted. Of
these, the only one that really seems even possible is the last,
assuming that the message is correct (that is, it is in the x86 folder),
and that the installation went correctly and completely, is the last
one. That being said, it isn’t very likely either, so I’m probably
missing something. Try switching to the folder indicated and executing
BUILD.EXE itself. If it doesn’t work, I would reinstall the WDK.

I think, but am not sure, that have also seen that message in cases
where a dependency is missing. I just checked x86\Build.EXE on my
machine, and noticed that it imports MSVCRT among other things (such as
NTDLL, which is curious). I have no idea whether this is your problem
or not, but, I’ve those horrible assemblies under the
Windows\WinSXS folder do stuff like this. I really hate those things.
Build does import, very indirectly, GDIPlus, which is a SAS (you can see
this using Depends). If you’re really desperate and bored, try
executing BUILD under WinDbg and see what you get.

All in all I would reinstall the WDK, unless you have a better idea,
which there must be.

MM

As far as the symbols go, I really don’t know the answer to this, as

>> xxxxx@yahoo.com 2006-09-09 22:42 >>>
I try to build the WDF samples using build.exe -ceZ in a Windows 2000
checked (or free for that matter) environment under the WDK RC1 (5600).
I get the following message in a modal error box:

C:WinDDK\5600\bin\x86\build.exe not a valid Win32 Application

I can’t go further after that error.

All I want out of this is to use KMDF 1.5. could I copy the library
files over to the WDF 1.1 stuff that does work and link with those and
make sure I use the 1.5 co-installer from the 5600 subdirectory?

I also noticed there are no symbols for 1.5 under the 5600 directory.
Is this coming off of the symbol server now since it is a release
candidate or are they not yet available? This
machine is a dual P3 running Windows 2K SP4.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

3

I sorted jumped around this problem by copying the 1.5 libraries from WDK RC1 (5600) to the WDF 1.1 folder (I renamed the old libraries in the WDF folder by putting an ‘x’ at the end of the extension, so if this didn’t work, I could easily go back. I build under the WDF directory as before and change the .inf files references to 1.5 where appropriate.

It worked! At least I believe it did. I am enumerating my USB device on a win2k SP4 machine and was able to switch to the alternate interface and get the continuous Int reader working. Which I couldn’t do using 1.1 or even 1.5 from the 5483 build.

Well, sort of working. I am dropping nine words of data in between packets–I have a continuously incrementing 16 bit counter and I transfer 32 bytes every 1 mS. So there so never be any gaps in a reliable transfer like INT. I think something in my firmware is amiss. Because when I ran the continous reader w/o switching to the alternate interface on this machine (when I couldn’t under 1.1); there was never a dropped word of data.

4

MARKLOSANGELES:

Glad to hear that it worked. I’m very confused, however. What does
the location of WDF libraries have to do with the dialog box? I know
more or less nothing about KMDF, so I’m just curious.

>> xxxxx@yahoo.com 2006-09-10 00:35 >>>
I sorted jumped around this problem by copying the 1.5 libraries from
WDK RC1 (5600) to the WDF 1.1 folder (I renamed the old libraries in the
WDF folder by putting an ‘x’ at the end of the extension, so if this
didn’t work, I could easily go back. I build under the WDF directory as
before and change the .inf files references to 1.5 where appropriate.

It worked! At least I believe it did. I am enumerating my USB device
on a win2k SP4 machine and was able to switch to the alternate interface
and get the continuous Int reader working. Which I couldn’t do using 1.1
or even 1.5 from the 5483 build.

Well, sort of working. I am dropping nine words of data in between
packets–I have a continuously incrementing 16 bit counter and I
transfer 32 bytes every 1 mS. So there so never be any gaps in a
reliable transfer like INT. I think something in my firmware is amiss.
Because when I ran the continous reader w/o switching to the alternate
interface on this machine (when I couldn’t under 1.1); there was never a
dropped word of data.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

5

If I invoked a Checked Build environment from the WDK RC1 (5600) Menu on the Start menu, it sets the paths and environment to everything being C:\winnt\5600\ etc and I get the above mentioned error.

If I invoke a check Build Environment from the DDK 3790.1830 Menu on the Start Menu, it sets up different paths and I uses the build command that came with the 3790.1830 install which works. I wonder if I could copy build.exe from the 3790.1830 and place it in c:\winnt\5600\bin\x86 directory overwriting the current version. Maybe I will try that if I get some time.

6

Symbols: they are on the symserver now, not a part of the WDK

Have you tried installing the WDK on an OS post win2k? does it work on
xp?

As for dropped packets, KMDF always pends an xfer. Perhaps in the
transition from one interface setting to another, the device loses
packets b/c it cannot send them.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Saturday, September 09, 2006 11:57 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] problems building WDK 5600 WDF samples

If I invoked a Checked Build environment from the WDK RC1 (5600) Menu on
the Start menu, it sets the paths and environment to everything being
C:\winnt\5600\ etc and I get the above mentioned error.

If I invoke a check Build Environment from the DDK 3790.1830 Menu on the
Start Menu, it sets up different paths and I uses the build command that
came with the 3790.1830 install which works. I wonder if I could copy
build.exe from the 3790.1830 and place it in c:\winnt\5600\bin\x86
directory overwriting the current version. Maybe I will try that if I
get some time.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

7

WDK (RC1 and newer) does not support w2k as a develeopment platform even
though it supports w2k as target environment. I may be mentioned in the
release notes of WDK.

kumar

wrote in message news:xxxxx@ntdev…
>I try to build the WDF samples using build.exe -ceZ in a Windows 2000
>checked (or free for that matter) environment under the WDK RC1 (5600). I
>get the following message in a modal error box:
>
> C:WinDDK\5600\bin\x86\build.exe not a valid Win32 Application
>
> I can’t go further after that error.
>
> All I want out of this is to use KMDF 1.5. could I copy the library files
> over to the WDF 1.1 stuff that does work and link with those and make sure
> I use the 1.5 co-installer from the 5600 subdirectory?
>
> I also noticed there are no symbols for 1.5 under the 5600 directory. Is
> this coming off of the symbol server now since it is a release candidate
> or are they not yet available? This
> machine is a dual P3 running Windows 2K SP4.
>
>

8

Kumar said:

WDK (RC1 and newer) does not support w2k as a develeopment platform even
though it supports w2k as target environment. I may be mentioned in the
release notes of WDK.

I looked for that. Actually what is says is that *some* samples will not build in 2000 or XP build environments, and will give a warning as such. But It is not explicit (at least to me) in the relnote.htm that 5600 *won’t work* on a 2000 build machine. If that was your intention you may want to be explicit about that.

Doron said:

Have you tried installing the WDK on an OS post win2k? does it work on xp?

I haven’t tried that, as I am going to use that infamous Dell notebook (with USB to serial) mentioned in previous posts to the WINDBG list on this site to be the host machine, I will install it and use the Win 2k box (w/ legacy serial port–it works!) as target machine. So I will probably install it in the next day or so, but for the people who can’t use the 5600 build environments, at least they have an option to use 1.5 if they copy the library files from the 5600 wdf directory to WDF directory.

As for dropped packets, KMDF always pends an xfer. Perhaps in the transition from one interface >setting to another, the device loses packets b/c it cannot send them.

But interesting enough, it is consistently dropping 9 words, but this could be me doing something wrong in my firmware. I am seeing the pend in the analyzer. I could put up a text dump of about 10-20 transactions from the analyzer in this post if there was interest. Since it is a software analyzer, it shows the traffic from the driver stack perspective.