... I'll go chastise myself in a quiet corner now. :)
Careful now! You might incite fadedrose to add some extra epithets to the previously quite impressive list :-).
I'm really quite grateful for your encyclopaedic knowledge of BOINC versions because having you around absolves me of any responsibility in that direction. So let me show my complete ignorance by asking a (probably) dumb question. I remember (I think) that 7.0.65 was a 'recommended' version and after that I don't remember much until the 'struggle' to get out a 'recommended' 7.2.X. A comment recently from Richard somewhere suggested that 7.2.39 may not be the end of this 'struggle'.
However I digress. The questions are these. I thought development on the 7.0.X line stopped at 7.0.65, or thereabouts. Is there any correlation between the numbers you are now quoting (7.0.78) and the current 7.2.X line? In other words, are new features in 7.2.X being back ported to 7.0.X? Apart from cosmetic differences due to skinning, are there other subtle differences that might cause confusion when trying to give instructions about things like 'copying and pasting from the event log' for example? Are there features in 7.0.78 that are not in 7.2.39, and vice versa?
I too have long ago lost track of Boinc versioning, indeed I wondered why there has not been a suppression of emission of such fine-grained variants. FWIW I ( only an amateur dilettante of a 'developer' ) thought that 'nightly builds' were of restricted interest only to a small group of devotees. Thus : is there an overarching intent/actuality to 'milestone' BOINC development ? A dangerous question perhaps ....
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
However I digress. The questions are these. I thought development on the 7.0.X line stopped at 7.0.65, or thereabouts.
It did for main BOINC.
But the versions that run under other names don't necessarily need the updates that main BOINC has needs for. Or don't need it at this time. Or are at the end of their development cycle and only get small hotfixes.
New features, such as OpenCL for CPU and built in VirtualBox support aren't necessarily needed for these third party projects. But changes like that attribute to upping the minor number in the BOINC numbering scheme of Major.minor.revision, where Major means that changes in this version are of major consequence, the BOINC before this one did things totally different.
An example of this is how BOINC 6 had a Messages tab, and BOINC 7 had an Event Log; BOINC 6 had general GPU support, BOINC 7 added OpenCL support; BOINC 6 did its scheduling based on debt, BOINC 7 changed this to a different formula.
The Minor versions show whether it's a development version of BOINC, when this number is odd, thus 1, 3, 5, 7 etc. These versions are hot material, they can potentially break stuff on your computer, or require you to constantly reboot, or that you have to put back a previous save point. Volatile. Not to be used by the general public.
When it's an even number (0, 2, 4, 6 etc.) it's either a safe-to-try beta, or the recommended version. Both of which can still contain bugs. But these are usually bugs people can live with, or which aren't of such importance that they need to be squashed right this minute.
The revision number is just that, it shows that it's a newer version than the last.
Now then, does all that mean that nothing from the present 7.2 range made it into older 7.0 versions for GR/CE/WCG/PtP/Sony?
Well, the Sony version is at end of life, as I have understood. It won't get any further updates, although users are allowed to update to a Berkeley or WCG BOINC as they see fit. GR/CE/WCG/PtP all get updates, but none of them require any of the latest additions to BOINC, such as OpenCL for CPUs or the VirtualBox addition, so these aren't added to their versions.
I did see for instance that the latest change to the source code, the making of BOINC user accounts only when BOINC is installed as a service, has already been released through CE 7.0.79. This is a change that isn't in any present Berkeley BOINC yet. It'll probably be in 7.3.7 or .8. BOINC 7.3 is the present alpha range, although its numbering may be strange, since the majority of these version numbers have been released as recommended on Android. I will have to ask Rom about what's going on there.
As for 7.2.39, it contains a big bug that requires a hotfix, but the testing for the HTC release got in the way. I expect 7.2.40 to be recommended any day now, or maybe that they just re-release 7.2.39 with a fixed BOINC Manager included. Silently. Wouldn't be the first time they did that.
Thank you, very interesting stuff. All of my CPU only machines are still on V6. I think pretty much all with nvidia GPUs are on 6.12.34. There may be a couple on 7.1.3 which I chose when I wanted to play with app_config.xml. Most with an AMD GPU are on 7.1.3 or 7.2.33. I was about to bite the bullet and upgrade most of the fleet when 7.2.33 was the recommended version but I never did find the time. Then 7.2.39 came along and I almost got started with that. Sometimes procrastination pays off :-).
I think I'll wait for a recommended version that lasts for say two months without change before I entertain these thoughts again :-).
As for 7.2.39, it contains a big bug that requires a hotfix, but the testing for the HTC release got in the way. I expect 7.2.40 to be recommended any day now, or maybe that they just re-release 7.2.39 with a fixed BOINC Manager included. Silently. Wouldn't be the first time they did that.
Can they do the 'silent' update without me having to reinstall on each of my machines? Or will I have to reinstall to get the 'fix'?
It'll be a full update. 7.2.42 can be tested for Windows. A version for Linux, FreeBSd and Mac is to follow, but the problem here is that the developers have already updated their machines to wxWidgets 3.0, while BOINC 7.2 works still with 2.8; so Rom is busy building several virtual machines with which he can build new versions of BOINC 7.2
Edit: although you can also just update BOINC Manager with an older hotfix. Steps on how to do that, are here.
It'll be a full update. 7.2.42 can be tested for Windows. A version for Linux, FreeBSd and Mac is to follow, but the problem here is that the developers have already updated their machines to wxWidgets 3.0, while BOINC 7.2 works still with 2.8; so Rom is busy building several virtual machines with which he can build new versions of BOINC 7.2
Edit: although you can also just update BOINC Manager with an older hotfix. Steps on how to do that, are here.
dil·et·tante
1.
a person who takes up an art, activity, or subject merely for amusement, especially in a desultory or superficial way; dabbler.
2.
a lover of an art or science, especially of a fine art.
adjective
Mike, there's a helluva difference between Definition No. 1 and being a Moderator. Does the boss know you're just here to have fun?
I had to look up the word and thank you for it. All too often there are dilettantes doing dabbling in areas where skill is not commensurate with funnybone issues. I hope that made sense. Editing doesn't help that sentence.
Finally. I know what I am. A dilettante. Not as good as a debutante but nobody I know would know the difference.
Am a bit shy about causing all the trouble and head-scratching with this:
Quote:
Message 129415 - Posted 24 Feb 2014 21:27:48 UTC - in response to Message 129413.
I put Boinc in Search Help and it came up with 52 files. None is named "event" file
Then, I wish I could remember this:
Quote:
What you're looking for is the Event Log, available from either simple view or advanced view, by pressing CTRL+SHIFT+E simultaneously (as has already been said by Holmis).
____________
Jord
But I already forgot what that procedure was supposed to do. When I open my "messages" file in GridRepublic, I used that keyboard trick, and nothing happened. What was supposed to happen?
All the talk about versions, has there been a decision made on which Boinc version is the one to use to look at the event file? The numbers are so similar, all 7 something or other. Maybe they should name them like they do with hurricanes and storms.. easier to remember.
Rather than using the keyboard CTRL-SHIFT-E, why can't they just put a tab there to touch when information is needed? What is supposed to happen when I use that
procedure because nothing happens when I do it. Should a window open or what?
I honestly can't remember why I wanted to look at the event file.
RE: ... I'll go chastise
)
Careful now! You might incite fadedrose to add some extra epithets to the previously quite impressive list :-).
I'm really quite grateful for your encyclopaedic knowledge of BOINC versions because having you around absolves me of any responsibility in that direction. So let me show my complete ignorance by asking a (probably) dumb question. I remember (I think) that 7.0.65 was a 'recommended' version and after that I don't remember much until the 'struggle' to get out a 'recommended' 7.2.X. A comment recently from Richard somewhere suggested that 7.2.39 may not be the end of this 'struggle'.
However I digress. The questions are these. I thought development on the 7.0.X line stopped at 7.0.65, or thereabouts. Is there any correlation between the numbers you are now quoting (7.0.78) and the current 7.2.X line? In other words, are new features in 7.2.X being back ported to 7.0.X? Apart from cosmetic differences due to skinning, are there other subtle differences that might cause confusion when trying to give instructions about things like 'copying and pasting from the event log' for example? Are there features in 7.0.78 that are not in 7.2.39, and vice versa?
Cheers,
Gary.
Serious face .. :-) I too
)
Serious face .. :-)
I too have long ago lost track of Boinc versioning, indeed I wondered why there has not been a suppression of emission of such fine-grained variants. FWIW I ( only an amateur dilettante of a 'developer' ) thought that 'nightly builds' were of restricted interest only to a small group of devotees. Thus : is there an overarching intent/actuality to 'milestone' BOINC development ? A dangerous question perhaps ....
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: However I digress. The
)
It did for main BOINC.
But the versions that run under other names don't necessarily need the updates that main BOINC has needs for. Or don't need it at this time. Or are at the end of their development cycle and only get small hotfixes.
New features, such as OpenCL for CPU and built in VirtualBox support aren't necessarily needed for these third party projects. But changes like that attribute to upping the minor number in the BOINC numbering scheme of Major.minor.revision, where Major means that changes in this version are of major consequence, the BOINC before this one did things totally different.
An example of this is how BOINC 6 had a Messages tab, and BOINC 7 had an Event Log; BOINC 6 had general GPU support, BOINC 7 added OpenCL support; BOINC 6 did its scheduling based on debt, BOINC 7 changed this to a different formula.
The Minor versions show whether it's a development version of BOINC, when this number is odd, thus 1, 3, 5, 7 etc. These versions are hot material, they can potentially break stuff on your computer, or require you to constantly reboot, or that you have to put back a previous save point. Volatile. Not to be used by the general public.
When it's an even number (0, 2, 4, 6 etc.) it's either a safe-to-try beta, or the recommended version. Both of which can still contain bugs. But these are usually bugs people can live with, or which aren't of such importance that they need to be squashed right this minute.
The revision number is just that, it shows that it's a newer version than the last.
Now then, does all that mean that nothing from the present 7.2 range made it into older 7.0 versions for GR/CE/WCG/PtP/Sony?
Well, the Sony version is at end of life, as I have understood. It won't get any further updates, although users are allowed to update to a Berkeley or WCG BOINC as they see fit. GR/CE/WCG/PtP all get updates, but none of them require any of the latest additions to BOINC, such as OpenCL for CPUs or the VirtualBox addition, so these aren't added to their versions.
I did see for instance that the latest change to the source code, the making of BOINC user accounts only when BOINC is installed as a service, has already been released through CE 7.0.79. This is a change that isn't in any present Berkeley BOINC yet. It'll probably be in 7.3.7 or .8. BOINC 7.3 is the present alpha range, although its numbering may be strange, since the majority of these version numbers have been released as recommended on Android. I will have to ask Rom about what's going on there.
As for 7.2.39, it contains a big bug that requires a hotfix, but the testing for the HTC release got in the way. I expect 7.2.40 to be recommended any day now, or maybe that they just re-release 7.2.39 with a fixed BOINC Manager included. Silently. Wouldn't be the first time they did that.
Thank you, very interesting
)
Thank you, very interesting stuff. All of my CPU only machines are still on V6. I think pretty much all with nvidia GPUs are on 6.12.34. There may be a couple on 7.1.3 which I chose when I wanted to play with app_config.xml. Most with an AMD GPU are on 7.1.3 or 7.2.33. I was about to bite the bullet and upgrade most of the fleet when 7.2.33 was the recommended version but I never did find the time. Then 7.2.39 came along and I almost got started with that. Sometimes procrastination pays off :-).
I think I'll wait for a recommended version that lasts for say two months without change before I entertain these thoughts again :-).
Cheers,
Gary.
RE: As for 7.2.39, it
)
Can they do the 'silent' update without me having to reinstall on each of my machines? Or will I have to reinstall to get the 'fix'?
It'll be a full update.
)
It'll be a full update. 7.2.42 can be tested for Windows. A version for Linux, FreeBSd and Mac is to follow, but the problem here is that the developers have already updated their machines to wxWidgets 3.0, while BOINC 7.2 works still with 2.8; so Rom is busy building several virtual machines with which he can build new versions of BOINC 7.2
Edit: although you can also just update BOINC Manager with an older hotfix. Steps on how to do that, are here.
RE: It'll be a full update.
)
Thankyou
RE: dil·et·tante 1. a
)
Mike, there's a helluva difference between Definition No. 1 and being a Moderator. Does the boss know you're just here to have fun?
I had to look up the word and thank you for it. All too often there are dilettantes doing dabbling in areas where skill is not commensurate with funnybone issues. I hope that made sense. Editing doesn't help that sentence.
Finally. I know what I am. A dilettante. Not as good as a debutante but nobody I know would know the difference.
Am a bit shy about causing
)
Am a bit shy about causing all the trouble and head-scratching with this:
Then, I wish I could remember this:
But I already forgot what that procedure was supposed to do. When I open my "messages" file in GridRepublic, I used that keyboard trick, and nothing happened. What was supposed to happen?
All the talk about versions,
)
All the talk about versions, has there been a decision made on which Boinc version is the one to use to look at the event file? The numbers are so similar, all 7 something or other. Maybe they should name them like they do with hurricanes and storms.. easier to remember.
Rather than using the keyboard CTRL-SHIFT-E, why can't they just put a tab there to touch when information is needed? What is supposed to happen when I use that
procedure because nothing happens when I do it. Should a window open or what?
I honestly can't remember why I wanted to look at the event file.
Thanks.