Disable Fake Window Overlay

  • Thread starter Thread starter Tom McDonnell
  • Start date Start date
T

Tom McDonnell

There is this 'feature' in NT5.1 which overlays a fake window that
doesn't get updated over the top of a window that is consuming a lot of
processor cycles or something. How can it be disabled?

Why do I want it disabled? With dual monitors the fake window gets left
behind masking a quarter of one of the monitors, and programs appear
frozen when they are actually doing something.
 
I doubt you can. This happens when a window freezes. A freeze is where the program is not picking up it's messages (and thus Windows can't get the program to redraw). A freeze is detected by the program not picking up any messages in so many seconds. Poorly designed programs will appear to freeze. You programs should be picking up their messages.

Windows draws what it cans for frozen programs as it knows a lot will come good.
 
A freeze is where the program is not picking up it's messages (and thus Windows can't get the program to redraw).
Ok, of course, that is the reason.
Poorly designed programs will appear to freeze.
Click to expand...
On non-NT 5.1 OSes yes, but on 5.1 we get a non-updating window
overlayed. I don't have this problem on NT5.0, just 5.1, a Get Latest
Version from Source Safe in Visual Studio 2003 causes this freez-a-thon,
where I'm left to guess what is happening cos the window can't update.

No dis to you David, this is down to MS.
 
There is this 'feature' in NT5.1 which overlays a fake window that
doesn't get updated over the top of a window that is consuming a lot of
processor cycles or something. How can it be disabled?

Why do I want it disabled? With dual monitors the fake window gets left
behind masking a quarter of one of the monitors, and programs appear
frozen when they are actually doing something.
Click to expand...

Sorry, I've never heard of this as a feature of the operating system. It
sounds more like a setting that would be managed by the application.
 
Sorry, I've never heard of this as a feature of the operating system. It
sounds more like a setting that would be managed by the application.
Click to expand...

Never mind and apologies.
 
Suggest checking in one of the VS.Net newsgroups, especially the one dealing
with VSS, since this is where you are having the issue. Personally, it
sounds as if the VSS server and/or the VSS clients are improperly
configured, or improperly coded "user exits" have been applied.

--

Star Fleet Admiral Q @ your Service!

http://www.google.com
Google is your "Friend"
 
Back
Top