Windows Logo Kit 1.5 Required Starting February 1, 2010 The Windows Logo Program would like to inform our partners that Windows Logo Kit (WLK) 1.5 will be a required kit for logo submissions effective February 1, 2010. Partners can choose to use either WLK 1.4 or WLK 1.5 for logo submissions until February 1, 2010. WLK 1.4 expires on February 1, 2010. Please note that we no longer provide hotfixes (QFEs) for WLK 1.4, effective with the release of WLK 1.5 on November 25, 2009. WLK 1.5 is available through the Microsoft Connect Web site (registration required): https://connect.microsoft.com/site/sitehome.aspx?SiteID=668. News for Windows Hardware and Driver Developers Debugging Tools for Windows Available Only in WDK and Windows SDK Starting with the current version (6.12.1.591), Debugging Tools for Windows is available only as part of the Windows Driver Kit (WDK). This version will also be made available in an upcoming release of the Windows Software Development Kit (SDK). To download the WDK and install Debugging Tools for Windows: 1. Download and install the WDK ( http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx). 2. Find the debugging tools link on the screen that appears and click to install the debuggers to a location of your choice. 3. After the installation is complete, you can find the debugger shortcuts by clicking Start, pointing to All Programs, and then pointing to Debugging Tools for Windows. Note: Windows Symbols Packages are not available in the WDK and are still available on WHDC ( http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx). Windows TestedApproved.com Is Launched At CES this year, www.testedapproved.com launched as the go-to site for customers to learn about the "Compatible with Windows 7" logo program. The site helps to educate customers on the value of the Windows logo program and links to the Windows 7 Compatibility Center, encouraging customers to discover products that have earned the Windows logo. The testedapproved.com site is just one way that customers are learning more about the value of the Windows 7 logo program. In addition, the Windows logo program continues to receive increased visibility as a featured component on a variety of consumer Web sites, including this sample page from shopper.com. To find out more about how your device or product can receive the "Compatible with Windows 7" logo, visit the Windows 7 logo program overview page on Windows Hardware Developer Central (WHDC) Web site: http://www.microsoft.com/whdc/winlogo/default.mspx. High Definition Audio Tool The High Definition Audio (HD Audio) tool is used to define and validate Pin Configuration Register definitions for audio designs that comply with the Intel High Definition Audio (HD Audio) specification ( http://www.intel.com/standards/hdaudio/). The tool works in combination with the HD Audio drivers that are included in Windows 7 and is available for both x86 and x64 product versions. Correct use of this tool is necessary to pass the Windows 7 Logo Program tests in the area of Universal Audio Architecture compliance. Plug and Play and Power Management in WDF Drivers The Windows Driver Foundation (WDF) implements a fully integrated model for Plug and Play and power management in both the user-mode driver framework (UMDF) and the kernel-mode driver framework (KMDF). The model provides intelligent defaults so that some drivers do not require any code to support simple Plug and Play or power management. To support more complex features, drivers implement event callbacks. This paper provides guidelines for implementing Plug and Play and power management support in UMDF and KMDF drivers. This paper has been updated and republished in order to add information about new UMDF features and update links and sample locations for Windows 7. ( http://www.microsoft.com/whdc/driver/wdf/WDF_pnpPower.mspx) What's New in Blogs for Hardware and Driver Developers "The Case of the Slow Logons" by Mark Russinovich in "Mark's Blog" Emails containing troubleshooting cases keep arriving in my inbox. I've received many cases that start with a seemingly unsolvable problem and end a few steps later with a solution or - often just as useful - a workaround. I've amassed several hundred such cases that I've captured in over 400 PowerPoint slides, giving me great material from which to draw for my blog and the Case of the Unexplained talk series I've delivered at a number of major industry conferences. I'm always looking for fresh cases, use of obscure tool features, and unique troubleshooting techniques, so please keep them coming. This time, I'm sharing a fascinating case that highlights two useful techniques: comparing Sysinternals Process Monitor logs from working and problematic systems, and using Sysinternals PsExec to capture activity during a logon. Read more: http://blogs.technet.com/markrussinovich/archive/2010/01/13/3305263.aspx New Things Happening with the WDK Get the Latest Release of the Windows Driver Kit Documentation By using this download, you can install the latest Microsoft Windows Driver Kit (WDK) documentation for Windows 7. The Windows Driver Kit documentation is normally updated on MSDN and WHDC in bimonthly intervals between major releases. Either location might contain newer content than the version you currently have installed on your computer. To check, compare the build date in the footer section of any topic in your installed documentation against the release date of the WDK documentation download on WHDC or the topic on MSDN. If the release date on WHDC is more recent, you should consider updating your locally installed documentation. WHDC: http://www.microsoft.com/whdc/DevTools/WDK/WDKdocs.mspx MSDN: http://msdn.microsoft.com/en-us/library/aa972908.aspx Windows Logo Program News New Process for Driver Update Acceptable (DUA) Submissions for Multiple-Function Devices Effective February 1, 2010, you can resubmit a passing CPK from a Windows Logo Kit (WLK) 1.5 test run along with updated INF files, and send the submission ID to logofb@microsoft.com. The logo program team will review and manually pass your submission. Single-function devices can continue to use the existing DUA process. |