Technical features new to Windows Vista

Windows Vista (formerly codenamed Windows "Longhorn") has many significant new features compared with previous Microsoft Windows versions, covering most aspects of the operating system.

In addition to the new user interface, security capabilities, and developer technologies, several major components of the core operating system were redesigned, most notably the audio, print, display, and networking subsystems; while the results of this work will be visible to software developers, end-users will only see what appear to be evolutionary changes in the user interface.

As part of the redesign of the networking architecture, IPv6 has been incorporated into the operating system, and a number of performance improvements have been introduced, such as TCP window scaling. Prior versions of Windows typically needed third-party wireless networking software to work properly; this is no longer the case with Windows Vista, as it includes comprehensive wireless networking support.

For graphics, Windows Vista introduces a new as well as major revisions to Direct3D. The new display driver model facilitates the new Desktop Window Manager, which provides the tearing-free desktop and special effects that are the cornerstones of the Windows Aero graphical user interface. The new display driver model is also able to offload rudimentary tasks to the GPU, allow users to install drivers without requiring a system reboot, and seamlessly recover from rare driver errors due to illegal application behavior.

At the core of the operating system, many improvements have been made to the memory manager, process scheduler, heap manager, and I/O scheduler. A Kernel Transaction Manager has been implemented that can be used by data persistence services to enable atomic transactions. The service is being used to give applications the ability to work with the file system and registry using atomic transaction operations.

Audio

Windows Vista features a completely re-written audio stack designed to provide low-latency 32-bit floating point audio, higher-quality digital signal processing, bit-for-bit sample level accuracy, up to 144 dB of dynamic range and new audio APIs created by a team including Steve Ball and Larry Osterman.[1][2] The new audio stack runs at user level, thus increasing stability. The Windows Vista audio engine is designed to run faster than the Windows XP audio engine, and has tighter requirements on audio buffer position accuracy. Also, the new Universal Audio Architecture (UAA) model has been introduced, replacing WDM audio, which allows compliant audio hardware to automatically work under Windows without needing device drivers from the audio hardware vendor.

There are three major APIs in the Windows Vista audio architecture:

Audio stack architecture

Applications communicate with the audio driver through Sessions, and these Sessions are programmed through the Windows Audio Session API (WASAPI). In general, WASAPI operates in two modes. In exclusive mode (also called DMA mode), unmixed audio streams are rendered directly to the audio adapter and no other application's audio will play and signal processing has no effect. Exclusive mode is useful for applications that demand the least amount of intermediate processing of the audio data or those that want to output compressed audio data such as Dolby Digital, DTS or WMA Pro over S/PDIF. WASAPI exclusive mode is similar to kernel streaming in function, but no kernel mode programming is required. In shared mode, audio streams are rendered by the application and optionally applied per-stream audio effects known as Local Effects (LFX) (such as per-session volume control). Then the streams are mixed by the global audio engine, where a set of global audio effects (GFX) may be applied. Finally, they're rendered on the audio device.

The higher level APIs such as the Waveform-Audio Interface (waveXxx functions) and DirectSound use shared mode, which results in pre-mixed PCM audio that is sent to the driver in a single format (in terms of sample rate, bit depth and channel count). This format is configurable by the end user through Control Panel.

After passing through WASAPI, all host-based audio processing, including custom audio processing, can take place (sample rate conversion, mixing, effects). Host-based processing modules are referred to as Audio Processing Objects, or APOs. All these components operate in user mode. The only portion of this architecture that runs in kernel mode is the audio driver (which contains the Port Class driver, the vendor Miniport driver and the vendor HAL).

The Windows Kernel Mixer (KMixer) is completely gone. There is no direct path from DirectSound to the audio drivers; DirectSound and MME are emulated as Session instances. Since the whole point of DirectSound acceleration is to allow hardware to process unmixed audio content, DirectSound cannot be accelerated in this audio model, and DirectSound3D is not supported at all, which also breaks EAX extensions.[4] APIs such as ASIO and OpenAL are not affected.

Audio performance

Windows Vista also includes a new Multimedia Class Scheduler Service (MMCSS) that allows multimedia applications to register their time-critical processing to run at an elevated thread priority, thus ensuring prioritized access to CPU resources for time-sensitive DSP processing and mixing tasks.

For audio professionals, a new WaveRT port driver has been introduced that strives to achieve real-time performance by using the multimedia class scheduler and supports audio applications that reduce the latency of audio streams. Consequently, user mode applications can completely govern streams of audio without any code execution in the kernel during runtime. WaveRT allows the user mode application direct access to the internal audio hardware buffers and sample position counters (data in the memory that is mapped to the audio hardware DMA engine). It allows applications to poll the current position in the DMA memory window that the hardware is accessing. WaveRT also supports the notion of a hardware generated clock notification event, similar to the ASIO API, so that applications need not poll for current position if they don't want to.

All the existing audio APIs have been re-plumbed and emulated to use these APIs internally, all audio goes through these three APIs, so that most applications "just work".

Issues

A fault in the MME WaveIn/WaveOut emulation was introduced in Windows Vista: if sample rate conversion is needed, audible noise is sometimes introduced, such as when playing audio in a web browser that uses these APIs. This is because the internal resampler, which is no longer configurable, defaults to linear interpolation, which was the lowest-quality conversion mode that could be set in previous versions of Windows. The resampler can be set to a high-quality mode via a hotfix for Windows 7 and Windows Server 2008 R2 only.[5][6]

Audio signal processing

New digital signal processing functionalities such as Room Correction, Bass Management, Loudness Equalization and Speaker Fill have been introduced. Speaker Fill mixes 2-channel content to use all available speakers in a manner similar to Creative's CMSS. Bass Management can be used to redirect the subwoofer signal to the main speakers. If a channel is missing, a feature called Channel Phantoming allows the best use of the speakers that are there, by redirecting the sound of the missing channels through these speakers. Whether you have a multi-channel or stereo sound system in your home theater or living room, Windows Vista also includes the ability to calibrate your speakers for your room. By placing a microphone where you plan to sit and then running a wizard that measures the room response, Windows Vista can automatically set the levels, delay and frequency balance for each channel accordingly for this position. For PCs equipped with stereo headphones, Vista adds the ability to have surround sound using a new feature called Headphone Virtualization, which uses technology based upon a Head-related transfer function.[7]

Windows Vista also includes the ability to use custom host-based digital signal processing effects as part of the audio device manufacturer-supplied driver's value-added features. These effects are packaged as user-mode System Effect Audio Processing Objects (sAPOs).[8] These sAPOs are also reusable by third-party software.

Audio devices support

Windows Vista builds on the Universal Audio Architecture, a new class driver definition that aims to reduce the need for third-party drivers, and to increase the overall stability and reliability of audio in Windows.

Other audio enhancements

Microsoft has also included a new high quality voice capture DirectX Media Object (DMO) as part of DirectShow that allows voice capture applications such as instant messengers and speech recognition applications to apply Acoustic Echo Cancellation and microphone array processing to speech signals.[16]

Speech recognition

Windows Speech Recognition tutorial

Windows Vista is the first Windows operating system to include fully integrated support for speech recognition. Under Windows 2000 and XP, Speech Recognition was installed with Office 2003, or was included in Windows XP Tablet PC Edition.

Windows Speech Recognition allows the user to control his/her machine through voice commands, and enables dictation into many applications. The application has a fairly high recognition accuracy and provides a set of commands that assists in dictation. A brief speech-driven tutorial is included to help familiarize a user with speech recognition commands. Training could also be completed to improve the accuracy of speech recognition.

Windows Vista includes speech recognition for 8 languages at release time: English (U.S. and British), Spanish, German, French, Japanese and Chinese (traditional and simplified). Support for additional languages is planned for post-release.

Speech recognition in Vista utilizes version 5.3 of the Microsoft Speech API[17] (SAPI) and version 8 of the Speech Recognizer.

Speech synthesis

Speech synthesis was first introduced in Windows with Windows 2000, but it has been significantly enhanced for Windows Vista (code name Mulan). The old voice, Microsoft Sam, has been replaced with two new, more natural sounding voices of generally greater intelligibility: Anna and Lili, the latter of which is capable of speaking Chinese. The screen-reader Narrator which uses these voices has also been updated. Microsoft Agent and other text to speech applications now use the newer SAPI 5 voices.[18]

Print

Windows Vista includes a redesigned print architecture,[19] built around Windows Presentation Foundation. It provides high-fidelity color printing through improved use of color management, removes limitations of the current GDI-based print subsystem, enhances support for printing advanced effects such as gradients, transparencies, etc., and for color laser printers through the use of XML Paper Specification (XPS).

The print subsystem in Windows Vista implements the new XPS print path as well as the legacy GDI print path for legacy support. Windows Vista transparently makes use of the XPS print path for those printers that support it, otherwise using the GDI print path. On documents with intensive graphics, XPS printers are expected to produce much greater quality prints than GDI printers.

In a networked environment with a print server running Windows Vista, documents will be rendered on the client machine,[20] rather than on the server, using a feature known as Client Side Rendering. The rendered intermediate form will just be transferred to the server to be printed without additional processing, making print servers more scalable by offloading rendering computation to clients.

XPS print path

The XPS Print Path introduced in Windows Vista supports high quality 16-bit color printing.[21] The XPS print path uses XML Paper Specification (XPS) as the print spooler file format, that serves as the page description language (PDL) for printers. The XPS spooler format is the intended replacement for the Enhanced Metafile (EMF) format which is the print spooler format in the Graphics Device Interface (GDI) print path.[22] XPS is an XML-based (more specifically XAML-based) color-managed device and resolution independent vector-based paged document format which encapsulates an exact representation of the actual printed output. XPS documents are packed in a ZIP container along with text, fonts, raster images, 2D vector graphics and DRM information. For printers supporting XPS, this eliminates an intermediate conversion to a printer-specific language, increasing the reliability and fidelity of the printed output. Microsoft claims that major printer vendors are planning to release printers with built-in XPS support and that this will provide better fidelity to the original document.[23]

At the core of the XPS print path is XPSDrv, the XPS-based printer driver which includes the filter pipeline. It contains a set of filters which are print processing modules and an XML-based configuration file to describe how the filters are loaded. Filters receive the spool file data as input, perform document processing, rendering and PDL post-processing, and then output PDL data for the printer to consume. Filters can perform a single function such as watermarking a page or doing color transformations or they can perform several print processing functions on specific document parts individually or collectively and then convert the spool file to the page description language supported by the printer.

Windows Vista also provides improved color support through the Windows Color System for higher color precision and dynamic range. It also supports CMYK colorspace and multiple ink systems for higher print fidelity. The print subsystem also has support for named colors simplifying color definition for images transmitted to printer supporting those colors.

The XPS print path can automatically calibrate color profile settings with those being used by the display subsystem. Conversely, XPS print drivers can express the configurable capabilities of the printer, by virtue of the XPS PrintCapabilities class, to enable more fine-grained control of print settings, tuned to the individual printing device.

Applications which use the Windows Presentation Foundation for the display elements can directly print to the XPS print path without the need for image or colorspace conversion. The XPS format used in the spool file, represents advanced graphics effects such as 3D images, glow effects, and gradients as Windows Presentation Foundation primitives, which are processed by the printer drivers without rasterization, preventing rendering artifacts and reducing computational load. When the legacy GDI Print Path is used, the XPS spool file is used for processing before it is converted to a GDI image to minimize the processing done at raster level.

Print schemas

Print schemas provide an XML-based format for expressing and organizing a large set of properties that describe either a job format or print capabilities in a hierarchically structured manner. Print schemas are intended to address the problems associated with internal communication between the components of the print subsystem, and external communication between the print subsystem and applications.

Networking

The Network and Sharing Center

Windows Vista contains a new networking stack, which brings large improvements in all areas of network-related functionality.[24] It includes a native implementation of IPv6, as well as complete overhaul of IPv4. IPv6 is now supported by all networking components, services, and the user interface. In IPv6 mode, Windows Vista can use the Link Local Multicast Name Resolution (LLMNR) protocol to resolve names of local hosts on a network which does not have a DNS server running. The new TCP/IP stack uses a new method to store configuration settings that enables more dynamic control and does not require a computer restart after settings are changed. The new stack is also based on a strong host model and features an infrastructure to enable more modular components that can be dynamically inserted and removed.

The user interface for configuring, troubleshooting and working with network connections has changed significantly from prior versions of Windows as well. Users can make use of the new "Network Center" to see the status of their network connections, and to access every aspect of configuration. The network can be browsed using Network Explorer, which replaces Windows XP's "My Network Places". Network Explorer items can be a shared device such as a scanner, or a file share. Network Location Awareness uniquely identifies each network and exposes the network's attributes and connectivity type. Windows Vista graphically presents how different devices are connected over a network in the Network Map view, using the LLTD protocol. In addition, the Network Map uses LLTD to determine connectivity information and media type (wired or wireless). Any device can implement LLTD to appear on the Network Map with an icon representing the device, allowing users one-click access to the device's user interface. When LLTD is invoked, it provides metadata about the device that contains static or state information, such as the MAC address, IPv4/IPv6 address, signal strength etc.

Support for wireless networks is built into the network stack itself, and does not emulate wired connections, as was the case with previous versions of Windows. This allows implementation of wireless-specific features such as larger frame sizes and optimized error recovery procedures. Windows Vista uses various techniques like Receive Window Auto-scaling, Explicit Congestion Notification, TCP Chimney offload and Compound TCP to improve networking performance. Quality of Service (QoS) policies can be used to prioritize network traffic, with traffic shaping available to all applications, even those that do not explicitly use QoS APIs. Windows Vista includes in-built support for peer-to-peer networks and SMB 2.0. For improved network security, Windows Vista supports for 256-bit and 384-bit Diffie-Hellman (DH) algorithms, as well as for 128-bit, 192-bit and 256-bit Advanced Encryption Standard (AES) is included in the network stack itself, while integrating IPsec with Windows Firewall.

Kernel and core OS changes

Boot process

Windows Vista introduces an overhaul of the previous Windows NT operating system loader architecture NTLDR. Used by versions of Windows NT since its inception with Windows NT 3.1, NTLDR has been completely replaced with a new architecture designed to address modern firmware technologies such as the Unified Extensible Firmware Interface.[35][36] The new architecture introduces a firmware-independent data store and is backward compatible with previous versions of the Windows operating system.[36]

Memory management

File systems

Drivers

Windows Vista introduces an improved driver model, Windows Driver Foundation which is an opt-in framework to replace the older Windows Driver Model. It includes:

Processor Power Management

Windows Vista includes the following changes and enhancements in processor power management:[53]

System performance

Programmability

.NET Framework 3.0

Main article: .NET Framework

Windows Vista is the first client version of Windows to ship with the .NET Framework. Specifically, it includes .NET Framework 2.0 and .NET Framework 3.0 (previously known as WinFX) but not version 1.0 or 1.1. The .NET Framework is a set of managed code APIs that is slated to succeed Win32. The Win32 API is also present in Windows Vista, but does not give direct access to all the new functionality introduced with the .NET Framework. In addition, .NET Framework is intended to give programmers easier access to the functionality present in Windows itself.

.NET Framework 3.0 includes APIs such as ADO.NET, ASP.NET, Windows Forms, among others, and adds four core frameworks to the .NET Framework:

WPF

Windows Presentation Foundation (codenamed Avalon) is the overhaul of the graphical subsystem in Windows and the flagship resolution independent API for 2D and 3D graphics, raster and vector graphics (XAML), fixed and adaptive documents (XPS), advanced typography, animation (XAML), data binding, audio and video in Windows Vista. WPF enables richer control, design, and development of the visual aspects of Windows programs. Based on DirectX, it renders all graphics using Direct3D. Routing the graphics through Direct3D allows Windows to offload graphics tasks to the GPU, reducing the workload on the computer's CPU. This capability is used by the Desktop Window Manager to make the desktop, all windows and all other shell elements into 3D surfaces. WPF applications can be deployed on the desktop or hosted in a web browser (XBAP).

The 3D capabilities in WPF are limited compared to what's available in Direct3D. However, WPF provides tighter integration with other features like user interface (UI), documents, and media. This makes it possible to have 3D UI, 3D documents, and 3D media. A set of built-in controls is provided as part of WPF, containing items such as button, menu, and list box controls. WPF provides the ability to perform control composition, where a control can contain any other control or layout. WPF also has a built-in set of data services to enable application developers to bind data to the controls. Images are supported using the Windows Imaging Component. For media, WPF supports any audio and video formats which Windows Media Player can play. In addition, WPF supports time-based animations, in contrast to the frame-based approach. This delinks the speed of the animation from how slow or fast the system is performing. Text is anti-aliased and rendered using ClearType.

WPF uses Extensible Application Markup Language (XAML), which is a variant of XML, intended for use in developing user interfaces. Using XAML to develop user interfaces also allows for separation of model and view. In XAML, every element maps onto a class in the underlying API, and the attributes are set as properties on the instantiated classes. All elements of WPF may also be coded in a .NET language such as C#. The XAML code is ultimately compiled into a managed assembly in the same way all .NET languages are, which means that the use of XAML for development does not incur a performance cost.

WCF

Windows Communication Foundation (codenamed Indigo) is a new communication subsystem to enable applications, in one machine or across multiple machines connected by a network, to communicate. WCF programming model unifies Web Services, .NET Remoting, Distributed Transactions, and Message Queues into a single Service-oriented architecture model for distributed computing, where a server exposes a service via an interface, defined using XML, to which clients connect. WCF runs in a sandbox and provides the enhanced security model all .NET applications provide.

WCF is capable of using SOAP for communication between two processes, thereby making WCF based applications interoperable with any other process that communicates via SOAP. When a WCF process communicates with a non-WCF process, XML based encoding is used for the SOAP messages but when it communicates with another WCF process, the SOAP messages are encoded in an optimized binary format, to optimize the communication. Both the encodings conform to the data structure of the SOAP format, called Infoset.

Windows Vista also incorporates Microsoft Message Queuing 4.0 (MSMQ)[61] that supports subqueues, poison messages (messages which continually fail to be processed correctly by the receiver), and transactional receives of messages from a remote queue.

WF

Windows Workflow Foundation is a Microsoft technology for defining, executing and managing workflows. This technology is part of .NET Framework 3.0 and therefore targeted primarily for the Windows Vista operating system. The Windows Workflow Foundation runtime components provide common facilities for running and managing the workflows and can be hosted in any CLR application domain.

Workflows comprise 'activities'. Developers can write their own domain-specific activities and then use them in workflows. Windows Workflow Foundation also provides a set of general-purpose 'activities' that cover several control flow constructs. It also includes a visual workflow designer. The workflow designer can be used within Visual Studio 2005, including integration with the Visual Studio project system and debugger.

Windows CardSpace

Main article: Windows CardSpace

Windows CardSpace (codenamed InfoCard), a part of .NET Framework 3.0, is an implementation of Identity Metasystem, which centralizes acquiring, usage and management of digital identity. A digital identity is represented as logical Security Tokens, that each consist of one or more Claims, which provide information about different aspects of the identity, such as name, address etc.

Any identity system centers around three entities — the User who is to be identified, an Identity Provider who provides identifying information regarding the User, and Relying Party who uses the identity to authenticate the user. An Identity Provider may be a service like Active Directory, or even the user who provides an authentication password, or biometric authentication data.

A Relying Party issues a request to an application for an identity, by means of a Policy that states what Claims it needs and what will be the physical representation of the security token. The application then passes on the request to Windows CardSpace, which then contacts a suitable Identity Provider and retrieves the Identity. It then provides the application with the Identity along with information on how to use it.

Windows CardSpace also keeps a track of all Identities used, and represents them as visually identifiable virtual cards, accessible to the user from a centralized location. Whenever an application requests any identity, Windows CardSpace informs the user about which identity is being used and needs confirmation before it provides the requestor with the identity.

Windows CardSpace presents an API that allows any application to use Windows CardSpace to handle authentication tasks. Similarly, the API allows Identity Providers to hook up with Windows CardSpace. To any Relying Party, it appears as a service which provides authentication credentials.

Other .NET Framework APIs

Media Foundation

Main article: Media Foundation

Media Foundation is a set of COM-based APIs to handle audio and video playback that provides DirectX Video Acceleration 2.0 and better resilience to CPU, I/O, and memory stress for glitch-free low-latency playback of audio and video. It also enables high color spaces through the multimedia processing pipeline. DirectShow and Windows Media SDK will be gradually deprecated in future versions.

Search

Main article: Windows Search

The Windows Vista Instant Search index can also be accessed programmatically using both managed as well as native code.[62] Native code connects to the index catalog by using a Data Source Object retrieved from Windows Vista shell's Indexing Service OLE DB provider. Managed code use the MSIDXS ADO.NET provider with the index catalog name. A catalog on a remote machine can also be specified using a UNC path. The criteria for the search is specified using a SQL-like syntax.

The default catalog is called SystemIndex and it stores all the properties of indexed items with a predefined naming pattern. For example, the name and location of documents in the system is exposed as a table with the column names System. ItemName and System. ItemURL respectively.[63] An SQL query can directly refer these tables and index catalogues and use the MSIDXS provider to run queries against them. The search index can also be used via OLE DB, using the CollatorDSO provider.[64] However, OLE DB provider is read-only, supporting only SELECT and GROUP ON SQL statements.

The Windows Search API can also be used to convert a search query written using Advanced Query Syntax (or Natural Query Syntax, the natural language version of AQS) to SQL queries. It exposes a method GenerateSQLFromUserQuery method of the ISearchQueryHelper interface.[65] Searches can also be performed using the search-ms: protocol, which is a pseudo protocol that lets searches be exposed as an URI. It contains all the operators and search terms specified in AQS. It can refer to saved search folders as well. When such a URI is activated, Windows Search, which is registered as a handler for the protocol, parses the URI to extract the parameters and perform the search.

Networking

Winsock Kernel (WSK) is a new transport-independent kernel-mode Network Programming Interface (NPI) for that provides TDI client developers with a sockets-like programming model similar to those supported in user-mode Winsock. While most of the same sockets programming concepts exist as in user-mode Winsock such as socket, creation, bind, connect, accept, send and receive, Winsock Kernel is a completely new programming interface with unique characteristics such as asynchronous I/O that uses IRPs and event callbacks to enhance performance. TDI is supported in Windows Vista for backward compatibility.

Windows Vista includes a specialized QoS API called qWave (Quality Windows Audio/Video Experience),[66] which is a pre-configured Quality of Service module for time dependent multimedia data, such as audio or video streams. qWave uses different packet priority schemes for real-time flows (such as multimedia packets) and best-effort flows (such as file downloads or e-mails) to ensure that real time data gets as little delays as possible, while providing a high quality channel for other data packets.

Windows Filtering Platform allows external applications to access and hook into the packet processing pipeline of the networking subsystem.

Cryptography

Windows Vista features an update to the Microsoft Crypto API known as Cryptography API: Next Generation (CNG). CNG is an extensible, user mode and kernel mode API that includes support for Elliptic curve cryptography and a number of newer algorithms that are part of the National Security Agency (NSA) Suite B. It also integrates with the smart card subsystem by including a Base CSP module which encapsulates the smart card API so that developers do not have to write complex CSPs.

Other features and changes

See also

Notes and references

  1. "Steve Ball - Learning about Audio in Windows Vista". Channel 9. Microsoft. September 15, 2005. Archived from the original on 2006-02-13. Retrieved 2006-04-29.
  2. "Windows Vista Audio Stack and API". Channel 9. Microsoft. December 13, 2005. Retrieved 2006-04-29.
  3. MSDN - A Wave Port Driver for Real-Time Audio Streaming
  4. Creative Technology - Support - Audio in Windows Vista
  5. "Policy for Sample Rate Conversion of Audio Streams (Windows Drivers)". Dev Center - Hardware. Microsoft. Retrieved 2012-01-17.
  6. "Artifacts on Windows 7 due to sample rate conversion". Windows Desktop Development Forums discussion thread. Retrieved 2012-01-17.
  7. 1 2 3 Allchin, Jim (December 6, 2006). "Audio Improvements in Windows Vista". Windows Vista Team Blog. Microsoft. Archived from the original on December 9, 2006. Retrieved November 3, 2015.
  8. Custom Audio Effects in Windows Vista
  9. See the USB Midi Devices 1.0 standard document for more information on MIDI Elements.
  10. See section 3.3 of the USB Audio Devices 1.0 standard document for more information on endpoint types.
  11. Scoble, Robert (January 4, 2006). "Robert Fripp - Behind the scenes at Windows Vista recording session". Channel 9. Microsoft. Retrieved April 25, 2015.
  12. Allchin, Jim (November 9, 2006). "The Sounds of Windows Vista". Windows Vista Team Blog. Microsoft. Archived from the original on November 10, 2006. Retrieved April 25, 2015.
  13. Oiaga, Marius (December 7, 2006). "The Windows Vista Volume Mixer". Softpedia. Retrieved April 25, 2015.
  14. "Audio Innovations in Windows Vista". TechNet. Microsoft. August 24, 2006. Retrieved April 25, 2015.
  15. Microsoft (April 21, 2014). "Microphone Array Support in Windows" (DOC). Retrieved April 25, 2015.
  16. "Eliminating Acoustic Echo". TechNet. Microsoft. Retrieved April 25, 2015.
  17. Windows Vista, SAPI Talking Windows.
  18. Vista Speech Demo from the Professional Developers Conference 2005 (link requires Internet Explorer)
  19. Printing Enhancements in Windows Vista
  20. Client Side Rendering
  21. 16 bits and more printing on Windows
  22. XPS and Color Printing Enhancements in Microsoft Windows Vista
  23. Tim Sneath (November 17, 2005). "Inside Windows Vista Printing". Channel 9. Microsoft. Retrieved 2006-05-12.
  24. "New Networking Features in Windows Server 2008 and Windows Vista". Microsoft TechNet. Microsoft. February 15, 2006. Retrieved 2006-04-29.
  25. "About Kernel Transaction Manager". MSDN. Microsoft.
  26. Inside the Windows Vista Kernel: Part 1, Microsoft Technet
  27. Inside the Windows Vista Kernel: Part I
  28. Protected Processes in Windows Vista
  29. Windows NT 6.x Kernel Changes. (Word document)
  30. Plug and Play: Architecture and Driver Support
  31. See Boot Configuration Data Editor Frequently Asked Questions for details on BCD.
  32. The space bar is the new F8 when it comes to Vista and Server 2008 boot options
  33. Microsoft. "Restart Manager". MSDN Library. Microsoft.
  34. Shutdown Changes for Windows Vista and Handling OS shutdown in Windows Vista
  35. Ritz, Andrew (2004). "EFI and Windows 'Longhorn'". Microsoft. Archived from the original (PPT) on June 9, 2004. Retrieved April 18, 2015.
  36. 1 2 Microsoft (February 4, 2008). "Boot Configuration Data in Windows Vista" (DOCX). Retrieved April 18, 2015.
  37. Low-fragmentation Heap: Heap functions - MSDN
  38. 1 2 3 4 Mangefeste, Tony; Walp, David (2006). "Optical Platform: Windows Vista and Beyond". Microsoft. Archived from the original (PPT) on June 4, 2011. Retrieved December 21, 2015.
  39. Microsoft. "Image Mastering API - What's New". MSDN. Retrieved December 21, 2015.
  40. IMAPI 2.0 is a DLL, not a Windows service
  41. 1 2 Microsoft. "Description of the Image Mastering API v2.0 (IMAPIv2.0) update package in Windows Feature Pack for Storage 1.0". Support. Retrieved December 21, 2015.
  42. "Universal Disk FOrmat (UDF) Beta Chat Transcript (September 01, 2006)". MSDN Blogs. Microsoft. Retrieved December 21, 2015.
  43. Loveall, John (2006). "Windows Storage Directions: Windows Vista And Beyond". Microsoft. Archived from the original (PPT) on September 28, 2007. Retrieved December 21, 2015.
  44. "Self-healing NTFS in Windows Server 2008 and Windows Vista". TechNet. Microsoft. February 13, 2008. Retrieved December 21, 2015.
  45. Microsoft. "Chkdsk". TechNet. Retrieved December 21, 2015.
  46. Microsoft. "Microsoft support policy for 4K sector hard drives in Windows". Support. Retrieved December 21, 2015.
  47. Gan, Jabez (September 16, 2005). "NTFS Changes in Vista. Any changes?". MSBlogs. Retrieved December 21, 2015.
  48. Microsoft. "Notable Changes in Windows Vista Service Pack 1". TechNet. Retrieved December 21, 2015.
  49. CNET.com (2007). "Windows Vista Ultimate Review". Retrieved 2007-01-31.
  50. "Digital Signatures for Kernel Modules on x64-based Systems Running Windows Vista". WHDC. Microsoft. May 19, 2006. Archived from the original on 2006-04-12. Retrieved 2006-05-19.
  51. The staging and the installation of driver packages by using the PnP Utility (Pnputil.exe) in Windows Vista
  52. Microsoft (November 20, 2007). "Processor Power Management in Windows Vista and Windows Server 2008" (DOCX). Retrieved April 26, 2015.
  53. Tom Archer (April 14, 2006). "ReadyBoost - Using Your USB Key to Speed Up Windows Vista". Tom Archer's Blog. Microsoft. Retrieved 2006-05-21.
  54. Inside the Windows Vista kernel
  55. "Windows Vista: Performance". Microsoft. 2006. Retrieved 2006-04-30.
  56. Microsoft (May 11, 2006). "I/O Prioritization in Windows Vista". Driver Fundamentals. Windows Hardware Developer Central. Retrieved 2006-12-31.
  57. Aul, Gabriel (2006). "Windows Vista Performance Technologies" (PPT). Microsoft. Retrieved July 9, 2015.
  58. Russinovich, Mark. "Inside the Windows Vista Kernel: Part 1". TechNet. Microsoft. Retrieved July 15, 2015.
  59. Jim Allchin. "Offline Files". Retrieved 2007-06-14.
  60. "What's New in Message Queuing 4.0". Message Queuing (MSMQ). Microsoft Developer Network. Retrieved 2006-08-05.
  61. "Searching data". Retrieved 2007-03-17.
  62. Catherine Heller. "Windows Vista Search: Syntax Update". Retrieved 2007-06-23.
  63. "Querying the Index Programmatically". MSDN. Retrieved 2007-06-23.
  64. "ISearchQueryHelper::GenerateSQLFromUserQuery Method". Retrieved 2007-06-23.
  65. "Quality Windows Audio-Video Experience - qWave". Microsoft. Archived from the original on 2007-07-13. Retrieved 2007-10-09.
  66. "Extend The Global Reach Of Your Applications With Unicode 5.0". MSDN. Retrieved 2007-01-30.
  67. "What's New in Windows Vista — System Font (Segoe UI)". MSDN. Retrieved 2006-04-21.
  68. "Windows Vista - ClearType - Meiryo". PC Watch. August 29, 2005.
  69. Microsoft release regarding Network Projection
  70. http://windows.microsoft.com/en-us/windows/network-projectors-faq#1TC=windows-7
  71. Top Ten UI breakthroughs for WPF
  72. Kristan M. Kenney (June 5, 2006). "Guided Help in Windows Vista". digitalfive.
  73. Enabling Text Correction for Custom Ink Collectors
  74. "FRS and Sysvol Improvements". What's New in Group Policy in Windows Vista and Windows Server 2008. Microsoft TechNet. Retrieved 2006-08-04.

External links

This article is issued from Wikipedia - version of the Saturday, April 02, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.