So should I turn off the folding while playing games? Or is there an easier solution to the problem I am having when playing GTA San Andreas?
I believe there's an interaction between Folding@Home on Windows and games that use OpenGL graphics. I don't know whether GTA uses OpenGL, but if it does that may be the problem.
The best solution if this is the case is probably to run the non-graphical, command line version of Folding@Home, as that doesn't run a graphical display of the protein and therefore shouldn't have any interaction with OpenGL. The folding client software itself is supposed to have minimal impact on other programs. It should reduce its CPU usage as soon as other programs need heavy lifting.
I gave a link to the command line client in an earlier post.
If I pause it, then quit, does it lose all the work?
The folding client checkpoints its progress, and can usually restore its condition to the last checkpoint after a reboot, a quit, or even after a crash. I'm running the SMP beta for Mac OS X, and this works fine. The folding process seems to fail if I pause it, and it then has to restart the work unit when I resume it, but I suspect this is a bug in the beta version I'm running.