The 4.0 client is out of beta now, and available for general download:
http://www.stanford.edu/group/pandegrou ... nload.html
4.0 client official released
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
I almost did the "lazy jerk" thing and posted asking what the changes are in 4.0. In contrition, I went to the F@H site and looked for myself. Here are some highlights:
- Configurable minimum checkpointing frequency (3-30 minutes). (In GUI, controlled with a slider.)*
- If client run with verbosity of at least 5, FahCore_78 will print out a message whenever a timered checkpoint occurs.*
- -configonly flag added to configure then exit.
- -oneunit flag added to exit after completing one unit.
- -forceSSE flag added. Returns -forceasm to its former meaning of forcing assembly generally, and takes on the function of forcing SSE specifically.*
- Warnings printed if -forceasm/-forceSSE flags given.
- Benchmarking not done except at start of normal operation (for example, not if only configuring, listing queue, deleting unit, etc.).
- Warning if attempt to run client with Machine ID of already running client (catches most common cases, including if running same client twice)
- Upon finishing a unit, if fails to return the result but succeeds in getting new work, immediately tries sending all results again.
- Checks user name and team number for legality of use in statistics. (In GUI, gives popup error).
- Assignment/work server request authentication
- CPU usage default of 100 printed out during Configuration.
- Maximum machine IDs raised to 8.
- Upload and download bandwidths estimated to send to AS.
- If fails to post data, includes server and port in message. Also outputs HTTP status code (before this was only done if I.E. settings used).
- Bug fixed where performance fraction could exceed 1.
- Version information added to executables.
* Items with an asterisk require FahCore_78.exe v. 1.53 to be functional -- certain work servers are already forcing downloads of this core.
- Configurable minimum checkpointing frequency (3-30 minutes). (In GUI, controlled with a slider.)*
- If client run with verbosity of at least 5, FahCore_78 will print out a message whenever a timered checkpoint occurs.*
- -configonly flag added to configure then exit.
- -oneunit flag added to exit after completing one unit.
- -forceSSE flag added. Returns -forceasm to its former meaning of forcing assembly generally, and takes on the function of forcing SSE specifically.*
- Warnings printed if -forceasm/-forceSSE flags given.
- Benchmarking not done except at start of normal operation (for example, not if only configuring, listing queue, deleting unit, etc.).
- Warning if attempt to run client with Machine ID of already running client (catches most common cases, including if running same client twice)
- Upon finishing a unit, if fails to return the result but succeeds in getting new work, immediately tries sending all results again.
- Checks user name and team number for legality of use in statistics. (In GUI, gives popup error).
- Assignment/work server request authentication
- CPU usage default of 100 printed out during Configuration.
- Maximum machine IDs raised to 8.
- Upload and download bandwidths estimated to send to AS.
- If fails to post data, includes server and port in message. Also outputs HTTP status code (before this was only done if I.E. settings used).
- Bug fixed where performance fraction could exceed 1.
- Version information added to executables.
* Items with an asterisk require FahCore_78.exe v. 1.53 to be functional -- certain work servers are already forcing downloads of this core.
Just to fill in for those who missed the opening credits...wussboy wrote:Is there any way I can run this without losing my current WU?TRC-13 wrote:Yes. It converts the queue.
- Once you upgrade to 4.0, there is no going back to 3.xx since the 'queue' file is converted.
- You SHOULD just be able to stop Folding@Home and fire up 4.0, which will recognize that it needs to convert the queue, and take up where the 3.xx client left off. To be extra safe, wait till the completion of a WU to upgrade. At that point, even if things get totally trashed, you won't loose anything.
David