| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: New Version of World Community Grid Software Now Available for Windows and Mac |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 34
|
|
| Author |
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges: 
|
Except for the skin when in simple view, zero zippo difference in the user front end and as knreed explained, really underneath it neither, a 7.16.5 code level integration included. ah. Got it. So I can ignore any mention of the WCG software - thanks Lava.  |
||
|
|
Chris Raisin
Cruncher Joined: Feb 21, 2018 Post Count: 2 Status: Offline Project Badges: 
|
I have found a major difference between the two "versions" of the BOINC Manager frontends (comparing latest BOINC and WCG versions).
When installing WCG on a machine (and saving working data to the same data folders as used by other BOINC or WCG installations on your network), there is an installation error if any other BOINC or WCG program is currently running. The error is due to the fact that BOINC/WCG Manager frontends lock certain files in those folders when they are using/storing data. When the WCG installation encounters a locked file while installing, the installations reports an error and then rolls back the installation. I am not sure whether shutting down all other instances of BOINC/WCG on other computers before installing WCG on a new machine rectifies this situation, or whether running WCG on multiple machines can only work if each installation uses a different data store for its operations, but the BOINC version has no problems with multiple instances running on the same network using the same data stores, and installation while other machines have BIONC currently running experiences no "lock" problems. (It must overlook this situation and continues on with it's installation). Since the BOINC version is so stable and changes to the program seem to be thoroughly tested and found to be stable before release, I will stay with the BOINC version and give the WCG version a miss. |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If I'm understanding the description correctly, this seems very problematic to me. I guess the terms "data folders" probably needs a little clarification. If the lowest level directory used for the boinc data directory is unique to each machine that would probably work as each BOINC instance would essentially have it's own unique data directory. However, if the data_dir variable passed to BOINC is identical for each instance, that seems like a potential problem. One thing that comes to mind is the slots directory. I would think there should only be one BOINC instance using slot x at a time. If all instances were using the same data directory, multiple instances would be using the same slot x directory. Additionally, there are files in the directory above the project directory that should be unique to each instance like the client_state.xml, sched_request.<project_url>.xml, and others. These files contain the host id and if multiple instances are using it how does the client keep the host ids from corrupting each other. I have to be missing something here...
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
New version does not install correctly on x86 Windows 10. Systems can not find "World Community Grid. msi" in the standard donwload folder. I did not cahnge any parameters. Thx ERV
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
I have found a major difference between the two "versions" of the BOINC Manager frontends (comparing latest BOINC and WCG versions). When installing WCG on a machine (and saving working data to the same data folders as used by other BOINC or WCG installations on your network), there is an installation error if any other BOINC or WCG program is currently running. The error is due to the fact that BOINC/WCG Manager frontends lock certain files in those folders when they are using/storing data. When the WCG installation encounters a locked file while installing, the installations reports an error and then rolls back the installation. I am not sure whether shutting down all other instances of BOINC/WCG on other computers before installing WCG on a new machine rectifies this situation, or whether running WCG on multiple machines can only work if each installation uses a different data store for its operations, but the BOINC version has no problems with multiple instances running on the same network using the same data stores, and installation while other machines have BIONC currently running experiences no "lock" problems. (It must overlook this situation and continues on with it's installation). The WCG installer is built using a slightly modified BOINC installer. The type of behavior you see here should be the same from both installers. What version of the BOINC client are/were you running and what installation options had you used? Since the BOINC version is so stable and changes to the program seem to be thoroughly tested and found to be stable before release, I will stay with the BOINC version and give the WCG version a miss. We are in no way recommending the WCG version over the BOINC version. Nor are we recommending the BOINC version over the WCG version. However, we do encourage you to use one of the versions that is greater than 7.14.2 (i.e. our 7.14.3 windows version or the the BOINC 7.16 windows version) as that contains the security fix. |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges: 
|
New version does not install correctly on x86 Windows 10. Systems can not find "World Community Grid. msi" in the standard donwload folder. I did not cahnge any parameters. Thx ERV @ FC091359: The error you are experiencing is a Microsoft install shield error. Please download and install/run this: https://support.microsoft.com/en-us/help/1758...eing-installed-or-removed Then un install your current version of BOINC (if you have not already done this) and re install: https://www.worldcommunitygrid.org/reg/ms/viewDownloadAgain.do ErikaT |
||
|
|
mosia1962@yahoo.co.uk
Cruncher Joined: Apr 5, 2012 Post Count: 1 Status: Offline Project Badges: 
|
Thank you ErickaT
Floundered around trying to get the new version running. Gave up and then realized old version was gone. Ploughed through topic - confusing until I reached ErikaT's post - no flim flam - straightforward - followed the instructions and new version installed. Thank you thank you Erikat |
||
|
|
Vikram Dinesh
Cruncher India Joined: Nov 16, 2004 Post Count: 4 Status: Offline Project Badges: 
|
Why is there only a 32 bit client? Where is the 64 bit version? I am already running 7.16.5 and plan to stick to it even though I only contribute to WCG.
---------------------------------------- [Edit 1 times, last edit by Vikram Dinesh at Apr 16, 2020 4:39:39 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You don't need a 64 bit but if you do because your OS is set to only run 64 bit apps, you can get the 64 bit at Berkeley which you already have.
FYI, the 32 bit WCG build is as good at managing 64 bit science apps which is really what BOINC with it's Manager does... it's just a traffic manager. It's convenient to WCG, a 1 size fits all, particularly for the corporate contributors and their security angst. |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 865 Status: Offline Project Badges: 
|
Why is there only a 32 bit client? Where is the 64 bit version? I am already running 7.16.5 and plan to stick to it even though I only contribute to WCG. Me too, Vikram. Although I guess I'm playing with some Rosetta@home work units, but WCG has been my one and only BOINC project for decades. Personal opinion is I'm not a big fan of the fragmentation in the releases. There's already such slow progress in BOINC client, manager, and server development work since it's currently all volunteer-based that I'd prefer if one codebase is used with no skinning (or other customizations) and no divergence in releases. It helps pool very scarce development, testing, and security auditing resources into a single branch of code. Or heck, maybe a future version of BOINC (8.x?) will allow for individual BOINC projects to bolt on their own skins, their own cc_config.xml files, their own projects pre-attached, and an easier ability for enterprise bulk installs, management, and configuration. I realize that many of the WCG security audit findings from IBM Security get merged back into BOINC upstream, but I'd still prefer exactly one binary from exactly one master branch of code.
[Edit 1 times, last edit by hchc at Apr 16, 2020 8:37:57 AM] |
||
|
|
|