not getting work units anymore

Quote:

There are logic bugs where you get a syntax error.
Design flaws where is does not do as you expected.
Then the "Features" that don't please the user and don't function as they expected.

You raise three points which I'd like to answer:-

1. Syntax errors?? How do you compile code with syntax errors? Surely you are talking about logic bugs where people like us find them and help the devs fix them. Seems pretty normal and expected to me.
{{Most syntax errors are found at compile time, tho not all. The Shuttle failed to launch because someone forgot the ";" to end a line.}}

2. Design Flaws?? In whose opinion - yours?? You have a perfect right along with everyone else to make suggestions for design changes in either Problems and Bug Reports or the Wishlist. I've observed the process work quite well where the person reporting the problem shows that he has done a bit of basic research into the causes of the problem and can clearly identify the causes of the problem. Just stating "It's a bug" or "It's bad design" doesn't actually make it so. Also you should figure out if the design flaw is BOINC only or EAH only or in fact a combination of the two and report in the correct forum.
{{yes new features go on a wish list, bad functioning on the bug list. I know the "customer" seldom knows what to ask for, or does not define the project well. The main focus should be (1)doing required science, ie real customer, (2)making the set up easy enough that the target "customer" can do it (3)making it function as the target "customer" expects (4)making it fun for the target "customer" so you gain users to do the real customer's work.}}

3. Bad or Non-functional features?? Once again, a matter of opinion and once again, research it and fully report it. As far as BOINC features are concerned, why don't you download a copy of the code and develop a patch to fix the feature or improve its functionality? That'd be far more helpful than just being a winger. The devs are very receptive to well written enhancements. Just look at what JM7 has done by deciding to get his hands dirty in the code.
{{Yes if I had lots of free time I could download the code and go thru it and make suggestions. I am here just to waste some time between my real jobs. I am just saying that if I can't easily understand or don't agree with the LTD and the functioning if it and it does things I don't expect what do you think non-programmers do? LIkely they drop the project or they drop other projects to see if they can get some done with their favorite. project.

I said from the beginning this is likely a BOINC problem, tho I am not sure. The results are that my CPU does less E@H WU's than others. This is just robbing this project from getting real work done.

Now for a suggestion to who ever. Ever user should have at lease ONE WU per CPU on their machine, even if it is 100% certain to get stale before getting done. This is a problem the USER can see and understand. The message "requesting 0 seconds of work" makes no sense to the average user and took me way too long to find an answer.

I am just think about the "average" user. My software is only used by a few well train people so I don't have to do the "idiot" testing required by most general release software. I know my average user could not set Boinc up without just accepting all defaults.

The Boinc deafults should be set to work well for the average user doing ALL projects.

Each project should have a help page to give suggestioned settings for fast, slow, single, and multiple project computers.}}

Actually I still think you owe JM7 an apology.
{{I do not think so, I did not call his or anyone's work bad, or call him names, nor address my comments to them personally}}

Quote:

It seems to be doing well after I cleared the LTD and now has a a few WU's from each project.

Translation - it seems to be doing well now that I've told it to ignore my own choices for resource shares. It should have been smart enough in the first place to have figured out that it needs to do "What I think I want" rather than "what I actually said I want". Isn't it a piece of stupid, bug ridden software.

Quote:

Now if the LTD is the hidden driving force then the user should get this explained in the help or on the BOINC site. The "Requesting 0 seconds" message is no reason to make the user think there is a problem.

You say you write code for a living. Code writers write code - Documenters write documentation. It would be quite unusual to get daily updates in the documentation as the daily code changes roll out. Documentation invariably lags well behind and because of the many changes in the area of STD/LTD that have happened in the last couple of months it would be an absolute miracle (and a complete waste of time) if the documentation were right up to the minute. Tomorrow the code will be different.

However the BOINC project is indeed fortunate to have a dedicated team of documenters headed by Paul Buck who are doing a marvellous job with the BOINC Wiki. Once again, your "broad brush" and unjustified criticism has failed to notice how much of the intricacies of BOINC are actually documented in the Wiki. Go and read it some time and find out how well the concept of "debt" is explained there.

Quote:

Now the average user should have about 4 things to set up. 1) network connection 2) Select projects to do 3) set network connection time / cache size 4) fiddle with the percentages to give each project.

I am sure the average user could not follow the explanation of what is really happening nor why it is not a bug.

Statements like this suggest that you really haven't given the system a fair appraisal and you are certainly underestimating the capabilities of the average user. The 4 steps you suggest are really all that the average user needs to do. What more blindingly difficult steps are there? In fact the user can choose the defaults for most preferences and leave out step 3 and if the user has previously browsed the net, there shouldn't be much if anything to do in step 1.

The average user doesn't need to be troubled by STD/LTD and therefore can be completely oblivious to the underlying mechanisms. All the average user needs to do is set a sane value for "connect to network", stick to what is decided regarding resource shares and then have the good sense to leave BOINC alone to follow the orders. If you must fiddle, then it's your duty to understand the consequences of your own insanity. You can hardly blame BOINC for that.