Re: Layered Windows in VMWare and Terminal Services
- From: "Ivan Brugiolo [MSFT]" <ivanbrug@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Dec 2007 14:17:57 -0800
Does this behavior reproes, for example, on the local machine,
without WMWare or anything else, when you have installed
the VGA display driver and you change,
for example, from 800x600@32bpp to 800x600@16bpp,
or from 800x600@32bpp to 1024x768@32bpp ?
In general, Layered Windows can be of two kind:
ULW (from UpdateLayeredWindow) or SLWA (SetLayeredWindowAttribute).
ULW window are always backed by a system memory redirection
surface, while SLWA may have a video-memory copy, depending
on what the display driver supports,
and if you are running Win20009, WinXp, Win2003 or Vista.
You naturally understand that any display-driver realization is lost
and possibly transfered between mode-changes, but, the system is
designed in such a way that either the resource is transferred (the ULW
case),
or, if it is destroyed, the application is asked to repaint
in order to recreate the resource underneath (this would be the SLWA case).
That said for the general theory of mode-changes, I seem to remember
that most of the Visual Machine software do emulate some well-known
ancient video-card (for example, an S3 from the late 90's), for which
either VGA.sys is the display driver, or, some un-optimized compatible
display driver is used.
Can you describe, at this point, a little bit better what the application
is doing, what are the expected results, and what are the actual results ?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Fredo" <fredo@xxxxxxxxxxx> wrote in message
news:t7CdnabLGasLs_XanZ2dnUVZ_tOtnZ2d@xxxxxxxxxxxxxxx
Our application uses layered windows in several places and, invariably, we
have issues running the app inside Terminal Services and VMWare.
I've noticed that, at least in VMWare (I haven't tested this in terminal
services yet), if I change the screen resolution while the app is running
(even if I change it and then change it back to the original settings),
the app then displays properly until I close the app. It's like something
gets triggered by the resolution change that makes layered windows work.
Does anyone have any idea what might be going on here? Maybe it's
something I can reproduce programmatically (without actually changing the
screen resolution).
Thanks
.
- Follow-Ups:
- References:
- Layered Windows in VMWare and Terminal Services
- From: Fredo
- Layered Windows in VMWare and Terminal Services
- Prev by Date: Layered Windows in VMWare and Terminal Services
- Next by Date: Matrix
- Previous by thread: Layered Windows in VMWare and Terminal Services
- Next by thread: Re: Layered Windows in VMWare and Terminal Services
- Index(es):
Relevant Pages
|
Loading
