my work pc recieves a constant flow of wu's. Everytime one completes I get another. However, at home it NEVER recieves a another wu when one completes. I gave boinc internet accsess and pass lock privliges and it never recieves another wu. I have to manualy transfer it every time and then "update" to recieve another. In the past my pc could crunch at least 3 to 4 wu's a day. Know it's only one, because it never recieves or sends any wu's.
Do I need to enable "com surrogate" or "client server something" to let BOINC send and recieve wu's?

---

In your account preferences you may have a setting of "Connect every xxx days" too low. It is this setting which determines how many WUs to download.

---

Are there any messages in the BOINC window? Perhaps there is a defer for xx days or something.

---

BOINC Doc | Team-Site | BOINC-Podcast

If you have used separate preferences for home, I believe that there is still a bug in that part.

With Rom working hard on the cross-platform GUI (which will fix that problem, if it is still there) this is an issue that can wait. Try setting the Home machine to the same preferences set as the one at work ...

---

I have the connect every xx days set to 0.1, I believe the default. I think I have figurd it out, Allthough I'm using maxthon web browser I still needed to give IE acsses to the net. I didn't need to do the manuel thing this morning, I'll find out tonight for sure. I do miss the cache option though, it worked well with my work pc.
Thanks all,

---

> I do miss the cache option though, it worked
> well with my work pc.

???
If you want to cache units, set the connect every X days to some other value, such as 4.
I've got mine set the the maximum (10).

---

Grant
Darwin NT

> If you want to cache units, set the connect every X days to some other value,
> such as 4.
> I've got mine set the the maximum (10).

For SETI@Home you do not want to use a value that is above 7 as the high watermark is 7 * 2 = 14 which is the deadline. With 10 it is 20 days and you will have some WU that may expire.

Now, note that if the compute time is always reported high and you can complete all WU before the deadline, belay my last.

---

For SETI@Home you do not want to use a value that is above 7 as the high watermark is 7 * 2 = 14 which is the deadline.
==========

Supposedly they did away with the x2 Paul, now if you choose 7 days thats what you get 7 days. I seen this posted somewhere in the Forum ...

> For SETI@Home you do not want to use a value that is above 7 as the high
> watermark is 7 * 2 = 14 which is the deadline.
> ==========
>
> Supposedly they did away with the x2 Paul, now if you choose 7 days thats what
> you get 7 days. I seen this posted somewhere in the Forum ...
>
This is NOT a supposedly it is a fact! If you look VERY closely at the code the line that has the "x2" in has a "\" near the beginning of it. In code language \\ means "ignore this line". The next line says that you can have a max of 10 days cache. Dr. Anderson posted this in another message.

---

Poorboy; Mikey,

> This is NOT a supposedly it is a fact! If you look VERY closely at the code
> the line that has the "x2" in has a "" near the beginning of it. In code
> language \ means "ignore this line". The next line says that you can have a
> max of 10 days cache. Dr. Anderson posted this in another message.

And that is what I get for taking a nap!

:)

If I can't keep up, I should take notes ...

Ok, one more thing to look at ...

I wonder if that is now a configurable parameter as other projects may have different guidelines, including one where 10 days is also too long ...

---