I get that with Win98 after a while using lots of graphic resources in projects.
Its because Win98 has limited GDI resources. WinXP has unlimited GDI resources and that should not happen.
It's strange.
What happens if you close other applications down and only have Scope running?.
<font size=-1>[ This Message was edited by: Aries on 2006-04-21 07:14 ]</font>
oops, I read the first post, but some info went in & straight back out
XP SP2 here & that doesn't happen with optimaster as an STM insert (which is how we normally use it) or as standalone device, so it's not an optimaster bug. That much I know
Is XP running in 'classic' modes with everything tweaked for performance?
Are you running the latest ATi drivers? If so, you might want to try older drivers if all else fails.
I think someone here on Z will have the answer for you Paul, but as usual with problems, some more (well, a lot more) info on your system, system settings & graphics settings etc would be a big help in terms of giving you constructive advice.
If you're sure it only happens with optimaster, try this:_ remove the optimaster device from it's Scope directory location. Restart Scope with a project which isn't looking for it. Close Scope, Restart computer. Obtain a new copy of the optimaster device file. Put the optimaster device file back in it's intended location & restart Scope. Check if the redraw bug still happens with optimaster & only optimaster.
On 2006-04-21 09:22, paulrmartin wrote:
Shroomz, thanks for your eagerness to help but I stated in the 3rd post of this thread that it doesn't happen only with Optimaster.
What happens if you close all other programs down (sequencer, etc) and only have Scope running?.
I looked at my ATI settings and I was not using Default Monitor in there. I changed it back but I have to finish a job before I reboot and check if this fixed the problem.
Well, I rebooted and loaded up as many crazy modules I could without a hitch. It must have been the default monitor setting that was messing things up.