Folding Forum

I have a suggestion for the current 6.30 beta client. in short, default to -smp flag unless either the cpu is single core. allows a manual overriden. The pseudo code is: //something to think about: /*if(hyperthreading enabled) number of cores /= 2;*/ if(single cpu) run uniprocessor work units; else ...

reverse engineering F@H probably isn't something PG appreciates.

if they had some extra cash to spend on development i'd suggest a way to cancel a work unit and notify the server (maybe even upload a partially completed wu) .. even though it isn't something that is needed often. i've had to abandon some wus in the past every now and then when configuring and reco...

it just seems to me that if the contribution was large enough, like an Alzheimer's group offering an insane amount of computing power if it was used for alzheimers research only, for example. would be a good thing. this way there isn't any neglect for other disease by the general folding@home userba...

What about cherry picking disease (or other objective) without being able to cherry pick the actual project numbers for that disease?

has anyone ever compiled a brochure or pamphlet for promoting Folding@Home?

hopefully new client will do away with the machine id concept and try to manage it automatically.

I'd go with the v6.30 SMP client. I'd like to point out a potential problem to people who are new to folding@home. You should know that this client now supports both single processor and multiple cores. If you do not specify the -smp flag when running the client, it will default to single processor ...

can you try running with -verbosity 9 so maybe can see more information about the connection error? it looks like a network issue more than anything else, but I'd like to see more info to be sure.

edit:
yes, you must have the port (and/or the ip address) allowed in your firewall, if you have one.

it isn't battery efficient but if you want to leave your cell phone folding over night while its on the charger, I see no problem. minimal resources would demand minimal work units, though.

I have only been folding for a few years (circa 2007), but when I really got into the idea, I end up spending a majority of my inheritance money to build machines for the main purpose of folding. I will continue to invest in new hardware when ever I can.

* automatically sense all available openCL targets and make full use of these targets by default (recommended)
* manual override to tell the science cores to only run on user-specified openCL targets

I am putting off recruiting new F@H users until an easy to use unified client is available. when it is released there should be a mass media frenzy for it and capitalize on that. i suggest that in anticipation, compile a list of journalists that would be ideal to communicate with once a unified clie...

next gen cpu from intel and amd have a new parallelization architecture. this introduces a 256 bit SIMD capability with the addition of a few new assembly instructions. It is assumed that this target will be supported through OpenCL. It would be interesting to fully utilize your CPU's parallel capab...

Strange behavior. this particular WU refuses to do any work. [06:33:12] + Processing work unit [06:33:12] Core required: FahCore_82.exe [06:33:12] Core not found. [06:33:12] - Core is not present or corrupted. [06:33:12] - Attempting to download new core... [06:33:12] + Downloading new core: FahCore...