| 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: 3
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This message is kind-of-a 2-parter.
----------------------------------------Finally noticed the note in the Messages tab that a new version was available. I've downloaded the windows version, and set one windows machine's BOINC to No New Tasks on the Projects tab, and they've run out... so I'm ready to upgrade that one machine. The printable installation page mentions only new installs, not upgrades. The link at the bottom of that page to windows install help on the berkeley.edu site (http://boinc.berkeley.edu/win_install.php ) returns a 404 error. If it were just a regular upgrade, I could let the WCG 6.10.58 installer put it right over the top of 6.2.28 without even having to stop the BOINC client/manager. Is that the correct upgrade method for most windows users? I looked through this forum back to the BOINC 6.10.58 thread, whose last message seemed to be posted prior to the release of the WCG-skinned version of 6.10.58, then up here to the top and don't find any specific thread addressing the proper upgrade methods. This *seems like* the appropriate forum for such issues. ================================== part 2 But... the particular machine I'm upgrading first keeps getting the error on about every task. It's not overclocked, 2 passes of the memtest86 boot CD did not find anything wrong with the 2x512MB sticks of RAM, 95+GB of hard drive free, there are no newer versions of graphics drivers for the ATI Radeon card in it (I don't run the BOINC screen saver, anyway... ), and nothing 'new' has been installed on the machine for months before it started throwing these errors. The HPF2 WU's typically run from 2 to 6+ hours before erroring out; HCMD2 WU's rarely ran for more than 0.2 hours; FAAH WU's were crunching along and finishing just fine (but there's no work for that task ATM). Most betas ran fine on it, though one errored out with exit code 195 (0xc3) and 'no state to restore.' I hadn't even noticed that beta error before now. Anyway... the FAQ/email-screengrab posted by Sekerob in a thread that discusses that specific error suggests upgrading the BOINC client. So, I *think* what I should do in this case is uninstall the 6.2.28 WCG version first rather than just installing over the top of it. Is that the correct route to go in this particular case? This machine is an older single core, but is still second or third from being replaced by an octo-core...
It's no screamer, but it's not my slowest (or even second slowest) computer at the moment, either. Thanks! edit1: I also found all (but only a few) DDDT2 WU's in Results completed without error on that machine. [Edit 1 times, last edit by Former Member at Oct 12, 2010 9:14:18 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
ZoSo,
----------------------------------------1. Before you run the actual update, take the machine off the internet, then denote the data_dir location in the old client message log (it's near/before the portion you've already posted). After, just run 6.10.58 installer which will take care to stop the 6.2.28 client. During the install process make sure that the data_dir location is shown as same and if not to change that. Only when the installation is complete and shows the old data_dir is being used you're ready to reconnect to the internet, whilst the client is running. 2. 1073741819 is nasty. Sometimes a simple boot gets rid of it. For sure visit the FAQ index which has a topic on this specific error.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
1) Yes, it's not installed as a service, so its data subdir is the typical %allusersprofile%\application data\boinc.
2) That machine does a scheduled reboot once a week, then logs in by itself when it comes back up (using Start->Run, control userpasswords2 [Enter] obsoletes the autologon from TweakUI, et cetera)... though I did reboot it a couple times extra, anyway. I think I'll apply the slew of XP updates that are waiting, first (today must have been "update tuesday")... then install the new version. |
||
|
|
|