Well the title says it all. I'm just in the process of downloading. These last days have seen a lot of new versions..

---

[cynic mode-on]
Yup, I'm downloading it also, at least we'll have it installed before the cogent link goes down for the weekend. Also, atleast we'll have the whole weekend to find the weak spots in this one.
[cynic mode-off]

BRB, with my assessment, waiting for d/l to finish.

Let me know what your first impressions are when you've run it for a while. I'm getting a little shy about racing to run the latest dev version the minute it's out.

---

installation went smooth.

4.38 benchmarks:

11/05/2005 11:20:28|| Number of CPUs: 1
11/05/2005 11:20:28|| 1978 double precision MIPS (Whetstone) per CPU
11/05/2005 11:20:28|| 3822 integer MIPS (Dhrystone) per CPU

4.39 benchmarks:

13/05/2005 00:21:02|| Number of CPUs: 1
13/05/2005 00:21:02|| 2019 double precision MIPS (Whetstone) per CPU
13/05/2005 00:21:02|| 3770 integer MIPS (Dhrystone) per CPU

---

LOL, still running 4.19 /w optimized crunchers for now...

---

Aloha, Uli

Yeah, installed it, until now it looks good. Manual Update is working again.

Would like to get some infos, how the new scheduling in 4.39 is working. Are there differences / changes to the descriptions from 4.38 or is 4.39 only a bugfix ?

---

Supporting BOINC, a great concept !

Slight issue found with 4.39...

With LHC@Home, the client is sending the scheduler request twice when requesting new work.

13/05/2005 8:43:43 AM|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
13/05/2005 8:43:43 AM|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
13/05/2005 8:43:45 AM|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded

Same with SETI:

13/05/2005 8:56:57 AM|SETI@home|Requesting 604800.00 seconds of work
13/05/2005 8:56:57 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
13/05/2005 8:56:57 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
13/05/2005 8:56:58 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

Not sure if this means the server is receiving two requests or not, but if it is, then it would be placing unneeded strain on it.

---

Installs went well on AMD and Intel... no strange warnings... buttons work... not asking for un-needed work... so far so good.

5/12/2005 6:00:12 PM||Finished CPU benchmarks
5/12/2005 6:00:12 PM|climateprediction.net|Deferring computation for result 2383_200118483_1
5/12/2005 6:00:12 PM|SETI@home|Resuming computation for result 27dc04aa.2258.30242.997154.70_4 using setiathome version 4.09
5/12/2005 6:00:12 PM||Resuming computation and network activity
5/12/2005 6:00:12 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
5/12/2005 6:00:13 PM||schedule_cpus: must schedule
5/12/2005 6:00:14 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded

---

7,049 S@H Classic Credits

Well, my story is a little different. I signed off, uninstalled, signed back on, Installed 4.39. My mcafee asked for access permission for the manager, but not the Client. I tried to "project update" to report my uploaded WUs. It failed. I shut down the puter and restarted. The manager took a minute or two to display the tab windows(stupid hour glass forever), then I signed online. Then I as prompted to give the client access, then everything started working like it should. So far. In 3 minutes a PPAH WU will finish and I'll be able to tell more. Oh yeah, Manual update now works again.

5/12/2005 6:42:31 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
5/12/2005 6:42:34 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

PPAH finished and uploaded and reported:

5/12/2005 6:57:54 PM|ProteinPredictorAtHome|Computation for result h0007A_1_22923_0 finished
5/12/2005 6:57:54 PM||schedule_cpus: must schedule
5/12/2005 6:57:54 PM||earliest deadline: 1116404429.000000 h0007A_1_26539_3
5/12/2005 6:57:54 PM|ProteinPredictorAtHome|Starting result h0007A_1_26539_3 using mfoldB125 version 4.28
5/12/2005 6:57:55 PM|ProteinPredictorAtHome|Requesting 11547.60 seconds of work
5/12/2005 6:57:55 PM|ProteinPredictorAtHome|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
5/12/2005 6:58:01 PM|ProteinPredictorAtHome|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded

So, I'd give this one a shot if I were you.

WARNING 4.39 is "Developmental" Software and can do strange things. Stick with "Official" release software if you're not ready to accept the risks.

---

WARNING 4.39 is "Developmental" Software and can do strange things. Stick with "Official" release software if you're not ready to accept the risks.

Roll the dice and let it ride, baby!!

---

7,049 S@H Classic Credits

<blockquote>Roll the dice and let it ride, baby!!</blockquote>

The warning/Boiler plate disclaimer is added so that new people won't think they need to download the new client. In the Past I've seen user "Swear" they were "forced" to upgrade, and wasn't happy. We don't need people complaining when Developmental software goes terribly wrong.

Hi All,
I have noticed that the problem with "connection failed" is not happening anymore. Seems to be working great so far.


Respectfully,

Rocky

---

www.boincsynergy.com

I too am getting 'double hits'. I only run SETI
This log straight after re-boot - no buttons touched.

13/05/2005 00:20:00|SETI@home|Resuming computation for result 28ja05aa.5288.4514.379824.174_2 using setiathome version 4.11
13/05/2005 00:20:02|SETI@home|Requesting 9311.25 seconds of work
13/05/2005 00:20:02|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
13/05/2005 00:20:02|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
13/05/2005 00:20:02||schedule_cpus: must schedule
13/05/2005 00:20:03|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
13/05/2005 00:20:03|SETI@home|Message from server: Not sending work - last RPC too recent: 539 sec
13/05/2005 00:20:03|SETI@home|Deferring communication with project for 10 minutes and 0 seconds

This also happened before the re-boot when I clicked update - and BOINC.EXE went 95% CPU, but did respond to window close, and exit from system tray.

---

<blockquote>Hi All,
I have noticed that the problem with "connection failed" is not happening anymore. Seems to be working great so far.


Respectfully,

Rocky</blockquote>

FYI, You Must Reset your permissions in you use a fire wall
other wise you will get a cant connect, But yet BOINC is running under Task Manager!

---

Your language deteriorates Tim. I'm wondering why people don't use a firewall that doesn't ask you every 2 seconds if something is allowed to go through or not. My software firewall doesn't.

---

<blockquote>Your language deteriorates Tim. I'm wondering why people don't use a firewall that doesn't ask you every 2 seconds if something is allowed to go through or not. My software firewall doesn't. </blockquote>
Because if a trojan is sneaky enough to overwrite a trusted .exe, (as many are known to do...) it has full access to the net. Do you really want that? I sure don't! I would much rather have a firewall that knows when an .exe (previously trusted) has changed, and lets me know when it wants to access my connection.

But hey, maybe that's just me. ;)

Edit: Oh, and back on topic, 4.39 appears to be running well for me. I haven't seen any double scheduler requests. -knock on wood-

---

Hey,

4.39 didn't last long - 4.40 is already out!!!

---

Cheers,
Gary.

<blockquote>Hey,

4.39 didn't last long - 4.40 is already out!!!</blockquote>

Gary, you were the first, would you start the new thread? Its your honor.

tony

---

<blockquote><blockquote>Hey,

4.39 didn't last long - 4.40 is already out!!!</blockquote>

Gary, you were the first, would you start the new thread? Its your honor.

tony</blockquote>

Already done thanks mate!! You're a true gentleman :).

---

Cheers,
Gary.

<blockquote>Hey,

4.39 didn't last long - 4.40 is already out!!!</blockquote>
#^%$&!