How to find the Server 2003 DDK?
in [Device Drivers]
|
Prev: Simple Hack To Get $2000 To Your PayPal Account
Next: Is it possible to determine (programmatically) if system was just powered up or rebooted
From: Maxim S. Shatskih on 11 Jul 2010 11:04 > 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. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
From: mjbraun on 11 Jul 2010 13:02 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: > > 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. > > -- > Maxim S. Shatskih > Windows DDK MVP > maxim(a)storagecraft.com > http://www.storagecraft.com > > . >
From: Maxim S. Shatskih on 11 Jul 2010 13:42 > 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. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
From: mjbraun on 11 Jul 2010 14:07 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
From: mjbraun on 11 Jul 2010 17:31
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 |