I'm running SETI on 7 computers. Now all of them with the same system.
And one of them is unable to connect to BOINC for over three of days. I have set the wU buffer to five days, so the machine has still enough to crunch, but I am annoyed as all the other computers do connect without any problems. Plenty of space, connection works with all ohter problem, it worked smooth for about a month.

Updating doesn't help.
Restarting the computer doesn't help.
And I don't want to lose computed WUs.

Any suggestions?

Marek

---

Now I have 17 completed WUs, ready to report and I do not want to lose them. Is there a way to keep them over reseting SETI?

---

> Now I have 17 completed WUs, ready to report and I do not want to lose them.
> Is there a way to keep them over reseting SETI?
>
no

---

How much memory does that one machine have? If it is only 64 meg or ram that is the problem, Boinc now requires 64 meg "free".
Meaning that when I had a machine with 128 meg of ram and 64 meg of it set up for the onboard graphics card, Boinc refused to run. I changed the graphics memory to 32 meg and Boinc runs fine.

---

> How much memory does that one machine have? If it is only 64 meg or ram that
> is the problem, Boinc now requires 64 meg "free".
> Meaning that when I had a machine with 128 meg of ram and 64 meg of it set up
> for the onboard graphics card, Boinc refused to run. I changed the graphics
> memory to 32 meg and Boinc runs fine.

I do not think this is a problem as the client keeps running and crunching and even uploading, it only does not report completed WUs and update the credit from the seti servers.
Also the computer stopped reporting only three days ago without any apparent change done.

But I will have a look anyway. Thanks.

Marek

---