Nothing seems to happen when I change my computing preferences on the SETI website and then update BOINC. I've been fiddling with the "number of processors," "percent of processors," and "percent of time" settings. No matter what I set these to, BOINC always runs all cores/threads, 100%.

I have an i7 CPU and run the optimized apps.

---

I'm new here ... so I am not sure of much. But, I have seen that Boinc will not pay attention to Seti website if I have set local preferences with 'Advanced -> Preferences ...' menu options. There is also an option to clear local preferences there if they are set.

You can see in your 'Messages' tab when Boinc reads 'Local' preferences from disk or 'Global' preferences from the website.

Yes, BOINC will ignore the online preferences if local preferences exist. Also, online preferences aren't immediately deployed. Online preferences must be downloaded by the client on the next server contact.

---

I couldn't see any local preferences to change, but hadn't tried the "Clear" function. That appears to have done it. Thanks.

---

I couldn't see any local preferences to change, but hadn't tried the "Clear" function. That appears to have done it. Thanks.

There seems to be a bug or so in the later versions of Boinc Manager, which in some cases, with some screen resolutions, makes the Advanced/preferences windows so small that all options becomes hidden/invisible. You can resize the window the normal ways until all options are visible.

The 6.10.18 version for example have so many bugs that I can't believe it's ever gone through a real beta testing, and if it was beta tested, it must have been tested by blind people. It's so many bugs that I don't even care to report them. The development team can't be too serious anyhow, if they let that kind of crap through without even noticing it.

The version I used before, 6.2.19 had no bugs that I noticed whatsoever.


Sten-Arne

Too bad you feel that way instead of offering to help.....

---

Official Abuser of Boinc Buttons...
And no good credit hound!

My my, got out the wrong end of the bed this morning?

The least one could expect though, is that the software they release is thorougly beta tested before it's released.

There are always new people needed for the alpha tests. Why don't you contact Rom or David and tell them you're eager to help them out with the tests, instead of taking your frustrations out on a group of people who volunteered to test the software? Even with all the tests done it's always possible that the software behaves completely different on your system. That's just not possible to prevent, unless you yourself, with that hardware, add yourself to the test and speak up about all the troubles and problems you find.

If that's too much trouble for you, you're not really qualified to flame the alpha testers.

---

Good Job it's not Friday today.


Dave

---

I couldn't see any local preferences to change, but hadn't tried the "Clear" function. That appears to have done it. Thanks.

Glad that cleared the problem.

The 6.10.18 version for example have so many bugs .....

The version I used before, 6.2.19 had no bugs that I noticed whatsoever.

Sten-Arne

It is easy to go back - just install again 6.2.19 (or 6.4.7 or 6.6.38) - no need to uninstall the 6.10.18 first

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I couldn't see any local preferences to change, but hadn't tried the "Clear" function. That appears to have done it. Thanks.

There seems to be a bug or so in the later versions of Boinc Manager, which in some cases, with some screen resolutions, makes the Advanced/preferences windows so small that all options becomes hidden/invisible. You can resize the window the normal ways until all options are visible.

The 6.10.18 version for example have so many bugs that I can't believe it's ever gone through a real beta testing, and if it was beta tested, it must have been tested by blind people. It's so many bugs that I don't even care to report them. The development team can't be too serious anyhow, if they let that kind of crap through without even noticing it.

The version I used before, 6.2.19 had no bugs that I noticed whatsoever.


Sten-Arne

Too bad you feel that way instead of offering to help.....

Offering to help? G*d Da**it, I'm helping every day, by running the client, yes even the optimized client on several computers. The least one could expect though, is that the software they release is thorougly beta tested before it's released.

So, I do help, but I do not get a program good enough to help with it seems eh? Upgrading from my old version, was the biggest mistake I made. However on one computer I had to do it because the old version could not run CUDA. Of course I upgraded computer 2 (this one) also, being stupid enough to believe that the latest recommended version must be at least as good as my old 6.2.19. At least I still have the old version on 2 other computers still, and it will snow in hell before I upgrade them.


I stand by what I said about the beta testing. Either the beta testers are blind, or the only thing they did with the program was to install it and let it run, only being interested in getting as much credit as possible.

A real beta tester has only one interest, and that is to abuse the program in every possible way, to find out in what situations it craps out, and why it happens. The science result for the beta tester should come in the last place, unless of course the program is so crappy that it doesn't produce even valid results.

They can't have tried all the different options it has, like mark up WU's and delete them, just as one example. Sure they get deleted and disappear most of the time, but often they get deleted but doesn't disappear from the managers view until you close down and restart the manager (without exiting the app of course). Even if you connect to another computer with the manager, it still shows the old computers WU's when this crap happens (which is too often)


Sten-Arne

Just who are these Beta Testers you are talking about? They are you and I, that is all there is. I B*tch a lot but am also willing to put up or shut up! So I guess it is up to everyone else to make a client you like. I wish they had the resources to test the way you feel it should be done, maybe if you add a green star they will be that much closer to getting there....

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Sorry to be so Negative Sten but I believe in one of the emails I recieved recently the Beta team had only like 9 responces in the last month. That will not move things along very fast. I did a test the other night that wiped over 1800RAC from my machine, guess what, it is all coming back and hopefully I helped with a major fix so it will work better for you and everyone else. They really do have LIMITED RESOURSES....

---

Official Abuser of Boinc Buttons...
And no good credit hound!

The 6.10.18 version for example have so many bugs .....

The version I used before, 6.2.19 had no bugs that I noticed whatsoever.

Sten-Arne

It is easy to go back - just install again 6.2.19 (or 6.4.7 or 6.6.38) - no need to uninstall the 6.10.18 first

I have to disagree. I've run just about every test release since 4.19. There has never been a Boinc version that didn't have some kind of bug or that didn't have some issue that needed to be addressed. All three of the mentioned versions had major problems that have to a large part been addressed although some minor things remain to be looked at. I've found very few releases, be they alpha or public that where unusable to a point of having to return to more than a previous minor revision.

I personally don't agree with the way scheduling was re-written but given time Boinc does adapt to the changes. The precipitous way that CUDA was introduce was ill thought out. They should have gone with a more independent GPU scheduler, possibly parallel code, with its own RS, STD, LTD and DCF. That is another issue that will hopefully be looked at in the future.

That being said I only crunch on the CPU, not having yet had a need to upgrade my system, so my knowledge of GPU problems have been gleamed from the forums at the various projects I contribute to.

Boinc has evolved, and changes have been made to the way it works. I don't always agree with the changes made, or the developers priorities, but a wholesale condemnation of the current version isn't productive. If there are specific issues, with the current version, they should be pointed out as accurately as possible so that they can be looked at. If the users don't report the problems they are having, how can they ever be fixed.

At one point they had maybe 50 or 100 Alpha testers and a few hundred people like myself that run the latest Alpha versions but don't go through the full testing procedures. That isn't close to being representative of all the possible system configurations of the 1/2 million computers that are running Boinc. Without proper feedback, people can complain all they want, but it wont help solve the problems, real or perceived, that they are having.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Too bad you feel that way instead of offering to help.....

I stand by what I said about the beta testing. Either the beta testers are blind, or the only thing they did with the program was to install it and let it run, only being interested in getting as much credit as possible.

Thank you for offending most of us who have a "volunteer tester" tag.

One of the problems with BOINC testing is that a lot of people grab the latest development version, run it for ten minutes, and then complain (here) that it does not work.

If you want to test BOINC, then you need to join the BOINC Alpha mailing list, do as many of the tests as you can, and report your results.

If you see an anomaly, report it.

That's "helping test."

... and for what it's worth, your "green star" benefits SETI@Home. BOINC is not SETI@Home, and SETI@Home is not BOINC.

If you don't want to test, that's fine. But don't say "I'm helping" and then torpedo the people who are doing the testing.

Now, where did I leave that white cane?

---

Too bad you feel that way instead of offering to help.....

I stand by what I said about the beta testing. Either the beta testers are blind, or the only thing they did with the program was to install it and let it run, only being interested in getting as much credit as possible.

Thank you for offending most of us who have a "volunteer tester" tag.

One of the problems with BOINC testing is that a lot of people grab the latest development version, run it for ten minutes, and then complain (here) that it does not work.

If you want to test BOINC, then you need to join the BOINC Alpha mailing list, do as many of the tests as you can, and report your results.

If you see an anomaly, report it.

That's "helping test."

... and for what it's worth, your "green star" benefits SETI@Home. BOINC is not SETI@Home, and SETI@Home is not BOINC.

If you don't want to test, that's fine. But don't say "I'm helping" and then torpedo the people who are doing the testing.

Now, where did I leave that white cane?

I did'n grab any development version, I grabbed the official 6.10.18, and I run it not for 10 minutes, but for a long time and didn't complain for a month about the flaws.

I'm helping SETI dammit, by running the client(s) 24/7, and I can say whenever I want that "I'm helping", at the same time as I complain about the version release. If you as a tester feel torpedoed by that, then maybe you feel guilty about not testing thorougly eh?

And again, my Green star is with my power company, something you people with almost free energy (and endless pumping out of crap into Atmosphere) seems totally incapable of understanding.

And if I have to repeat it again (since you obviously use a white cane) I'm a volunteer user of BOINC in SETI only, I want to use the program not test it. If the testers doesn't do a good job, I will and I have the right to complain. Just as much as I complain when Windows behaves crappy. I do have the right to do that without being part of any MS beta test group.

Just a year or so back, I grabbed the then official version 6.2.19, and now a month ago I upgraded to 6.10.18. One might almost be led to believe that the churning out of new versions with such a speed, may be one reason for the bugs. They aren't tested enough before they become the official latest version.

With that speed, Windows would today perhaps not be called Windows 7, but rather Windows 700.

Sten-Arne

I think you're pointing the Blame in the wrong direction, Boinc 6.10.17 was the first 6.10.x release that was given recommended status, it's a vast improvement over 6.4.x and 6.6.x,
but still work in progress,
While i'm not an Official Alpha tester, i report any Bugs, Typos and Inconsistencies i find, and so do others, the Developers don't always do anything about them straight away,

I reported one such Bug on 27th October, Another User confirmed it on a older development version, but there was no comment from the developers,
The developers went ahead with releasing 6.10.17 anyway, then 6.10.18 was released shortly afterwards,
The Bug didn't get fixed until 11th Nov, so the fix made it into 6.10.19, but that's not a Recommended version, and there hasn't been another since,
Now, 3 of my projects have the options affected by my Bug, and we're still on a Recommened version of 6.10.18,
There's talk of recommending 6.10.32 soon, as there's been lots of fixes & feature changes since 6.10.18, but the Alpha testers and Others are still testing it,

Claggy

I did'n grab any development version, I grabbed the official 6.10.18, and I run it not for 10 minutes, but for a long time and didn't complain for a month about the flaws.

I'm helping SETI dammit, by running the client(s) 24/7, and I can say whenever I want that "I'm helping", at the same time as I complain about the version release. If you as a tester feel torpedoed by that, then maybe you feel guilty about not testing thorougly eh?

The volunteer testers doesn't have a month to test a new possible release, it's instances there the testers only get a couple days to report-back if there's any major problems to hold-up the release.

Also, even if the testers does report a bug, it's not given it's deemed bad enough to hold-up a release. Generally speaking, any crashes has 1st. priority, and will hold-up a release. Any other problems that will affect many users, like computer sitting idle and so on, will also hold-up the release. Minor problems that's either already present in previous BOINC-client-releases, it's only a cosmetic problem (example typing-errro), or only a small minority of users is affected by the problem, will normally not hold-up a release.

And again, my Green star is with my power company, something you people with almost free energy (and endless pumping out of crap into Atmosphere) seems totally incapable of understanding.

No problem, volunteer the way you can.

And if I have to repeat it again (since you obviously use a white cane) I'm a volunteer user of BOINC in SETI only, I want to use the program not test it. If the testers doesn't do a good job, I will and I have the right to complain. Just as much as I complain when Windows behaves crappy. I do have the right to do that without being part of any MS beta test group.

Just a year or so back, I grabbed the then official version 6.2.19, and now a month ago I upgraded to 6.10.18. One might almost be led to believe that the churning out of new versions with such a speed, may be one reason for the bugs. They aren't tested enough before they become the official latest version.

There are too few active testers that reports any problems to catch all the various bugs, and it's a problem that new BOINC-client-releases is often driven by adding new features while majority of the known bugs is pushed to next release. Despite of this, the wast majority of BOINC-users seems to have minimal or no problems with BOINC.

So yes, you'll likely to find some bugs in BOINC, even v6.10.18 is the current release-build it does have many bugs. You'll also entitled to complain about bugs. But, just complaining isn't generally very useful, and any posts like "BOINC is too buggy" won't really help, since no-one will know what bugs you're talking about, and not knowing the bugs it's also impossible to fix them and by this hopefully improve the next release-build.

You don't need to be a volunteer tester, and you don't need to run the latest test-build of BOINC. Still, when you hit a problem, and doesn't find any thread about this on the forum, it's still an advantage if you can do something like this:

1: If there's not a generic thread about example BOINC-version v6.10.18, make a new thread of your own. Don't use a completely unrelated thread to complain or report problems, since it's much less change your report will be seen, and it's much larger chance your post will be deleted due to being completely off-topic for the thread.
2: Post as delailed a description of your problem as you can, if there's an easy way to replicate a problem please include this if you've found this method.
3: It's often best to include only one problem in a post, but including multiple problems can be an option. If multiple problems, it's an advantage if you numbers the problems since this makes it easier to comment on individual parts, and it also clearly shows there's multiple problems.
4: Include any relevant info like OS and BOINC-version, including cpu & memory is often not relevant for the problem but still including it is generally easier than needing to include it later.
5: Check-back to the thread within a day or something, in case there's any posts asking for more info, or methods to fix your problem in case it's a known problem.
6: Don't expect immediate replies to your post.
7: Even if you've found a real new bug, don't expect it's fixed in the next release-build. Still, it's better to report a bug anyway.

Using something like this increases the chance of fixing any bugs, so thanks in advance for your report. A non-reported bug has basically zero chance of being fixed...

So, looking on your posts in this thread, I can only see a single reported problem, even you do alludes to multiple major problems. Also, I'm sorry to say, but I don't understand the description of the problem you did mention.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

I'm helping SETI dammit, by running the client(s) 24/7, and I can say whenever I want that "I'm helping", at the same time as I complain about the version release. If you as a tester feel torpedoed by that, then maybe you feel guilty about not testing thorougly eh?

You said testers were "blind" and that's why BOINC does not work.

I'm offended by that characterization. Both parts.

If you just want to run BOINC, and complain about it, that's fine, but there is a huge difference between "helping SETI" and "helping BOINC."

If you don't want to test BOINC, then don't insult those who do.

---

The Bug didn't get fixed until 11th Nov, so the fix made it into 6.10.19, but that's not a Recommended version, and there hasn't been another since,
Now, 3 of my projects have the options affected by my Bug, and we're still on a Recommened version of 6.10.18

I develop software for a living and right now the next release of my major commercial project is getting ready to go into beta test.

... and people who don't code don't realize what goes into that.

Here is a good example. I found a way to speed up one function sixty times (this was code that was fast enough a few years ago, but slow now), and I put in the change. Took a couple of hours to find all the spots that were affected.

I spent the next ten hours testing and verifying that everything worked. It was flawless here.

I then put it into a production environment and ran for a day.

I gave it to a small group of alpha testers, and spent yesterday fixing two serious bugs that simply did not show up in my exact circumstances.

A big part of developing and releasing software is testing, and for something like BOINC where there is a fairly loose connection between the developers and the projects (Sten-Arne is a good example, he's complaining about BOINC and disparaging the testers, but he isn't doing it in a BOINC forum), it makes the release process glacially slow.

... especially when the average BOINC user is set-and-forget -- that they may not look at their machines at all. You want to make sure you don't change BOINC in some way that hurts the smaller machine that is not a dedicated cruncher.

---

I'm helping SETI dammit, by running the client(s) 24/7, and I can say whenever I want that "I'm helping", at the same time as I complain about the version release. If you as a tester feel torpedoed by that, then maybe you feel guilty about not testing thorougly eh?

You said testers were "blind" and that's why BOINC does not work.

I'm offended by that characterization. Both parts.

If you just want to run BOINC, and complain about it, that's fine, but there is a huge difference between "helping SETI" and "helping BOINC."

If you don't want to test BOINC, then don't insult those who do.

Whatever.....

I give up on you.

.... and I haven't. I'm hoping that you can understand that the testers (and the developers) are real people, who don't like being called incompetent.

---

I, nor any of the mods are going to ban anyone for speaking their opinion in a civilized manner. What I have a problem with is the generalizations of all Americans as Yankees, which in this context is meant to be an insult. Making such insulting generalizations is no way to get your point across, nor does it really have anything to do with the issue at hand (i.e. your problems with BOINC).

So I am asking nicely, please do not continue in such an insulting manner. If you do, we will have to start removing posts.

---

Get off your high Yankee horses. Nobody in this household is impressed by any Yankee antics. You can't scare me.

What will you do? Nuke my entire country eh? Have me banned for voicing my opinion, because you feel offended?

Sten-Arne, I am not the one who brought up genocide.

I think that qualifies as "abusive comments involving race or nationality."

Calling testers "blind and incompetent" is being offensive to a large group.

The only thing I've accused you of is being rude.

---