Wednesday, January 20, 2010

Microsoft Hardware Newsletter for January 20, 2010

WHDC
Top Story

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).

Compatible with Windows 7 logo  
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.


New Blog from the Sensor and Location Platform Team

The Sensor and Location Platform team has started a new blog. The goal of this blog is to provide useful and timely information to the hardware development ecosystem on this new platform in Windows 7.

Read more: http://blogs.msdn.com/sensorslocation/archive/2009/12/08/Welcome-to-the-Sensor-and-Location-Platform-Team-Blog.aspx


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 Sensor and Location Platform Drill Down - Part 1 : The Sensor DDI" in the "Sensor and Location Platform Team Blog"

As we resume our blog in the new year, we begin by doing a series of what we call drill-down posts, where we look at a particular part of the Sensor & Location Platform and do a deep dive into its various components and piece through its technical aspects.

Read more: http://blogs.msdn.com/sensorslocation/archive/2010/01/12/the-sensor-and-location-platform-drill-down-part-1-the-sensor-ddi.aspx


"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


"Answering the question "What's wrong with my device?" Using USB Trace Messages" in the "Windows USB Core Team Blog"

This is Philip Ries posting again with more on the USB tracing that's new in Windows 7. In my last post I introduced the instrumentation in the USB stack. I gave instructions for taking USB ETW traces and opening them in Netmon. This time I'll go through an example scenario and trace, showing how to identify a USB issue.

Read more: http://blogs.msdn.com/usbcoreblog/archive/2009/12/21/answering-the-question-what-s-wrong-with-my-device-using-usb-etw.aspx


"Sensors and Windows" in the "Windows Portable Devices Team Blog"

Prior to the introduction of WPD, developers wrote a significant amount of code to integrate data from sensors into their Windows applications. But, with the release of WPD, it was possible to create a driver that handled communications between the operating system and the remote device. And, once the driver was written, a developer could write an application with a minimal code footprint-200 lines or less-to retrieve sensor data. For an example, refer to the downloadable whitepaper and code at: http://wpdtempsensor.codeplex.com/. (For an example WPD driver, refer to the WpdBasicHardwareDriver that ships in the Windows Driver Kit.)

Read more: http://blogs.msdn.com/wpdblog/archive/2009/12/17/sensors-and-windows.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

Windows 7 logo  
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.


Windows Logo Program Test Categories

The Windows Logo Program contains nearly 100 categories. This page lists all available logo categories and operating systems: http://www.microsoft.com/whdc/winlogo/categories.mspx.


Driver Test Manager Webcasts

You must use the Driver Test Manager (DTM) in order to qualify a device or system for a Windows logo. This set of Webcasts demonstrates how to install and use key components of the DTM.

- Driver Test Manager Client Installation. You use the Driver Test Manager (DTM) Client to test whether your product meets the requirements of the Windows Logo Program for hardware. This brief demonstration shows you how to install the DTM Client. (http://www.microsoft.com/whdc/media/WinLogo/Windows_Logo_Kit_-_Installing_the_DTM_Client.wvx)

- Driver Test Manager Controller Installation. To qualify a device or system for a Windows Logo, you must install the Driver Test Manager (DTM) Controller. This brief demonstration shows you how to install the DTM Controller. (http://www.microsoft.com/whdc/media/WinLogo/Windows_Logo_Kit_-_Installing_the_DTM_Controller.wvx)

- Driver Test Manager Log Viewer Tool. You use the Driver Test Manager (DTM) Log Viewer to triage logo program test failures. This brief demonstration shows you how to download and install the DTM Logo Viewer, view passed and failed tests, and open the associated test log files. (http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032420323&Culture=en-US%20)

- Driver Test Manager Studio Installation. You use the Driver Test Manager (DTM) Studio to create, edit, and manage test jobs. This brief demonstration shows you how to install the DTM Studio. (http://www.microsoft.com/whdc/media/WinLogo/Windows_Logo_Kit_-_Installing_DTM_Studio.wvx)


Microsoft Hardware Newsletter
Edition for

January 20, 2010
In This Issue:
Windows Logo Kit 1.5 Required Starting February 1, 2010
News for Windows Hardware and Driver Developers
What's New in Blogs for Hardware and Driver Developers
New Things Happening with the WDK
Windows Logo Program News
Tools and Links for Developers
Windows Driver Developer Kits, Tools, and Programs
Windows Driver Kit
Windows Logo Kit
WDK Documentation (monthly updates)
Windows Symbols (October 2009)
Windows Logo Program
Developing Drivers with the Windows Driver Foundation
Events
Microsoft Tech Ed North America 2010
June 7-10, 2010
New Orleans, Louisiana, USA

The Microsoft Hardware Newsletter provides manufacturers and developers the latest technical details for how to succeed with the Windows platform. Register now, if you're not already receiving the Microsoft Hardware Newsletter.

To cancel your subscription to this newsletter, reply to this message with the word UNSUBSCRIBE in the Subject line. You can also unsubscribe at the Microsoft.com Web site. You can manage all your Microsoft.com communication preferences at this site.

Legal Information.

This newsletter was sent by the Microsoft Corporation
1 Microsoft Way
Redmond, Washington, USA
98052
Sign up for other newsletters | Unsubscribe | Update your profile
© 2010 Microsoft Corporation Terms of Use | Trademarks | Privacy Statement
Microsoft

Your cOmment"s Here! Hover Your cUrsOr to leave a cOmment.


Subscribe to: Post Comments (Atom)