<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>craigrow : Windows Driver Kit</title><link>http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx</link><description>Tags: Windows Driver Kit</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Device Selection Scripting Object, MSDN Wikis and WinHEC</title><link>http://blogs.msdn.com/craigrow/archive/2007/04/16/device-selection-scripting-object-msdn-wikis-and-winhec.aspx</link><pubDate>Mon, 16 Apr 2007 20:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2155640</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/2155640.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=2155640</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=2155640</wfw:comment><description>&lt;P&gt;The WLK docs team release two exciting items last week.&amp;nbsp; The first is the addition of Wiki functionality to the &lt;A class="" href="http://msdn2.microsoft.com/en-us/library/ms789401.aspx" mce_href="http://msdn2.microsoft.com/en-us/library/ms789401.aspx"&gt;DTM documentation on MSDN&lt;/A&gt;.&amp;nbsp; Check it out, you can be a virtual member of the WLK docs team.&lt;/P&gt;
&lt;P&gt;The second is the release of the &lt;A class="" href="http://www.microsoft.com/whdc/DevTools/WDK/DTM/DTM_DSSO.mspx" mce_href="http://www.microsoft.com/whdc/DevTools/WDK/DTM/DTM_DSSO.mspx"&gt;Device Selection Scripting Object white paper&lt;/A&gt;.&amp;nbsp; This white paper docs all of the interfaces we use in the Device Manager and provides sample code which will enable you to create your own wrapper around DTM, even your own custom UI.&amp;nbsp; Combined with the WTTCL utility you can now wrap all of your logo testing in your own automation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;lt;Shameless WinHEC plug&amp;gt;&lt;/P&gt;
&lt;P&gt;Would you like to hear details on how one of our partners has used DSSO and WTTCL to wrap the DTM entirely in their own custom automation?&amp;nbsp; Come to WinHEC.&amp;nbsp; If you're still on the fence wrt attending WinHEC, check out the amount of WLK and logo content available.&amp;nbsp; This is the best WinHEC for logo testing ever.&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 0.75in"&gt;&lt;FONT face=Calibri size=3&gt;DTM Specific&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-C387/ DVR-C473 : Driver Test Manager: How to use the DTM&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CON-H421: Certification Tests for Portable Devices: Workshop&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CLN-467: Audio Testing: DTM Best Practices&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;SVR-T329: Windows Server Logo Testing: Planning&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;SVR-C330: Windows Server Logo Testing: Implementation&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CLN-T352: Audio Testing for Devices and Systems Using DTM&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;WNS-C444: Logo Program for Storage: Best Practices&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-C451: WDTF Based Logo Tests: An In-Depth Look &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 0.75in"&gt;&lt;FONT face=Calibri size=3&gt;Logo Program&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CLN-T375: Certified for Windows Vista: Customer Awareness&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CLN-C376: Windows Vista Logo Program: Directions&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CLN-T495: Windows Logo Program: Strategic Directions&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;CLN-C404: Windows Logo Program: Best Practices &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 0.75in"&gt;&lt;FONT face=Calibri size=3&gt;Other Driver Testing&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-T388: Building USB Device Simulations with DSF&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-T389: Automating Device Testing: WDTF &lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-T381: Static Analysis and Verification of Drivers&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-T382: Static Analysis Tools: PRE&lt;I&gt;f&lt;/I&gt;ast for Drivers&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 10pt 1.25in"&gt;&lt;FONT face=Calibri size=3&gt;DVR-T407: Driver Verifier: Advanced and Best Practices&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;/Shameless WinHEC plub&amp;gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2155640" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>Next rev of the DTM is available today</title><link>http://blogs.msdn.com/craigrow/archive/2007/04/05/next-rev-of-the-dtm-is-available-today.aspx</link><pubDate>Thu, 05 Apr 2007 19:32:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2033608</guid><dc:creator>craigrow</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/2033608.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=2033608</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=2033608</wfw:comment><description>&lt;P&gt;The next rev. of the DTM has been released.&amp;nbsp; See the official announcement &lt;A class="" href="http://www.microsoft.com/whdc/whql/resources/news/WHQLNews_040407.htm" mce_href="http://www.microsoft.com/whdc/whql/resources/news/WHQLNews_040407.htm"&gt;here&lt;/A&gt;.&amp;nbsp; The most significant change to this release is the creation of a new product, the Windows Logo Kit (WLK).&amp;nbsp; Over the last several months we're been breaking the components of the Windows Driver Kit (WDK) necessary for developing drivers apart from the pieces necessary to certify drivers, DTM, logo tests and related docs.&amp;nbsp; The development components will ship as the WDK.&amp;nbsp; They need to sim-ship with the OS.&amp;nbsp; The WLK needs to stay closely sync'd with the logo program which is now on an annual cycle, refreshing each June.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;Also in this release, you'll see a lot of work to improve the stability and reliability of both the DTM and the tests.&amp;nbsp; In our &lt;A class="" href="http://blogs.msdn.com/craigrow/archive/2007/01/15/please-complete-the-dtm-survey.aspx" mce_href="http://blogs.msdn.com/craigrow/archive/2007/01/15/please-complete-the-dtm-survey.aspx"&gt;recent survey&lt;/A&gt; you told us that improving stability and reliability was the highest impact item we could deliver.&amp;nbsp; This is the first step in addressing that ask.&amp;nbsp; One of the other top items was diagnose-ability.&amp;nbsp; The WLK has a new feature which enables our support saff to add troubleshooting information in the field.&amp;nbsp; We do this via the errata mechanism.&amp;nbsp; The errata filters are looking for failures we know to be false and automatically flipping those to be passes for you.&amp;nbsp; In the new release these filters will also look for &lt;EM&gt;ture&lt;/EM&gt; failures then populate the logs with additional information to assist you in troublehsooting those failures.&amp;nbsp; The best part is, we can push out new troubleshooting information at any time via errata.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;Finally, the 1.0.a release has previews of the new tests that will be required when the logo program refreshes in June of this year.&amp;nbsp; You may not want to upgrade your production environment to 1.0.a as the 1.0.b release will include the final version of these new tests and you'll be required to use it for submission in the future.&amp;nbsp; However, you should definitely start using 1.0.a in some form to get a preview of the new tests.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2033608" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>Please complete the DTM survey</title><link>http://blogs.msdn.com/craigrow/archive/2007/01/15/please-complete-the-dtm-survey.aspx</link><pubDate>Mon, 15 Jan 2007 20:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1472109</guid><dc:creator>craigrow</dc:creator><slash:comments>4</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/1472109.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=1472109</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=1472109</wfw:comment><description>&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face=Calibri size=3&gt;We have posted a short 10 question DTM survey on Connect.&amp;nbsp; Please take a few minutes this week to help us ensure we’re prioritizing features as you would like by completing the survey this week.&lt;/FONT&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;FONT face=Calibri size=3&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/o:p&gt;&lt;/P&gt;
&lt;P class=MsoNormal style="MARGIN: 0in 0in 0pt"&gt;&lt;FONT face=Calibri size=3&gt;Survey is here: &lt;/FONT&gt;&lt;A href="https://connect.microsoft.com/Survey/Survey.aspx?SurveyID=3399&amp;amp;SiteID=148"&gt;&lt;FONT face=Calibri size=3&gt;https://connect.microsoft.com/Survey/Survey.aspx?SurveyID=3399&amp;amp;SiteID=148&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P mce_keep="true"&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1472109" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>Backup you DTM database</title><link>http://blogs.msdn.com/craigrow/archive/2006/09/15/756254.aspx</link><pubDate>Fri, 15 Sep 2006 20:41:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:756254</guid><dc:creator>craigrow</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/756254.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=756254</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=756254</wfw:comment><description>One of the most consistent things I've heard from both our internal and external partners since WinHEC is the need for more and better DTM documentation.&amp;nbsp; What we can get into the product is pretty much locked down at this point.&amp;nbsp; However, that won't stop us.&amp;nbsp; We have a number of mechanisms for getting critical documentation out.&amp;nbsp; &lt;A href="http://www.microsoft.com/whdc/DevTools/WDK/DTM/DB_opts.mspx"&gt;This &lt;/A&gt;is an example, describing DTM database maintenance procedures.&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=756254" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>WHQL Log Viewer available</title><link>http://blogs.msdn.com/craigrow/archive/2006/08/14/700262.aspx</link><pubDate>Tue, 15 Aug 2006 01:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:700262</guid><dc:creator>craigrow</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/700262.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=700262</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=700262</wfw:comment><description>The first DTM Power Toy is available for &lt;A href="http://www.microsoft.com/whdc/whql/WHQLdwn.mspx"&gt;download&lt;/A&gt;.&amp;nbsp; This tool opens the packages you create to submit your drivers to WHQL letting you browse through the results and logs.&amp;nbsp; Send feedback on the tool to &lt;A href="mailto:whqldt@microsoft.com"&gt;whqldt@microsoft.com&lt;/A&gt;.&amp;nbsp; If things go the way I hope this will be only the first of many&amp;nbsp;DTM Power Toys.&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=700262" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category><category domain="http://blogs.msdn.com/craigrow/archive/tags/Other+stuff/default.aspx">Other stuff</category></item><item><title>It's official, WinHEC 2007 in the Big Easy</title><link>http://blogs.msdn.com/craigrow/archive/2006/08/10/694511.aspx</link><pubDate>Thu, 10 Aug 2006 19:27:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:694511</guid><dc:creator>craigrow</dc:creator><slash:comments>5</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/694511.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=694511</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=694511</wfw:comment><description>&lt;A href="http://www.microsoft.com/whdc/winhec/default.mspx"&gt;This &lt;/A&gt;announcement has been made quietly.&amp;nbsp; I guess my &lt;FONT face="Times New Roman"&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;Campaign &lt;/SPAN&gt;for anything bug Seattle can be retired now.&lt;/FONT&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=694511" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category><category domain="http://blogs.msdn.com/craigrow/archive/tags/Other+stuff/default.aspx">Other stuff</category></item><item><title>DTMSupp to continue</title><link>http://blogs.msdn.com/craigrow/archive/2006/07/19/670045.aspx</link><pubDate>Wed, 19 Jul 2006 22:22:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:670045</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/670045.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=670045</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=670045</wfw:comment><description>&lt;P&gt;When I wrote this article I expected to see a lot of complaints about moving all support to a public forum.&amp;nbsp; I had hoped to use those complaints to argue for keeping the alias.&amp;nbsp; The good news is I didn't need that support.&amp;nbsp; The &lt;A href="mailto:DTMSupp@microsoft.com"&gt;DTMSupp@microsoft.com&lt;/A&gt; alias will continue to be available for support issues indefinitely.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=670045" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>DTM Support moving to newsgroup model</title><link>http://blogs.msdn.com/craigrow/archive/2006/06/26/647498.aspx</link><pubDate>Mon, 26 Jun 2006 19:02:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:647498</guid><dc:creator>craigrow</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/647498.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=647498</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=647498</wfw:comment><description>&lt;P&gt;DTM support is moving to a newsgroup model which should make the increasing volumes easier to manage.&amp;nbsp; From our support team...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;DTM now has a newsgroup:&lt;BR&gt;microsoft.public.windows.hardware_and_drivers.logotesting.dtm&lt;/P&gt;
&lt;P&gt;Please start telling DTM customers about this newsgroup.&amp;nbsp; We (DTM Support) will be monitoring the newsgroup to ensure timely response to customer posts.&amp;nbsp; I’ve posted a couple of FAQ posts to get started...We will start transitioning over to this newsgroup as the primary source of support for DTM (instead of &lt;A href="mailto:dtmsupp@microsoft.com"&gt;dtmsupp@microsoft.com&lt;/A&gt;).&amp;nbsp; We expect to decommission the &lt;A href="mailto:dtmsupp@microsoft.com"&gt;dtmsupp@microsoft.com&lt;/A&gt; alias at RC1.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=647498" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>Hardware and driver developer blog list</title><link>http://blogs.msdn.com/craigrow/archive/2006/06/20/636527.aspx</link><pubDate>Wed, 21 Jun 2006 07:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:636527</guid><dc:creator>craigrow</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/636527.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=636527</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=636527</wfw:comment><description>I have no idea how long &lt;A href="http://www.microsoft.com/whdc/resources/blogs.mspx"&gt;this list &lt;/A&gt;has been available.&amp;nbsp; If you're looking for Windows driver and hardware blogs this is the place to start.&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=636527" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>DTM help docs posted for download</title><link>http://blogs.msdn.com/craigrow/archive/2006/06/20/640825.aspx</link><pubDate>Wed, 21 Jun 2006 05:52:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:640825</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/640825.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=640825</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=640825</wfw:comment><description>The current &lt;A href=" http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/dtm.chm"&gt;DTM CHM&lt;/A&gt; has been posted for download.&amp;nbsp; This is the same documentation you get in the DTM Studio today and is the best source of information on how to setup systems for and run the logo tests.&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=640825" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>WinHEC slides</title><link>http://blogs.msdn.com/craigrow/archive/2006/06/19/636521.aspx</link><pubDate>Tue, 20 Jun 2006 07:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:636521</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/636521.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=636521</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=636521</wfw:comment><description>&lt;P&gt;The WDK Intro slide deck from WinHEC has been posted &lt;A href="http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/DEV041_WH06.ppt"&gt;here&lt;/A&gt;.&amp;nbsp; It is a nice overview of the tools in the kit with an extensive list of pointers to additional documentation.&amp;nbsp;&amp;nbsp; This is a good starting point for someone new to the kit.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://news.com.com/Microsoft+bug-checking+tools+promise+fewer+crashes/2100-1002_3-6077604.html?tag=nefd.top"&gt;Here &lt;/A&gt;is a related cnet article that came from WinHEC.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=636521" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>DTMSupp and WDKSupp</title><link>http://blogs.msdn.com/craigrow/archive/2006/06/18/636498.aspx</link><pubDate>Mon, 19 Jun 2006 06:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:636498</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/636498.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=636498</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=636498</wfw:comment><description>&lt;P&gt;Steve made &lt;A href="http://kernelmustard.com/2006/06/05/ddk-feedback-changes/"&gt;mention &lt;/A&gt;of the LDKFB alias going away.&amp;nbsp; I'm glad to hear he's had a good experience with the DDKSupp alias.&amp;nbsp; I can tell you that the people on the WDKSupp alias have the same level of commitment and real access to the people on the product team.&amp;nbsp; In fact, we've implemented a twice monthly review of top support issues lead by the WDKSupp team and attended by the key people on the product team.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;For WDK users the transition to WDKSupp is a big step in the right direction.&amp;nbsp; It means that, for the first time, people attempting to do logo testing have full-time support professionals at their disposal.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;Also, because the LDKFB alias is gone doesn't mean we're not interested in product feedback.&amp;nbsp; Please feel free to use &lt;A href="mailto:craigrow@microsoft.com"&gt;me &lt;/A&gt;for that.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=636498" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>High Definition Audio for the Digital Home</title><link>http://blogs.msdn.com/craigrow/archive/2006/05/24/606201.aspx</link><pubDate>Wed, 24 May 2006 20:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:606201</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/606201.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=606201</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=606201</wfw:comment><description>&lt;P&gt;I was just handed an advance copy of&lt;A href="http://www.intel.com/intelpress/sum_haud.htm"&gt; this book &lt;/A&gt;by the authors after my presentation at &lt;A href="http://www.microsoft.com/winhec"&gt;WinHEC &lt;/A&gt;this morning.&amp;nbsp; Chapter 11 has a few paragraphs describing, and recommending, the Windows Driver Kit and Driver Test Manager.&amp;nbsp; I think they did&amp;nbsp;a nice job of providing a concise description and making the case for using the WDK and DTM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;David, Wayne, thanks for the book!&amp;nbsp; I'm just trying to figure out how to display pp. 388-9 in the office so everyone can see it.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=606201" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>New code signing whitepaper</title><link>http://blogs.msdn.com/craigrow/archive/2006/05/23/605000.aspx</link><pubDate>Tue, 23 May 2006 20:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:605000</guid><dc:creator>craigrow</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/605000.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=605000</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=605000</wfw:comment><description>I expect kernel mode code signing will be a hot topic at WinHEC and I expect a lot of good information will start to be delivered as well.&amp;nbsp; For starters, a new whitepaper has been posted.&amp;nbsp; It's the best discussion that I've seen yet on code signing tools and practices.&amp;nbsp; Check it out &lt;A href="http://www.microsoft.com/whdc/winlogo/drvsign/best_practices.mspx"&gt;here&lt;/A&gt;.&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=605000" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item><item><title>DTM Screencasts: Just in time for Beta 2</title><link>http://blogs.msdn.com/craigrow/archive/2006/05/22/604131.aspx</link><pubDate>Tue, 23 May 2006 00:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:604131</guid><dc:creator>craigrow</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/craigrow/comments/604131.aspx</comments><wfw:commentRss>http://blogs.msdn.com/craigrow/commentrss.aspx?PostID=604131</wfw:commentRss><wfw:comment>http://blogs.msdn.com/craigrow/rsscomments.aspx?PostID=604131</wfw:comment><description>&lt;P&gt;When you get your Beta 2 build of the DTM you'll have a new resource.&amp;nbsp; Below are links to the first series of DTM screencasts.&amp;nbsp; Each is a 15-minute, or so, tutorial on how to do a specific task within the DTM.&amp;nbsp; Please let me know what other topics you'd like to see.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/Installing-DTM-Controller_Training.exe"&gt;DTM Controller install&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/DTM-Studio-Installation_Training.exe"&gt;DTM Studio install&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/DTM-Client-installation_Training.exe"&gt;DTM Client install&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/Using-DTM-studio_Training.exe"&gt;Using DTM Studio tutorial&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/Preparing-Testing-for-Vista-Systems-Logo_Training.exe"&gt;System logo demo&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=604131" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/craigrow/archive/tags/Windows+Driver+Kit/default.aspx">Windows Driver Kit</category></item></channel></rss>