Vista - Vista windows resize redraw issue in VS2008, Acrobat and others

Vista windows resize redraw issue in VS2008, Acrobat and others

Here is a video describing the problem:

http://m0.interactive.googlepages.com/Vista.wmv

Is anyone looking to FIX this? We do not want a workaround... we need a
fix... All the performance improvement are worth 0% if i spend 10-15% of my
time reseizing.....

The Microsoft Vista team does not really read this for suggestions. There is
a 'feedback' link available in IE help, and the 'contact us' link on the MS
site should get much better response for your problem.

Select a product to start: http://support.microsoft.com/gp/assistsupport

--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales...eAPostAsAnswer
Mark L. Ferguson
..

"arch" <arch@xxxxxx> wrote in message
news:B661D368-4633-4CCA-AC49-10E6A7AAC00E@xxxxxx

Thank you for your response...

I have in fact located the problem... it seems to be connected to Logitech's
Setpoint Software.... ( any version vrom 2.1 to 4.40)

Uninstalling the mouse software fixed the problems... ALL of them.

Used to happen with Logitech’s Setpoint software too, and I stopped using it.
I can’t stop using the wacom driver �.

I have found a couple of applications with this problem.

With the wacom driver installed:

1. Right click on the volume icon and open Volume Mixer. IF the bug is to
occur you will black box corruption in one or more of the sliders.
2. In Visual studio 2008 resizing the window causes the main frame (center
up, middle) to become corrupt and black.
3. Resizing in Adobe Acrobat (guess you already knew about that).

I’ve discovered that while the HID driver is running in the processes window
the error will occur.

Here is a small video with the problem
http://m0.interactive.googlepages.com/Vista.wmv

Please note that this also happens on XP 64.

The older driver DOES NOT have this problem… but it is hard to find on your
web site. I finally found it in the wacom asia via google.
WacomTablet_604-4

ALSO… From what I’ve read Microsoft is aware of the problem and even has a
Knowledge Base article on it as an unresolved issue.


"arch" wrote: