|
|
| This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
From the Editor
Getting Ready for Windows Vista Compatibility Testing for PCI Express: The Microsoft Windows Vista operating system introduces native support for PCI Express (PCIe), including support for features such as Message Signaled Interrupts (MSI), Express Card hot plug, and native wake signaling. Here's some news I just received from the Windows Base team about PCIe testing with Windows Vista.
With the upcoming release of Windows Vista, now is the time for manufacturers to ensure that their PCI Express-capable systems and add-in cards are compatible with support for PCIe and the specific features in Windows Vista. We want to encourage system and device manufacturers to submit their systems or add-in cards to Microsoft's test labs for inclusion in regular compatibility and interoperability testing of Windows Vista.
What to Do? Submit Your PCIe Add-In Cards to Microsoft's PCI Test Labs. Microsoft invites hardware vendors designing ExpressCard or PCIe add-in cards to take advantage of this opportunity to test and validate their hardware running on Windows Vista systems and to work with Microsoft developers and testers to understand the changes in Windows Vista. By submitting your PCIe add-in cards to Microsoft's PCI test labs, you can help ensure that your hardware is ready for the Windows Vista launch. Microsoft is looking for additional test coverage in the following areas:
| • |
MSI- and MSI-X -capable devices and device drivers
|
| • |
ExpressCard hot plug
|
| • |
Wake-capable PCIe add-in cards
|
| • |
Active State Power Management (ASPM), particularly for devices configured to use the L1 ASPM link power state
|
By providing your PCI Express devices and drivers to Microsoft, you broaden your interoperability testing to ensure compatibility with other systems and components. Testing on Windows Vista in conjunction with the PCI team in the Windows Division will allow you to identify and fix problems now, before your products enter the market, thus saving your company valuable time and resources.
Please note that any testing done in the Windows Labs will be for functional test and validation only and will not substitute for a submission to WHQL for Windows Logo Program testing.
To make arrangements to submit your PCIe devices and drivers to Microsoft for testing or for questions about PCI Express support, send e-mail to: pciesup@microsoft.com- Annie Pearson
for the WHDC Web team
WHDC After Dark:
| • |
Theban Mapping Project: Caution--before you click this link, know that it includes panoramic videos of the interiors of every tomb in the Valley of Kings, zoom-in aerial photos of maps of the Necropolis (you can see dimples in the sand), and links to a host of research, maps, videos, cool graphics, and Egyptology. So you've been warned that you'll lose most of the morning once you click this link.
|
| • |
|
|
"Critical Updates" on WHDC Web
We publish previews and early drafts at WinHEC every year. Especially as we prepare to release Windows Vista, the development teams are revising papers and specifications with new information, deeper examples, and clarifications requested by other developers. Here are some important updates for you to download and review.
This paper provides an exhaustive review of code-signing technologies and Windows operating systems together with a thorough presentation of the best practices for code signing, focusing on code-signing issues for Windows Vista and Windows Server codename "Longhorn." Important new information in this paper includes:
| • |
"Code Signing during Software Development," which discusses how to handle test signing.
|
| • |
"Code-Signing Service Example Topologies," which outlines several ways to manage a code-signing environment.
|
| • |
The appendices, which include explicit examples of various signing operations.
|
How to Install Windows Drivers with Software Applications The samples and guidelines in this paper have been updated with this important information: In a HardwareId INF, each Plug and Play hardware ID in the HardwareId directives must be enclosed in quotes. Only one Plug and Play hardware ID can be specified per HardwareId directive. To specify multiple hardware IDs, use multiple HardwareId directives, one per line.
Hardware Design for Windows Vista
Adrian Marinescu on Channel 9: Diving into the Windows Vista Heap
Adrian is lead developer on the Windows Kernel team, focusing on the Heap Manager and associated technologies. The Heap Manager plays a big role in shaping system performance and security. Adrian explains how the heap has been improved in Windows Vista and why it will help make Windows Vista both more performant and secure.
Windows Logo Program Update
|
