BOINC 7.4.42 is the new recommended version, is there any issues to be aware of when upgrading from 7.4.36?

I upgraded one host (7526144) this morning without a problem, but that's a very "generic" machine -- YMMV.

-Werecow

---

BOINC 7.4.42 is the new recommended version, is there any issues to be aware of when upgrading from 7.4.36?

Upgraded a pc running Lunatics without any issues..

P.

---

Upgrade went through with no problems. My cruncher is very vanilla though.
What changes were made to this new version?

---

Upgrade went through with no problems. My cruncher is very vanilla though.
What changes were made to this new version?

Not many. Release Notes

AFAIK, in v7.4.36 the '0 resource share' didn't worked.

In v7.4.42 it work again (work request at this project with '0' if BOINC have no WUs ready for crunching)?

---

AFAIK, in v7.4.36 the '0 resource share' didn't worked.

In v7.4.42 it work again (work request at this project with '0' if BOINC have no WUs ready for crunching)?

Re-read the release note page I linked. That was a mistake in v7.4.26/27, and it was fixed in v7.4.36

I had to read this part of the release notes, in known issues, a few times to believe my eyeballs.

Windows
Service Installation, GPU detection and Windows XP: Due to problems with up-to-date GPU drivers causing BOINC to crash or hang, it was decided that for all versions of Windows the GPU detection will no longer work when BOINC is installed as a service. This may change in a future version, but only after the GPU manufacturers have adjusted their driver code. So even in Windows 2000 and XP you can now no longer install BOINC as a service yet still have it detect your GPU(s) and run work on it. This change is present since 6.12.38

High marks for creativity, but sadly incorrect with respect to it being about GPU drivers. Windows Session 0 Isolation is an operating system security feature, not something drivers can or should attempt to workaround. You can make a service launch a Session1 application instance once an interactive login is detected, but then that'd be harder than launching Boinc at login anyway...

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I had to read this part of the release notes, in known issues, a few times to believe my eyeballs.

Windows
Service Installation, GPU detection and Windows XP: Due to problems with up-to-date GPU drivers causing BOINC to crash or hang, it was decided that for all versions of Windows the GPU detection will no longer work when BOINC is installed as a service. This may change in a future version, but only after the GPU manufacturers have adjusted their driver code. So even in Windows 2000 and XP you can now no longer install BOINC as a service yet still have it detect your GPU(s) and run work on it. This change is present since 6.12.38

High marks for creativity, but sadly incorrect with respect to it being about GPU drivers. Windows Session 0 Isolation is an operating system security feature, not something drivers can or should attempt to workaround. You can make a service launch a Session1 application instance once an interactive login is detected, but then that'd be harder than launching Boinc at login anyway...

That's why I still run BOINC v6.12.34 on my Windows XP machines - last version of BOINC which works in service mode on an OS which doesn't need that trickery (and for personal use, I'm prepared to accept the security risk, such as it is).

Edit - IIRC, when that was first written (it was a long time ago), it was only ATI drivers which caused a crash/hang when BOINC attempted GPU detection.

Edit - IIRC, when that was first written (it was a long time ago), it was only ATI drivers which caused a crash/hang when BOINC attempted GPU detection.

Yeah there always seem to be some growing pains whenever a core change like that happens, and some or another vendor finds the pitfalls first. There have been, (and maybe still are), ways to trick nv gpu equipped systems into using Tesla Compute Cluster Drivers (Which internally don't present as a graphics device to the service), But I think if it's a choice between letting Boinc code into my kernel space, and having to login (either automatically or manually) then I'll choose the latter :)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I had to read this part of the release notes, in known issues, a few times to believe my eyeballs.

Well, you have to give them at least a couple of balls for admitting it is broken...LOL.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I had to read this part of the release notes, in known issues, a few times to believe my eyeballs.

Well, you have to give them at least a couple of balls for admitting it is broken...LOL.

haha true. Maybe they could reword it something nicer like "*Somebody* (i.e. m$) went and changed the rules for services & GPUs from Vista onwards, and this affects XP because GPU vendors want their updated drivers to pass certification...and not Bluescreen..."

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Maybe they could reword it something nicer...

This is the BOINC User Manual Wiki. It's mainly kept up-to-date by BOINC users. Or at least, by those two or three still surviving/interested ones who pass by there once in a blue moon and who when they see something wrong, may edit it.

So you could friendly ask someone with an account to do so and tell what to change; e.g. Richard has an account, I have one.

But easiest is to just get your own account so that in the future when your eyeballs burn out of their sockets again, you don't have to sneakily flame the person who wrote something there, but instead you can go in and change it immediately. To do so, email David and ask for an account, then go edit and reword everything in your own image.

---

Thanks for the advice, and invitation, and no 'sneaky flaming' intended. I reread my posts here and see a technical challenge, which I appreciate some may get defensive about (while others thrive on it).

As to the recommended direct approach, that's been attempted in other (not very related) areas and met with similar defensiveness when technical facts are presented.

While I'll most certainly discuss the dated/incomplete information with Richard in due course (as partially achieved here), recent history has taught me my place is best one step removed from the situation, so as to have some perspective different to those battling from the inside.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.