If your running BOINC, and you disconnect from the Internet, and you run out of work suddenly you get a million pop-up messages telling you that you lost your connection.

Not only would one message be enough, but it's impossible to get back up to the menu to shut off the network access.

Other than that I like the program very much.

This can be regulated by changing the reminder frequency to 120 minutes.
Open Boinc Manager, Advanced, Options, General. Slide the Reminder Frequency bar to the right. Press OK.

If you have an older version of Boinc (4.xx to 5.2.x), it's found under Options, Options, General.

---

This can be regulated by changing the reminder frequency to 120 minutes.
Open Boinc Manager, Advanced, Options, General. Slide the Reminder Frequency bar to the right. Press OK.

If you have an older version of Boinc (4.xx to 5.2.x), it's found under Options, Options, General.

Be better if only one pop up was up at a time. I can come back to my computer and have multiple of these pop ups open - even with a setting of 120 minutes.

I've requested for an option to turn it off all together. Denied. :-(

But it's probable that it's no longer around in the simple GUI.

---

My connection error message aren't as frequent as those above but I do find that in the recent versions, 5.7.x and 5.8.x, that when a connection is lost Boinc won't reconnect on its own. It seems happy to use any already established connection but if it is the only program dialling out then it just comes back with the errors. If 5.6.5 finds no connection it will show the error, make the connection in the background (no message saying it is doing so)then use it after whatever the deferral time was. I'm on broadband, but programs need to make their own connection if one hasn't already been made, and the newest versions can't do this on their own.
Perhaps this bit of code has been inadvertantly omitted in the search to make the front end more friendly. I like the return of the pies last seen way back in 4.19, but the legend should, perhaps, be moved over to the blank area on the left. No criticism intended. In fact I hope it's helpful; as the BBC climate model finishes there will be a flood of people whose only contact with distributed computing will have been through their trimmed down interface so the simpler and prettier you can make the next stable release the better.

---

I thought the connection issue was fixed in 5.8.3 as it phoned home OK on startup but if the connection is dropped any subsequent connection request results in the errors again. If Boinc is shut down and restarted, connections are enabled again, but again only for the initial request and not any subsequent ones if the connection is interupted.
I seem to remember this happening with an earlier build, but I can't remember which, sorry.

Another variation on the above;
If Boinc is in the tray it can't dial out, but can as soon as the icon is clicked and it becomes the open window.
This is with the brand new 5.8.8 but I've tried 5.8.3 (above)and 5.7.4 before with the same symptoms. I have found 5.6.5 to be the newest version that doesn't have these connection issues but obviously this is before the simple gui.
On initial startup a connection is established after the first communication failed message. Subsequent communications are fine once the connection is active or using one already established. However, if the connection is dropped, no further communication is possible until the connection is either manually reconnected or another programme dials out.
While minimised to tray communications are fine with an existing connection but it cannot make its own. With no connection there are multiple communication error messages but as soon as it is brought up to be an open window it goes and dials out immediately without any problem.
Just observations. Hope they're useful.

Another variation on the above; {snip}

Passed on to the developers.

---

Tried 5.8.11 today and found the same symptoms. I found this thread from May '06 and this one from Dec '05 so it doesn't look like this is a new problem. What stopped it working?
I'll have a try over the next couple of days and report back if I can find the latest version that can phone home on the second attempt. (They can all do it at the first try but it's the subsequent ones when it's left to fend for itself overnight that it hits this snagette.)
Hope I'm being helpful :0/