Windows Server 2003 DDK
Note: The Driver Development Kit (DDK) has been superseded by the Windows Driver Kit (WDK). Use the Windows Server 2003 build environments in the WDK to build drivers that use new features or functionality available only in Windows Server 2003. Use the Windows 2000 build environments in the WDK to build drivers designed to run on Windows Vista, Windows Server 2003, Windows XP, or Windows 2000. The Windows 2000 build environment in the WDK includes updated headers and libraries for Windows 2000 Service Pack 4 (SP4). Archive: Windows Server 2003 SP1 DDK
DDK Support Information
Frequently Asked QuestionsQ: What is the Windows Server 2003 SP1 DDK? A: This is a consolidated driver development kit (DDK) that provides documentation, driver samples, build environment and tools to support driver development for multiple Windows operating system editions. Q: Which Windows editions does this DDK support? A: This release of the DDK supports the following platforms [this same support is available in the current WDK]:
Q: The supported platforms list includes Service Pack levels. Does this mean that I need to get a previous Windows DDK to build drivers for machines that do not have the Service Pack installed? A: No. Drivers developed with the build environment provided in this DDK will be compatible with the original release of the Windows product. This release updates the Windows DDK to support bug fixes have been made to DDK content and to files based on the operating system source code. Q: Can I use this to build drivers for all the supported platforms? A: Yes. Q: I already have a Windows XP DDK or an earlier version of the Windows DDK installed on my machine. Can I just run this installation into the existing directory and install over it? A: No. Install the Windows Server 2003 SP1 DDK into a new directory, and copy your files into the new directory structure. The installation program does not have the ability to update a previous release of a DDK. Q: Are there any known issues or problems with the Windows DDK? A: All related details are listed in the Release Notes and in "Release Note Updates" later on this page. Q: Can I use the Windows DDK to develop for the 64-bit Windows edition? A: Yes. Q: How can I get the Windows DDK on CD? A: The Windows DDK CDs are shipped by:
Release Note UpdatesUsing Binplace.exe Binplace.exe in the Windows Server 2003 SP1 RC2 DDK is missing a required DLL and will not work as shipped. If you require binplace.exe, you can either copy the file symbolcheck.dll from the debugger directory to <ddk root directory> \bin\x86, or use a version of binplace.exe from an earlier kit. PREfast with driver-specific enhancements Prior to this release of the DDK, a standard version of PREfast was the default used in the DDK build environments. A manual process described in the PREfast documentation described how to invoke a special version with enhanced driver-specific analysis. With this release the driver-specific PREfast is now the default version. It is no longer necessary to perform the manual process to access this feature. This change will result in more information about real and possible issues in source code. The manual process now has no net effect, and can continue to be used if convenient. Please refer to PREfast documentation to learn more about the driver specific rules and ways to use filters to reduce common warnings. Driver Build and Install Platforms for Windows 2000In conformance with Microsoft support policy, Microsoft is removing Windows 2000 from its list of supported installation platforms for the Windows Driver Kit (WDK). The WDK continues to provide a Windows 2000 build environment for the development of drivers targeting Windows 2000. Windows 2000 has moved from Mainstream to Extended Support (as defined in the Microsoft Support Lifecycle policy available at http://support.microsoft.com/lifecycle/). The Extended Support phase includes security updates and paid support only; it does not provide support for design changes or new product features. Resources |
