Oh well I'll tell ya I wrote this huge reply to this tread and explained it all but it took so lonk to type it when I pressed submit it vanished. I copied it first just in case. Look I had this same problem with Mojoworld. Mojoworld is even harder on the cpu that Vue. It make the computer unusable while rendering. I had a program that showed the cpu usage. The link for it is posted here somewhere cause it was that link of how I found it in the first place. I don't know the name of the program. This is not my computer I'm using so I cannot look it up. In XP and 2000 you can adjust the cpu priority of most programs. You can't in ME and 98 without some extra program. The glitches. The screen refresh. Things in the active render will vanish from the screen but they're rendering just fine. File will save just fine. Just ignore it. Say it's in idle when a complete line is done. The line will save fine but it may not show it on the screen. In Mojoworld whole blocks vanish but they're there also when you save the file you just can't see them. What you do is set the program to idle. It will render at almost 100% cpu when it's in focus but if you start up something else it will drop to almost 0% while the other program is being used to do somthing. As soon as extra cycles are available it will shoot back up to almost 100% rendering but it will back off to allow other programs to run if needed. This is what most people expect the computer to behave like. Normal cpu priority will not give you that when it comes to rendering but Idle does. Search google for "cpu priority" with quotes for instructions on how to change it for programs. There is lots of links, you want only the links that show you how to set individual programs and not the entire computer. Other glitches. Crashing other programs while doing this may crash the render too. It's adds a bit of risk.