Well in 7 days I will see if BT is even worth having on My hdd again, cause if I find that Boinc Manager has no such problem(which happened under 7.0.62 when I did run BT and 7.0.62 together), I had plenty of work on the hdd then as I do now, just BT thinking no gpu work was available and so no gpu activity, yet the cpu had plenty, yet there were no massive downloads when BT restarts, just restarting 5 work units... Cause if I find no problems, it will be uninstall and full folder erase of BT and any and all BT installers, cause I will be done here for good, since I don't like being abandoned...

You can even run the BOINC Manager alongside BoincTasks.
BoincTasks is only the visual shell, doesn't start or stop anything all by itself.
It may have been caused by going from V7 back to V6.
And there are so many BOINC version that it's impossible for me to test them all, again and again.

There are thousands of BoincTasks users and this is the only report of this kind of problem.

You are not forced to use BoincTasks....

---

TThrottle The way to control your CPU and GPU temperature.
BoincTasks The best view of BOINC.
My other activities

Well in 7 days I will see if BT is even worth having on My hdd again, cause if I find that Boinc Manager has no such problem(which happened under 7.0.62 when I did run BT and 7.0.62 together), I had plenty of work on the hdd then as I do now, just BT thinking no gpu work was available and so no gpu activity, yet the cpu had plenty, yet there were no massive downloads when BT restarts, just restarting 5 work units... Cause if I find no problems, it will be uninstall and full folder erase of BT and any and all BT installers, cause I will be done here for good, since I don't like being abandoned...

You can even run the BOINC Manager alongside BoincTasks.
BoincTasks is only the visual shell, doesn't start or stop anything all by itself.
It may have been caused by going from V7 back to V6.
And there are so many BOINC version that it's impossible for me to test them all, again and again.

There are thousands of BoincTasks users and this is the only report of this kind of problem.

You are not forced to use BoincTasks....

Then I'll have to stop all downloads, done, once I'm out I'll have to uninstall 6.10.58 and rename the Boinc folders and start over from scratch, after detaching from Seti, then reattach all over again...

---

Play MULE, 42 is irrelevant

@VW Bobier: Both BOINC Manager and BOINCTasks are graphical user interfaces. They allow you to give commands to the underlying BOINC client in an easier way than having to do so through a command line window. Other than storing around 2,000 lines of text in the Event Log/Messages, they do not do any of the downloading, uploading, reporting, caching of work, scheduling which project to run next and all those other fun things that you see being done.

All that is done by the BOINC client. Which is a separate program. Both BOINC Manager and the BOINC client are developed and made by Berkeley.

Fred his programs are third party, they work with the BOINC client. He does not work for the developers in Berkeley, although he does work with them at times when a bug is found. As far as I know, Fred lives nowhere near Berkeley --though I could be mistaken, wasn't it Blaricum? ;-)

If you find that downloading, uploading, reporting or running of work has changed between BOINC versions, then it's due to differences in those BOINC versions, not due to BOINCTasks.

---

@VW Bobier: Both BOINC Manager and BOINCTasks are graphical user interfaces. They allow you to give commands to the underlying BOINC client in an easier way than having to do so through a command line window. Other than storing around 2,000 lines of text in the Event Log/Messages, they do not do any of the downloading, uploading, reporting, caching of work, scheduling which project to run next and all those other fun things that you see being done.

All that is done by the BOINC client. Which is a separate program. Both BOINC Manager and the BOINC client are developed and made by Berkeley.

Fred his programs are third party, they work with the BOINC client. He does not work for the developers in Berkeley, although he does work with them at times when a bug is found. As far as I know, Fred lives nowhere near Berkeley --though I could be mistaken, wasn't it Blaricum? ;-)

If you find that downloading, uploading, reporting or running of work has changed between BOINC versions, then it's due to differences in those BOINC versions, not due to BOINCTasks.

I never said Fred worked or had anything to do with Berkeley, Ageless...

---

Play MULE, 42 is irrelevant

Please don't put words in My mouth that I didn't say, ageless...

---

Play MULE, 42 is irrelevant

I did not put words in your mouth, instead am trying to explain to you something about the working of BOINC versus BOINC Manager versus BOINC Tasks. You on the other hand should start to read what Fred is trying to tell you.

You said here: Something is going on Fred, Tonight I may shut down BoincTasks 1.47 and use BoincManager 6.10.58 instead... Cause I don't like the idea of the gpu stopping work... When the gpu has plenty of work on hand and yet forgets that it has any...

Fred answered here: You lost me, BoincTasks does nothing, just shows you what's going on. The BOINC client is the one that does all the work, like running GPU tasks.

You said here: Look there was no lack of work on the hdd, the cpu kept doing work, just the gpu stopped doing work cause BT thought there was none to be done... Capice?

Fred answered here: BoincTasks only does something when you tell it to, not by itself.

You said here: if I see a problem ok, if I do not see a problem like where no gpu tasks are being worked on and such, yet there was evidence of a full cache of gpu work, like happened under BT 1.47, then what Fred?

Fred answered here: And as I said the problem isn't BoincTasks related as far as I can tell.

You said here: I had plenty of work on the hdd then as I do now, just BT thinking no gpu work was available and so no gpu activity, yet the cpu had plenty, yet there were no massive downloads when BT restarts, just restarting 5 work units...

Fred answered here: BoincTasks is only the visual shell, doesn't start or stop anything all by itself.

Now, you can quote this whole post (as if I didn't know what I just posted) and angrily tell me off for whatever, but that doesn't mean you can't start reading what is being said to you, that in all the cases addressed above you're talking about the BOINC client doing that, not BOINCTasks, not BOINC Manager.

---

What about this?

He does not work for the developers in Berkeley, although he does work with them at times when a bug is found. As far as I know, Fred lives nowhere near Berkeley --though I could be mistaken, wasn't it Blaricum? ;-)

I didn't say He did any of the above...


So when My cache is empty I'll detach and uninstall Boinc, then rename the two folders boinc knew about and then reinstall boinc 6.10.58 x64 and reattach, as that seems to be the only solution open to Me, since I had thought I'd done enough before, I used the old folders last time I started over and lost cpu work in the process, this time the old folders will not be reused as it seems something might be borked, but if this still doesn't fix the problem, then what do I do?

---

Play MULE, 42 is irrelevant

By continuously stating that BOINCTasks was causing the GPUs not to do work, or doing other command decisions, you imply that BOINCStats is a program made by Berkeley, is part of BOINC and is the whole culprit of the problems you see... while it isn't, it's the BOINC client that does so and is.

That has nothing to do with putting words in anyone's mouth (which I still haven't done, not even in the sentence that you quote. Please go reread what I wrote), but all to do with a combination of barking and wrong tree.

Apropos, as per your I don't want or see the need to run 7.0.64 yet, since there are no native apps outside of Beta, 7.0.64 is the recommended BOINC client for Windows, 7.0.65 is recommended for Linux and Macintosh.

BOINC 7 has nothing to do with Seti v7. Seti v7 will eventually come out of beta, and then it'll be able to run on any BOINC client that's used out there, from 4.19 through to 7.x.x (whichever it is that's recommended then or being tested).

Seti is a project, just as Einstein, World Community Grid, GPUGrid, Primegrid, Malariacontrol.net, Climateprediction.net etc. are. The science application version numbering has nothing to do with the BOINC version being used. Please make sure you understand the distinction.

I've asked other moderators to take over in this thread. I'm stepping out of here, not going to be further drawn into a fight.

Ok, I have to apologize to both Ageless and to Fred, :O , I uninstalled Boinc yesterday, renamed the two folders so that when I reinstalled Boinc there would be new folders and files created(I didn't get the hidden one that pertains I think only basic data, like where the data file goes), I attached to Seti and started work at 8pm, I'd tried to go to sleep at 11:30pm couldn't, so at 1:30am I got up and stayed up until 2:30am, the last time a gpu work unit was processed was at 2:59:59am, the next one started a little before 6:18:50am,when I moved mouse, which I found odd to say the least, as I'd seen this more than once, so I did a Google search concerning that time frame of 3:00am, guess what? It might be Windows Update shutting the video card down, as it's has a default time of 3:00am if one is downloading but not installing updates or if one wants to be notified of new up dates, so I had to set for full automatic so the time could be set for like 9:00am and there are 3 boxes there, one to Microsoft I unchecked and one for recommended updates I unchecked, but who can install updates is still checked, it just means I would have to pay attention to the hardocp for update news, I found this in a Bitcoin forum of all places, I'll know more Sunday morning, for now I can only wait. Windows can be so complicated in what effects what...

---

Play MULE, 42 is irrelevant

So, original thread cleaned out as requested by Fred. Any posts that belong in the original thread, please let me know.

Oh and excuse me for the large amount of PMs one both of you will have. I wonder why we can't turn that off...