• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Weird Folding@Home lockup issue - Catalyst 3.7's to blame?

Jeff7

Jeff7

Lifer
This started sometime around when I installed the Catalyst 3.7's, I think. I'm using the F@H screensaver dealy.
Anyway, whenever I go to the Screensaver tab of Display Properties, with F@H as the screensaver, the system locks up dead. In Safe Mode, I just get an error in opengl32.dll, and the Display Properties window locks up. So what gives here - the Catalyst 3.7's are just fine otherwise; is this just one bug they bring? Or did I get a corrupted install that seems to cause no other problems at all.
Any suggestions for settings to change? Basic specs:
8RDA+ motherboard
Radeon 9700 Pro
WinXP Pro SP1
 
I've had that happen with other screensavers, on other systems where a different video card was being used. The F@H screensaver is a buggy and slow program, and if you're wanting to run F@H with graphics I'd highly suggest the GUI client that runs in the system tray (but can be maximized to show the OpenGL rendering when you want it), as it's much faster and (in my experience) stable.
 
Originally posted by: OverVolt
Better yet just run the CLI client, i love it
Click to expand...

How does that go - does it run at lowest priority all the time, or better yet, is there a way of making it kick in after a certain period of inactivity, similar to a screensaver?
 
Originally posted by: Jeff7
Originally posted by: OverVolt
Better yet just run the CLI client, i love it
Click to expand...
How does that go - does it run at lowest priority all the time, or better yet, is there a way of making it kick in after a certain period of inactivity, similar to a screensaver?
Click to expand...
The GUI and CLI clients run at the lowest priority all the time, and do not appear to have any noticeable impact on performance. The advantage of having a client that runs all the time is that it can use spare cycles even while you're working on the computer. For example, if you're typing a document in a word processor, you may only be using 10% of the CPU for that task, leaving the other 90% to waste; with the CLI or GUI clients, that time would not be wasted, and F@H would be able to do much more work, without affecting your work at all.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top