KNOWN BUGS, COMPATIBILITY ISSUES, AND RUNNING NOTES
Please note that the Windows GPU client for Folding@Home is a beta release. While we have done lots of testing in house, there are limits to the bugs we can find in these limited tests (and hence the need for a beta test). As in the use of any beta software, please make sure to back up your hard drive, and do not run this client on any machine which cannot tolerate even the slightest instability or problems.
Thus, we expect that there will be many problems with the client that need to be resolved. Below is a list of some of the relevant known issues or bugs for beta testers of this new client.
Known Bugs
1. The GUI pause core command doesn't work
2. The GUI Client will automatically quit when running fullscreen directx apps (games), it may be a little slow at doing this though
3. In some rare situations, one needs to set the Hardware acceleration to max if the Catalyst install didn't do this. To do this, go into the Display Properties/Settings/Advanced/TroubleShoot tab and double check that the Hardware acceleration was set to "Max".
Known compatibility issues
1. One must use specific Catalyst drivers (6.5 or 6.10) and a recent DX version-- see the HOW TO above
2. The GPU core does not run under WINE in linux (nor do we have plans to support WINE)
Notes for running
1. The GUI client will slow down the scientific core (since both use the GPU heavily). We do not recommend the GUI client for long term use, unless you have two graphics cards.
2. Multiple GPUs are currently not supported (but will be supported in future releases); Crossfire is also not supported -- Crossfire will make FAH run more slowly than using a single GPU (this isn't a bug as much as a fundamental issue regarding the nature of a Crossfire/SLI type architecture).
3. The GPU client is not meant to be run in the background while one uses the computer for applications with heavy GPU usage -- it will greatly slow down the response of programs which make heavy use of a GPU
4. Do not run multiple GPU clients simultaneously -- there will be a huge (non-linear) slow down in performance. We currently do not support multiple GPU configurations, although a second GPU can help speed up the graphics of the GUI.
5. Client looks like it is using lots of CPU time: Graphics drivers must poll the GPU to see if it is done. This will look like a lot of CPU time being used, but nothing is really being done, so one can run other relatively CPU heavy code at the same time. However, we do not recommend running multiple FAH clients, as this can significantly slow down the GPU client.
Trouble shooting EUE's
1. Some Alpha testers have found an excessive number of Early Unit End's (EUE's) -- we have not reproduced that at Stanford or ATI and we need help from beta testers to help track this down. If you see many EUE's (i.e. more than 20%), please make a post in the GPU section of the forum with your system configuration (ATI driver version, DX version, OS) and hardware (card, CPU, motherboard type). With the help of beta testers, we hope to nail down what's going on.
2. If you are seeing lots of EUE's, please download the ATItool application and check that your core voltage is set to 1.4V. This has been shown to lead to problems.
Policy Notes
1. The client will stop working after 2 months (this is a limited release beta -- new clients will be available before the current version ends its test period)
2. Deadlines will be set to be much shorter than normal, as we need to get data back quickly in this beta test and we are releasing to a very specific set of hardware. This will likely change in time, as we move from a beta test and as we move towards supporting other graphics cards.