|
|
| This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
From the Editor
As we've discussed in earlier newsletters, kernel-mode software must be digitally signed to be loaded on x64-based versions of Windows Vista and later versions of Microsoft Windows operating systems.
The Windows team has published a new paper-- Kernel-Mode Code Signing Walkthrough--that provides detailed information about how to use the code-signing tools to digitally sign kernel-mode software designed for Windows Vista. The paper addresses the following issues, where many developers have had questions:
| • |
Where to obtain code-signing tools
|
| • |
How to prepare systems to use code-signing tools to build, sign, and test kernel-mode software
|
| • |
How to use the tools to test and release-sign kernel-mode software, with detailed examples
|
| • |
How to troubleshoot common signing-related problems
|
| • |
How to verify the signature
|
| • |
How to install signed kernel-mode software
|
| • |
How to disable signature enforcement
|
The new kernel-mode code-signing policy applies to all kernel-mode software for x64-based systems that run Windows Vista. However, Microsoft encourages publishers to digitally sign all kernel-mode software, including device drivers for both 32-bit and 64-bit platforms. Although kernel-mode driver signatures are not required for 32-bit systems, Windows Vista verifies kernel-mode signatures on these systems as needed to support protected media content.
In addition, content protection policies for next-generation premium content might require signed kernel-mode software for certain configurations of x86 systems. For more information about support for protected media, see Code Signing for Protected Media Components in Windows Vista on the WHDC Web site. When you download and review the paper, you'll also find contact information for discussing your issues with the Windows team responsible for code signing tools and issues.
-- Annie Pearson
for the WHDC Web team
WHDC After Dark: Play the GROTRIAN Pianolina: It's summer. I think that music + physics = about the most taxing experience we should expect of ourselves.
|
Windows Logo Program Updates
Windows Logo Program 3.0 Update - Version 1.03
These Logo Program requirement clarifications and modifications can be reviewed in the revised release of the Windows Logo Program Suite 3.0, Revision 1.03, which will be available on the WHDC Web site later this week:
GRAPHICS-0034 - Clarification and reduction to list of entries that the Windows Display Driver Model (WDDM) driver must populate in the registry and INF
DISPLAY-0023 - Removed from Windows Logo Program
DISPLAY-0024; DISPLAY-0025 - Removed reference to enhanced auxiliary display
DISPLAY-0026 - Removed from Windows Logo Program
DISPLAY-0028 - Updated to reflect language in the Windows Driver Kit (WDK)
DISPLAY-0029 - Removed from Windows Logo Program
INPUT-0007 - Updated text to clarify expected behavior of IR receiver and transceiver
NETWORK-0046 - Text updated for clarification
SYSFUND-0090 - Updated in server document to match system document
IMAGING-0004; IMAGING-0010 - Relaxed to "if implemented" until June 1, 2007
NETWORK-0045 - Text clarified to allow secondary network adapter to be 10/100
STREAM-0010 - Updated text to clarify intent of requirement
STREAM-0014 - Updated title and text to be specific to TV tuner filters
STREAM-0023 - Updated text to note either UYVY or YUY2, and removed design note
Clarification on the Windows Logo Program Requirements for Vista--Final: In May 2006, we released the Windows Logo Program Requirements Version 3.0, Revision 1.0 suite of documents for Client, Server, and Devices. Based on feedback from partners and customers testing on Beta 2 of Windows Vista, we have subsequently released two updates to the requirements. The primary intent for these revisions is to keep the industry aware of changes to the requirements as soon as possible based on feedback from Beta 2. To date, the updates to the Windows Logo Program requirements have addressed the following:
| • |
Clarifications of the intent through additional information provided as a part of the requirement.
|
| • |
Relaxation of some or part of the requirements where appropriate, based on the feedback and where the relaxation does not materially impact the quality and customer experience scenarios in any significant manner.
|
| • |
Corrections of typographical errors.
|
| • |
Introduction of new requirements for future implementation (these are not effective for Windows Vista).
|
It is difficult to predict how many more such changes could occur before the release of Windows Vista, but please note the following:
| • |
In the recent updates, no new hardware requirements have been introduced that impact Windows Vista.
|
| • |
Partners who have planned their product designs based on Windows Logo Program Suite 3.0, Revision 1.0 should be able to continue with their plans because any updates only relaxed the requirements. Products designed for Windows Logo Program Suite 3.0, Revision 1.0 should meet the test criteria.
|
| • |
We do not anticipate any changes to the requirements that impact Windows Vista after Release Candidate 1 (RC1), at which time you should be able to begin making the submissions for logo.
|
If you have feedback or concerns, please contact the Windows Hardware Logo Program team at logofb@microsoft.com.
WDK Update
|
|
WDK EDW Build 5456 is now available for download at https://connect.microsoft.com/default.aspx. This build is the first release since Beta 2 was made available in May. Please use this build for your beta testing and for confirming your previously resolved bugs.
|
|
|
Based on requests from driver developers, the WDK team has provided a standalone version of the Help file for Driver Test Manager (DTM). This document provides preview information about using DTM to test your device driver or system.
|
|
