That there were no other test clients out for so long, was because of the need to mature the BOINC for Android client a lot more, while on the other hand the main build system of the build developer had broken down, so he couldn't build a new BOINC even if he had wanted to.

7.0.28 is out. I'm waiting @ 7.0.27 until I see some posts on if it is better. I will probably wait until the first week of June as I will be out of town later in the week. I'm also going to cutting back to summertime crunching levels; one half of my CPU cores and only at night.

7.0.27 compiles fine on gentoo (stable 64bit) and no noticable hiccups running it so far.

So why wait now?

I asked for 7.0.26 to be promoted several days ago, but will probably not get an answer on that until after the weekend. It seems the developers are taking their weekends off this year. ;-)

The minimum work buffer setting sets the minimum amount of work you're going to request.
The maximum additional work buffer sets the additional days worth of work you want to have.

Not quite. The meaning of the prefs is:

- The client requests work for a given resource when the amount of buffered work falls below min.
- It requests (from the highest-priority project) enough work to bring the amount up to min + additional.

If Boinc 6.12.43 isn't listed on the Download page, very few will use it

Most of the fixes in that version (and the ones before) are for Test4Theory. But since Test4Theory hasn't upgraded their vboxwrapper app yet to work with the bug-fixes in this version, there's no real use for testing it at this time.

Those three hours were finished and uploaded, however they weren't reported. I had to manualy report them two minutes after deadline. Hopefully they weren't sent to someone in that time.

Uploading is just moving data from your hard drive to a hard drive on the server.
Reporting accesses the database, whereby it must be noted that when you report one task that it takes as much overhead on the database server as when you report ten tasks or one hundred tasks. So projects and BOINC prefer it if you report tasks in bunches, to keep things nice and tidy.

The RRI option is there to allow reports to be done immediately on projects like WCG which make daily backups of their data. That way you have a good chance that your reported tasks were in before the backup.

Other projects don't like RRI that much. Einstein and CPDN have been reported as disliking RRI, whereby you can lose data.

So use at your own discretion.

Those three hours were finished and uploaded, however they weren't reported. I had to manualy report them two minutes after deadline. Hopefully they weren't sent to someone in that time.

That sucks. Use the report_tasks_immediately option in a cc_config.xml file.

My problem is that in this case it isn't completing all the work units.

My machine was shut off for several days. As a result in Cosmology (long work units all about the same length) ordered by deadline I have 7 work units, then a several day gap, then more work units. It appears that the early wus will not finish by deadline.

At this point, I have Boinc running 4 high priority wus from Cosmology, but these are NOT 4 units from the early group. BOINC has run and completed units from the late group and even downloaded additional units. But seemingly will not run any of the early units.

I've finally shut off downloading, more units have finished, but not from the early group.

But with 13 tasks from 1 project started and the scheduler then gives the CPU to a task that hasn't been started then it's clear the scheduler is not following the FIFO rule. If 13 tasks are already started then, according to John, they must have started because they were in first. If they were in first then why doesn't the scheduler give the CPU back to one of them? Instead it starts a task that hasn't started because, according to John, it came in later.

The XML code used with BOINC is developed specifically for BOINC. It cannot at this time be compared to real XML, perhaps in the future.

Thank you for sympathy. I didn't mean to whimper. I'm just a little saddened, that the original idea of spare time crunching was effectively put away.