Since I don't see any reason why we should be denied access to beta versions - as long as we remember that they are just that - the new beta (4.46) is available here.

My early experiences are telling me to give this one some time before downloading...I have just had a computational error with a CPDN unit, and the apps keep popping up the graphics windows. It seems to be somehow related to the new client as I wasn't seeing this at all before.

Just my early observations.

[Edit]Wonder how long it might take for this thread to be shut down...[/Edit]

[2nd Edit]New features noted to date - Update all button to update all projects simultaneously. Communications deferrals are counted down in the Status column of the Projects tab. There is a new setting in the options menu designed to set how often I would like to be reminded of possible connection events, ranging from 0-240 minutes, however each time I return to this setting it displays the default 60 minutes regardless of my changes.[2nd Edit]

---

Kolch - Crunching for the BOINC@Australia team since July 2004.
Search for your own intelligence...

Since I don't see any reason why we should be denied access to beta versions - as long as we remember that they are just that - the new beta (4.46) is available here.

My early experiences are telling me to give this one some time before downloading...I have just had a computational error with a CPDN unit, and the apps keep popping up the graphics windows. It seems to be somehow related to the new client as I wasn't seeing this at all before.

Just my early observations.

[Edit]Wonder how long it might take for this thread to be shut down...[/Edit]

i snagged a copy, just in case i feel daring later today...i'm still using 4.25...every version after that wants to crunch seti...and only seti...leaving einstein sitting with nothing to do for days...so maybe they've fixed that particular problem in this version.

---

PROUD TO BE TFFE!

i snagged a copy, just in case i feel daring later today...i'm still using 4.25...every version after that wants to crunch seti...and only seti...leaving einstein sitting with nothing to do for days...so maybe they've fixed that particular problem in this version.

Hrm, I've run 4.45 for a while, and am doing multiple projects. No issues, on everything from P3-600 - P4 1.8G. Everthing goes well.

I heard that you may be able to fix some of the issues with 4.45 and BoincView, by resetting the Long Term Debt, which is what can cause your issues. But I never ran into the issues.

If left alone, it takes a few days for the debt to get straightened out, but it does fix itself.

---

My movie https://vimeo.com/manage/videos/502242

I agree that 4.45 worked quite well. I just like to try new things :-D

Some might say I'm a sucker for punishment.

---

Kolch - Crunching for the BOINC@Australia team since July 2004.
Search for your own intelligence...

From the Dev mail list:

The "unsolicited graphics" are a result of a bug I introduced earlier today. Fixed now.
-- David

I don't know if this fix has made it to the 4.46 download, but I guess it must have as it is the testers version.

---

If left alone, it takes a few days for the debt to get straightened out, but it does fix itself.

PoohBear27, I agree. I have not missed a deadline on any of the several projects I run. It seemed to take about three days and the debt situation seemed to work it's way out. We will see how much changes when orbit, and LHC have new WU's.

Respectfully,

Rocky

---

www.boincsynergy.com

I used to be a credit (W)hore(der), now with the optimised boinc core client and seti app there is very little chance of me utilising a dev release unless it is optimised to suit my P4. I am hereby relinquishing my testing function. You may now call a credit sl#t!

Live long and crunch.

---

Paul
(S@H1 8888)
And proud of it!

I used to be a credit (W)hore(der), now with the optimised boinc core client and seti app there is very little chance of me utilising a dev release unless it is optimised to suit my P4. I am hereby relinquishing my testing function. You may now call a credit sl#t!

Live long and crunch.

Hi Paul,
remember the thread 'No schedulars responded'?
I do still have that problem. And because the problem got worse after the last week (cache is empty, can't report/download, no idea why, deadline 10 days away, aso) i gave CC4.46 a try. The no schedulers responded message changed to this:

26/06/2005 15:03:33|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
26/06/2005 15:03:33|SETI@home|Requesting 345600 seconds of work, returning 32 results
26/06/2005 15:03:41|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
26/06/2005 15:03:41|SETI@home|No schedulers responded
26/06/2005 15:03:42|SETI@home|Deferring communication with project for 6 minutes and 10 seconds

So there seems to be a number for this error now. If i recall the other thread correct, there was written something about the 500-error. Maybe we can figure out what causes this seldom mistake. More over there.

---

_\|/_
U r s

From the Dev mail list:

The "unsolicited graphics" are a result of a bug I introduced earlier today. Fixed now.
-- David

I don't know if this fix has made it to the 4.46 download, but I guess it must have as it is the testers version.

Well I am still seeing this unsolicited graphic when new WU's start...So it is not fixed.

[edit]Also I am seeing this message:

27/06/2005 12:09:23 AM|SETI@home|Result 01dc03ab.23198.17809.448574.66_2 exited with zero status but no 'finished' file
27/06/2005 12:09:23 AM|SETI@home|If this happens repeatedly you may need to reset the project.

Looks like I will have to reset and report if that helps.[/edit]

---

Kolch - Crunching for the BOINC@Australia team since July 2004.
Search for your own intelligence...

This isn't release to Alpha testers.
Good luck

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

Fred,
Care to clarify that remark please?

---

Kolch - Crunching for the BOINC@Australia team since July 2004.
Search for your own intelligence...

I'm not sure that everyone is supposed to know about this release. I was invited by Rom because I'm a dial up user and he wanted it tested before release. I have seen a few issues with this new version.

The request for work are more frequent than the 58 seconds listed.
The "update all" button doesn't seem to work.
There's a new prompt asking for network access, but when you select "yes", you get a "Can't connect to the internet" message.
My Cpu time quit working and this morning I had to uninstall, delete folders, and reinstall to get it working again. When trying to reattach to seti I get the following:

6/26/2005 11:29:59 AM|http://setiathome.berkeley.edu/|Master page download succeeded
6/26/2005 11:30:00 AM|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/26/2005 11:30:00 AM|http://setiathome.berkeley.edu/|Requesting 172800 seconds of work, returning 0 results
6/26/2005 11:30:17 AM|http://setiathome.berkeley.edu/|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
6/26/2005 11:30:17 AM|http://setiathome.berkeley.edu/|No schedulers responded
6/26/2005 11:30:17 AM|http://setiathome.berkeley.edu/|Resetting project
6/26/2005 11:30:17 AM||request_reschedule_cpus: exit_tasks
6/26/2005 11:30:17 AM|http://setiathome.berkeley.edu/|Detaching from project
6/26/2005 11:34:03 AM|http://setiathome.berkeley.edu/|Master page download succeeded
6/26/2005 11:34:04 AM|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/26/2005 11:34:04 AM|http://setiathome.berkeley.edu/|Requesting 8640 seconds of work, returning 0 results
6/26/2005 11:34:20 AM|http://setiathome.berkeley.edu/|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
6/26/2005 11:34:20 AM|http://setiathome.berkeley.edu/|No schedulers responded
6/26/2005 11:34:20 AM|http://setiathome.berkeley.edu/|Resetting project


I don't think you will enjoy this one, just yet.

tony

Yeah I feel a bit like I let the ugly cat out of the bag...

Thread name changed accordingly.

---

Kolch - Crunching for the BOINC@Australia team since July 2004.
Search for your own intelligence...

I don't think you will enjoy this one, just yet.

tony

That's the post I was waiting for!!

---

Boinc....Boinc....Boinc....Boinc....

And yes, the Seti graphic pops up (uninvited) every time the seti wu starts.

here's what's in my stderrdae:

2005-06-26 10:56:41 [http://setiathome.berkeley.edu/] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 10:56:41 [http://setiathome.berkeley.edu/] No schedulers responded
2005-06-26 10:56:41 [http://setiathome.berkeley.edu/] Couldn't connect to URL http://setiathome.berkeley.edu/.
Please check URL.
2005-06-26 11:30:17 [http://setiathome.berkeley.edu/] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:30:17 [http://setiathome.berkeley.edu/] No schedulers responded
2005-06-26 11:30:17 [http://setiathome.berkeley.edu/] Couldn't connect to URL http://setiathome.berkeley.edu/.
Please check URL.
2005-06-26 11:34:20 [http://setiathome.berkeley.edu/] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:34:20 [http://setiathome.berkeley.edu/] No schedulers responded
2005-06-26 11:34:20 [http://setiathome.berkeley.edu/] Couldn't connect to URL http://setiathome.berkeley.edu/.
Please check URL.
2005-06-26 11:54:17 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:54:17 [SETI@home] No schedulers responded
2005-06-26 11:54:18 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 11:54:42 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:54:42 [SETI@home] No schedulers responded
2005-06-26 11:54:43 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 11:55:04 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:55:04 [SETI@home] No schedulers responded
2005-06-26 11:55:25 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:55:25 [SETI@home] No schedulers responded
2005-06-26 11:55:26 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 11:55:45 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:55:45 [SETI@home] No schedulers responded
2005-06-26 11:55:46 [SETI@home] Deferring communication with project for 1 minutes and 28 seconds
2005-06-26 11:56:20 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:56:20 [SETI@home] No schedulers responded
2005-06-26 11:56:21 [SETI@home] Deferring communication with project for 3 minutes and 48 seconds
2005-06-26 11:56:49 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:56:49 [SETI@home] No schedulers responded
2005-06-26 11:56:50 [SETI@home] Deferring communication with project for 11 minutes and 45 seconds
2005-06-26 11:57:14 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:57:14 [SETI@home] No schedulers responded
2005-06-26 11:57:15 [SETI@home] Deferring communication with project for 15 minutes and 24 seconds
2005-06-26 11:57:42 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:57:42 [SETI@home] No schedulers responded
2005-06-26 11:57:43 [SETI@home] Deferring communication with project for 2 hours, 12 minutes, and 23 seconds
2005-06-26 11:58:02 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:58:02 [SETI@home] No schedulers responded
2005-06-26 11:58:03 [SETI@home] Deferring communication with project for 2 hours, 30 minutes, and 56 seconds
2005-06-26 11:58:15 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:58:15 [SETI@home] No schedulers responded
2005-06-26 11:58:16 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 11:58:24 [SETI@home] Fetching master file
2005-06-26 11:59:37 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 11:59:37 [SETI@home] No schedulers responded
2005-06-26 11:59:38 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 12:00:14 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:00:14 [SETI@home] No schedulers responded
2005-06-26 12:00:15 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 12:00:54 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:00:54 [SETI@home] No schedulers responded
2005-06-26 12:01:13 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:01:13 [SETI@home] No schedulers responded
2005-06-26 12:01:25 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:01:25 [SETI@home] No schedulers responded
2005-06-26 12:01:26 [SETI@home] Deferring communication with project for 1 minutes and 59 seconds
2005-06-26 12:01:43 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:01:43 [SETI@home] No schedulers responded
2005-06-26 12:01:51 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:01:51 [SETI@home] No schedulers responded
2005-06-26 12:01:52 [SETI@home] Deferring communication with project for 17 minutes and 29 seconds
2005-06-26 12:02:05 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:02:05 [SETI@home] No schedulers responded
2005-06-26 12:02:06 [SETI@home] Deferring communication with project for 6 minutes and 54 seconds
2005-06-26 12:02:23 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:02:23 [SETI@home] No schedulers responded
2005-06-26 12:02:33 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:02:33 [SETI@home] No schedulers responded
2005-06-26 12:02:42 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:02:42 [SETI@home] No schedulers responded
2005-06-26 12:02:43 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 12:02:44 [SETI@home] Fetching master file
2005-06-26 12:03:01 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:03:01 [SETI@home] No schedulers responded
2005-06-26 12:03:02 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 12:03:10 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:03:10 [SETI@home] No schedulers responded
2005-06-26 12:03:11 [SETI@home] Deferring communication with project for 58 seconds
2005-06-26 12:03:23 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:03:23 [SETI@home] No schedulers responded
2005-06-26 12:03:33 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:03:33 [SETI@home] No schedulers responded
2005-06-26 12:03:45 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:03:45 [SETI@home] No schedulers responded
2005-06-26 12:03:46 [SETI@home] Deferring communication with project for 2 minutes and 2 seconds
2005-06-26 12:04:05 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:04:05 [SETI@home] No schedulers responded
2005-06-26 12:04:06 [SETI@home] Deferring communication with project for 4 minutes and 19 seconds
2005-06-26 12:04:23 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:04:23 [SETI@home] No schedulers responded
2005-06-26 12:04:38 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2005-06-26 12:04:38 [SETI@home] No schedulers responded
2005-06-26 12:04:39 [SETI@home] Deferring communication with project for 8 minutes and 53 seconds

Anyone wanna walk me though using Windbg to extract the callstacks? I have the symbols library extracted and installed in the "Boinc" folder. I have windbg installed.

[edit] do you notice how it says "retry in" and then ignores it and retries immediately?
tony

I have a couple of issues with V4.46
I have a return of the no connection to local host. It takes several attempt to connect. This issue had been resolved completly in the last Revision.

I am also getting the unsolisited graphic at start-up. This could be a big problem since the graphics have caused my system to lock up in the past. Luckily both the Seti and Einstein graphic that have shown so far have not had a detrimental effect on my system so far. But, this needs to be looked into immediately.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

The failure of the CPU time issue was first thought by me to be the fact I was "playing" with the Windbg. However, I uninstalled, deleted Boinc folder and completely reinstalled. I stopped getting the 500 message after PPAH and Seti/Beta finished downloading their files, and I downloaded 4.18 and ONE WU. Now Seti has locked up again(note: seti, seti beta, and PPAH locked up last nite).

my stderr shows the following:
Can't set up shared mem: -1

any ideas?

The failure of the CPU time issue was first thought by me to be the fact I was "playing" with the Windbg. However, I uninstalled, deleted Boinc folder and completely reinstalled. I stopped getting the 500 message after PPAH and Seti/Beta finished downloading their files, and I downloaded 4.18 and ONE WU. Now Seti has locked up again(note: seti, seti beta, and PPAH locked up last nite).

my stderr shows the following:
Can't set up shared mem: -1

any ideas?

Yeah, send me your logs ... :)

No idea what is wrong ... but I want to mine the messages ...

---

I'm not sure that everyone is supposed to know about this release. I was invited by Rom because I'm a dial up user and he wanted it tested before release. I have seen a few issues with this new version.

Yep. I was also asked to test it, and agree with your comments. This would be a good one for the masses to avoid.

seti beta stderr shows:
Can't set up shared mem: -1
No heartbeat from core client for 31 sec - exiting