I just got four brand new Results to crunch, and the status Board is pure green!!

---

The good thing is with a 6 day cache is that I didn't run out of work, but it lowered just perfectly for LHC to get a good go at it now that they are also giving out work. Haaaa, the wonders of BOINC.

Live long and crunch.

---

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

If "Thereeee Back!", how come I STILL can't get any work units from their server? - think I'll have to see how to set a 6-day cache in my preferences too! ..... assuming I GET any more work to cache up!! :-)

---

If "Thereeee Back!", how come I STILL can't get any work units from their server? - think I'll have to see how to set a 6-day cache in my preferences too! ..... assuming I GET any more work to cache up!! :-)

Becase as soon as there's any to download, someone else gets there before you.
No, there's nothing you can do about it but wait, you'll get work eventually.
After a long outage like this I doubt they'll be any surplus for 24-36 hours.

---

woo hoo one of my machines managed to grab 4 :) Bless it's lil heart...

---

My machine is still idle with S@h WUs....i am now crunching SIMAP WUs, just 25 minutes per WU. Hope to see Berkeley up and running smooth soon.

Best regards,
Stefan

---

If "Thereeee Back!", how come I STILL can't get any work units from their server? - think I'll have to see how to set a 6-day cache in my preferences too! ..... assuming I GET any more work to cache up!! :-)

Becase as soon as there's any to download, someone else gets there before you.
No, there's nothing you can do about it but wait, you'll get work eventually.
After a long outage like this I doubt they'll be any surplus for 24-36 hours.

O-O-O-O-O-O-K-K-K ..... I suppose that means that all those West Coast super-geeks out there with 4 + uber-machines all hunting for units will hog them all for a few days, unitl I, with my humble home PC here in the UK get the left-overs when the pool becomes full again! .... such is life!
Thanks for the clarification, Mike

---

i believe our computers will be fed with new WUs within' the next few hours....


happy crunching,
Stefan

---

i believe our computers will be fed with new WUs within' the next few hours....


happy crunching,
Stefan

Awwwright!! Got one! I'm back in crunchworld .... and happy about it :-)!!

---

ahh got one on the machine that still had cached, not the dry box....oh well dry box got something from beta instead

---

uninstall dyslexica.o : Permission denied


AMD Athlon 64 3000+ w/Windows
AMD Athlon 1800+ w/Linux

All green on the web site here in UK, but I guess we'll have to wait a bit to get any work. In the meantime I'm crunching for Einstein.

Chris S.

---

i am still getting the message "no work from project" Fortunately, i can wait with the purchase of my new AMD X2 processor :-)

---

i prefer crunching for SIMAP, as i believe, it is a useful grid computing application. Also, it is a project from the University (munich information center for protein sequences) of Munich, which is very reliable.

---

Got 28 WUs so far across 4 machines. The caches will fill up over the next 24-36 hours.

---

It's good to be back amongst friends and colleagues

Hmm, all machines drained, nothing left, no new WU's as of yet. Hope to see something soon, throttling off the other projects on my SETI dedicated units, so will have a 20 hour cache drain for SETI WU's to show up in.

---

Beach Bums Current Stats:


Come Join us at Hawaiian Beach Bums

Hmm, all machines drained, nothing left, no new WU's as of yet. Hope to see something soon, throttling off the other projects on my SETI dedicated units, so will have a 20 hour cache drain for SETI WU's to show up in.

the same thing happend with my wu/s i try and try, but ne wu(s reaching my system....

Greatings jürgen

[quote]Hmm, all machines drained, nothing left, no new WU's as of yet. Hope to see something soon, throttling off the other projects on my SETI dedicated units, so will have a 20 hour cache drain for SETI WU's to show up in.

the same thing happend with my wu/s i try and try, but ne wu(s reaching my system....

Greatings j?/quote]
.... I've got a work unit OK, but it's suspended (actual status report "activities suspended"), and I can't restart nor get rid of it - I also can't request another. The default system message I see is "04/03/2006 09:43:57||Remote control not allowed; using loopback address", and when I attempt to manually update, I get "04/03/2006 09:48:50||request_reschedule_cpus: project op
"...... what's with that - does anyone out there know?

---

[quote]Hmm, all machines drained, nothing left, no new WU's as of yet. Hope to see something soon, throttling off the other projects on my SETI dedicated units, so will have a 20 hour cache drain for SETI WU's to show up in.

the same thing happend with my wu/s i try and try, but ne wu(s reaching my system....

Greatings j?/quote]
.... I've got a work unit OK, but it's suspended (actual status report "activities suspended"), and I can't restart nor get rid of it - I also can't request another. The default system message I see is "04/03/2006 09:43:57||Remote control not allowed; using loopback address", and when I attempt to manually update, I get "04/03/2006 09:48:50||request_reschedule_cpus: project op
"...... what's with that - does anyone out there know?

That's it, I think this work unit is frelled - the messages I've most recently got are in the chain below :-

"04/03/2006 10:17:35|SETI@home|Resuming computation for result 09au01aa.21558.2640.28390.1.154_0 using setiathome version 418
04/03/2006 10:17:35||Resuming computation and network activity
04/03/2006 10:17:35||request_reschedule_cpus: Resuming activities
04/03/2006 10:17:36|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
04/03/2006 10:17:36|SETI@home|Reason: Requested by user
04/03/2006 10:17:36|SETI@home|Note: not requesting new work or reporting results
04/03/2006 10:17:47|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
04/03/2006 10:23:21||Suspending computation and network activity - user is active
04/03/2006 10:23:21|SETI@home|Pausing result 09au01aa.21558.2640.28390.1.154_0 (removed from memory)
04/03/2006 10:23:22||request_reschedule_cpus: process exited
04/03/2006 10:30:17||Resuming computation and network activity
04/03/2006 10:30:17||request_reschedule_cpus: Resuming activities
04/03/2006 10:30:17|SETI@home|Restarting result 09au01aa.21558.2640.28390.1.154_0 using setiathome version 418
04/03/2006 10:45:19||Suspending computation and network activity - user is active
04/03/2006 10:45:19|SETI@home|Pausing result 09au01aa.21558.2640.28390.1.154_0 (removed from memory)
04/03/2006 10:45:20||request_reschedule_cpus: process exited
"

If it is a knackered work unit, how do I get rid of it from my queue (that's a laugh - a queue of 1!), so as to never darken my doorstep again?

---

[quote]Hmm, all machines drained, nothing left, no new WU's as of yet. Hope to see something soon, throttling off the other projects on my SETI dedicated units, so will have a 20 hour cache drain for SETI WU's to show up in.

the same thing happend with my wu/s i try and try, but ne wu(s reaching my system....

Greatings j?/quote]
.... I've got a work unit OK, but it's suspended (actual status report "activities suspended"), and I can't restart nor get rid of it - I also can't request another. The default system message I see is "04/03/2006 09:43:57||Remote control not allowed; using loopback address", and when I attempt to manually update, I get "04/03/2006 09:48:50||request_reschedule_cpus: project op
"...... what's with that - does anyone out there know?

That's it, I think this work unit is frelled - the messages I've most recently got are in the chain below :-

"04/03/2006 10:17:35|SETI@home|Resuming computation for result 09au01aa.21558.2640.28390.1.154_0 using setiathome version 418
04/03/2006 10:17:35||Resuming computation and network activity
04/03/2006 10:17:35||request_reschedule_cpus: Resuming activities
04/03/2006 10:17:36|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
04/03/2006 10:17:36|SETI@home|Reason: Requested by user
04/03/2006 10:17:36|SETI@home|Note: not requesting new work or reporting results
04/03/2006 10:17:47|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
04/03/2006 10:23:21||Suspending computation and network activity - user is active
04/03/2006 10:23:21|SETI@home|Pausing result 09au01aa.21558.2640.28390.1.154_0 (removed from memory)
04/03/2006 10:23:22||request_reschedule_cpus: process exited
04/03/2006 10:30:17||Resuming computation and network activity
04/03/2006 10:30:17||request_reschedule_cpus: Resuming activities
04/03/2006 10:30:17|SETI@home|Restarting result 09au01aa.21558.2640.28390.1.154_0 using setiathome version 418
04/03/2006 10:45:19||Suspending computation and network activity - user is active
04/03/2006 10:45:19|SETI@home|Pausing result 09au01aa.21558.2640.28390.1.154_0 (removed from memory)
04/03/2006 10:45:20||request_reschedule_cpus: process exited
"

If it is a knackered work unit, how do I get rid of it from my queue (that's a laugh - a queue of 1!), so as to never darken my doorstep again?

Hey, nobody respond to this, 'cos I think I was aslepp when I was assessing the situation ... by opening BOINC, my computer was not idle, and I remember my preferences were set to "only process if idle" ..... doh! Sorry, folks! (the unit processes OK otherwise)

---

04/03/2006 10:45:19||Suspending computation and network activity - user is active
04/03/2006 10:45:19|SETI@home|Pausing result 09au01aa.21558.2640.28390.1.154_0 (removed from memory)
04/03/2006 10:45:20||request_reschedule_cpus: process exited

... by opening BOINC, my computer was not idle, and I remember my preferences were set to "only process if idle" ..... doh! Sorry, folks! (the unit processes OK otherwise)

A tip, for anyone whose preferences are set that way: when working with BOINC Manager be sure to choose "run always" from the menu, at the start of your session, so that your interactions with it don't prevent the apps from working. Just remember to switch back to "run according to preferences" before you quit.

---