| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have just tried V 7.0.44 both 32/64bit and it freezes my machine after approx 1min runtime. On restart I am told that the system failed to load, I am running an 8 core AMD with 32GB memory and Windows 8 Pro.
Suggestions? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
----------------------------------------Well, it's a test client, where in first line operating problems are to be reported over at Berkeley, forum, but ideally the alpha mail list which developers actually read and the real user experts converse. Edit: Been running 7.0.44 for past 12 hours or so on an Octo-W7-64, no GPU crunching and so far nothing of note for me...zzzzz set-forget state. Later today, when CEP2 finishes, will also put it on Quad-W8-64 to see what this release brings. [Edit 1 times, last edit by Former Member at Jan 11, 2013 8:05:38 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
P.S. Of course, if your interest is not putting test clients through their paces, the only suggestion I have is to revert to your previous client version. 7.0.42 was quite stable to me. If you came from version 6.10, then there's no road back without loosing all work in progress, but given you're on W8, the likely client minimum version would have been 7.0.31 as a clean 6.10 install fails on W8.
----------------------------------------[Edit 1 times, last edit by Former Member at Jan 11, 2013 8:11:17 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just installed 7.0.44 64 bit on W8-64 Pro as a regular user, not under a MS account which bodes guaranteed trouble. Selected to not install in Protected Application Execution mode [so as to be able to GPU crunch] and also "Allow all users", so all accounts can run the BOINC Manager without connect failure. So far 1 task completed and validated, which previously was started under the 7.0.42 install.
|
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges:
|
I accidentallly updated from 7.0.42 to 7.0.44 on one of my Linux machines yesterday evening. Both CPU and GPU WUs have been running smoothly ever since (at least 12 hours).
----------------------------------------![]() |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
I have just tried V 7.0.44 both 32/64bit and it freezes my machine after approx 1min runtime. On restart I am told that the system failed to load, I am running an 8 core AMD with 32GB memory and Windows 8 Pro. Suggestions? Did you uninstall the old version first? That's the best way to update and none of your settings will be lost. Been using 7.0.44 since it was available. No problems so far.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
![]() ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Actually, the installer does that for you [on Windows], nanoprobe, you just don't see it. Some notice when the install fails because they've been overzealous in cleaning or been running overzealous purge software that's erasing the old installers and then getting the infamous "Path not found too... msi".
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I could use some advice/help here regarding installing BOINC_v7.0.44.
----------------------------------------The situation: I have BOINC_7.0.27 on my Ubu12.10-machine. I installed BOINC_7.0.42 to use the client-workload customization-features of an app_config. I didn't want BOINC_7.0.42 to displace my default BOINC_7.0.27 so I installed BOINC_7.0.42 in an isolated and self-contained folder. BOINC_7.0.42 has been working just about fine crunching SN2S_6.20-CPU-WUs and HCC_7.08-GPU-WUs. There were issues I ran into using BOINC_7.0.42, but nothing that I wasn't able to recover from. Now I want to try out BOINC_7.0.44. My query -- How do I install BOINC_7.0.44 so that: 1] As much of the settings I had under BOINC_7.0.42 is preserved including the WCG WUs*. 2] I retain the flexibility to possibly move back to BOINC_7.0.42 for whatever reason. 3] My default BOINC_7.0.27 is preserved regradless of anything and everything. Notes: *That is, for the WUs to go through the transition from being managed by BOINC_v7.0.42 to one managed by BOINC_7.0.44. Thanks in advance. ; ; andzgridPost#803 ; [Edit 1 times, last edit by Former Member at Jan 11, 2013 11:39:59 PM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
Actually, the installer does that for you [on Windows], nanoprobe, you just don't see it. I never see it because I always uninstall first. ![]()
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
![]() ![]() |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
My query -- How do I install BOINC_7.0.44 so that: 1] As much of the settings I had under BOINC_7.0.42 is preserved including the WCG WUs. 2] I retain the flexibility to possibly move back to BOINC_7.0.42 for whatever reason. I don't run Linux, so possibly you'll need to do something special here, but atleast under windows: #1: Just install v7.0.44 to same directories. #2: Uninstall v7.0.44 for so installing v7.0.42 again. As long as where's not some major changes to BOINC-client, like between v6 and v7, it's normally possible to downgrade to an earlier client with no problems, but it's important to uninstall before downgrading. Since v7.0.42 also supports app_config.xml, it shouldn't be any problems switching back-and-forth between 7.0.42 - 7.0.44 multiple times if you so desires. Downgrading to 7.0.41 or earlier clients on the other hand will give problems since these clients doesn't work correctly with app_config.xml. If you're not using app_config.xml, where shouldn't be any problems (appart for possible client-bugs in earlier clients) to downgrade to 7.0.27 or something. ![]() "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
|