This is a beta release and should only be used by those willing to test its functionality and accept possible errors or bugs. Details of this release can be found here

---

Crunching for the benefit of humanity and in memory of my dad and other family members.

If no major bugs were introduced,this may be the next "good" stable build, at least based on the release notes of the versions (the accumulation of ALL the 6.6.x versions) ... though I think that there are going to be migration issues with LTD because of the major changes from 6.5.0 and prior versions in the calculations and maintenance of those numbers ...

Still, I think I will wait for a bit before trying my luck ...

To avoid such problems the setup could set all debts to zero if 6.6.x is installed over a previous version.

MrS

---

Scanning for our furry friends since Jan 2002

To avoid such problems the setup could set all debts to zero if 6.6.x is installed over a previous version.

That was suggested several times... Dr. Anderson suggests that you use the configuration file switch to set the debts to zero and then remove the switch. Of course, the people that might need the help the most, the less able users, are not going to be able to do this well ...

I was just raising a warning for folks like you to be aware that this may cause several weeks of strange work fetch so that you can be on the look-out if someone talks of it and they just went to the 6.6.x series ... especially as Rom seems to think that they are close to making this the preferred version ... not sure which is going to be the one, but he has said that he thinks they are close ...

Thanks for the warning, I surely wasn't aware of this. And:

Dr. Anderson suggests that you use the configuration file switch to set the debts to zero and then remove the switch.

What the ****?! The people who are going to run into problems with this will not even know it's caused by LTD, so why would they even consider using this method?

MrS

---

Scanning for our furry friends since Jan 2002

One thing I noticed is I got file size mismatch on a suspended file xfer with this one. By the time I had turned on the appropiate debug flags it seems to have gone away. Maybe someone else might like to try it.

Seti is out of work and Einstein is down at the moment so its a bit hard for me to test. I would suggest turning on the file_xfer_debug flag first. It might just have been a glitch with the 2 files in question as I haven't seen any more do this.

I did post this on the boinc_alpha mailing list but as I said its a bit hard for me to retest this as most of my projects aren't giving out work - except GPUgrid of course :-)

---

BOINC blog

From the Dev mailing list,

Feb 20:

We still need a way for people to repair
systems where LTD is way out of whack.
I'll do this with a cc_config.xml flag (simple but clumsy)

-- David

I know there was more discussion on this, but can't seem to find the right word to search on ...

I did suggest that we have a button / link in the advanced menu, but, they have this "thing" about micromanagement. If they don't want a feature the explanation is that it will lead to micromanagement. Of course, there are lots of ways, most of them awkward that does allow for micromanagement ... it is just more annoying.

Even sadder, features that would lead to less micromanagement get eliminated or sidetracked because of this fetish. One of the project types and I argued for a limit on how many tasks could be running on a system as a project level setting. In this case, CPDN where I don't want more than one CPDN task on my systems at a time. Yet, if I don't manually set and unset NNW, I can get upwards of 5 tasks running on my 8 core systems ... why BOINC D/L extra tasks when the one should be sufficient to satisfy my resource share I don't know ... worse, BOINC will put ALL of them in-flight so that a system error will kill 5 tasks instead of just the one ... sigh ...

I have a similar problem with QCN where my OS-x system seems to want to try to run two tasks at the same time, instead of only one like it should ... again, if I had a setting I could cure this ...

Even more annoying is the insistence that only one Non_CPU intense task at a time can be run on a system. When you have 8 cores that makes no sense at all ... it almost makes sense if you say that you can only run 8 non-CPU intense tasks ... less any GPU tasks ... again, this new way of looking at it would allow the queuing of non-CPU intense tasks, which is not possible now (this would also cure the QCN issue).

Anyway, when the new version comes out, we are likely going to have people that are going to see very weird work fetch patterns until the LTDs get balanced which may require the use of the switch, or massive project resets (reset for all attached projects) ... or lots of patience ...

6.6.18 caused random blue screens on my Vista x64 box. I downgraded and all is running smoothly again.

6.6.18 caused random blue screens on my Vista x64 box. I downgraded and all is running smoothly again.

Did you report this on the Alpha mailing list? If not you should ...