Mouse Trails in AREV (AREV Specific)
At 25 FEB 2002 07:37:17PM Donald Bakke wrote:
A client is reporting that when they run AREV in full screen on their XP machine (I believe it's a Gateway P4 with LCD monitor) that a trail of blocks appear whenever the mouse is moved. These blocks do not go away. There are no problems when running AREV in windowed mode.
Has anybody seen this or know what the problem might be?
Thank you,
At 26 FEB 2002 10:07AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Don,
We're guessing here. As an experiment, try adjusting the Windows video resolution (640*480/800*6000/1600*1200 etc) and see what transpires. If the problem persists, we're tipping that the mouse driver is interacting with the video array. If you can get it into full screen mode, then that may help. Optionally, turn off BIOS shadow RAM and see if you can shake it that way. Another option would be to try another brand of mouse (hopefully with a different driver, and thus a different video address). There might also be some Windows shortcut properties in the Misc tab to toggle (try different fonts). Logitech mouse?
World Leaders in all things RevSoft
At 26 FEB 2002 02:10PM Donald Bakke wrote:
Sprezz,
As an experiment, try adjusting the Windows video resolution (640*480/800*6000/1600*1200 etc) and see what transpires.
Did that, no help.
If you can get it into full screen mode, then that may help.
The problem only occurs in full screen mode.
Optionally, turn off BIOS shadow RAM and see if you can shake it that way.
Haven't tried that yet.
Another option would be to try another brand of mouse (hopefully with a different driver, and thus a different video address).
Haven't tried that yet either.
There might also be some Windows shortcut properties in the Misc tab to toggle (try different fonts).
Tried everything under the sun with this.
Logitech mouse?
Gateway's optical USB mouse. Don't know if they simply put their name on another manufacturer's brand, but I suspect they do. We'll experiment with another mouse.
Thanks for the feedback. Looks like there's a few other things we can try.