Skywise <into@oblivion.nothing.com> wrote:

DaveT <svirtftcyt@yahoo.com> wrote in
news:oavau4dgrv1fp2hpft9ue6lamacmecos5l@4ax.com: 

A pleasant side-effect...
I use this computer for three non-Seti functions:
recording HD video, running VMware workstation,
and playing HD video. I only use the Nvidia card 
for playing HD video, otherwise I use the built-in
ATI graphics adapter with a smaller monitor. It 
happens that the ArcSoft video capture program
locks up if I start it with the CPU Seti running, 
I have to suspend it first. Video capture co-exists 
very well with the GPU Seti, however. 

It would do you well to suspend Seti if you intend to
do anything that uses the graphics card. I've had to
three-finger-crash my system a few times before I learned.

I use the onboard ATI graphics adapter for VMware server
and High Def video capture. CUDA co-exists well with these, 
running as it does on the Nvidia card.

Right now, I only use the Nvidia card for (CUDA and) High Def video
playback with the 28" monitor. And yes, I do have to suspend
CUDA for it to work properly. I launch the player on the 15" 
monitor and then drag it over to the 28" monitor and make it
full screen. This is the only way I've found to do this, because
I can't manipulate Windows Explorer on a monitor that's
10 feet away. 

The point I was trying to make is that the Video capture 
application is really the first one I have run into in 9
years and 10 monhs of Seti that is actually interfeared with
by (the CPU version of) Seti. Seti runs at a low priority, so
applications generally run right along side of it with no
problem. Sometimes I might shut down Seti to give them
a little more "umph", but that's all. However, if I forget to stop 
(the CPU) Seti before starting HD video capture, I'll be rebooting.

Dave

Brian