WHDC
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.
This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.

From the Editor
Device Finish-Install Actions on Windows Vista. Device installation on the Microsoft Windows Vista operating system has been enhanced to enable a class installer, class co-installer, or device co-installer to run one or more processes in an administrator user context.
This capability, called finish-install actions, extends the notion of finish-install wizard pages that you might already be providing in your driver package for released versions of Windows.
If you install value-add applications for your device, you can use finish-install actions to run an application installation program (with its own user interface) as the final step of device installation on a system running Windows Vista.
Finish-install actions run after all other installation operations for a device (including finish-install wizard pages) are finished and the device has been started. On a new system, finish-install actions run the first time that the Windows operating system starts after Windows Setup is finished.
This capability, called finish-install actions, extends the notion of finish-install wizard pages that you might already be providing in your driver package for released versions of Windows.
Finish-install actions cannot be used to apply any critical settings that must be present for the device to work, since the device is started before the finish-install actions run.
Finish-install actions run only in the context of a user with administrator privileges. On Windows Vista, User Account Protection (UAP, formerly called least-privileged user account or LUA) enables users to run at low privilege most of the time and elevate privilege only when necessary. If finish-install actions are triggered when a nonadministrator user is logged on to the system, Windows Vista prompts the user for consent and any credentials that are required to run the finish-install actions.
Read Device Finish-Install Actions on Windows Vista for more details about how you can take advantage of finish-install actions in your driver package.
—Annie Pearson
for the WHDC team

Windows Vista and Windows Server "Longhorn" Previews
Windows Vista introduces the XPS print path as part of a new print architecture that is designed to improve support for printers and document processing. An important part of these advancements is the modular, filter-based XPSDrv print driver that provides a more flexible print path than is possible with a print driver based on Windows graphics device interface (GDI).

A new XPS white paper on WHDC provides information for hardware and software vendors who publish printers or print drivers to help plan their strategy for migrating their existing code to the new print architecture. Developers who are writing new print drivers can use this paper to understand the details of the filter pipeline of an XPSDrv print driver.

The features and benefits of the XPS print path are described in XPS and Color Printing Enhancements in Windows Vista.
Next year some laptops and Tablet PCs will begin to incorporate a new feature that is supported under Windows Vista: auxiliary displays, which let you view certain information without having to open up the computer and wait for it to resume. Some of the auxiliary display devices will be integrated into laptops and Tablet PCs; others will appear on peripheral devices. Windows SideShow (available in Windows Vista Beta 1) is a new platform that developers can use to write gadgets that extend their applications to a range of display devices. Examples of potential SideShow-compatible devices include:
A display embedded in a laptop lid, which caches data for use offline and can be used to check appointments and e-mail messages.
A display in a keyboard, which can be used to read messages while playing a game in full-screen mode, listening to music, or watching a video.
A mobile phone, which can be used to remotely control applications, such as advancing slides in Microsoft PowerPoint from across a room.
See more about the hardware design issues for auxiliary displays in this WinHEC 2005 presentation.
Download a preliminary draft of the Microsoft Windows Vista User Experience Guidelines (or “UX Guide” for short). These guidelines describe what’s new in Windows Vista, design principles, and guidelines for controls, text, windows, and aesthetics.

Windows Vista and Windows Server Longhorn Favorites from PDC
Many driver writers and hardware engineers were hard at work and missed the Professional Developers Conference (PDC) in September. We picked a couple of the "best-of-the-best" topics of interest for hardware industry professionals:
System Internals and Your Application: Windows Vista and Server Longhorn [in PowerPoint]. Insights from Windows Base and Windows Mobile developers about upcoming changes, deep inside the operating system.
Developing Power-Aware Applications for Windows Vista [in PowerPoint]. Details from the Windows Base team about the new power management capabilities in Windows Vista, to enhance and extend power management usage models, improve the reliability of sleep transitions, and enable maximum energy savings.

Insights from Microsoft Experts
We’ve been collecting tips, implementation guidelines, chalk-talks, and lectures by people from the Windows Division at Microsoft. Some specific "how to" details are provided here in advance of future versions of the Windows Driver Kit (WDK).
The goals of the Security Development Life Cycle (SDL), now embraced by Microsoft, are twofold: to reduce the number of security-related design and coding defects, and to reduce the severity of any defects that remain. This follows our oft-cited motto, "Secure by Design, Secure by Default, Secure in Deployment and Communication" (also known as SD3+C). SDL focuses mainly on the first two elements of this motto. Secure by Design means getting the design and code secure from the outset, and Secure by Default is a recognition that you never will.

Michael Howard’s new article on MSDN looks at each major phase and outlines what you can do within your own organization to implement SDL. This article outlines how to apply the SDL to your own software development processes and explains how you can take some of the lessons that we have learned at Microsoft when implementing SDL. SDL adds security-specific checks and measures to any existing software development process.
One thing that is incredibly easy to do with virtual machines is kernel debugging. You can do this by either connecting two virtual machines to the same named pipe (creating a virtual null-modem cable as it were) or by debugging a virtual machine directly over a named pipe from the host operating system. On Ben’s recent blog, he describes the steps for doing this. Because it’s a brand new blog entry, it hasn’t yet gotten as many views as his most popular article: Running Windows Vista Beta 1 under Virtual PC/Virtual Server.

WHDC After Dark
At PDC 2005, we had a great time meeting the folks from Phidgets USA and playing with their programmable toys. And you’ve noticed in WHDC After Dark that we’re fans of the fun that people have playing with gadgets--like the creative and heroic efforts of home-inventors to manage heat dissipation on their overclocked PCs. We’ve discovered some local efforts that are easy for you to innovate on:
Partying with Bluetooth on Channel 9. Anil Dhawan, a program manager with the Windows Mobile product group, built a media box that he controls with a Windows Mobile Smartphone over Bluetooth wireless. On Channel 9, he shows the architecture and demonstrates the device. On his blog, Anil has a series of articles on how to build such a box by using an embedded Windows operating system and Bluetooth wireless technology.
Look at Me: Coding4Fun Plays with WIA and a Webcam. Windows Image Acquisition (WIA) is an API that is included in Windows and attempts to unify the acquisition of images from devices such as scanners and cameras. The WIA Automation Layer features a simple COM API for Visual Basic 6 and ASP developers. MVP Scott Hanselman of Corillian Corporation has some fun on Coding4Fun with programming a Webcam by using Visual Studio .NET 2005.

Microsoft Hardware Newsletter
Edition for

October 26, 2005
In This Issue:
Windows Vista and Windows Server "Longhorn" Previews
Insights from Microsoft Experts
WHDC After Dark
Events
IEE Mobility Conference 2005
2nd International Conference on Mobile Technology, Applications, and Systems
November 15-17, 2005
Majestic Hotel, Guangzhou, China
WinHEC 2006
May 23-26, 2006
Washington State Convention and Trade Center
Seattle, WA
Registration begins February 6, 2006
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
© 2005 Microsoft Corporation  Terms of Use | Trademarks | Privacy Statement
Microsoft