V 5.10.7 is officially the recommended version

Download page

New Features:

* Grid based views.
* Advanced preferences dialog.
* Project list in the attach to project wizard.
* Improved Windows Vista compatibility.
* An Uninstaller is now included with the Macintosh BOINC Manager distribution.
* Support for x64 on Windows and Linux.

· NOTE: BOINC may NOT start at startup if you are running Windows Defender (WinXP, WinXPx64, WinVista, WinVistax64). This issue should be resolved in a future version of BOINC. In order to have BOINC start automatically you'll need to install as a service. On Vista the user account will need to have administrative access to the system.

· NOTE Also: V 5.8.16 is still the recommended version for Win95, WinNT4.0 as these OS are no longer being supported by the new releases.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

It needs to be stated that going to this version will result in people seeing project-side aborts with SETI. I'm sure that we'll see an increase in gnashing of fingers because people don't understand it...

Well, given the recent problems from the Mac version I had - deleting optimized app on it's own. Self deleting screwing around with people quota on the windows version i'll stick to an older version for now, will see what other problems crop up.

It needs to be stated that going to this version will result in people seeing project-side aborts with SETI. I'm sure that we'll see an increase in gnashing of fingers because people don't understand it...

You know, if you'd explain this now, I'm sure it would help! at least for me.

thanks.

dan

---

Plus 5,026 SETI Classic Units

It needs to be stated that going to this version will result in people seeing project-side aborts with SETI. I'm sure that we'll see an increase in gnashing of fingers because people don't understand it...

You know, if you'd explain this now, I'm sure it would help! at least for me.

thanks.

dan

If you have a result that you haven't started yet that has already met quorum and has been validated, the next time you connect with the scheduler, the scheduler will send your system an instruction to abort that unit, resulting in it not starting up at all from your side, you seeing messages to that effect in your messages tab, and the result showing up as "client error" on the web page. There is some discussion going on about changing it to be "Didn't Need" instead of "client error", but for now it will be "client error".

The reason behind this is because they don't feel that they need the extra result from a scientific basis if they already have a strongly similar pair. They could've sent aborts even if you had the result already in progress, but chose to be more "user friendly" and abort the unit only if there had not been any processing done on it already from your side.

This feature is supported in BOINC version 5.8.17 and higher, so 5.8.16, the previously "reccommended release" did not support it. 5.10.7 will support it and it is actively in use by SETI (other projects may or may not use the abort capabilities).

If you want to read more about it, read this message.

V 5.10.7 is officially the recommended version

Download page

New Features:

* Grid based views.
* Advanced preferences dialog.
* Project list in the attach to project wizard.
* Improved Windows Vista compatibility.
* An Uninstaller is now included with the Macintosh BOINC Manager distribution.
* Support for x64 on Windows and Linux.

· NOTE: BOINC may NOT start at startup if you are running Windows Defender (WinXP, WinXPx64, WinVista, WinVistax64). This issue should be resolved in a future version of BOINC. In order to have BOINC start automatically you'll need to install as a service. On Vista the user account will need to have administrative access to the system.

· NOTE Also: V 5.8.16 is still the recommended version for Win95, WinNT4.0 as these OS are no longer being supported by the new releases.

I run 5.8.16 on a dual boot system [Windows XP Pro X64 and Windows Ultimate 64] with Boinc installed on a third drive under both systems. If I am running X64 and reboot to Vista, then Boinc picks right up under Vista where it left off under X64.
If I Install the new version, will I have to do an install under both OS to the same location again?
Will I have to reinstall the chicken apps again?

---

When we finally figure it all out, all the rules will change and we can start all over again.

Last time I attempted to upgrade to the x64 version, it wanted to reset every project was attached to! I quickly stopped BOINC from getting more work and reverted and restored my old BOINC x32 folder.

Is there a more elegant way of upgrading without having to reset the project and losing all current work other than clearing my queue before I upgrade? Can/will something more elegant be automated through the software for those wanting to switch from 32bit to 64bit in an easy fashion?

---

Last time I attempted to upgrade to the x64 version, it wanted to reset every project was attached to! I quickly stopped BOINC from getting more work and reverted and restored my old BOINC x32 folder.

Is there a more elegant way of upgrading without having to reset the project and losing all current work other than clearing my queue before I upgrade? Can/will something more elegant be automated through the software for those wanting to switch from 32bit to 64bit in an easy fashion?

This was a problem with some of the earliest v5.9.xx-clients, and I don't remember in which version this was fixed. But atleast none of the v5.10.xx-Windows-clients resets project if you switches between 32-bit and 64-bit clients, and I've myself tested the upgrade from v5.8.16 to 64-bit without any problems.

With v5.10.6 and later you can also safely switch back and forth between 32-bit and 64-bit whenever you want. Switching back to 32-bit can be needed, since not all projects has yet upgraded their Scheduling-server to accept 64-bit clients.

I've not tried downgrading to v5.8.16 or earlier, but it should possibly work...

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

V 5.10.7 is officially the recommended version

Download page

New Features:

* Grid based views.
* Advanced preferences dialog.
* Project list in the attach to project wizard.
* Improved Windows Vista compatibility.
* An Uninstaller is now included with the Macintosh BOINC Manager distribution.
* Support for x64 on Windows and Linux.

· NOTE: BOINC may NOT start at startup if you are running Windows Defender (WinXP, WinXPx64, WinVista, WinVistax64). This issue should be resolved in a future version of BOINC. In order to have BOINC start automatically you'll need to install as a service. On Vista the user account will need to have administrative access to the system.

· NOTE Also: V 5.8.16 is still the recommended version for Win95, WinNT4.0 as these OS are no longer being supported by the new releases.

I run 5.8.16 on a dual boot system [Windows XP Pro X64 and Windows Ultimate 64] with Boinc installed on a third drive under both systems. If I am running X64 and reboot to Vista, then Boinc picks right up under Vista where it left off under X64.
If I Install the new version, will I have to do an install under both OS to the same location again?
Will I have to reinstall the chicken apps again?

Try installing only the 32 bit version under the XP to see if that works. The 64 bit version may cause grief for XP.

---

BOINC WIKI

Another thing about this SETI self-abort system is that anyone with an older machine might as well give up. With the speeds at which the Core 2 Duo and the Core 2 Quads are returning work any one with a machine slower than a P4 1.0GHz might as well retire them from the project.

I know that when the Mac finishes of the current queue of work it has it's bye bye BOINC for it.

Forget the above, i just tried installing 5.10.7, is it just me or does it seem like a step backwards, half the buttons seem missing and those that are there don't work, the "new" appearance is awful. Didn't even wait for the queue to finish SETI on the old Mac is dead. I found it totally user unfriendly. And if this is the way the boinc client is going I think I may stop all together. It's a shame becasue crunching for SETI, has been a laugh. I just wonder how long I can stick with 5.4.? what ever this laptop is using.

Forget the above, i just tried installing 5.10.7, is it just me or does it seem like a step backwards, half the buttons seem missing and those that are there don't work, the "new" appearance is awful. Didn't even wait for the queue to finish SETI on the old Mac is dead. I found it totally user unfriendly. And if this is the way the boinc client is going I think I may stop all together. It's a shame becasue crunching for SETI, has been a laugh. I just wonder how long I can stick with 5.4.? what ever this laptop is using.

Don't know if there's anything special with the Mac-client, but atleast with Windows-client there's now 3 views, "Simplified", "Advanced", and "Accessible view", there the last looks similar to "old advanced view" in earlier clients.

---

"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."

I have been running V 5.10.7 on Windows XP Pro, Windows XP Pro x64, Windows 2000, Linux x86_64, and Linux intel_x86 for about a week now. All appear to be stable, if you are running Linux projects that use the Boinc benchmark scores, the Linux scores for x86_64 are slightly low, and the i686 scores are WAY (50%) low.

---

Boinc Button Abuser In Training >My Shrubbers<

It wouldn't let me do anything, so i went back to 5.4.11, at least the old machne can have something to do during her final days.

I just installed 5.10.7, so far so good. I like the "accessible view", since it looks like the older versions. :-) Trying to get used to this "Maintain enough work for an additional (Requires 5.10+ client.)" stuff. Ill see how it works. Right now I run a setting of 0.5 days and 0.5 days, for now. Gonna have to play around with it a bit to see how this all works. LOL

Jeremy

---

It wouldn't let me do anything, so i went back to 5.4.11, at least the old machne can have something to do during her final days.

What exactly to you need to do in BOINC, anyway? It's all "set it and forget it". If you want all your buttons back, just go to View -> Accessible View. Voila!

---

Using winxp pro64 and the official 64b Boinc, I CAN get work from proteins, primegrid, WCG, Rosetta, Rieselsieve, malaria control, QMC, and Seti. I CAN'T get work from Leiden, RCN, Einstein, Tanpaku, LHC, and Chess960.

It wouldn't let me do anything, so i went back to 5.4.11, at least the old machne can have something to do during her final days.

It's all "set it and forget it".

Are you an undercover salesman for RONCO :)

---

Using winxp pro64 and the official 64b Boinc, I CAN get work from proteins, primegrid, WCG, Rosetta, Rieselsieve, malaria control, QMC, and Seti. I CAN'T get work from Leiden, RCN, Einstein, Tanpaku, LHC, and Chess960.

LHC is and has been out of work for a while now. In any case, you may want to check to see if you got a message back about detaching and reattaching due to the server migration...

It wouldn't let me do anything, so i went back to 5.4.11, at least the old machne can have something to do during her final days.

It's all "set it and forget it".

Are you an undercover salesman for RONCO :)

Someone said "It's showtime", and so he sprung into action... ;-)

Using winxp pro64 and the official 64b Boinc, I CAN get work from proteins, primegrid, WCG, Rosetta, Rieselsieve, malaria control, QMC, and Seti. I CAN'T get work from Leiden, RCN, Einstein, Tanpaku, LHC, and Chess960.

LHC is and has been out of work for a while now. In any case, you may want to check to see if you got a message back about detaching and reattaching due to the server migration...

NOTE: I have <work_fetch_debug/> set in my cc_config.xml file, so these won't be the messages most see, but I get this when trying to attach to LHC.

6/20/2007 9:56:08 PM|lhcathome|[work_fetch_debug] best project so far
6/20/2007 9:56:08 PM|lhcathome|[work_fetch_debug] compute_work_requests(): work req 19103.494041, shortfall 19103.494041, urgency Need immediately
6/20/2007 9:56:13 PM||[work_fetch_debug] time_until_work_done(): est 0.000000 ssr 120.000000 apr 1.977313 prs 100.000000
6/20/2007 9:56:13 PM|lhcathome|Sending scheduler request: Project initialization
6/20/2007 9:56:13 PM|lhcathome|Requesting 1 seconds of new work
6/20/2007 9:56:18 PM|lhcathome|Scheduler RPC succeeded [server version 505]
6/20/2007 9:56:18 PM|lhcathome|Message from server: platform 'windows_x86_64' not found
6/20/2007 9:56:18 PM|lhcathome|New host venue: home
6/20/2007 9:56:18 PM|lhcathome|Deferring communication for 1 days 0 hr 0 min 0 sec
6/20/2007 9:56:18 PM|lhcathome|Reason: requested by project
6/20/2007 9:56:18 PM||[work_fetch_debug] Request work fetch: RPC complete