How to find the Server 2003 DDK?

[mjbraun]

Greetings, and apologies if this is an easily answered question, but my
searching has not turned anything up. I appreciate any help or suggestions!

Simply put, I'm trying to learn how to interface with a 1394 device attached
to a 2003 Server, so my first step was to attempt to build the examples in
the newest WDK under src/1394, but they won't build. After some digging, I
discovered that the samples won't run under 2003 because the minimum version
requirements weren't met. So I've been trying to find the DDK for Server 2003
so that I can continue on, but the download link from
http://www.microsoft.com/whdc/devtools/ddk/default.mspx
takes me to the Connect site but the link is dead.

Any suggestions or alternate steps?

Thanks!

takes me to

[Don Burn]

You can find it under the Operating Systems - Server 2003 downloads on
MSDN. Also, I believe the Vista WDK had a sample that would still work
with older OS'es.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

> __________ Information from ESET Smart Security, version of virus
> signature
> database 5267 (20100710) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>

[Maxim S. Shatskih]

> the newest WDK under src/1394, but they won't build. After some digging, I
> discovered that the samples won't run under 2003 because the minimum version
> requirements weren't met

Use the same WDK but 2003 - not Win7 - build env.

--
Maxim S. Shatskih
Windows DDK MVP
ma...@storagecraft.com
http://www.storagecraft.com

[mjbraun]

Don,

Thank you very much for your help; I was able to pull down the Server 2003
SP1 DDK from
Technet. I appreciate the pointer!

"Don Burn" wrote:

> .
>

[mjbraun]

Maxim,

Thank you very much for your reply. The problem shows up under the 2003
build environment (specifically, I was using the 2003 x86 checked
environment). Here's what I get:

C:\WinDDK\7600.16385.1\src\1394>build -ceZ
BUILD: Compile and Link for x86
BUILD: Start time: Sun Jul 11 05:28:37 2010
BUILD: Examining c:\winddk\7600.16385.1\src\1394 directory tree for files to
com
pile.
c:\winddk\7600.16385.1\src\1394\vdev_hybrid\exe Invalidating OACR
warning lo
g for 'WDKSamples:x86chk'
1>BUILD: Building generated files in
c:\winddk\7600.16385.1\src\1394\vdev_hybrid
\kmdf directory
Configuring OACR for 'WDKSamples:x86chk' - <OACR on>
BUILD: Compiling c:\winddk\7600.16385.1\src\1394\vdev_hybrid\umdf directory
BUILDMSG: Warning : The sample
c:\winddk\7600.16385.1\src\1394\vdev_hybrid\umdf
is not valid for the current OS target.
BUILD: Compiling and Linking c:\winddk\7600.16385.1\src\1394\vdev_hybrid\exe
dir
ectory
_NT_TARGET_VERSION SET TO WS03
Compiling resources - vdev_hybrid\exe\wdf1394.rc
Compiling - vdev_hybrid\exe\1394.c
Compiling - vdev_hybrid\exe\async.c
Compiling - vdev_hybrid\exe\debug.c
Compiling - vdev_hybrid\exe\isoch.c
Compiling - vdev_hybrid\exe\util.c
Compiling - vdev_hybrid\exe\wdf1394.c
Compiling - vdev_hybrid\exe\generating code...
Linking Executable -
vdev_hybrid\exe\vdev_hybrid\exe\objchk_wnet_x86\i386\wdf139
4.exe
BUILD: Compiling and Linking
c:\winddk\7600.16385.1\src\1394\vdev_hybrid\kmdf di
rectory
BUILD: Linking for c:\winddk\7600.16385.1\src\1394\vdev_hybrid\umdf directory
BUILD: Finish time: Sun Jul 11 05:28:47 2010
BUILD: Done

9 files compiled
1 executable built

Note that the executable builds, but neither the UMDF nor the KMDF libraries
get built, and there's the "BUILDMSG: Warning : The sample
c:\winddk\7600.16385.1\src\1394\vdev_hybrid\umdf is not valid for the current
OS target." message. Checking the umdf makefile I see:

C:\WinDDK\7600.16385.1\src\1394\vdev_hybrid\umdf>more makefile
#
# Build using BUILD.EXE (Do not edit this section of this file, edit SOURCES)
#
MINIMUM_NT_TARGET_VERSION=0x600

but when I check the environment variables, I get:

_NT_TARGET_VERSION=0x502

Hence the problem. Here's to hoping the older DDK can perform!

"Maxim S. Shatskih" wrote:

> .
>

[Maxim S. Shatskih]

> Note that the executable builds, but neither the UMDF nor the KMDF libraries
> get built,

Why is this bad? When you build a Windows UI app, MFC42.DLL is also not built, so what?

>and there's the "BUILDMSG: Warning : The sample
> c:\winddk\7600.16385.1\src\1394\vdev_hybrid\umdf is not valid for the current
> OS target."

Probably 1394 vdevs are not supported on 2003.

Look at the README file for this sample.

> Hence the problem. Here's to hoping the older DDK can perform!

I think older DDK has neither KMDF not UMDF :-))

I'm absolutely real - you need to understand more of KMDF and UMDF.

The issues you have is because you have done something incorrectly, not because modern WDK is bad.

[mjbraun]

It's bad in that the executable is used to load one or both libraries :

"This document and the associated source code describe how to interact with
the 1394 driver stack. The WDF 1394 Hybrid Sample consist of two sample WDF
Drivers, a UMDF component (umdf1394vdev.dll) and a KMDF component
(kmdf1394vdev.sys). The sample also includes a user mode application that
instantiates the loading the WDF Hybrid Driver stack and allows interaction
with the 1394 bus driver through the installed WDF Hybrid Driver stack"

In the readme, the only reference I could see regarding compatibility was
the line:

"Please note that this sample only works on Windows XP and beyond." (which,
at least per Wikipedia, was released in 2001, vs. Server 2003 being released
in, well, 2003).

All that being said, if I have done something incorrectly, I would very much
like to know what it is. I want to learn more about accessing hardware under
Windows and the best way for me, personally, is to work with sample code,
pull it apart, and see what makes it tick. Given that the (kind of obscure)
device I'm working with does work under 2003, it is possible to interface
with it via 1394, so someone has done it. I just want to learn how they did.
If 2003 doesn't support VDEVs, that's fine: whatever means I should use to
communicate with the hardware is acceptable, as long as I can get it to work
for the rather basic tasks I need to complete (sending a few simple commands
and querying state).

While I would prefer to use a more contemporary OS, the hardware that I have
available to me would not support it, so I'm more-or-less stuck at the 2003
level.

"Maxim S. Shatskih" wrote:

> .
>

[Maxim S. Shatskih]

> If 2003 doesn't support VDEVs, that's fine

Sorry, but what are the real-world problems with the WDK?

The "vdev" sample cannot build? and? this is a show-stopper?

Or _your code_ cannot build? You have provided a log in the previous message. It can.

KMDF/UMDF _libraries_ are not built in the WDK, there is even no provided source for it. You just include the KMDF coinstaller DLL to your package.

Saying "it cannot build KMDF/UMDF libraries" is just nonsense.

[mjbraun]

Maxim,

I think you are mistaken: I never said there were real world problems with the WDK or that anything was a "show stopper". Furthermore, I never said there was any of *my* code. Rather, I attempted to build the sample code in the src/1394 directory. Per the instructions:

"The sample will produce three binaries: two WDF drivers (kmdf1394vdev.sys and umdf1394vdev.dll), and one EXE (WDF1394.exe) as well as the corresponding INF file (wdf1394vdev.inf)."

However building in the top-level (or lower level directories) fails because 2003 does not meet the set minimum version level for the test. I suggest you read the file WinDDK\7600.16385.1\src\1394\vdev_hybrid\wdf1394vdev.htm for more info.

---
frmsrcurl: http://msgroups.net/microsoft.public.development.device.drivers/How-to-find-the-Server-2003-DDK

[mjbraun]

As an addendum, the sample built successfully using the 2003 DDK and I was able to create, install, and query the virtual test device. Again, thank you everyone.

---
frmsrcurl: http://msgroups.net/microsoft.public.development.device.drivers/How-to-find-the-Server-2003-DDK