winxp_ddk.rar资源-CSDN文库

共408个文件

inf：183个

cab：182个

exe：16个

5星 · 超过95%的资源需积分: 10 142 浏览量 2012-04-10 11:13:18 上传评论 8 收藏 131.38MB RAR 举报

《Windows XP DDK详解》 Windows XP DDK（Device Driver Kit），全称为Windows XP设备驱动程序开发工具包，是微软为开发者提供的一套用于创建和调试Windows XP操作系统下硬件设备驱动程序的工具集。DDK包含了编译器、链接器、调试器等一系列工具，以及丰富的文档和技术支持，帮助开发者构建稳定、高效的驱动程序。 1. **DDK的主要组件** - **SETUP.EXE**：这是安装程序，用于引导整个DDK的安装过程，将所需的库、头文件、工具和其他资源安装到用户的开发环境中。 - **RELNOTE.HTM**：包含了版本发布说明，详细列出该版本DDK的新特性、改进和已知问题，对开发者了解新版本的功能更新至关重要。 - **INSTALL.HTM**：安装指南，提供了安装DDK的步骤和注意事项，对于首次使用者来说非常有帮助。 - **AUTORUN.INF**：自动运行配置文件，通常在光盘或可移动媒体上使用，当设备插入电脑时会自动执行指定的操作，如打开安装程序。 - **X86、IA64、COMMON**：这些目录分别包含了针对x86（32位）和IA64（Itanium架构，64位）平台的开发工具和共享资源。"X86"包含32位系统的开发工具，"IA64"则是为64位Itanium处理器准备的，"COMMON"则存储了适用于多个平台的通用文件。 2. **DDK的使用场景** - **驱动程序开发**：DDK的核心功能是帮助开发者编写和测试设备驱动程序。它提供了API接口、样例代码和详细的开发文档，使得开发者能够按照Windows XP的内核模式驱动模型（Kernel-Mode Driver Framework, KMD）来编写驱动。 - **调试工具**：DDK中的调试工具，如DEBUGGERS目录下的工具，可以用于调试驱动程序，找出并修复运行时错误，这对于保证驱动程序的稳定性和兼容性至关重要。 3. **DDK的限制** 需要注意的是，Windows XP DDK仅适用于XP系统，随着微软对Windows XP的技术支持终止，新的硬件可能不再提供驱动支持，且安全更新也已停止，这可能导致安全风险。因此，对于现代硬件和追求安全性的开发者，应转向更现代的Windows版本的DDK，如Windows 7或更高版本的WDK（Windows Driver Kit）。 4. **驱动程序开发流程** 使用DDK开发驱动程序通常涉及以下步骤： - 阅读文档理解驱动模型和API。 - 使用DDK提供的工具创建项目并编写源代码。 - 使用编译器和链接器生成驱动程序可执行文件。 - 利用调试器进行驱动程序的测试和调试。 - 安装驱动程序并进行实际系统测试。总结，Windows XP DDK是为Windows XP平台开发驱动程序的重要工具，它提供了一整套开发、编译、调试驱动的环境。尽管Windows XP已经过时，但其驱动开发经验对于理解操作系统与硬件交互的基本原理仍然具有参考价值。对于那些仍需维护XP系统或研究历史驱动开发的人员，DDK仍是一个宝贵的资源。

资源推荐

资源详情

资源评论

收起资源包目录

winxp_ddk.rar （408个子文件）

ME_DBG.CAB 9.06MB

IA6DLIB3.CAB 8.01MB

IA6DLIB1.CAB 7.42MB

X86DLIB1.CAB 6.58MB

IA6DLIB2.CAB 6.01MB

X86DLIB2.CAB 5.28MB

X86DLIB3.CAB 5.08MB

ME_ENV.CAB 4.89MB

W2K_LIBS.CAB 4.58MB

X86DBINS.CAB 4.57MB

WMEOTHER.CAB 3.92MB

IA6DBINS.CAB 3.09MB

TOOL_PRINTX.CAB 3.03MB

GRAPHICS.CAB 2.98MB

NETWORK.CAB 2.73MB

GENE_TOASTE.CAB 2.67MB

KMARCH.CAB 2.15MB

STREAM.CAB 2.14MB

TOOL_PROCAL.CAB 1.98MB

SDKINC2K3.CAB 1.4MB

X86DLIBC.CAB 1.19MB

VIDE_DISPLA.CAB 1.14MB

SDKINCS1.CAB 1.09MB

DDKINCS.CAB 970KB

TOOL_ACPIX.CAB 964KB

SDKINCS3.CAB 899KB

ME_TOOLS.CAB 885KB

SDKINCS2.CAB 882KB

DX7_SAMP.CAB 854KB

TOOL_PRINT.CAB 776KB

DX7_ENV.CAB 743KB

NETW_NDIS.CAB 729KB

INSTALL.CAB 722KB

DDKINC2K.CAB 674KB

TOOL_DIMAPCX.CAB 574KB

TOOL_DIMAPCI.CAB 557KB

STORAGE.CAB 529KB

INTINPUT.CAB 516KB

WDM_VIDEOC.CAB 500KB

STILL.CAB 489KB

BUSES.CAB 488KB

TOOL_AVSTREI.CAB 478KB

WDM_AUDIO.CAB 405KB

IOSGUIDE.CAB 400KB

PRIN_MINI.CAB 394KB

TOOL_AVSTREX.CAB 389KB

DDTOOLS.CAB 354KB

STOR_CLASS.CAB 324KB

TOOL_SAPTOOX.CAB 301KB

IME_CHS.CAB 290KB

APPENDIX.CAB 284KB

VDD_DOSIOC.CAB 267KB

MODEM.CAB 263KB

DDK_DBGI.CAB 263KB

PRIN_MSPLOT.CAB 263KB

TOOL_DEVICEX.CAB 262KB

TOOL_GENINFX.CAB 248KB

ME_SAMP1.CAB 241KB

SDKINC2K1.CAB 236KB

WIN98DDK.CAB 221KB

GLOSS.CAB 221KB

PRIN_OEMDLL.CAB 218KB

KERN_PARPOR.CAB 211KB

SETU_DEVUPG.CAB 210KB

WDM_USB.CAB 205KB

STOR_FDC.CAB 200KB

SDKINC2K2.CAB 189KB

DBGTOOLS.CAB 187KB

WDM_HID.CAB 177KB

WDM_WIA.CAB 172KB

ME_SAMP2.CAB 166KB

TOOL_CHKINF.CAB 162KB

KERN_SERIAL.CAB 156KB

TOOL_POOLTAX.CAB 146KB

PARALLEL.CAB 137KB

TOOL_TRACINX.CAB 136KB

DDK_DBGX.CAB 135KB

TOOL_TRACINI.CAB 134KB

INPU_PNPI80.CAB 131KB

IME_CHT.CAB 131KB

STOR_CHANGE.CAB 130KB

SERIAL.CAB 123KB

WDM_1394.CAB 118KB

SMART.CAB 109KB

TOOL_IRDAX.CAB 108KB

OTHER.CAB 102KB

NETW_IRDA.CAB 101KB

DXDDK.CAB 100KB

1284DOT4.CAB 97KB

BATTERY.CAB 95KB

TOOL_WIAI.CAB 95KB

GSTART.CAB 89KB

STOR_TAPE.CAB 88KB

TOOL_AVSTRE.CAB 86KB

TOOL_OTHERI.CAB 74KB

WDM_BDA.CAB 74KB

TOOL_DIMAPC.CAB 74KB

STOR_MINIPO.CAB 71KB

PRIN_MONITO.CAB 71KB

CMNBINS.CAB 68KB

共 408 条

<HTML> <HEAD> <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <TITLE>Windows XP DDK Release Notes</TITLE> </HEAD> <BODY link="#0000ff" vlink="#800080" bgcolor="#ffffff">  Late-Breaking News for the Microsoft® Windows®XP DDK </UL>  Installation Issues <UL> <H4>DDK Directory Structure</H4> The structure of the DDK directories have significantly changed from that used in Windows 2000. This change results from the Window DDK's inclusion of all the tools, headers, and libraries necessary to build drivers, and also to allow support for multiple build environments. Drivers should continue to reference ntddk.h or wdm.h in the same way they always have (that is, simply by specifying "#include <wdm.h>"). The build environment will automatically set the appropriate include and library file paths. Drivers may find that some header files have been moved from their technology specific directories (such as \network\inc) to a higher-level DDK directory (such as \inc\wxp). Moving these files to the higher-level include path, makes it unnecessary to specify the specific include path for these files. <H4>Dirs Files</H4> The method of generating Dirs files has changed. The Dirs are now created by the DDK setup program during the installation of the kit. If the Dirs need to be recreated after installation of the kit, a command line utility (MakeDirs) is supplied in the <DDKRoot>\bin\x86 directory. The uninstall program will also update the Dirs if a Basic Uninstall is selected. <H4>Microsoft®&nbspVirtual Machine</H4> The Microsoft® virtual machine (Microsoft VM) is designed to run on Microsoft® Windows® 95, Microsoft® Windows® 98, Microsoft® Windows® Millennium Edition (Me), Microsoft® Windows NT® 4.0, and Microsoft® Windows® 2000 or later. For a current download of the VM, please use this link: <A HREF="http://download.microsoft.com/download/vm/Install/3802/W9X2KMe/EN-US/msjavx86.exe">http://download.microsoft.com/download/vm/Install/3802/W9X2KMe/EN-US/msjavx86.exe </A> <H4>Multimon Functionality</H4> The Windows DDK setup program does not support running in a Multimon environment. The setup program will default to opening on the primary monitor, and must be completed on that monitor. </UL>  Changes to the DDK Build Environment <UL> <H4>Changes to Support Conditional Compilation Based on Build Environment</H4> The environment variable DDK_TARGET_OS has been introduced to allow conditional testing in the 'sources' file to determine if a driver is being built in the Windows 2000 or Windows XP build environments. This variable is set to "Win2K" or "WinXP" respectively. See %ddkroot%\src\general\cancel\sys\sources for an example of it's usage. <H4>Changes to the Windows 2000 Build Environment</H4> Additional headers have been added to more completely match the headers shipped for the Win XP environment. This was necessary to allow some of the samples to compile when built in the Win 2K build environment. When creating the Win2K build environment using the Start Menu icon (or manually running %ddkroot%\bin\w2k\set2k.bat), the environment variable BUILD_OPTIONS is set in order to exclude many samples from default compilation under this environment. This has a couple of effects and limitations (which apply only to the Win 2K environment). <UL> <LI>build -cZ from the root of the DDK now results in a clean build with no errors or warnings. <LI>When doing the above, not all samples are built. <LI>This does not prevent cd'ing into an arbitrary sample directory and attempting to build it. When doing so, samples that do not work correctly in the Windows 2000 build environment will still produce errors and/or warnings. </UL> </UL>  Compiling and Linking <UL> <H4>Tested Platforms and Compilers</H4> The DDK is now shipping a complete set of tools for building drivers. Microsoft Visual C++ is no longer required to be installed to use the DDK. Please use the included tools for all Windows 2000 and Windows XP drivers. This version of the Windows DDK does not support building Windows XP or Windows 2000 drivers using a version of Microsoft Visual C++ earlier than the one supplied with the DDK. Attempts to use in incorrect version of Visual C++ will result in the following error message from the compiler: error C1189: #error : Compiler version not supported by Windows DDK Some Windows Millennium drivers may require Visual C++ to be installed for use. This toolset has not been fully tested for use other than driver development. Development work on this toolset is not complete. <H4>Updated Setenv.bat</H4> The &ltBaseDir&gt\setenv64.bat has been merged into a &ltBaseDir&gt\setenv.bat. All build environments are still supported with the &ltBaseDir&gt\setenv.bat but the command line has been updated. The new command line is: SetEnv &ltDirectory&gt [fre|chk] [64]. Directory is the install location of the DDK, fre or chk are the build types and 64 is to select the building of the 64 bit platform. If the 64 option is used, fre or chk are required. <H4>Building Binary Compatible Drivers</H4> Drivers should typically be built in the build environment of the earliest operating system that the drivers will support. Therefore, a driver that will need to run on Windows 2000 and Windows XP should typically be built within the Windows 2000 build environment. Some drivers, however, may wish to use additional features that are available on the newer operating system, when they run on that operating system. Such drivers may d

评论收藏

内容反馈