<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">
<!---------------------------Title----------------------------------->
<FONT FACE="Verdana, Arial, Helvetica" SIZE=2>
<B><FONT FACE="Verdana" SIZE=+2> Late-Breaking News for the Microsoft® Windows®XP DDK</FONT></B>
</UL>
<!----------------------Installation Issues---------------------------->
<P><B><FONT face="Verdana, Arial, Helvetica" size="+1">Installation Issues</FONT></B>
<UL>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>DDK Directory Structure</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.</FONT></P>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.
</FONT></P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4><I>Dirs</I> Files</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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. </FONT></P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Microsoft<SUP>®</SUP> Virtual Machine</H4></FONT></B>
<FONT FACE="Verdana, Arial, Helvetica" SIZE=2>The Microsoft<SUP>®</SUP> virtual machine (Microsoft VM) is designed to run on Microsoft<SUP>®</SUP> Windows<SUP>®</SUP> 95, Microsoft<SUP>®</SUP> Windows<SUP>®</SUP> 98, Microsoft<SUP>®</SUP> Windows<SUP>®</SUP> Millennium Edition (Me), Microsoft<SUP>®</SUP> Windows NT<SUP>®</SUP> 4.0, and Microsoft<SUP>®</SUP> Windows<SUP>®</SUP> 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> </FONT></P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Multimon Functionality</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.</FONT></P>
<P>
</UL>
<!-------------------------Changes to the DDK Build Environment---------------------->
<P><B><FONT size="+1" face="Verdana, Arial, Helvetica">Changes to the DDK Build Environment</FONT></B>
<UL>
<P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Changes to Support Conditional Compilation Based on Build Environment</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.</FONT><P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Changes to the Windows 2000 Build Environment</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.</FONT><P>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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).</FONT><br>
<UL>
<LI>build -cZ from the root of the DDK now results in a clean build with no errors or warnings.<br>
<LI>When doing the above, not all samples are built.<br>
<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.<br>
</UL>
<P>
</UL>
<!-------------------------Compiling and Linking---------------------->
<P><B><FONT size="+1" face="Verdana, Arial, Helvetica">Compiling and Linking</FONT></B>
<UL>
<P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Tested Platforms and Compilers</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.</FONT><P>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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:</FONT><P>
<P><B><FONT face="Verdana, Arial, Helvetica" size="2">error C1189: #error : Compiler version not supported by Windows DDK</FONT></B><P>
<P><FONT face="Verdana, Arial, Helvetica" size="2">Some Windows Millennium drivers may require Visual C++ to be installed for use.</FONT><P>
<P><FONT face="Verdana, Arial, Helvetica" size="2">This toolset has not been fully tested for use other than driver development. Development work on this toolset is not complete.</FONT><P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Updated Setenv.bat</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">The <BaseDir>\setenv64.bat has been merged into
a <BaseDir>\setenv.bat. All build environments are still supported with the <BaseDir>\setenv.bat but the
command line has been updated. The new command line is: <B>SetEnv <Directory> [fre|chk] [64]</B>.
<I>Directory</I> is the install location of the DDK, <I>fre</I> or <I>chk</I> are the build types and <I>64</I>
is to select the building of the 64 bit platform. If the <I>64</I> option is used, <I>fre</I> or <I>chk</I> are required.
</FONT><P>
<P><B><FONT face="Verdana, Arial, Helvetica"><H4>Building Binary Compatible Drivers</H4></FONT></B>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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.</FONT><P>
<P><FONT face="Verdana, Arial, Helvetica" size="2">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
- 1
- 2
- 3
- 4
- 5
- 6
前往页