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
In Microsoft Windows XP, Windows Server 2003, and earlier versions of the Windows operating system, all services run in the same session as the first user who logs on to the console. This session is called Session 0. Running services and user applications together in Session 0 poses a security risk because services run at elevated privilege and therefore are targets for malicious agents looking for a means to elevate their own privilege level.
The Windows Vista operating system mitigates this security risk by isolating services in Session 0 and making Session 0 noninteractive. In Windows Vista, only system processes and services run in Session 0. The first user logs on to Session 1, and subsequent users log on to subsequent sessions. This means that services never run in the same session as users’ applications and are therefore protected from attacks that originate in application code.
What might be affected by this change? Possibly:
| • |
Any applications or drivers that are installed as services.
|
| • |
Any drivers that are loaded within operating system services.
|
| • |
Any processes running in Session 0 (such as printer drivers or UMDF drivers).
|
For example, if a device installer running in Session 0 creates a dialog box that requires user input to continue, the device installation never completes because the user does not see the dialog box. From the user's perspective, the device installer appears hung.
Other areas that might be affected include interprocess communication and assumptions about display resolution and the namespace that contains named objects.
What you should do in your drivers?
| • |
Use a client/server mechanism such as remote procedure call (RPC) or named pipes rather than window messages to communicate with applications.
|
| • |
Implement any user interface using WTSSendMessage or CreateProcessAsUser.
|
| • |
Query display properties in the user's session, not in Session 0.
|
| • |
Explicitly choose either the Local\ or Global\ namespace for any named objects.
|
| • |
Test the driver in Windows Vista to ensure that it runs properly. If that is not possible, test the driver in Windows XP with Fast User Switching enabled and multiple users logged on.
|
—Annie Pearson
for the WHDC team
WHDC After Dark:
|
Universal Audio Architecture
Increasing the quality and fidelity of the Windows audio experience requires contributions from all components in a Windows-based PC. The support provided through the Microsoft Universal Audio Architecture (UAA) initiative, in combination with PC audio device technologies, is key to delivering a simple yet compelling user experience with current and future versions of Windows.
The Microsoft audio class drivers that are supported by the UAA initiative, along with specific tools such as the Port Class helper library, enable lower cost driver development for internal, integrated, and external PC audio devices. By implementing specification-compliant PC audio technologies, and by following the UAA design guidelines, you can ensure that your device will meet the Windows Logo Program requirements while also ensuring that your customers have built-in driver support in future versions of Windows.
We’ve published a set of new and updated design and implementation guidelines for UAA that support High Definition Audio (HD Audio) in Windows operating systems, including the following papers.
Windows Logo Program Requirements
|
|
The Windows Vista logo program is based on specific Windows Vista technical requirements, including new device categories and driver models. For the first time since the introduction of the Windows Logo Program, the Windows Vista logo program has two tiers: a "standard" logo that delivers the promise of compatibility and a "premium" logo that delivers exciting new Microsoft Windows experiences.
We’ve published a set of frequently asked questions and supplemental information to help you understand marketing and implementation, plus specific issues for the hardware requirements and proposed requirements for Windows Server Longhorn.
|
|
|
You can download and review the draft now. Please provide feedback to Microsoft by October 19. Submit feedback and any questions by e-mail to hwlogo@microsoft.com.
|
Windows Vista and Windows Server Longhorn Advances for Systems and Devices
|
|
In future versions of the Windows operating systems, Microsoft plans to discontinue support for the Industry Standard Architecture (ISA) bus. Starting in the early 1990s, the PCI Local Bus architecture began to replace ISA. PCI Express is now becoming the new bus standard that offers faster performance and a more robust implementation than PCI.
Currently, ISA capability is supported in Microsoft Windows Vista, Windows Server 2003, Windows XP, Windows 2000, and Windows Me. Microsoft has not identified any customer dependency on this capability. If you are an IHV or OEM who has a business dependency on the ISA capability, please provide feedback to pciesup@microsoft.com.
|
|
|
Registry reflection in the 64-bit version of Windows 32-bit On Windows 64-bit (WOW64) copies specific registry keys and values between the 32-bit and 64-bit views of the registry to keep them synchronized, but conflicts can occur. Download this new paper to understand the latest mechanisms for controlling registry reflection in Windows Server 2003 with SP1, Windows Vista, and Windows Server Longhorn to prevent conflicts between 32-bit and 64-bit applications.
|
|
|
The Windows Vista operating system provides a new development platform for advanced color applications and devices called the Microsoft Windows Color System (WCS). WCS offers a strong foundation for ongoing innovation in color into the future. Other platform enhancements, such as the display and print infrastructure, will be delivered simultaneously. This combination will nurture a strong ecosystem in which all participants can innovate together. The WCS solution provides direct, short-term benefits as well as a path for end users toward the ultimate solution in color that "just works."
You can download a new white paper that introduces WCS. The information in this white paper is for independent software vendors (ISVs), independent hardware vendors (IHVs), developers, and decision-makers to help them understand how WCS can benefit their products and customers.
|
|
|
From the Windows Vista Developer Center: Understanding User Account Protection in Microsoft Windows Vista Beta 1 - Windows Security Access Control. By following these guidelines, developers will gain a more thorough understanding of UAP and how to develop applications in a more secure fashion.
|
Beta Downloads
|
|
Windows Server 2003 R2 release candidate software is available to download for evaluation in both x64 and x86 versions. Windows Server 2003 R2 RC0 software cannot be installed on anything other than software versions of Windows Server 2003 with Service Pack 1 (SP1). The Windows Server 2003 R2 release candidate software is available for evaluation for 180 days.
|
|
|
Windows Server Longhorn Beta 1 includes the core foundation and application programming interfaces (APIs) for server components. The goal of the beta 1 release is to gather feedback from original equipment manufacturers, independent hardware manufactures, system builders, independent software vendors, and developers who are participating in a private beta program.
|
|
|
Get the latest version of the WinFX Runtime Components and WinFX SDK Beta. MSDN subscribers can also download the Windows Vista beta releases from this site.
|
WinHEC 2006
|
|
Save this date and plan to join us in Seattle for WinHEC 2006!
WinHEC is the only Microsoft conference that focuses on designing hardware and drivers for computers that run Microsoft Windows. This annual industry event is a forum focused on technology roadmaps and trends, presenting in-depth technical content about the standards, Windows features, and Microsoft tools for advancing the Windows hardware platform. WinHEC is the best opportunity for industry professionals to partner with Microsoft in driving the future engineering and business directions of PC and device hardware, and to gain valuable information about future versions of Microsoft Windows operating systems.
|
Get Involved! Industry participation is the foundation of WinHEC:
| • |
Present a session
December 5, 2005 is the deadline for speaker presentation abstracts.
We are now accepting proposals for technical presentations to be considered for the conference program. This is your opportunity to join other industry leaders in sharing engineering and design innovations for the next generation of PCs, servers, and devices that run Windows.
|
| • |
Be a sponsor
Demonstrate your industry leadership by becoming a sponsor at the premier event for hardware developers, driver developers, and business planners who create Windows-based products!
|
| • |
Join the WinHEC Expo
The WinHEC Expo offers your company the opportunity to showcase its products to a broad, targeted audience of hardware developers and business decision makers. The most influential people in the industry attend WinHEC to learn about engineering and design innovations from companies like yours.
|
|
