| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: It would be nice if the scheduler thought about efficiency... |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 18
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's no need to uninstall, install. Just run the 7.0.xx and it takes care of first uninstalling the previous version. Think this is loss-less, which was not the case with the early 7.0.xx clients. I just took a look at the existing running BOINC processes...they're all 32-bit but running on x64 Win7.Given that BOINC client downloads at Berkeley (latest being 7.0.44) now differentiate between 32-bit and 64-bit, I guess I'll find out just how smart the installer is...both in terms of whether it can cleanly uninstall the 32-bit client and whether it installs itself to "Program Files" rather than "Program Files (x86)"...that is, whether it installs based upon x64 requirements or makes decisions based upon existing registry information. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What the installer does is call the installer of the old version [the .msi file which overzealous cleaning software may have removed] and give it the "remove" parm, so I'd be surprised it would not do it proper if the old version's boinc.msi file is still there.
WCG previously only offered a 32 bit version. Don't know what they're going to do with v7 and the fact that there's now 5-6 sciences in 64 build and "pure" 64 bit systems. That said, a 32 bit client is as well capable to manage 64 bit science apps... after all, it's only a process coordinator. |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
I just took a look at the existing running BOINC processes...they're all 32-bit but running on x64 Win7. Switching from 32-bit to 64-bit was a problem if you ran the old v6.2.xx-client, since v6.2.xx always uninstalled by moving the data-directory to the BOINC-program-directory. For later clients like v6.10.xx on the other hand the data-directory isn't moved, so as long as you chooses the same data-directory during installation there shouldn't be any problems.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I just took a look at the existing running BOINC processes...they're all 32-bit but running on x64 Win7. Switching from 32-bit to 64-bit was a problem if you ran the old v6.2.xx-client, since v6.2.xx always uninstalled by moving the data-directory to the BOINC-program-directory. For later clients like v6.10.xx on the other hand the data-directory isn't moved, so as long as you chooses the same data-directory during installation there shouldn't be any problems. Being somewhat distrustful of things I didn't write (which is not to say that things that I have written haven't surprised me by doing what I wrote instead of what I meant), I'm backing the BOINC data directory up on the first system I upgrade anyway. A useful decision, anyway, as it revealed that BOINC/WCG only uses 19.6 GB of disk space for data/projects, which in turn suggests that my allocation of up to 100 GB of disk space is as pointless as my permitting BOINC to use 90% of 12 GB of memory is. The physical memory/disk usage demands of things BOINC just aren't that high. (Edit: I realize that said backup itself is not necessary as long as I backup the client configuration information in order to avoid the possibility of new BOINC client IDs being generated. But I got tired of newly generated client IDs resulting in phantom systems some time ago.) [Edit 1 times, last edit by Former Member at Feb 3, 2013 10:26:51 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hmmmm...installation of BOINC client 7.0.44 from Berkeley did not, in fact, trigger uninstallation of WCG's BOINC client 6.10.58 as downloaded from http://www.worldcommunitygrid.org/clients/wcg...0.58_windows_intelx86.exe
Gee...guess I'll uninstall both the WCG BOINC and the Berkley BOINC from the test system and then reinstall the Berkley BOINC so as to avoid all of the bad things that can happen with partial installs/uninstalls. And, on the rest of my systems, uninstall the WCG BOINC client prior to installing the Berkeley BOINC. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So to conclude what I ended up having to do was:
On each machine: 1) Suspend all attached projects via BOINC client 2) Uninstall BOINC 6.10.58 client downloaded from WCG/Harvard 2a) Not necessary per se, but as they are Windows boxes take the opportunity to run chkdsk on system and data drives (most systems run BOINC 24/7 so being proactive if I'm down anyway just makes sense) 2b) Again not necessary, but upgrade to latest graphics drivers to pull in latest OpenCL 3) Boot, check for issues that might affect future unplanned/unattended system restarts (e.g., power outages that exceed UPS capacity and/or those lovely Windows critical updates) in event logs 4) install BOINC 7.0.44 x64 client from Berkeley 5) adjust antivirus scanner exclusions to account for BOINC client shift from "Program Files (x86)" to "Program Files" directory (32-bit to 64-bit) 6) Boot again and look for startup issues 7) Resume all projects via BOINC client Although I aborted a hundred or so "Ready to start" CEP2 tasks on one box as their deadlines indicated it would be difficult to complete them, I decided to generally let BOINC try to clean up its act by itself and so still show 69 tasks across three systems in the "Waiting to run"/partially-completed state that indicates that they were bumped by "higher priority"/closer to deadline tasks under the 6.10.58 client. I'll give it a day or two to "settle" before I decide whether it is necessary start messing with cc_config.xml and app_config.xml (Totally extraneous: The newer screensaver is "cooler" and doesn't seem to interfere with monitor shutdown as configured in Windows' power settings.) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We're so terribly sorry you have to be put through all these troubles and commotions. (The download link you posted is broken!). Anyways, tell us in a few days how the crunching experience is, which given that you do have an extreme regard of Mr. Murphy, unavoidable will lead to some groan to be incurred ;>)
(Did remember that the exception to the auto-uninstall/install process has something to do with the custom kit that WCG is.) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We're so terribly sorry you have to be put through all these troubles and commotions. (The download link you posted is broken!). Anyways, tell us in a few days how the crunching experience is, which given that you do have an extreme regard of Mr. Murphy, unavoidable will lead to some groan to be incurred ;>) I just right-clicked the download link I embedded and selected "Open Link in New Window" under Chrome and it worked...but for clarity's sake, I just copied the download link from(Did remember that the exception to the auto-uninstall/install process has something to do with the custom kit that WCG is.) http://www.worldcommunitygrid.org/reg/ms/viewDownloadAgain.do And the removal/reinstallation process wasn't that much trouble...not when I compare it to, say, trying to install functional Highpoint SATA drivers that - hey - require a firmware upgrade, too...or install a Microsoft SQL Server service pack that can't find a MSI/MSP file supposedly cached by Windows Installer...or upgrading a Nvidia RAID driver that breaks RAID sets during install...or attempting to upgrade a Marvell network driver when the system has had Marvell's "custom" LAN aggregation package installed...or... I.e., the fact that I had stopped all things BOINC prior to attempting the upgrade-that-wasn't precluded the possibility that I might have ended up with multiple BOINC client processes hammering the exact same config files and project slots in a shared-by-accident data directory. The key take-away point is that WCG/BOINC contributors who have installed BOINC from the WCG download need to uninstall the WCG BOINC by hand prior to installing a later BOINC client from Berkeley...or they'll have problems since the Berkley BOINC and the WCG BOINC do not share a common "upgrade" code (in the Windows installer vernacular). |
||
|
|
|