Hi all,

I just upgraded from a P4 1.7Ghz to a P4 3.4Ghz on one machine, the other 3 remaining as is.

On the upgraded machine, it is running XPSP2 and since the new CPU came in and as the motherboard was capable of supporting it all, I now have hyperthreading running properly on it. This means 2 BOINCs running at the same time crunching data.

Normally, I dont have a problem with that but periodically I do. If I SUSPEND Boinc I get all possible processing time back but sometimes that isnt what I intend. I would like to be able to keep processing Seti@home/Boinc on one "side" and susped the other now and then.

I know I am asking for a lot but if you dont ask, you never know. So, is it possible?

Also, when you exit Boinc Manager, Seti keeps right on plugging away at things. I would like to be able to exit Seti at the moment I exit Boinc Manager (which is what I used to do prior to it being called Boinc *Manager*). In order to exit both, I have to call up the task manager and cancel Boinc to get rid of Seti for now and then exit Boinc manager. Any better way that doesnt involve "suspend"?

Thanks,

Greg.

You can set your preferences to only use 1 CPU in a multi-CPU system. That is currently the only way to do what you are looking for. Also I assume that by "This means 2 BOINCs running at the same time.." just means that BOINC is running 2 work units at the same time. You should NOT have 2 copies of BOINC running.

As for the problem of seti continuing to run, I'm not sure what to tell you. When I exit BOINC, it automatically shuts down seti and any other project I'm running. I think there was an older version of BOINC that had problems with this but they fixed it a couple months ago. And the switch to calling it the "work manager" is NOT an official name change. That term was introduced here on the message boards to try and help the confusion people were having because there is the 'core client' (now called the 'work manager' by many here) and the 'science application'. (seti@home, lhc, cpdn, etc.) Officially it is still called the core client.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

> You can set your preferences to only use 1 CPU in a multi-CPU system. That is

Thanks for that. Will look at that one then!

> currently the only way to do what you are looking for. Also I assume that by
> "This means 2 BOINCs running at the same time.." just means that BOINC is
> running 2 work units at the same time. You should NOT have 2 copies of BOINC
> running.

I guess I mean there is Boinc Manager, Boinc and 2 copies of Seti@home running in Task Manager.

>
> As for the problem of seti continuing to run, I'm not sure what to tell you.
> When I exit BOINC, it automatically shuts down seti and any other project I'm
> running. I think there was an older version of BOINC that had problems with
> this but they fixed it a couple months ago. And the switch to calling it the
> "work manager" is NOT an official name change. That term was introduced here
> on the message boards to try and help the confusion people were having because
> there is the 'core client' (now called the 'work manager' by many here) and
> the 'science application'. (seti@home, lhc, cpdn, etc.) Officially it is
> still called the core client.
>


I am using Boinc Manager V4.56 which appears to be the latest one. Prior to using it, when I wanted the CPU time entirely to myself, I would exist what was then called "Boinc" and that would stop Seti@home running. Now, when I exit Boinc Manager, it shows it gone in Task Manager but Boinc and the 2 Seti@home WUs are running. Oh wait, I just kept exiting Boinc Manager (right click on tray icon then exit) then restarting it from the shortcut I pinned to the start menu. Sometimes it exits peacefully and other times just Boinc Manager is gone. Not sure what to say now.

One other thing I forgot about - I have backups happen twice a week on all machines. When Boinc Manager is running, it keeps the session open on each machine not allowing the program that does backups to reboot the machine and do the backup itself. A pain in the arse!

Oh well, I know I am looking at a Beta version.

Thanks for the help.

Greg.

The version 4.5x line ups the confusion a bit, it is divided into 3 parts. There is the manager, boincmgr.exe, which the user uses to interact with BOINC. The core client, boinc.exe, which does the house keeping. And the science applications which do the actual work (names vary with project).

In my experience 4.56 has normally exited the core client whenever I exit the manager, and the manager has started the client any time it runs, in 4.55 neither would happen. I also see a windows message that boinc.exe will not end when I do a restart, however it does exit after a moment. I am doing it manually though, that message may be enough to block the automatic restart for some reason though.

The 4.5x line is still pretty rough around the edges, I do not recomend running it if you do not have a specific reason to do so.

---

BOINC WIKI

BOINCing since 2002/12/8

> The version 4.5x line ups the confusion a bit, it is divided into 3 parts.
> There is the manager, boincmgr.exe, which the user uses to interact with
> BOINC. The core client, boinc.exe, which does the house keeping. And the
> science applications which do the actual work (names vary with project).
>
> In my experience 4.56 has normally exited the core client whenever I exit the
> manager, and the manager has started the client any time it runs, in 4.55
> neither would happen. I also see a windows message that boinc.exe will not end
> when I do a restart, however it does exit after a moment. I am doing it
> manually though, that message may be enough to block the automatic restart for
> some reason though.
>
> The 4.5x line is still pretty rough around the edges, I do not recomend
> running it if you do not have a specific reason to do so.
>

Thanks but I have to. I was finding, on 4.53, that my WUs that were completed when I wasnt online would be deleted and never sent back which is why I had to upgrade. I didnt upgrade to 4.53. That was forced down the pipe to me and upgraded for me.

The problem still occurs, though. Still intermittently not exiting Seti WUs or BOINC when shutting Boincmgr.exe down. A real annoyance!

Hi

The upload bug is fixed in 4.56.
I didn´t have this problem, but the shutdown issue is tricky.

greetz Mike

---

With each crime and every kindness we birth our future.

> Hi
>
> The upload bug is fixed in 4.56.
> I didn´t have this problem, but the shutdown issue is tricky.
>
> greetz Mike
>
>

Yes, I understand but 4.56 has other problems such as not exiting gracefully etc.

Such is life!