I had to uninstall my video driver, because the chipset drivers say they should be installed first. Too bad I didn’t read that earlier. So I installed the chipset drivers and then the video driver again. Plus, I had to re-activate Windows XP 64 because the chipset drivers changed the hardware profile.

Before I could install the drivers, I had to go into the Services console to set the disabled services to Automatic. I probably could have set the disabled services to Manual as well. 

Then I tested Vue 64 again. I also looked at the Task Manager. There were a dozen new services running.  Vue reported that it would take 2 hours to render “Peeking Through”.

I turned the unneeded services back to disabled. I have these unneeded services listed in a text file, so that I can remember which services to turn-off. Four or five reboots later and some tweaking, I was able to get a VueMark score of: 

647 

That was the last run of the evening. The next morning I cold-booted XP-64 and ran Vue/VueMark.  The render times were scaled by a factor of four. I cut the renders short and tried again. This time the renders were scaled by a factor of two. I ran out of time and left for work.

Start a new day – get a new service running? I don’t know. An e-onsoftware tech has acknowledged that background services can slow a render down. Their waiting for some additional feedback from me on what progress I make by cutting back services.

Now, I’m off to XP-64. I’m planning on setting some of the Automatic services to Manual.  Then run one test after another. 

Also, I ran XP-32 and Vue/VueMark today when I got home from work. My score was: 

591 

I’ve yet to tweak XP-32.

I admit I’m still confused why I get a fast render and then a very slow render. 

I read about the PriorityMaster during my research on priority.  It looks like a valid $40 program, except that Vue changes its priority after its start-up which is when PriorityMaster asserts itself.

I also read about a program that uses a configuration file to set its process priority. In other words, the programmer’s are empowering the user to decide how to run the program (e-onsoftware are you listening?).

Charles