I have not recieved any work from the Einstein project since I added in the Beta programs... Someone please help me get back to work!
Hi Jakobius,
Welcome to the EAH project.
When you talked about "Beta programs" I'm sure that some of us thought you were referring to the EAH beta science app which this thread is all about. Actually from your EAH results list you are running the standard 4.79 science app so your question is nothing to do with this thread, I suspect. I think you are talking about Beta Projects like SAH Beta Test that shows up in the messages you posted.
In future it would be very helpful if you would post questions such as this one in a brand new thread, probably best in the "Getting started" forum. That way we will be able to help you a lot more easily without hijacking a completely different discussion.
The answer to your question is simply that it is not the correct time for EAH to have more work. Here is the relevant bit from your messages:-
Quote:
11/9/2005 1:22:08 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
11/9/2005 1:22:08 AM|Einstein@Home|Reason: Requested by user
11/9/2005 1:22:08 AM|Einstein@Home|Note: not requesting new work or reporting results
You have given an "Update" to EAH in order to try to get more work. The "Update" was correctly recognised but BOINC is telling you that more work is simply not needed as it's not yet time for EAH to run again.
Everything is controlled by the resource shares that you have specified when you added each project. BOINC will do its absolute best to properly manage the flow of work so that those shares are honoured correctly. You have at least seven projects so BOINC is going to have a bit of a job keeping all that lot going. There are bound to be times when BOINC will prevent one project from downloading simply to make the task more manageable. If you really want to help BOINC there are really two key things to do:-
1. Set up the resource shares you really want and then leave BOINC alone to do the job.
2. Set the "connect to network" preference setting under your general preferences on the website to a small value like 0.1 days so that any one project doesn't download too much work and wreck things.
Your computer takes around 15 hours to crunch an EAH result. If your seven projects all have equal shares, each project is only entitled to just over 3 hours/day if running 24/7. It's going to take close to 5 days to process just one EAH result. Can you understand now why BOINC doesn't need another one just yet? BOINC will allow one to be downloaded exactly when it's needed.
I downloaded and am attempting to run the EAH Beta that you can download from their website. That is why I was wondering why I was getting no work when I am finishing all my other projects in less than 5-8 hours... See my concern?
I downloaded and am attempting to run the EAH Beta that you can download from their website. That is why I was wondering why I was getting no work when I am finishing all my other projects in less than 5-8 hours... See my concern?
The beta application does show in the messages, thats the one that says "Einstein@Home|Found app_info.xml; using anonymous platform".
Did you click "no new work" for Einstein@Home? If so, you have to click "allow work" so BOINC requests some from the project scheduler. Switch to the "Projects" tab, select "Einstein" and check the top three buttons. They should be "Update", "suspend" and "no new work".
If they're correct, check the "status" column to see if it has anything - it should be blank.
Actually, I don't think you have a concern at all. OK, so you are going to use the beta science app the very next time BOINC decides that it is time for EAH to run. From your results list, the last result that you submitted was done with einstein 4.79. I presume you have placed the files as per the instructions in the beta app page on the website? In that case the app_info.xml file will ensure that the beta app (version 0.18 I believe) will run the next time that BOINC decides that EAH needs to run. All you have to do is sit back, be patient, read again what I wrote in the last message and wait for it all to happen.
If you are still sure that there really is some problem then please describe what you did and please give us more detail about the resource shares you have set and the website preferences you have configured. None of us can see those sort of details.
Edit: Sorry Walt, didn't see your reply when I posted. I got distracted after I had started mine and it took a lot longer to finish than anticipated.
I hit the reset work button and it finally connected and received wok. had nothing to do with waiting. That should get added to the instructions so people don't wait for something that won't happen withut it.
I hit the reset work button and it finally connected and received wok. had nothing to do with waiting. That should get added to the instructions so people don't wait for something that won't happen withut it.
Jakobius,
I tested the 0.18 beta about 2 months ago, and the transition from 4.79 went smoothly and seamlessly. It should be noted though, that I crunch only Einstein, so there were no concerns over project shares and scheduling, which seems to be what was causing your problems. Long story short - resetting is neither necessary nor recommended, as you can read from many others' experiences with the beta(s) earlier in this thread. It (resetting) just skews Boinc's balancing act.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
FYI: Ricky Moore has started a Beta 18 thread on Cruncher's Corner. There are a few posts there already (including a couple of mine). I think the subject matter might be a little more appropriate over here and I thought you might want to consider moving the thread.
If you look at the Beta app's Message Board (Message boards : Cafe Einstein : NEW: WINDOWS TEST APPLICATION FOR EINSTEIN@HOME) you'll see a lot of positive comments. You'll also see a few negative comments. But, for the most part, the negatives aren't about bugs. They are complaints (like yours) about processing time.
I'm sorry, but I think that a slight increase in processing time is a small price to pay for a product that will likely eliminate the major problem that most new users encounter. Most of my posts on these boards (over 200 posts now) have been related to advocating the Beta app in response to "Screensaver/Client error" problems. (And invariably those complaining say something like "but Seti is working fine".) I would estimate that less than a third of those "recommendees" have actually bothered to try the Beta. Most of them either just continue to crank out failed results (like the "poor soul" you referred to the previous post) or they quit the project.
Gary Roberts recently started a new thread on the "Getting Started" board for Seti Classic users who may have to switch to BOINC in mid-December. (And I have a post there, too.) Gary's point in starting the thread is that, when Seti Classic closes, Einstein will have a good opportunity to expand its base. I agree with his premise - but I think we will fail miserably if Einstein 4.79 is still the "official" application.
Stick,
I agree absolutely with you in regard to desparately needing a replacement for the old 4.79 app, to bring it into compliance with the newer Boinc clients. :-)
I see no good reason why we should settle for a replacement that is less efficient. IMO, there is still some tweaking needed to 0.18 before accepting it as the official replacement, that's all. It's just not good enough yet. It still "feels" like a rough, stopgap measure. They can do better, I'm certain, and we deserve better. IMO, they could even do away with the kiddie kandy graphics completely, and solve the problem altogether. How many crunchers do you think are that wrapped up in the cute little uninformative sphere? If the 0.18 beta as is becomes the de facto app, automatically being downloaded and replacing something that works well for me and 1000s of others, it will leave me with a difficult choice, to crunch Einstein with 0.18 or not at all, and I'm not prepared to say on which side of that dilemma I would fall. I'm very sorry to say that.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: I have not recieved any
)
Please copy and post the recent messages under your BOINC Manager "Messages" tab.
11/8/2005 8:36:11
)
11/8/2005 8:36:11 PM||Starting BOINC client version 5.2.5 for windows_intelx86
11/8/2005 8:36:11 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
11/8/2005 8:36:11 PM||Data directory: C:\\Program Files\\BOINC
11/8/2005 8:36:11 PM|Einstein@Home|Found app_info.xml; using anonymous platform
11/8/2005 8:36:11 PM||Processor: 1 GenuineIntel Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz
11/8/2005 8:36:11 PM||Memory: 510.92 MB physical, 862.32 MB virtual
11/8/2005 8:36:11 PM||Disk: 54.48 GB total, 45.28 GB free
11/8/2005 8:36:11 PM|rosetta@home|Computer ID: 43849; location: home; project prefs: default
11/8/2005 8:36:11 PM|climateprediction.net|Computer ID: 242199; location: home; project prefs: default
11/8/2005 8:36:11 PM|Einstein@Home|Computer ID: 432212; location: home; project prefs: default
11/8/2005 8:36:11 PM|LHC@home|Computer ID: 69421; location: home; project prefs: default
11/8/2005 8:36:11 PM|Predictor @ Home|Computer ID: 169511; location: home; project prefs: default
11/8/2005 8:36:11 PM|SETI@home|Computer ID: 1585623; location: home; project prefs: default
11/8/2005 8:36:11 PM|SETI@home Beta Test|Computer ID: 2787; location: home; project prefs: default
11/8/2005 8:36:11 PM||General prefs: from SETI@home Beta Test (last modified 2005-11-02 00:57:14)
11/8/2005 8:36:11 PM||General prefs: no separate prefs for home; using your defaults
11/8/2005 8:36:11 PM||Remote control not allowed; using loopback address
11/8/2005 8:36:11 PM|climateprediction.net|Deferring computation for result 1765_300076530_0
11/8/2005 8:36:11 PM|SETI@home Beta Test|Deferring computation for result 03oc03aa.9124.1185.723592.186_1
11/8/2005 8:36:11 PM|LHC@home|Deferring computation for result wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2
11/8/2005 8:36:11 PM|Predictor @ Home|Deferring computation for result h0012B_1_173817_0
11/8/2005 8:36:11 PM|SETI@home|Resuming computation for result 02no03aa.20101.28273.23586.212_2 using setiathome version 418
11/8/2005 8:36:11 PM|rosetta@home|Deferring computation for result 1hz7A_abrelaxmode_random_gauss_length20_jitter02_03897_1
11/8/2005 8:36:11 PM|Predictor @ Home|Started upload of bprion_1_14053_1_0
11/8/2005 8:36:11 PM|Predictor @ Home|Started upload of bprion_1_14053_1_1
11/8/2005 8:36:11 PM|SETI@home Beta Test|Restarting result 03oc03aa.9124.1185.723592.186_1 using setiathome_enhanced version 409
11/8/2005 8:36:11 PM|SETI@home|Pausing result 02no03aa.20101.28273.23586.212_2 (left in memory)
11/8/2005 8:36:14 PM|Predictor @ Home|Finished upload of bprion_1_14053_1_0
11/8/2005 8:36:14 PM|Predictor @ Home|Throughput 8328 bytes/sec
11/8/2005 8:36:14 PM|Predictor @ Home|Started upload of bprion_1_14053_1_2
11/8/2005 8:36:15 PM|Predictor @ Home|Finished upload of bprion_1_14053_1_1
11/8/2005 8:36:15 PM|Predictor @ Home|Throughput 36428 bytes/sec
11/8/2005 8:36:18 PM|Predictor @ Home|Finished upload of bprion_1_14053_1_2
11/8/2005 8:36:18 PM|Predictor @ Home|Throughput 9420 bytes/sec
11/8/2005 8:38:29 PM||request_reschedule_cpus: result op
11/8/2005 8:38:30 PM|SETI@home Beta Test|Pausing result 03oc03aa.9124.1185.723592.186_1 (left in memory)
11/8/2005 8:38:30 PM|rosetta@home|Restarting result 1hz7A_abrelaxmode_random_gauss_length20_jitter02_03897_1 using rosetta version 478
11/8/2005 8:38:46 PM||request_reschedule_cpus: project op
11/8/2005 8:38:47 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
11/8/2005 8:38:47 PM|Predictor @ Home|Reason: Requested by user
11/8/2005 8:38:47 PM|Predictor @ Home|Reporting 1 results
11/8/2005 8:38:52 PM|Predictor @ Home|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
11/8/2005 8:38:57 PM|Predictor @ Home|Deferring communication with project for 1 seconds
11/8/2005 8:42:38 PM||request_reschedule_cpus: result op
11/8/2005 8:42:39 PM|LHC@home|Restarting result wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2 using sixtrack version 467
11/8/2005 8:42:39 PM|rosetta@home|Pausing result 1hz7A_abrelaxmode_random_gauss_length20_jitter02_03897_1 (left in memory)
11/8/2005 9:20:21 PM|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
11/8/2005 9:20:21 PM|LHC@home|Reason: To fetch work
11/8/2005 9:20:21 PM|LHC@home|Requesting 164 seconds of new work
11/8/2005 9:20:26 PM|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
11/8/2005 9:20:27 PM|LHC@home|Started download of wnov1B_v6s4hvnom_mqx__13__64.279_59.299__8_10__6__20_1_sixvf_boinc77073.zip
11/8/2005 9:20:31 PM|LHC@home|Deferring communication with project for 1 seconds
11/8/2005 9:20:31 PM|LHC@home|Finished download of wnov1B_v6s4hvnom_mqx__13__64.279_59.299__8_10__6__20_1_sixvf_boinc77073.zip
11/8/2005 9:20:31 PM|LHC@home|Throughput 10039 bytes/sec
11/8/2005 9:20:32 PM||request_reschedule_cpus: files downloaded
11/8/2005 9:20:32 PM|climateprediction.net|Restarting result 1765_300076530_0 using hadsm3 version 413
11/8/2005 9:20:32 PM|LHC@home|Pausing result wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2 (left in memory)
11/8/2005 9:35:53 PM||request_reschedule_cpus: result op
11/8/2005 9:35:54 PM|climateprediction.net|Pausing result 1765_300076530_0 (left in memory)
11/8/2005 9:35:54 PM|SETI@home|Resuming result 02no03aa.20101.28273.23586.212_2 using setiathome version 418
11/8/2005 9:35:58 PM||request_reschedule_cpus: result op
11/8/2005 10:35:59 PM|climateprediction.net|Resuming result 1765_300076530_0 using hadsm3 version 413
11/8/2005 10:35:59 PM|SETI@home|Pausing result 02no03aa.20101.28273.23586.212_2 (left in memory)
11/8/2005 10:38:58 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
11/8/2005 10:38:58 PM|climateprediction.net|Reason: To send trickle-up message
11/8/2005 10:38:58 PM|climateprediction.net|Note: not requesting new work or reporting results
11/8/2005 10:39:03 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
11/8/2005 11:36:00 PM|climateprediction.net|Pausing result 1765_300076530_0 (left in memory)
11/8/2005 11:36:00 PM|Predictor @ Home|Restarting result h0012B_1_173817_0 using mfoldB125 version 428
11/9/2005 12:06:39 AM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
11/9/2005 12:06:39 AM|Predictor @ Home|Reason: To fetch work
11/9/2005 12:06:39 AM|Predictor @ Home|Requesting 21 seconds of new work
11/9/2005 12:06:44 AM|Predictor @ Home|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
11/9/2005 12:06:45 AM|Predictor @ Home|Started download of bprion_1_28210.ini
11/9/2005 12:06:45 AM|Predictor @ Home|Started download of bprion_1_28210.inp
11/9/2005 12:06:49 AM|Predictor @ Home|Deferring communication with project for 1 seconds
11/9/2005 12:06:49 AM|Predictor @ Home|Finished download of bprion_1_28210.ini
11/9/2005 12:06:49 AM|Predictor @ Home|Throughput 664 bytes/sec
11/9/2005 12:06:49 AM|Predictor @ Home|Finished download of bprion_1_28210.inp
11/9/2005 12:06:49 AM|Predictor @ Home|Throughput 54 bytes/sec
11/9/2005 12:06:49 AM|Predictor @ Home|Started download of bprion_1_28210.seq
11/9/2005 12:06:49 AM|Predictor @ Home|Started download of bprion_1_28210.res
11/9/2005 12:06:51 AM|Predictor @ Home|Finished download of bprion_1_28210.seq
11/9/2005 12:06:51 AM|Predictor @ Home|Throughput 8000 bytes/sec
11/9/2005 12:06:51 AM|Predictor @ Home|Finished download of bprion_1_28210.res
11/9/2005 12:06:51 AM|Predictor @ Home|Throughput 15 bytes/sec
11/9/2005 12:06:52 AM||request_reschedule_cpus: files downloaded
11/9/2005 12:06:52 AM|LHC@home|Resuming result wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2 using sixtrack version 467
11/9/2005 12:06:52 AM|Predictor @ Home|Pausing result h0012B_1_173817_0 (left in memory)
11/9/2005 12:10:29 AM||request_reschedule_cpus: process exited
11/9/2005 12:10:29 AM|LHC@home|Computation for result wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2 finished
11/9/2005 12:10:29 AM|LHC@home|Starting result wnov1B_v6s4hvnom_mqx__13__64.279_59.299__8_10__6__20_1_sixvf_boinc77073_2 using sixtrack version 467
11/9/2005 12:10:31 AM|LHC@home|Started upload of wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2_0
11/9/2005 12:10:38 AM|LHC@home|Finished upload of wnov1A_v6s4hvnom_mqx__12__64.265_59.285__6_8__6__40_1_sixvf_boinc45313_2_0
11/9/2005 12:10:38 AM|LHC@home|Throughput 14526 bytes/sec
11/9/2005 1:08:19 AM||request_reschedule_cpus: project op
11/9/2005 1:08:20 AM|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
11/9/2005 1:08:20 AM|LHC@home|Reason: Requested by user
11/9/2005 1:08:20 AM|LHC@home|Reporting 1 results
11/9/2005 1:08:20 AM|Predictor @ Home|Resuming result h0012B_1_173817_0 using mfoldB125 version 428
11/9/2005 1:08:20 AM|LHC@home|Pausing result wnov1B_v6s4hvnom_mqx__13__64.279_59.299__8_10__6__20_1_sixvf_boinc77073_2 (left in memory)
11/9/2005 1:08:25 AM|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
11/9/2005 1:08:30 AM|LHC@home|Deferring communication with project for 1 seconds
11/9/2005 1:09:10 AM||request_reschedule_cpus: result op
11/9/2005 1:09:15 AM||request_reschedule_cpus: result op
11/9/2005 1:19:20 AM||request_reschedule_cpus: process exited
11/9/2005 1:19:20 AM|Predictor @ Home|Computation for result h0012B_1_173817_0 finished
11/9/2005 1:19:20 AM|SETI@home|Resuming result 02no03aa.20101.28273.23586.212_2 using setiathome version 418
11/9/2005 1:19:22 AM|Predictor @ Home|Started upload of h0012B_1_173817_0_0
11/9/2005 1:19:22 AM|Predictor @ Home|Started upload of h0012B_1_173817_0_1
11/9/2005 1:19:26 AM|Predictor @ Home|Finished upload of h0012B_1_173817_0_0
11/9/2005 1:19:26 AM|Predictor @ Home|Throughput 1371 bytes/sec
11/9/2005 1:19:26 AM|Predictor @ Home|Started upload of h0012B_1_173817_0_2
11/9/2005 1:19:27 AM|Predictor @ Home|Finished upload of h0012B_1_173817_0_1
11/9/2005 1:19:27 AM|Predictor @ Home|Throughput 16050 bytes/sec
11/9/2005 1:19:28 AM|Predictor @ Home|Finished upload of h0012B_1_173817_0_2
11/9/2005 1:19:28 AM|Predictor @ Home|Throughput 15094 bytes/sec
11/9/2005 1:19:43 AM||request_reschedule_cpus: project op
11/9/2005 1:19:47 AM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
11/9/2005 1:19:47 AM|Predictor @ Home|Reason: Requested by user
11/9/2005 1:19:47 AM|Predictor @ Home|Reporting 1 results
11/9/2005 1:19:52 AM|Predictor @ Home|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
11/9/2005 1:19:57 AM|Predictor @ Home|Deferring communication with project for 1 seconds
11/9/2005 1:22:06 AM||request_reschedule_cpus: project op
11/9/2005 1:22:08 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
11/9/2005 1:22:08 AM|Einstein@Home|Reason: Requested by user
11/9/2005 1:22:08 AM|Einstein@Home|Note: not requesting new work or reporting results
11/9/2005 1:22:08 AM|SETI@home|Pausing result 02no03aa.20101.28273.23586.212_2 (left in memory)
11/9/2005 1:22:09 AM|Predictor @ Home|Starting result bprion_1_28210_0 using mfoldB125 version 428
11/9/2005 1:22:13 AM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
11/9/2005 1:22:18 AM|Einstein@Home|Deferring communication with project for 55 seconds
RE: I have not recieved any
)
Hi Jakobius,
Welcome to the EAH project.
When you talked about "Beta programs" I'm sure that some of us thought you were referring to the EAH beta science app which this thread is all about. Actually from your EAH results list you are running the standard 4.79 science app so your question is nothing to do with this thread, I suspect. I think you are talking about Beta Projects like SAH Beta Test that shows up in the messages you posted.
In future it would be very helpful if you would post questions such as this one in a brand new thread, probably best in the "Getting started" forum. That way we will be able to help you a lot more easily without hijacking a completely different discussion.
The answer to your question is simply that it is not the correct time for EAH to have more work. Here is the relevant bit from your messages:-
You have given an "Update" to EAH in order to try to get more work. The "Update" was correctly recognised but BOINC is telling you that more work is simply not needed as it's not yet time for EAH to run again.
Everything is controlled by the resource shares that you have specified when you added each project. BOINC will do its absolute best to properly manage the flow of work so that those shares are honoured correctly. You have at least seven projects so BOINC is going to have a bit of a job keeping all that lot going. There are bound to be times when BOINC will prevent one project from downloading simply to make the task more manageable. If you really want to help BOINC there are really two key things to do:-
1. Set up the resource shares you really want and then leave BOINC alone to do the job.
2. Set the "connect to network" preference setting under your general preferences on the website to a small value like 0.1 days so that any one project doesn't download too much work and wreck things.
Your computer takes around 15 hours to crunch an EAH result. If your seven projects all have equal shares, each project is only entitled to just over 3 hours/day if running 24/7. It's going to take close to 5 days to process just one EAH result. Can you understand now why BOINC doesn't need another one just yet? BOINC will allow one to be downloaded exactly when it's needed.
Hope this helps.
Cheers,
Gary.
I downloaded and am
)
I downloaded and am attempting to run the EAH Beta that you can download from their website. That is why I was wondering why I was getting no work when I am finishing all my other projects in less than 5-8 hours... See my concern?
RE: I downloaded and am
)
The beta application does show in the messages, thats the one that says "Einstein@Home|Found app_info.xml; using anonymous platform".
Did you click "no new work" for Einstein@Home? If so, you have to click "allow work" so BOINC requests some from the project scheduler. Switch to the "Projects" tab, select "Einstein" and check the top three buttons. They should be "Update", "suspend" and "no new work".
If they're correct, check the "status" column to see if it has anything - it should be blank.
Walt
RE: See my
)
Actually, I don't think you have a concern at all. OK, so you are going to use the beta science app the very next time BOINC decides that it is time for EAH to run. From your results list, the last result that you submitted was done with einstein 4.79. I presume you have placed the files as per the instructions in the beta app page on the website? In that case the app_info.xml file will ensure that the beta app (version 0.18 I believe) will run the next time that BOINC decides that EAH needs to run. All you have to do is sit back, be patient, read again what I wrote in the last message and wait for it all to happen.
If you are still sure that there really is some problem then please describe what you did and please give us more detail about the resource shares you have set and the website preferences you have configured. None of us can see those sort of details.
Edit: Sorry Walt, didn't see your reply when I posted. I got distracted after I had started mine and it took a lot longer to finish than anticipated.
Cheers,
Gary.
I hit the reset work button
)
I hit the reset work button and it finally connected and received wok. had nothing to do with waiting. That should get added to the instructions so people don't wait for something that won't happen withut it.
RE: I hit the reset work
)
Jakobius,
I tested the 0.18 beta about 2 months ago, and the transition from 4.79 went smoothly and seamlessly. It should be noted though, that I crunch only Einstein, so there were no concerns over project shares and scheduling, which seems to be what was causing your problems. Long story short - resetting is neither necessary nor recommended, as you can read from many others' experiences with the beta(s) earlier in this thread. It (resetting) just skews Boinc's balancing act.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
FYI: Ricky Moore has started
)
FYI: Ricky Moore has started a Beta 18 thread on Cruncher's Corner. There are a few posts there already (including a couple of mine). I think the subject matter might be a little more appropriate over here and I thought you might want to consider moving the thread.
RE: If you look at the Beta
)
Stick,
I agree absolutely with you in regard to desparately needing a replacement for the old 4.79 app, to bring it into compliance with the newer Boinc clients. :-)
I see no good reason why we should settle for a replacement that is less efficient. IMO, there is still some tweaking needed to 0.18 before accepting it as the official replacement, that's all. It's just not good enough yet. It still "feels" like a rough, stopgap measure. They can do better, I'm certain, and we deserve better. IMO, they could even do away with the kiddie kandy graphics completely, and solve the problem altogether. How many crunchers do you think are that wrapped up in the cute little uninformative sphere? If the 0.18 beta as is becomes the de facto app, automatically being downloaded and replacing something that works well for me and 1000s of others, it will leave me with a difficult choice, to crunch Einstein with 0.18 or not at all, and I'm not prepared to say on which side of that dilemma I would fall. I'm very sorry to say that.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK