Just attach the BOINC on my home computer to another project other than Seti@home?

I've never done that, but I could give it a try.

Well, it's been over 24 hours with this issue on the home computer...with that "http file not found" in the messages.

OTOH, with my work computer, I don't have any problems. For some reason, the work computer has 10 or 11 tasks, though it only works on one at a time. Very confusing.

I clicked the update button, which I think normally gets new work, doesn't it? At least, it's worked in the past.

But, that's the basic message I've gotten since yesterday on my home computer.

The update button only gets new work if its needed. If BOINC determines that it doesn't need new work, then it will not fetch more even if the update button is pressed.

Also, I would advice against manually fetching work by hitting the update button unless its absolutely necessary. I would recommend letting BOINC retrieve work when it needs to, unless you're on dial-up and you don't plan to be on very long or need more work for a longer outage in the future.

The second comment first. Because there is a cost to switching tasks frequently, BOINC only does one task per CPU. If you only have one logical or physical CPU, then you only run one task at once. The number of tasks on hand is determined by "Connect every X days" and "Additional work". Connect every X days is a promise by you that you will connect at least that often. Extra work is to tide you over for short outages. For longer outages, there is nothing like having a second (or third, or fifty third) project attached.

For the first question. Is BOINC on the computer that is having trouble attached to any other projects? If it is not, could you try attaching it to some other project for diagnostics? I would not suggest CPDN as the tasks take a couple of months to complete.

Well, it's been over 24 hours with this issue on the home computer...with that "http file not found" in the messages.

OTOH, with my work computer, I don't have any problems. For some reason, the work computer has 10 or 11 tasks, though it only works on one at a time. Very confusing.

I clicked the update button, which I think normally gets new work, doesn't it? At least, it's worked in the past.

But, that's the basic message I've gotten since yesterday on my home computer.

The update button only gets new work if its needed. If BOINC determines that it doesn't need new work, then it will not fetch more even if the update button is pressed.

Also, I would advice against manually fetching work by hitting the update button unless its absolutely necessary. I would recommend letting BOINC retrieve work when it needs to, unless you're on dial-up and you don't plan to be on very long or need more work for a longer outage in the future.

The second comment first. Because there is a cost to switching tasks frequently, BOINC only does one task per CPU. If you only have one logical or physical CPU, then you only run one task at once. The number of tasks on hand is determined by "Connect every X days" and "Additional work". Connect every X days is a promise by you that you will connect at least that often. Extra work is to tide you over for short outages. For longer outages, there is nothing like having a second (or third, or fifty third) project attached.

For the first question. Is BOINC on the computer that is having trouble attached to any other projects? If it is not, could you try attaching it to some other project for diagnostics? I would not suggest CPDN as the tasks take a couple of months to complete.

I clicked the update button, which I think normally gets new work, doesn't it? At least, it's worked in the past.

But, that's the basic message I've gotten since yesterday on my home computer.

The update button only gets new work if its needed. If BOINC determines that it doesn't need new work, then it will not fetch more even if the update button is pressed.

Also, I would advice against manually fetching work by hitting the update button unless its absolutely necessary. I would recommend letting BOINC retrieve work when it needs to, unless you're on dial-up and you don't plan to be on very long or need more work for a longer outage in the future.

The last two lines indicate that the communication with the server was successful, and I notice your client isn't requesting new work, probably because it already has enough or another project is getting CPU time.

Ok,
I'm running boinc on a vista machine. It's one of those snazzy new penryn chips, @4ghz and with 2 gigs of ram. It should handle everything I throw at it.
BUT. When I work on sketchup it seems that boinc won't let go of the processor, so I have to snoose boinc in order to work.
That's hardly like the idea of using 'spare' cpu cyles!

Anyone know what to do about it?

/Anton

There was a bug that I fixed around 5.10.20 that fixed this problem for some windows machines. Try upgrading to the latest version to see if the problem still persists.

I just installed BOINC and I'm running Seti@home, but when the screen saver comes on, it just has a floating BOINC logo, with the following message below it:

"Graphics cannot be displayed when configured to run as a Windows Service"

I must be missing something simple. Does anyone know what this means?

When my screensaver comes up, it's just the BOINC logo with the satus of the processing underneath. How can I get the cool SETI graphic to appear? There are no error messages that I can see.