|
|
| This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
From the Editor
In support of the Beta 2 releases of Microsoft Windows Vista and Windows Server Longhorn, the Windows development teams are providing a host of new information to help system manufacturers, hardware engineers, and driver developers understand how to implement new hardware and driver support for upcoming releases of Microsoft Windows. Here are three examples:
Brightness control in WDDM -- supporting ambient light sensors: In Windows Vista, brightness controls are implemented in the Windows-supplied monitor driver, which uses a Windows Management Instrumentation (WMI) interface to allow applications to interact with the brightness level. Manufacturers can use the brightness control APIs to expose the control of brightness to the end user through value-add software, hotkeys, power policy settings, or legacy IOCTLs. The Windows Graphics Platform team has published a paper that provides implementation guidelines--and the revision posted in June includes new guidelines for ambient light sensors, which allow brightness levels to automatically adapt to lighting conditions.
Network Explorer extensibility: Network Explorer in Windows Vista helps users to discover and use all network resources. The Windows Client Networking team provides this paper to explain how Network Explorer discovers a network device, displays device-specific information, and launches a device-specific application. The updated version published in June includes new sample code for both Web Services for Devices and UPnP solutions.
There's much more coming -- expect to find a host of new information on the WHDC Web site this summer, filled with details you can use from the Windows teams!
- Annie Pearson
for the WHDC Web team
WHDC After Dark:
| • |
End-of-Term Finals: Not currently part of mandated federal testing. And, unfortunately, recognizing the meta-ness of green-on-black screen doesn't get you a single point. I scored 24.45759%, which isn't great...but there were whole categories I was prepared to be tested on that never made the cut, plus I didn't earn points for "Know what this is, but chose not to get sucked into it" answers.
|
| • |
|
|
Windows Logo Program and Code Signing Updates
|
|
Cross-certificates for signing kernel-mode binary files for Windows Vista are now available on the WHDC Web site for these Certificate Authorities: Baltimore CyberTrust Root, Equifax Secure Certificate Authority, GTE CyberTrust Global Root, GlobalSign Root CA, GeoTrust Global CA, and VeriSign Class 3 Public Primary Certification Authority. For background information, see Driver Signing Requirements for Windows
|
|
|
The release of the Windows Logo Program Suite 3.0, Revision 1.0 does not include the final requirements for Windows Server Longhorn. Microsoft is continuing to work with hardware manufacturers on definitions of existing requirements in relation to servers. Additional new driver requirements will also be defined for Windows Server Longhorn. The review-and-modification process to modify requirements and release new requirements is ongoing until the release of the Revision 1.0 version of the requirements for Windows Server Longhorn.
|
|
|
The Windows Logo Program Suite 3.0 has been updated to include the following corrections and changes.
|
Server Processor changes:
SYSFUND-0008: Requirement changed to "If implemented." Title changed to "If processor(s) in a server system support performance states, the server system provides mechanisms to make these states available to Windows."
Imaging and Graphics changes:
IMAGING-0033: Typo in API referenced in this requirement. All references to InitializaPrintMonitor2 changed to InitializePrintMonitor2.
GRAPHICS-0008: This requirement was removed from the revision 1.0 device document, but it was not removed from the summary spreadsheet.
GRAPHICS-0019: Title changed to "Multi-headed display adapter or chipset functions as expected with additional restrictions."
Connectivity and Storage changes:
CONNECT-0071: Details of the physical length of the USB Transfer Cable have been changed. The sentence "Minimum of 6 feet (2 meters) in length" has been replaced with the following: "For Basic Logo a USB Transfer Cable must be a minimum of 5 feet in length. For Premium Logo a USB Transfer Cable must be a minimum of 8 feet in length."
STORAGE-0008, STORAGE-0009: Effective date changed to June 1, 2007.
Audio-related changes:
SYSFUND-0047: Effective date changed to June 1, 2008.
SYSFUND-0121: Updated Table B (Point #4) to clarify UAA-compliant solution such as USB Audio or HD Audio.
SYSFUND-0118, SYSFUND-0127, AUDIO-0006: Corrected frequency range for analog headphone out jack: magnitude response to 100 Hz, 20 kHz and Interchannel phase delay value.
AUDIO-0018, AUDIO-0019: Added link for guidelines.
AUDIO-0025: Corrected frequency range for analog headphone out jack: magnitude response to 100 Hz, 20 kHz.
AUDIO-0049: Updated design and implementation notes.
Windows Rally News
|
|
Microsoft Windows Rally is a collection of technologies that are designed to improve the way that network-connected devices work. To provide guidelines for use of related technologies, Microsoft hosts a quarterly partner summit to discuss Windows Rally technologies. The next event is July 18-19, 2006, in Redmond. This event provides the opportunity to find out more about these technologies and programs, to help you develop products that interoperate with Windows Vista and deliver a first-class customer experience with network devices. For information about the event and to engage with the Windows Rally team at Microsoft, please send e-mail to rally@microsoft.com.
|
Tools and Kits
|
|
The UMPC Display Emulator application enables you to test your application's layout and screen behavior as it appears on a UMPC. Use the UMPC Display Emulator to confirm that your program is legible and accessible, and provides a great user experience when running on a UMPC.
|
|
|
This toolkit and additional application compatibility resources are provided to help reduce the time, cost, and complexity of addressing application compatibility with Windows Vista.
Also, don't forget to review the Driver Compatibility for Windows Vista white paper.
|
|
|
This Beta release of Microsoft WinFX Runtime Components enables developers to continue experimenting with early builds of Windows Presentation Foundation, Windows Communication Foundation, and Windows Workflow Foundation.
|
|
