Peek at desktop setting grayed out in Windows.Microsoft introduced Aero Peek in Windows 7, which enables users to peek through all open windows for a desktop preview by hovering the cursor over a Show Desktop taskbar button.Although Windows 1.Aero effects, those platforms still retain Peek desktop previews.However, some Windows users have reported that the Use Peek setting is grayed out for them.This is how you can fix a grayed out peek at desktop setting in Windows 781.Update-Your-Video-Card-Drivers-on-Windows-7-Step-4-Version-2.jpg/aid1681913-v4-728px-Update-Your-Video-Card-Drivers-on-Windows-7-Step-4-Version-2.jpg' alt='Aero Display Driver Windows 7 Download' title='Aero Display Driver Windows 7 Download' />Check the Enable Peek Setting.First, check that Enable Peek is selected on the Visual Effects tab.To open System Properties, press the Win key R keyboard shortcut, input Sysdm.Windows_8_Aero_Lite_Theme_Windows_7.png' alt='Aero Display Driver Windows 7 Download' title='Aero Display Driver Windows 7 Download' />Runs text box and press OK.Select the Advanced tab on the System Properties window.Press the Performance Settings button on that tab to open the window below.If its not already selected, click the Visual Effects tab.Click the Enable Peek check box if its not selected.Press the Apply and OK buttons to confirm selected settings.Edit the Registry.Earlier this month, Microsoft made the Windows 7 beta available for anyone to download and test drive it.Unless you have a spare computer, it can be somewhat.You can also fix the Peek setting with a registry edit.Open Run with the Win key R hotkey, and then enter regedit to launch the Registry Editor.Click REGEDIT, HKEYCURRENTUSER Software Microsoft Windows DWM on the left navigation pane as below.Now you can double click Enable.Aero. Peek to open the window in the snapshot directly below.Run the Aero Troubleshooter in Windows 7.This is as fix more specifically for Windows 7 users.Some Windows 7 editions include an Aero troubleshooter that might help fix Aero Peek.You can run the Windows 7 Aero troubleshooter as follows.Press the Start button and enter aero in the search box.Now select Find and fix problems with transparency and other visual effects to open the Aero troubleshooter window.Click Advanced and select the Apply repairs automatically option.Press the Next button to run the scan.If the troubleshooter fixes anything, you can click View detailed information for further details about detected issues.Select an Aero Theme.Windows 7 users might find the Use Aero Peek to preview desktop option is grayed out for non Aero themes.As such, if Windows 7 currently has a non Aero theme, change it to an Aero theme instead by right clicking the desktop and selecting Personalize.Then select an alternative Aero theme.Disable the Log. Me.In Driver. The Log. Trial Version Of Microsoft Publisher 2008 . Me. In remote desktop software disables Aero Peek.The programs driver is incompatible with Windows Aero.So if youre using Log.Me. In, consider removing the program and replacing it with alternative remote desktop software.Or you can disable the Log.Me. In driver as follows.Open Run, enter devmgmt.OK to open the Device Manager window below.Select Display Adapters and right click the Log.Me. In driver listed there.Select the Disable option on the context menu.Then restart Windows when prompted.Close Anti Virus Software.Anti Virus software can also block the Enable Aero Peek option.If that happens, the setting might not be visible at all.So closing, or at least disabling, anti virus programs might also fix Peek.You can usually disable anti virus software from system tray.To do so, you can right click the softwares system tray icon and then configure the shield controls from the context menu.Alternatively, close the anti virus utility with Task Manager by right clicking the taskbar and selecting Task Manager.Click the Processes tab, and then scroll down to the software listed under Background processes.Select the anti virus utility and press End task to close it.Now open the taskbar settings or the Taskbar and Start Menu Properties window to select the Use Peek option.The peek at desktop setting will no longer be grayed out Thus, you can preview the desktop with the Show Desktop button once more.Windows Display Driver Model Wikipedia.Windows Display Driver Model WDDM1 is the graphic driver architecture for video carddrivers running Microsoft Windows versions beginning with Windows Vista.It is a replacement for the previous Windows 2.Windows XP display driver model XDDMXPDM3 and is aimed at enabling better performance graphics and new graphics functionality and stability.Display drivers in Windows Vista and Windows 7 can choose to either adhere to WDDM or to XDDM.With the removal of XDDM from Windows 8, however, WDDM became the only option.WDDM provides the functionality required to render the desktop and applications using Desktop Window Manager, a compositingwindow manager running on top of Direct.D. It also supports new DXGI interfaces required for basic device management and creation.The WDDM specification requires at least Direct.D 9 capable video card and the display driver must implement the device driver interfaces for the Direct.D 9. Ex runtime in order to run legacy Direct.D applications it may optionally implement runtime interfaces for Direct.D 1. 01. 0. 1 and higher.Features enabled by the WDDMeditWDDM drivers enable new areas of functionality which were not uniformly provided by earlier display driver models.These include Virtualized video memoryeditIn the context of graphics, virtualization means that individual processes in user mode cannot see the memory of adjacent processes even by means of insertion of forged commands in the command stream.WDDM drivers allow video memory to be virtualized,6 and video data to be paged out of video memory into system RAM.In case the video memory available turns out to be insufficient to store all the video data and textures, currently unused data is moved out to system RAM or to the disk.When the swapped out data is needed, it is fetched back.Virtualization could be supported on previous driver models such as the XP Driver Model to some extent, but was the responsibility of the driver, instead of being handled at the runtime level.SchedulingeditThe runtime handles scheduling of concurrent graphics contexts.Each list of commands is put in a queue for execution by the GPU, and it can be preempted by the runtime if a more critical task arrives and if it has not begun execution.This differs from native threads on the CPU where one task cannot be interrupted and therefore can take longer than necessary and make the computer appear less responsive.A hybrid scheduling algorithm between native and light threads with cooperation between the threads would achieve seamless parallelism.It is important to note that scheduling is not a new concept but it was previously the responsibility of individual driver developers.WDDM attempts to unify the experience across different vendors by controlling the execution of GPU tasks.Cross process sharing of Direct.D surfaceseditA Direct.D graphics surface is the memory area that contains information about the texturedmeshes used for rendering a 2.D or 3. D scene. WDDM allows Direct.D surfaces to be shared across processes.Thus, an application can incorporate a mesh created by another application into the scene it is rendering.Sharing textures between processes before WDDM was difficult, as it would have required copying the data from video memory to system memory and then back to video memory for the new device.Enhanced fault bilancementedit.Windows Vista alerting the user of a successful WDDM recovery.If a WDDM driver hangs or encounters a fault, the graphics stack will restart the driver.A graphics hardware fault will be intercepted and if necessary the driver will be reset.Drivers under Windows XP were free to deal with hardware faults as they saw fit either by reporting it to the user or by attempting to recover silently.With a WDDM driver, all hardware faults cause the driver to be reset and the user will be notified by a popup this unifies the behavior across vendors.Previous drivers were fully implemented in kernel mode, whereas WDDM is implemented partly in user mode.If the user mode area fails with an unrecoverable error, it will, at the most, cause the application to quit unexpectedly instead of producing a blue screen error as it would in previous driver models.WDDM also allows the graphics hardware to be reset and users to update drivers without requiring a reboot.LimitationseditThe new driver model requires the graphics hardware to have Shader Model 2.However, according to Microsoft as of 2.Windows Vista used the XDDM,1.WDDM capable. It also requires some other hardware features consequently some SM 2.Intel GMA 9. 00 fails the WDDM certification.One of the limitations of WDDM driver model version 1.If a multi monitor system has more than one graphics adapter powering the monitors, both the adaptors must use the same WDDM driver.If more than one driver is used, Windows will disable one of them.WDDM 1. 1 does not have this limitation.WDDM 1. 01. 1 does not allow some modes that were previously handled by the driver such as spanning mode stretching the desktop across two monitors1.Dual View is still available.Need for a new display driver modeleditOne of the chief scenarios the Windows Display Driver Model enables is the Desktop Window Manager.Since the desktop and application windows managed by DWM are Direct.D applications, the number of open windows directly affects the amount of video memory required.Because there is no limit on the number of open windows, the video memory available may prove insufficient, necessitating virtualization.As the window contents that DWM composes into the final desktop are generated by different processes, cross process surface sharing is necessary.Also, because there can be other Direct.X applications running alongside DWM on the DWM managed desktop, they must be able to access the GPU in a shared manner, necessitating scheduling.Though this is true for Microsofts implementation of a composited desktop under Windows Vista, on the other hand, a composited desktop need not theoretically require a new display driver model to work as expected.Successful implementations of composited desktops were done before Windows Vista on other platforms such as Quartz, Compiz, Window.FX. The approach Microsoft attempted was to try to make sure WDDM was a unified experience across different GPUs from multiple vendors by standardizing their features and performance.The software features missing from other driver models could be made immaterial by extensions or if a less restrictive or simply different driver model was in place.HistoryeditWDDM 1.Windows Vista introduced WDDM 1.HDCP. 1. 7WDDM 1.Windows 7 supports major additions to WDDM known as WDDM 1.Win. HEC 2. 00. 8.New features include 1.Hardware acceleration of GDI and Direct.DDirect. Write operations helps reduce memory footprint in Windows 7, because DWM compositing engine no longer needs to keep a system memory copy of all surfaces used by GDIGDI, as in Windows Vista.DXGI 1. 1, Direct.D 1. 1, Direct. 2D, and Direct.Write were made available with Windows Vista Platform Update however GDIGDI in Vista continues to rely on software rendering2.Desktop Window Manager continues to use Direct.D 9. Ex. 2. 6WDDM 1.WDDM 1. 0 specification both 1.Windows Vista with or without the Platform Update.WDDM 1. 2editWindows 8 includes WDDM 1.DXGI 1. 2. 2. 82.New features were first previewed at the Build 2.D rendering and video playback.Other major features include preemptive multitasking of the GPU with finer granularity DMA buffer, primitive, triangle, pixel, or instruction level,3.Windows 8, and Direct.D 1. 1 Video supports YUV 4 4 44 2 24 2 04 1 1 video formats with 8, 1.WDDM 1. 2 supports display only and render only WDDM drivers, such as Microsoft Basic Display Driver3.WARP based Microsoft Basic Render Driver which replaced kernel mode VGA driver.WDDM 1. 01. 1 only allows rudimentary task scheduling using batch queue granularity improvements to multitasking, as well as fast context switching and support for virtual memory, were initially expected in versions tentatively named WDDM 2.WDDM 2. 1, which were announced at Win.HEC 2. 00. 6. 3. 33.WDDM 1. 3editWindows 8.WDDM 1. 33. 6 and DXGI 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |