Content deleted Content added
not a proper noun |
Rescuing 50 sources and tagging 0 as dead.) #IABot (v2.0.8 |
||
Line 26:
| work=Channel 9
| publisher=Microsoft
| archive-date=2006-05-02
| archive-url=https://web.archive.org/web/20060502145621/http://channel9.msdn.com/ShowPost.aspx?PostID=145665
| url-status=live
}}</ref>
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 [[Windows Driver Model|WDM]] audio, which allows compliant audio hardware to automatically work under Windows without needing device drivers from the audio hardware vendor.
Line 31 ⟶ 34:
There are three major APIs in the Windows Vista audio architecture:
* Windows Audio Session API – Very low-level API for rendering audio, render/capture audio streams, adjust volume etc. This API also provides low latency for audio professionals through WaveRT (wave real-time) [[device driver|port driver]].<ref>
* Multimedia Device API – For enumerating and managing audio endpoints.
* Device Topology API – For discovering the internals of an audio card's topology.
Line 43 ⟶ 46:
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 [[Hardware Abstraction Layer|HAL]]).
The Windows Kernel Mixer ([[KMixer]]) is completely gone. There is no direct path from DirectSound to the audio drivers; DirectSound and [[MultiMedia Extensions|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 [[Environmental Audio Extensions|EAX extensions]].<ref name=creativeKB25937>
===Audio performance===
Line 55 ⟶ 58:
====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 [http://support.microsoft.com/kb/2653312 a hotfix] for Windows 7 and Windows Server 2008 R2 only.<ref>{{cite web|url=http://msdn.microsoft.com/en-us/library/windows/hardware/ff537758(v=vs.85).aspx|title=Policy for Sample Rate Conversion of Audio Streams (Windows Drivers)|work=Dev Center - Hardware|publisher=Microsoft|access-date=2012-01-17|archive-date=2012-07-27|archive-url=https://web.archive.org/web/20120727050220/http://msdn.microsoft.com/en-us/library/windows/hardware/ff537758(v=vs.85).aspx|url-status=live}}</ref><ref>{{cite web|url=http://social.msdn.microsoft.com/Forums/en-US/windowspro-audiodevelopment/thread/725546ce-57bf-40d0-b7aa-47e51de9c3ae/|title=Artifacts on Windows 7 due to sample rate conversion|work=Windows Desktop Development Forums discussion thread|access-date=2012-01-17|archive-date=2011-07-22|archive-url=https://web.archive.org/web/20110722090905/http://social.msdn.microsoft.com/Forums/en-US/windowspro-audiodevelopment/thread/725546ce-57bf-40d0-b7aa-47e51de9c3ae|url-status=live}}</ref>
===Audio signal processing===
Line 61 ⟶ 64:
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 Technology|Creative's]] [[Sound Blaster X-Fi#CMSS-3D|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 there is a multi-channel or stereo sound system in a home theater or living room, Windows Vista also includes the ability to calibrate the speakers for that room. By placing a microphone where the listener plans 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]].<ref name="AudioImprovements">{{cite web |url=http://windowsvistablog.com/blogs/windowsvista/archive/2006/12/06/audio-improvements-in-windows-vista.aspx |title=Audio Improvements in Windows Vista |last=Allchin |first=Jim |author-link=Jim Allchin |date=December 6, 2006 |publisher=[[Microsoft]] |work=Windows Vista Team Blog |archive-url=https://web.archive.org/web/20061209135853/http://windowsvistablog.com/blogs/windowsvista/archive/2006/12/06/audio-improvements-in-windows-vista.aspx |archive-date=December 9, 2006 |access-date=November 3, 2015}}</ref>
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).<ref>
===Audio devices support===
Line 77 ⟶ 80:
===Other audio enhancements===
* A new set of user interface sounds have been introduced, including a new startup sound created with the help of [[King Crimson]]'s [[Robert Fripp]].<ref name="Channel9Fripp">{{cite web |url=http://channel9.msdn.com/Blogs/scobleizer/Robert-Fripp-Behind-the-scenes-at-Windows-Vista-recording-session |title=Robert Fripp - Behind the scenes at Windows Vista recording session |last=Scoble |first=Robert |author-link=Robert Scoble
* Windows Vista also allows controlling system-wide volume or volume of individual audio devices and individual applications separately.<ref name="AudioImprovements"/><ref name="Softpedia">{{cite web |url=http://archive.news.softpedia.com/news/The-Windows-Vista-Volume-Mixer-41882.shtml |title=The Windows Vista Volume Mixer |last=Oiaga |first=Marius |date=December 7, 2006 |publisher=[[Softpedia]] |access-date=April 25, 2015 |archive-url=https://web.archive.org/web/20150214074429/http://archive.news.softpedia.com/news/The-Windows-Vista-Volume-Mixer-41882.shtml |archive-date=February 14, 2015 |url-status=dead |df=mdy-all }}</ref> This feature can be used from the new ''Volume Control'' windows or programmatically using the overhauled audio API. Different sounds can be redirected to different audio devices as well.
* Windows Vista includes integrated [[microphone array]] support which is intended to increase the accuracy of the [[Technical features new to Windows Vista#Speech recognition|speech recognition]] feature and allow a user to connect multiple microphones to a system so that the inputs can be combined into a single, higher-quality source.<ref name="AudioImprovements"/><ref name="AudioInnovationsWP">{{cite web |url=http://blogs.technet.com/b/windowsvista/archive/2006/08/24/450038.aspx |title=Audio Innovations in Windows Vista |date=August 24, 2006 |publisher=[[Microsoft]] |work=[[Microsoft TechNet|TechNet]] |access-date=April 25, 2015 |archive-date=January 9, 2015 |archive-url=https://web.archive.org/web/20150109105946/http://blogs.technet.com/b/windowsvista/archive/2006/08/24/450038.aspx |url-status=live }}</ref><ref name="MicrophoneArray">{{cite web |url=http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/MicArrays.doc |title=Microphone Array Support in Windows |date=April 21, 2014 |author=[[Microsoft]] |format=DOC |access-date=April 25, 2015 |archive-date=March 4, 2016 |archive-url=https://web.archive.org/web/20160304132915/http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/MicArrays.doc |url-status=live }}</ref>
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 messaging|instant messengers]] and speech recognition applications to apply [[Echo cancellation#Acoustic echo cancellation|Acoustic Echo Cancellation]] and microphone array processing to speech signals.<ref name="AcousticEcho">{{cite web |url=https://technet.microsoft.com/en-us/library/cc753619.aspx |title=Eliminating Acoustic Echo |publisher=[[Microsoft]] |work=[[Microsoft TechNet|TechNet]] |access-date=April 25, 2015 |archive-date=March 4, 2016 |archive-url=https://web.archive.org/web/20160304194500/https://technet.microsoft.com/en-us/library/cc753619.aspx |url-status=live }}</ref>
===Speech recognition===
Line 107 ⟶ 110:
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,<ref>
===XPS print path===
{{see also|XML Paper Specification}}
The XPS Print Path introduced in Windows Vista supports high quality 16-bit color printing.<ref>
| url=http://channel9.msdn.com/Showpost.aspx?postid=137532
| title=Inside Windows Vista Printing
Line 119 ⟶ 122:
| work=Channel 9
| publisher=Microsoft
| archive-date=2006-05-14
| archive-url=https://web.archive.org/web/20060514075418/http://channel9.msdn.com/Showpost.aspx?postid=137532
| url-status=live
}}</ref>
Line 143 ⟶ 149:
| work=Microsoft TechNet
| publisher=Microsoft
| archive-date=2006-08-30
| archive-url=https://web.archive.org/web/20060830131226/http://www.microsoft.com/technet/itsolutions/network/evaluate/new_network.mspx
| url-status=live
}}</ref> 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 (networking)|host model]] and features an infrastructure to enable more modular components that can be dynamically inserted and removed.
Line 155 ⟶ 164:
| work=MSDN
| publisher=Microsoft
| access-date=2008-12-21
| archive-date=2012-10-16
| archive-url=https://web.archive.org/web/20121016093406/http://msdn.microsoft.com/en-us/library/aa365993.aspx
| url-status=live
}}</ref>
* The memory manager and processes scheduler have been improved. The scheduler was modified to use the cycle counter register of modern processors to keep track of exactly how many [[Central Processing Unit|CPU]] cycles a thread has executed, rather than just using an interval-timer interrupt routine.<ref>[https://technet.microsoft.com/en-us/magazine/cc162494.aspx Inside the Windows Vista Kernel: Part 1] {{Webarchive|url=https://web.archive.org/web/20090521102641/http://technet.microsoft.com/en-us/magazine/cc162494.aspx |date=2009-05-21 }}, Microsoft Technet</ref> This new CPU cycle-based thread scheduling gives a greater fairness and more deterministic app behavior.<ref>
* Windows Vista includes support for [[condition variable]]s and [[reader-writer lock]]s.
* Process creation overhead is reduced by significant improvements to DLL address-resolving schemes.
* Windows Vista introduces a ''Protected Process'',<ref>
* ''Thread Pools'' have been upgraded to support multiple pools per process, as well as to reduce performance overhead using thread recycling. It also includes ''Cleanup Groups'' that allow cleanup of pending thread-pool requests on process shutdown.
* ''Threaded DPC'' [https://web.archive.org/web/20090424065603/http://msdn.microsoft.com/en-us/library/ms795178.aspx], conversely to an ordinary DPC (Deferred Procedure Call), decreases the system latency improving the performance of time-sensitive applications, such as audio or video playback.
* Data Redirection: Also known as ''data virtualization'', this virtualizes the [[Windows Registry|registry]] and certain parts of the file system for applications running in the [[Principle of least privilege|protected user context]] if [[User Account Control]] is turned on, enabling legacy applications to run in non-administrator accounts. It automatically creates private copies of files that an application can use when it does not have permission to access the original files. This facilitates stronger file security and helps applications not written with the [[least user access]] principle in mind to run under stronger restrictions. ''Registry virtualization'' isolates write operations that have a global impact to a per-user ___location. Reads and writes in the <tt>HKLM\Software</tt> section of the [[Windows Registry|Registry]] by user-mode applications while running as a standard user, as well as to folders such as "Program Files", are "redirected" to the user's profile. The process of reading and writing on the profile data and not on the application-intended ___location is completely transparent to the application.
* Windows Vista supports the [[PCI Express]] 1.1 specification, including PCI Express Native Control and [[Active State Power Management|ASPM]]. PCI Express registers, including capability registers, are supported, along with save and restore of configuration data.<ref>{{Cite web|title=Active State Power Management in Windows Vista|url=https://studylib.net/doc/7453014/active-state-power-management-in-windows-vista|access-date=2021-03-19|website=studylib.net|language=en|archive-date=2021-04-02|archive-url=https://web.archive.org/web/20210402174332/https://studylib.net/doc/7453014/active-state-power-management-in-windows-vista|url-status=live}}</ref>
* Native support and generic driver for [[Advanced Host Controller Interface]] (AHCI) specification for [[Serial ATA]] drives, SATA [[Native Command Queuing]], [[Hot swapping|Hot plugging]], and AHCI Link Power Management.
* Full support for the [[Advanced Configuration and Power Interface|ACPI]] 2.0 specification, and parts of ACPI 3.0.<ref name="kernelfeatures">[http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/kernel-en.doc Windows NT 6.x Kernel Changes] {{Webarchive|url=https://web.archive.org/web/20070303223841/http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/kernel-en.doc |date=2007-03-03 }}. (Word document)</ref> Support for throttling power usage of individual devices has been improved.
* Kernel-mode [[Plug-And-Play]] enhancements include support for PCI multilevel rebalance, partial arbitration of resources to support PCI subtractive bridges, asynchronous device start and enumeration operations to speed system startup, support for setting and retrieving custom properties on a device, an enhanced ejection API to allow the caller to determine if and when a device has been successfully ejected, and diagnostic tracing to facilitate improved reliability.<ref>{{Cite web |url=http://www.microsoft.com/whdc/system/pnppwr/pnp/default.mspx |title=Plug and Play: Architecture and Driver Support |access-date=2007-05-26 |archive-url=https://web.archive.org/web/20040616023120/http://www.microsoft.com/whdc/system/pnppwr/pnp/default.mspx |archive-date=2004-06-16 |url-status=dead }}</ref>
* The [[Windows Vista Startup Process|startup process for Windows Vista]] has changed completely in comparison to earlier versions of Windows. The [[NTLDR]] boot loader has been replaced by a more flexible system, with NTLDR's functionality split between two new components: [[winload.exe]] and [[Windows Boot Manager]].<ref name="bcd-faq">See [http://www.microsoft.com/technet/windowsvista/library/85cd5efe-c349-427c-b035-c2719d4af778.mspx Boot Configuration Data Editor Frequently Asked Questions] {{Webarchive|url=https://web.archive.org/web/20061208002701/http://www.microsoft.com/technet/windowsvista/library/85cd5efe-c349-427c-b035-c2719d4af778.mspx |date=2006-12-08 }} for details on BCD.</ref> A notable change is that the Windows Boot Manager is invoked by pressing the [[space bar]] instead of the F8 [[function key]].<ref>
* On [[Extensible Firmware Interface|UEFI]] systems, beginning with Windows Vista Service Pack 1, the x64 version of Windows Vista has the ability to boot from a disk with a [[GUID Partition Table]].
* Windows Vista includes a completely overhauled and rewritten ''Event logging'' subsystem, known as [[Windows Event Log]] which is [[XML]]-based and allows applications to more precisely log events, offers better views, filtering and categorization by criteria, automatic log forwarding, centrally logging and managing events from a single computer and remote access.
Line 174 ⟶ 187:
* ''Restart Manager'': The ''Restart Manager'' works with Microsoft's update tools and websites to detect processes that have files in use and to gracefully stop and restart services to reduce the number of reboots required after applying updates as far as possible for higher levels of the software stack. Kernel updates, logically, still require the system to be restarted.<ref>{{cite web | url=http://msdn.microsoft.com/en-us/library/aa373654.aspx | title=Restart Manager | author=Microsoft | publisher=Microsoft | work=MSDN Library | access-date=2008-12-21 | archive-url=https://web.archive.org/web/20090112123045/http://msdn.microsoft.com/en-us/library/aa373654.aspx | archive-date=2009-01-12 | url-status=dead }}</ref> In addition, the Restart Manager provides a mechanism for applications to stop and then restart programs. Applications that are written specifically to take advantage of the new ''Restart Manager'' features using the API can be restarted and restored to the same state and with the same data as before the restart. Using the ''Application Recovery and Restart'' APIs in conjunction with the ''Restart Manager'' enables applications to control what actions are taken on their behalf by the system when they fail or crash such as recovering unsaved data or documents, restarting the application, and diagnosing and reporting the problem using [[Windows Error Reporting]].
<!-- Deleted image removed: [[Image:Vista Shutdown.png|thumb|right|A screenshot of Windows Vista's shutdown overlay UI|{{deletable image-caption|1=Tuesday, 22 September 2009}}]] -->
* When shutting down or restarting Windows, previous Windows versions either forcibly terminated applications after waiting for few seconds, or allowed applications to entirely cancel shutdown without informing the user. Windows Vista now informs the user in a full-screen interface if there are running applications when exiting Windows or allows continuing with or cancelling the initiated shutdown. The reason registered, if any, for cancelling a shutdown by an application using the new ''ShutdownBlockReasonCreate'' API is also displayed.<ref>[http://msdn.microsoft.com/en-us/library/bb394721.aspx Shutdown Changes for Windows Vista] {{Webarchive|url=https://web.archive.org/web/20110427092544/http://msdn.microsoft.com/en-us/library/bb394721.aspx |date=2011-04-27 }} and [http://www.developer.com/net/cplus/article.php/3647411 Handling OS shutdown in Windows Vista] {{Webarchive|url=https://web.archive.org/web/20070429095017/http://www.developer.com/net/cplus/article.php/3647411 |date=2007-04-29 }}</ref>
* ''Clean service shutdown'': Services in Windows Vista have the capability of delaying the system shutdown in order to properly flush data and finish current operations. If the service stops responding, the system terminates it after 3 minutes. Crashes and restart problems are drastically reduced since the Service Control Manager is not terminated by a forced shutdown anymore.
===Boot process===
{{main|Windows Vista startup 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]].<ref name="Restructuring">{{cite web |url=http://download.microsoft.com/download/1/8/f/18f8cee2-0b64-41f2-893d-a6f2295b40c8/TW04022_WINHEC2004.ppt |title=EFI and Windows 'Longhorn' |archive-url=https://web.archive.org/web/20040609090303/http://download.microsoft.com/download/1/8/f/18f8cee2-0b64-41f2-893d-a6f2295b40c8/TW04022_WINHEC2004.ppt |archive-date=June 9, 2004 |last=Ritz |first=Andrew |date=2004 |publisher=[[Microsoft]] |format=PPT |access-date=April 18, 2015}}</ref><ref name="BCD">{{cite web |url=http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/BCD.docx |title=Boot Configuration Data in Windows Vista |author=[[Microsoft]] |date=February 4, 2008 |format=DOCX |access-date=April 18, 2015 |archive-date=July 2, 2014 |archive-url=https://web.archive.org/web/20140702181401/http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/BCD.docx |url-status=live }}</ref> The new architecture introduces a firmware-independent data store and is backward compatible with previous versions of the Windows operating system.<ref name="BCD"/>
===Memory management===
Line 190 ⟶ 203:
* Performance of ''Address Translation Buffers'' has been enhanced.
* [[Dynamic memory allocation|Heap]] layout has been modified to provide higher performance on 64-bit and [[Symmetric multiprocessing]] (SMP) systems. The new heap structure is also more scalable and has low management overhead, especially for large heaps.
* Windows Vista automatically tunes up the heap layout for improved fragmentation management. The ''Low Fragmentation Heap'' (LFH) is enabled by default.<ref>
* Lazy initialization of heap initializes only when required, to improve performance.
* The Windows Vista memory manager does not have a 64 kb read-ahead cache limitation unlike previous versions of Windows and can thus improve file system performance dramatically.
Line 197 ⟶ 210:
* [[Transactional NTFS]] allows multiple file/folder operations to be treated as a single operation, so that a crash or power failure won't result in half-completed file writes. Transactions can also be extended to multiple machines.
* [[Image Mastering API]] (''IMAPI v2'') enables [[DVD]] burning support for applications, in addition to CD burning.<ref name="WindowsVistaOpticalPlatform">{{cite web |url=http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/sto068_wh06.ppt |title=Optical Platform: Windows Vista and Beyond |last2=Walp |first2=David |last1=Mangefeste |first1=Tony |date=2006 |publisher=[[Microsoft]] |format=PPT |archive-url=https://web.archive.org/web/20110604214913/http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/STO068_WH06.ppt |archive-date=June 4, 2011 |access-date=December 21, 2015}}</ref> ''IMAPI v2'' supports multiple optical drives, even recording to multiple drives simultaneously, unlike IMAPI in Windows XP which only supported recording with one optical drive at a time.<ref name="WhatsNewIMAPI">{{cite web |url=https://msdn.microsoft.com/en-us/library/aa366457.aspx |title=Image Mastering API - What's New |author=[[Microsoft]] |work=[[Microsoft Developer Network|MSDN]] |access-date=December 21, 2015 |archive-date=April 4, 2016 |archive-url=https://web.archive.org/web/20160404150431/https://msdn.microsoft.com/en-us/library/aa366457.aspx |url-status=live }}</ref> In addition, multiple filesystems are supported. Applications using ''IMAPI v2'' can create, and burn [[disc image]]s—it is extensible in the sense that developers can write their own specific media formats and create their own file systems for its programming interfaces.<ref name="WindowsVistaOpticalPlatform"/> ''IMAPI v2'' is implemented as a [[Dynamic-link library|DLL]] rather than as a [[Windows service|service]] as was the case in [[Windows XP]],<ref>
* [[Live File System]]: A writable [[Universal Disk Format|UDF]] file system.<ref name="WindowsVistaOpticalPlatform"/> The Windows [[Universal Disk Format|UDF]] file system (UDFS) implementation was read-only in OS releases prior to Windows Vista. In Windows Vista, [[Mount Rainier (packet writing)|Packet writing]] (incremental writing) is supported by UDFS, which can now format and write to all mainstream optical media formats ([[Magneto-optical drive|MO]], CDR/RW, DVD+R/RW, DVD-R/RW/RAM). Write support is included for UDF format versions up to and including 2.50, with read support up to 2.60. UDF symbolic links, however, are not supported.<ref name="FilingCabinet">{{cite web |url=https://blogs.technet.com/filecab/articles/454702.aspx |title=Universal Disk FOrmat (UDF) Beta Chat Transcript (September 01, 2006) |publisher=[[Microsoft]] |work=MSDN Blogs |access-date=December 21, 2015 |archive-date=February 28, 2009 |archive-url=https://web.archive.org/web/20090228015926/http://blogs.technet.com/filecab/articles/454702.aspx |url-status=live }}</ref>
* [[Common Log File System]] (CLFS) API provides a high-performance, general-purpose log-file subsystem that dedicated user-mode and kernel-mode client applications can use and multiple clients can share to optimize log access and for data and event management.
* File encryption support superior to that available in [[Encrypting File System]] in Windows XP, which will make it easier and more automatic to prevent unauthorized viewing of files on stolen laptops or hard drives.
* ''File System Mini Filters model'' which are kernel mode non-device drivers, to monitor filesystem activity, have been upgraded in Windows Vista. The ''Registry filtering model'' adds support for redirecting calls and modifying parameters and introduces the concept of altitudes for filter registrations.
* ''Registry notification hooks'', introduced in Windows XP, and recently enhanced in Windows Vista, allow software to participate in registry related activities in the system.
* Support of UNIX-style [[NTFS symbolic link|symbolic links]].<ref name="SymbolicLinks">{{cite web |url=http://msdn.microsoft.com/en-us/library/aa365680%28VS.85%29.aspx?s=41 |title=Symbolic Links |author=[[Microsoft]] |work=[[Microsoft Developer Network|MSDN]] |access-date=December 21, 2015 |archive-date=December 23, 2015 |archive-url=https://web.archive.org/web/20151223072803/https://msdn.microsoft.com/en-us/library/aa365680(VS.85).aspx?s=41 |url-status=live }}</ref> Previous Windows versions had support for a type of cross-volume [[NTFS reparse point|reparse points]] known as [[NTFS junction point|junction points]] and [[hard link]]s. However, junction points could be created only for directories and stored absolute paths, whereas hardlinks could be created for files but were not cross-volume. [[NTFS symbolic link]]s can be created for any object and are cross-volume, cross-host (work over [[Uniform Naming Convention|UNC]] paths), and store relative paths. However, the cross-host functionality of symbolic links does not work over the network with previous versions of Windows or other operating systems, only with computers running [[Windows Vista]] or a later Windows operating system. Symbolic links can be created, modified and deleted using the ''Mklink'' utility which is included with Windows Vista. Microsoft has published some developer documentation on symbolic links in the MSDN documentation.<ref name="SymbolicLinks"/> In addition, [[Windows Explorer]] is now symbolic link-aware and deleting a symbolic link from Explorer just deletes the link itself and not the target object. Explorer also shows the symbolic link target in the object's properties and shows a shortcut icon overlay on a junction point.
* A new tab, "Previous Versions", in the ''Properties'' dialog for any file or folder, provides read-only snapshots of files on local or network volumes from an earlier point in time. This feature is based on the [[Volume Shadow Copy]] technology.
* A new file-based [[disk image]] format called [[Windows Imaging Format]] (WIM), which can be mounted as a partition, or booted from. An associated tool called [[ImageX]] provides facilities to create and maintain these image files.
* ''Self-healing NTFS'': In previous Windows versions, NTFS marked the volume "dirty" upon detecting file-system corruption and [[CHKDSK]] was required to be run by taking the volume "offline". With self-healing NTFS, an NTFS worker thread is spawned in the background which performs a localized fix-up of damaged data structures, with only the corrupted files/folders remaining unavailable without locking out the entire volume.<ref name="WindowsStorageDirections">{{cite web |url=http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/STO123_WH06.ppt |title=Windows Storage Directions: Windows Vista And Beyond |last=Loveall |first=John |date=2006 |format=PPT |publisher=[[Microsoft]] |archive-url=https://web.archive.org/web/20070928001422/http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/STO123_WH06.ppt |archive-date=September 28, 2007 |access-date=December 21, 2015}}</ref> The self-healing behavior can be turned on for a volume with the ''fsutil repair set C: 1'' command where ''C'' presents the volume letter.<ref name="SelfHealingNTFS">{{cite web |url=http://blogs.technet.com/b/apawar/archive/2008/02/14/self-healing-ntfs-in-windows-server-2008-and-windows-vista.aspx |title=Self-healing NTFS in Windows Server 2008 and Windows Vista |date=February 13, 2008 |publisher=[[Microsoft]] |work=[[Microsoft TechNet|TechNet]] |access-date=December 21, 2015 |archive-date=March 4, 2016 |archive-url=https://web.archive.org/web/20160304062743/http://blogs.technet.com/b/apawar/archive/2008/02/14/self-healing-ntfs-in-windows-server-2008-and-windows-vista.aspx |url-status=live }}</ref>
* New /B switch in [[CHKDSK]] for NTFS volumes which clears marked bad sectors on a volume and reevaluates them.<ref name="ChkdskVista">{{cite web |url=https://technet.microsoft.com/en-us/library/cc730714%28WS.10%29.aspx |title=Chkdsk |author=[[Microsoft]] |work=[[Microsoft TechNet|TechNet]] |access-date=December 21, 2015 |archive-date=December 23, 2015 |archive-url=https://web.archive.org/web/20151223082329/https://technet.microsoft.com/en-us/library/cc730714(WS.10).aspx |url-status=live }}</ref>
* Windows Vista has support for hard disk drives with large physical [[Disk sector|sector sizes]] (> 512 bytes per sector drives) if the drive supports 512-bytes logical sectors / emulation (called Advanced Format/512E).<ref name="KB2510009">{{cite web |url=https://support.microsoft.com/en-us/kb/2510009 |title=Microsoft support policy for 4K sector hard drives in Windows |author=[[Microsoft]] |work=Support |access-date=December 21, 2015 |archive-date=November 19, 2015 |archive-url=https://web.archive.org/web/20151119021146/https://support.microsoft.com/en-us/kb/2510009 |url-status=live }}</ref> Drives with both 4k logical and 4k physical sectors are not supported.
* The NLS casing table in NTFS has been updated so that partitions formatted with Windows Vista will be able to see the proper behavior for the 100+ mappings that have been added to [[Unicode]] but were not added to Windows.<ref name="NTFSChanges">{{cite web |url=http://www.msblog.org/2005/09/16/ntfs-changes-in-vista-any-changes/ |title=NTFS Changes in Vista. Any changes? |last=Gan |first=Jabez |date=September 16, 2005 |work=MSBlogs |access-date=December 21, 2015 |archive-date=December 22, 2015 |archive-url=https://web.archive.org/web/20151222232107/http://www.msblog.org/2005/09/16/ntfs-changes-in-vista-any-changes/ |url-status=live }}</ref>
* Windows Vista Service Pack 1 and later have built-in support for [[exFAT]].<ref name="WindowsVistaSP1NotableChanges">{{cite web |url=https://technet.microsoft.com/en-us/library/cc709618%28v=ws.10%29.aspx |title=Notable Changes in Windows Vista Service Pack 1 |author=[[Microsoft]] |work=[[Microsoft TechNet|TechNet]] |access-date=December 21, 2015 |archive-date=June 30, 2017 |archive-url=https://web.archive.org/web/20170630143938/https://technet.microsoft.com/en-us/library/cc709618%28v=ws.10%29.aspx |url-status=live }}</ref>
===Drivers===
Line 218 ⟶ 231:
* [[Windows Display Driver Model]] (WDDM), previously referred to as Longhorn Display Driver Model (LDDM), designed for graphics performance and stability.
* A new [[Kernel-Mode Driver Framework]], which will also be available for Windows XP and Windows 2000.
* A new user-mode driver model called the [[User-Mode Driver Framework]]. In Windows Vista, WDDM display drivers have two components, a kernel mode driver (KMD) that is very streamlined, and a user-mode driver that does most of the intense computations. With this model, most of the code is moved out of kernel mode. The audio subsystem also runs largely in user-mode to prevent impacting negatively on kernel performance and stability. Also, printer drivers in kernel mode are not supported. User-mode drivers are not able to directly access the kernel but use it through a dedicated API. User-mode drivers are supported for devices which plug into a USB or FireWire bus, such as digital cameras, portable media players, PDAs, mobile phones and mass storage devices, as well as "non-hardware" drivers, such as filter drivers and other software-only drivers. This also allows for drivers which would typically require a system reboot (video card drivers, for example) to install or update without needing a reboot of the machine. If the driver requires access to kernel-mode resources, developers can split the driver so that part of it runs in kernel-mode and part of it runs in user-mode. These features are significant because a majority of system crashes can be traced to improperly installed or unstable third-party device drivers.<ref>{{cite web
* Kernel-mode drivers on 64-bit versions of Windows Vista must be digitally signed; even administrators will not be able to install unsigned kernel-mode drivers.<ref name="kmsigning">{{cite web
| url=http://www.microsoft.com/whdc/system/platform/64bit/kmsigning.mspx
Line 229 ⟶ 242:
* Signed drivers are required for usage of PUMA, PAP (Protected Audio Path), and PVP-OPM subsystems.
* Driver packages that are used to install driver software are copied in their entirety into a "Driver Store", which is a repository of driver packages. This ensures that drivers that need to be repaired or reinstalled won't need to ask for source media to get "fresh" files. The Driver Store can also be preloaded with drivers by an OEM or IT administrator to ensure that commonly used devices (e.g. external peripherals shipped with a computer system, corporate printers) can be installed immediately. Adding, removing and viewing drivers from the "Driver Store" is done using <tt>PnPUtil.exe</tt><ref>
* Support for [[Windows Error Reporting]]; information on an "unknown device" is reported to Microsoft when a driver cannot be found on the system, via Windows Update, or supplied by the user. OEMs can hook into this system to provide information that can be returned to the user, such as a formal statement of non-support of a device for Windows Vista, or a link to a web site with support information, drivers, etc.
Line 259 ⟶ 272:
| author=Tom Archer
| work=Tom Archer's Blog
| publisher=Microsoft
| archive-date=2006-05-23
| archive-url=https://web.archive.org/web/20060523070440/http://blogs.msdn.com/tomarcher/archive/2006/04/14/576548.aspx
| url-status=live
}}</ref>
* '''ReadyBoot''' uses an in-RAM cache to optimize the [[Windows Vista Startup Process|boot process]] if the system has 700MB or more memory. The size of the cache depends on the total RAM available, but is large enough to create a reasonable cache and yet allow the system the memory it needs to boot smoothly. ReadyBoot uses the same ReadyBoost service.<ref>{{Cite web |url=http://www.microsoft.com/technet/technetmag/issues/2007/03/VistaKernel/ |title=Inside the Windows Vista kernel |access-date=2007-04-30 |archive-url=https://web.archive.org/web/20070331073321/http://www.microsoft.com/technet/technetmag/issues/2007/03/VistaKernel/ |archive-date=2007-03-31 |url-status=dead }}</ref>
* '''[[Windows Vista I/O technologies#ReadyDrive|ReadyDrive]]''' is the name Microsoft has given to its support for [[hybrid drive]]s, a new design of [[hard drive]] developed by [[Samsung]] and Microsoft. Hybrid drives incorporate [[non-volatile memory]] into the drive's design, resulting in lower power needs, as the drive's spindles do not need to be activated for every write operation. Windows Vista can also make use of the NVRAM to increase the speed of booting and returning from hibernation.<ref name="performance">{{cite web
| url=http://www.microsoft.com/windowsvista/features/foreveryone/performance.mspx | title=Windows Vista: Performance
| year=2006
| access-date=2006-04-30
| publisher=Microsoft
| archive-date=2006-04-25
| archive-url=https://web.archive.org/web/20060425023359/http://www.microsoft.com/windowsvista/features/foreveryone/performance.mspx
| url-status=live
}}</ref>
Line 276 ⟶ 297:
| work=Driver Fundamentals
| publisher=Windows Hardware Developer Central
| access-date=2006-12-31
| access-date=2006-12-31}}</ref> I/O has been enhanced with I/O asynchronous cancellation and I/O scheduling based on thread priority. Background applications running in low priority I/O do not disturb foreground applications. Applications like Windows Defender, Automatic Disk Defragmenter and Windows Desktop Search (during indexing) already use this feature.<ref name="PerformanceTechnologies">{{cite web |url=http://download.microsoft.com/download/5/b/9/5b97017b-e28a-4bae-ba48-174cf47d23cd/cpa131_wh06.ppt |title=Windows Vista Performance Technologies |last=Aul |first=Gabriel |date=2006 |format=PPT |publisher=[[Microsoft]] |access-date=July 9, 2015}}</ref> Windows Media Player 11 also supports this technology to offer glitch-free multimedia playback.<ref name="kernel1">{{cite web |url=http://www.microsoft.com/technet/technetmag/issues/2007/02/VistaKernel/ |title=Inside the Windows Vista Kernel: Part 1 |last=Russinovich |first=Mark |author-link=Mark Russinovich |publisher=[[Microsoft]] |work=[[Microsoft TechNet|TechNet]] |access-date=July 15, 2015 |archive-url=https://web.archive.org/web/20081118123903/http://www.microsoft.com/technet/technetmag/issues/2007/02/VistaKernel/ |archive-date=2008-11-18 |url-status=dead }}</ref>▼
| archive-date=2007-01-28
| archive-url=https://web.archive.org/web/20070128084917/http://www.microsoft.com/whdc/driver/priorityio.mspx
| url-status=live
▲
* The '''[[Offline Files]]''' feature, which maintains a client-side cache of files shared over a network, has been significantly improved. When synchronizing the changes in the cached copy to the remote version, the ''Bitmap Differential Transfer'' protocol is used so that only the changed blocks in the cached version are transferred, but when retrieving changes from the remote copy, the entire file is downloaded.<ref name="Offline">{{cite web | url = http://windowsvistablog.com/blogs/windowsvista/archive/2007/01/29/working-with-offline-files.aspx | title = Offline Files | author = Jim Allchin | access-date = 2007-06-14 | archive-url = https://web.archive.org/web/20070518233509/http://windowsvistablog.com/blogs/windowsvista/archive/2007/01/29/working-with-offline-files.aspx | archive-date = 2007-05-18 | url-status = dead }}</ref> are synchronized on a per-share basis and encrypted on a per-user basis and users can force Windows to work in offline mode or online mode or sync manually from the Sync Center. The Sync Center can also report sync errors and resolve sync conflicts. Also, if network connectivity is restored, file handles are redirected to the remote share transparently.
Line 350 ⟶ 375:
===Search===
{{main|Windows Search}}
The Windows Vista ''Instant Search'' index can also be accessed programmatically using both [[.NET Framework|managed]] as well as [[Win32|native]] code.<ref>{{cite web |title=Searching data |
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.<ref>{{cite web | url = http://blogs.msdn.com/cheller/archive/2006/11/10/windows-vista-search-syntax-update.aspx | title = Windows Vista Search: Syntax Update | author = Catherine Heller | access-date = 2007-06-23 | archive-date = 2007-07-03 | archive-url = https://web.archive.org/web/20070703133350/http://blogs.msdn.com/cheller/archive/2006/11/10/windows-vista-search-syntax-update.aspx | url-status = live }}</ref> 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.<ref name="SIP">{{cite web | url = http://msdn.microsoft.com/en-us/library/bb266517.aspx | title = Querying the Index Programmatically | publisher = MSDN | access-date = 2007-06-23 | archive-date = 2009-02-05 | archive-url = https://web.archive.org/web/20090205004910/http://msdn.microsoft.com/en-us/library/bb266517.aspx | url-status = live }}</ref> 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.<ref>{{cite web | url = http://msdn.microsoft.com/en-us/library/aa965439.aspx | title = ISearchQueryHelper::GenerateSQLFromUserQuery Method | access-date = 2007-06-23 | archive-date = 2008-10-15 | archive-url = https://web.archive.org/web/20081015124308/http://msdn.microsoft.com/en-us/library/aa965439.aspx | url-status = live }}</ref> Searches can also be performed using the ''search-ms:'' [[Protocol (computing)|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===
Line 390 ⟶ 415:
}}</ref>
** Latin fonts: [[Calibri]], [[Cambria (typeface)|Cambria]], [[Candara]], [[Consolas]] (monotype), [[Constantia (typeface)|Constantia]], and [[Corbel (typeface)|Corbel]]. [[Segoe UI]], previously used in [[Windows XP Media Center Edition]], is also included, despite licensing issues with [[Mergenthaler Linotype Company|Linotype]].
** [[Meiryo]], supporting the new and modified characters of the [[Japanese Industrial Standard|JIS]] X 0213:2004 standard<ref>{{cite web | url=http://pc.watch.impress.co.jp/docs/2005/0729/ms.htm | title=Windows Vista - ClearType - Meiryo | date=August 29, 2005 | publisher=PC Watch | access-date=March 7, 2007 | archive-date=February 22, 2007 | archive-url=https://web.archive.org/web/20070222142157/http://pc.watch.impress.co.jp/docs/2005/0729/ms.htm | url-status=live }}</ref>
** Non-Latin fonts: [[Microsoft JhengHei]] (Chinese Traditional), [[Microsoft YaHei]] (Chinese Simplified), Majalla UI (Arabic), Gisha (Hebrew), Leelawadee (Thai) and Malgun Gothic (Korean).
** Support for [[Adobe Systems|Adobe]] CFF/Type2 fonts, which provides support for contextual and discretionary [[Ligature (typography)|ligatures]].
Line 397 ⟶ 422:
* New support for [[infrared]] receivers and [[Bluetooth#Bluetooth v2.0 + EDR|Bluetooth 2.0]] wireless standards; devices supporting these can transfer files and sync data wirelessly to a Windows Vista computer with no additional software.
* A non-administrator user can share only the folders under his user profile. In addition, all users have a ''Public'' folder which is shared, though an administrator can override this.
* '''Network Projection'''<ref>
* New monitor configuration APIs make it possible to adjust the monitor's display area, save and restore display settings, calibrate color and use vendor-specific monitor features. Overall too, Windows Vista is designed to be more resolution-independent than its predecessors, with a particular focus on higher resolutions and high [[Dots per inch|DPI]] [[Computer display|displays]] [http://blogs.msdn.com/greg_schechter/archive/2006/09/14/753467.aspx]. [[Windows Presentation Foundation]] and WPF applications are fully [[resolution independence|resolution-independent]].<ref>{{Cite web |url=http://msdn.microsoft.com/msdnmag/issues/06/01/windowspresentationfoundation/default.aspx |title=Top Ten UI breakthroughs for WPF |access-date=2007-05-12 |archive-url=https://web.archive.org/web/20070517142803/http://msdn.microsoft.com/msdnmag/issues/06/01/WindowsPresentationFoundation/default.aspx |archive-date=2007-05-17 |url-status=dead }}</ref> Also, ''Transient Multimon Manager'', a new feature that uses the monitor's [[EDID]] enables automatic detection, setup and proper configuration of additional or multiple displays as they are attached and removed, on the fly. The settings are saved on a per-display basis when possible, so that users can move among multiple displays with no manual configuration.
* Windows Vista includes a [[Web Services for Devices|WSD]]-[[Windows Image Acquisition|WIA]] [[class driver]] that enables all devices compliant with Microsoft's Web Services for Scanner (WS-Scan) protocol to work with WIA without any additional driver or software.
* The ''Fax service'' and model are fully account-based. Fax-aware applications such as [[Windows Fax and Scan]] can send multiple documents in a single fax submission. The Fax Service API generates [[TIFF]] files for each document and merges them into a single TIFF file. Users can right-click a document in Windows Explorer and select ''Send to Fax Recipient''.
* Windows Vista introduces the 'Assistance Platform' based on [[Microsoft Assistance Markup Language|MAML]]. '''Help and Support''' is intended to be more meaningful and clear. '''Guided Help''', or '''Active Content Wizard''' is an automated tutorial and self-help system available with the release of Windows Vista where a series of animated steps show users how to complete a particular task.<ref>{{cite web | url=http://digitalfive.org/content/guided-help-in-windows-vista.html | title=Guided Help in Windows Vista | date=June 5, 2006 | author=Kristan M. Kenney | work=digitalfive | access-date=2007-02-26 | archive-url=https://web.archive.org/web/20070929224252/http://digitalfive.org/content/guided-help-in-windows-vista.html | archive-date=2007-09-29 | url-status=dead }}</ref> It highlights only the options and the parts of screen that are relevant to the task and darkening the rest of the screen. A separate file format is used for ACW help files. The guided help SDK got replaced in [[Windows 7]] with the Windows Troubleshooting Platform.
* All standard text editing controls and all versions of the 'RichEdit' control now support the [[Text Services Framework]]. Also, all Tablet/Ink API applications and all HTML applications which use Internet Explorer's [[Trident (layout engine)|Trident layout engine]] support the Text Services Framework.<ref>
* Windows Data Access Components (Windows DAC) replace [[Microsoft Data Access Components|MDAC 2.81]] which shipped with Windows XP Service Pack 2.
* '''DFS Replication''',<ref>{{cite web
| |||