Microsoft Hardware Newsletter
May 24, 2010
This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
Windows Summit 2010 Begins Tomorrow, May 25!
Windows Summit 2010 is for software and hardware developers, designers, engineers, and testers, who build or want to build hardware and software solutions on the Windows 7 and Internet Explorer (IE) platforms. From the convenience of your computer, this virtual event gives you access to content, tools, resources, and information about building great products on Windows 7 and Internet Explorer, including information about the Windows Logo Program - from how to certify your product to what's new in Windows Logo Kit (WLK) 1.5.
The event kicks off tomorrow, May 25, with two opening presentations and continues with the release of Device track content later in the day. System track content will be available starting June 2, and Software track content goes live on June 16. You must register to access this special event content.
Windows Summit 2010 Opening Talks
The Windows Summit 2010 virtual event begins tomorrow, May 25, with an opening talk by Michael Angiulo, General Manager of Windows Planning and PC Ecosystem Teams. Michael is responsible for the product planning input that drives the Windows vision process as well as various partner engagement programs such as WinHEC.
Shortly following Michael Angiulo's event-opening talk, Mark Relph, Senior Director of the Windows Developer and PC Ecosystem Team, leads off the Device track. Mark is responsible for building a rich ecosystem of hardware and software partners for Windows. This includes supporting world-class compatibility and showcasing the innovations from the ecosystem of Windows partners.
The System track begins June 2 and features Brad Brooks, Corporate Vice President for Windows Consumer Marketing and Product Management. Brad leads the consumer business for Windows client and oversees efforts to connect with consumers. In Brad's prior role as general manager of product marketing for the Windows Business Group, he led the global consumer and business marketing efforts.
Dean Hachamovitch, General Manager of the Internet Explorer Team, starts the Software track on June 16. Dean is responsible for the design, development, and release of Internet Explorer, the Microsoft RSS platform, and future versions of our web browser, as well as security and customer response for the currently supported versions of IE.
Specialized Content Tracks for Devices, Systems, and Software Experts
Windows Summit 2010 content will be available 24x7, released on a rolling schedule so you can select the tracks you want to watch. You will have the opportunity to ask questions and the experts' answers will be posted to the site on a regular basis, viewable by everyone.
Each track launches with a high-profile opening speaker. Related track content goes live after the opening talk. Below you can find the speakers and a sampling of sessions.
May 25 - Device track, led by Mark Relph , Senior Director, Windows Developer and PC Ecosystem Team:
June 2 - System track, led by Brad Brooks , Corporate Vice President, Windows Consumer Marketing and Product Management:
June 16 - Software track, led by Dean Hachamovitch , General Manager, Internet Explorer Team:
News for Windows Hardware and Driver Developers
Debugging Tools for Windows Included as Component Download in Windows SDK 7.1
On May 21, the Windows Software Development Kit (SDK) 7.1 released with a fully componentized download of the Debugging Tools for Windows included as part of the SDK installer.
Download Debugging Tools for Windows 18.104.22.1683 via Windows SDK 7.1: http://go.microsoft.com/fwlink/?LinkID=191420
When you reach the Installation Options dialog box in the Windows SDK setup wizard, make sure that only Debugging Tools for Windows is selected, and then click Next.
Note: You don't need the full .NET Framework 4 in order to download and install Debugging Tools for Windows.
Note also: Disc Space Requirements and Download Size in the Windows SDK setup wizard reflect the size of the entire installation package (MSI) and do not reflect the size of the Debugging Tools for Windows, which is considerably less.
Recently Published on WHDC
Getting Started with the Windows Driver Developer Environment
Getting started with Microsoft Windows-based device drivers can be difficult, even for experienced developers. This paper, written by Don Burn, Microsoft MVP, Windows Driver Kit, presents an overview of the debugging and testing tools that developers use to create a device driver for Windows operating systems. In particular, the paper examines ways to find and fix bugs early in development, to help you produce a high-quality device driver.
Don shares his experience and insights about the hardware and software you need for driver development, how to get started with the Windows Driver Kit (WDK) build environments and Build utility, and tips, techniques, and tools for all phases of development.
What's new: This paper has been updated with changes to the tools, build environment, and best practices from the Windows Server 2003 Service Pack 1 WDK to the WDK version 7.1. Techniques to obtain the best results with the Windows Driver Framework and the new testing capabilities of the WDK are emphasized.
Windows Hardware Error Architecture Generic Error Source
This paper provides information about the Windows Hardware Error Architecture (WHEA) for Windows operating systems. It provides guidelines for server platform vendors to properly implement a generic error source. This information applies for Windows Server 2008 R2.
Windows Hardware Error Architecture Predictive Failure Analysis
This paper provides information about the predictive failure analysis (PFA) that Windows Hardware Error Architecture (WHEA) performs for Windows operating systems. It provides guidelines for system administrators to understand and manage this feature. This information applies for Windows Server 2008 R2 and Windows 7.
What's New in Blogs for Hardware and Driver Developers
"Arbitration and Translation" by Jake Oshins in Doron Holan's "A Hole in My Head" Blog
Arbitration and Translation, Part 1
A while back Jake Oshins answered a question on NTDEV about bus arbitration and afterwards I asked him if he could write a couple of posts about it for the blog. Here is part 1.
History Lesson: In the history of computing, most machines weren't PCs. PCs, and the related "industry standard" server platforms, may constitute a huge portion of the computers that have been sold in the last couple of decades, but even during that time, there have been countless machines, both big and small, which weren't PCs. Windows, at least those variants which are derived from Windows NT, (which include Windows XP and everything since,) was originally targeted at non-PC machines, specifically those with a MIPS processor and a custom motherboard which was designed by in-house at Microsoft. In the fifteen years that followed that machine, NT ran on a whole pile of other machines, many with different processor architectures.
Arbitration and Translation, Part 2
Building on yesterday's post, I'm going to try to explain how Windows copes with machines with strange resource translations. I'll use two examples in this post, one related to I/O port resources and one related to interrupts.
Arbitration and Translation, Part 3
What is an Arbiter? In the NT PnP subsystem, an arbiter is an interface that a bus driver can expose which is able to intelligently assign PnP resources of a single specific type (memory, I/O ports, DMA channels, interrupts, bus numbers) to its children. In general, an arbiter cannot assign resources that it has not claimed from its parent.
Windows Logo Program News
Windows Logo Kit 1.5 QFE 001 Is Now Available on Connect
QFE 001 for Windows Logo Kit (WLK) 1.5 is now available for download on the WLK Connect site (https://connect.microsoft.com/site/sitehome.aspx?SiteID=668). WLK 1.5 QFE 001 updates USB device fundamentals tests to run USB 3 devices and also updates the USB Controller Power State test.
A number of USB device fundamentals tests are failing on USB 3 devices. Most of these failures are caused by a failing setup task, which is preventing the test from running. The fixes to get the USB device fundamentals tests to run on USB 3 devices are:
This QFE is needed only for USB 3 device submissions, USB controller submissions, and system submissions that have USB controllers. You can download the QFE from the WLK Connect website.
Network-Connected Printers Must Implement Windows Rally
This is a reminder that effective June 1, 2010, IMAGING-0048 will require that network-connected printers, scanners, and multi-function printers (MFPs) implement the Windows Rally technologies as described by CONNECT-0098, CONNECT-0099, CONNECT-0100, and IMAGING-0004. For more information, please refer to the referenced requirements, which are available on the Windows Quality Online Services (Winqual) website (http://winqual.microsoft.com/), and the Windows 7 Logo Program for Printers FAQ (http://www.microsoft.com/whdc/winlogo/Logoprinterfaq.mspx).
Clarifications to STORAGE-0026 for Optical Drives
When STORAGE-0026 takes effect on June 1, 2010, read-only optical drives will no longer be a device category in the Windows Logo Program. After June 1, systems with read-only optical drives must qualify such devices through the Unclassified category.
In response to partner feedback, we have made some clarifications in STORAGE-0026. These clarifications do not change the substance of the requirement and consequently there are no changes to the Windows Logo Kit (WLK) as a result of the clarifications. The new clarifications are described in detail below. You can read the full text of STORAGE-0026 on Logopoint (https://sysdev.microsoft.com).
Description of Changes
The following changes were made in the table of Microsoft requirements:
The following changes were made to the footnotes:
The following changes were made to the design and implementation notes:
To subscribe to the Windows Logo Program Newsletter, click here: http://www.microsoft.com/whdc/newsreq.mspx
Tools and Links for Developers
Windows Driver Developer Kits, Tools, and ProgramsM
Developing Drivers with the Windows Driver Foundation