Just upgraded from 4.16 to 4.17 on Intel 3.0 HT machine w/WinXPPRO. My upgrades went from 4.13 to 4.15 to 4.16 to 4.17 at present. I have had no problems except for the bug related to the 4.71 executable in terms of CPU Time but as soon as a 4.72 WU was crunched by 4.16 all was well. I followed this sequence to do the upgrade.
1. used File->Exit to stop the program.
2. downloaded the 4.17 boinc cc.
3. installed right over the 4.16 boinc cc.
4. ran the 4.17 boinc cc.
I observed that when I stopped the client that 1 seti and 1 einstein WU were running and when I restarted, after the speed test, it resumed operation like nothing has happened. At the moment, all is well.
I have 5 projects attached, SETI, Predictor, LHC, Einstein and climate. Each time I upgraded, the same procedure was used. And each time the upgrade went without a hitch. I did not detach and I did not uninstall.
Just upgraded from Boinc v4.15 to Boinc v4.17 and I've got problem. When Boinc client was restarted, it dropped all work and restarted all projects. So I'm now restroing backup of Boinc v4.15. Please help me with upgrade.
P.S. In error log, there was somenthing like this after upgrade:
> 2005-01-24 22:28:06 [---] H1_0205.4__0205.8_0.1_T09_Test02: error in command_line element
> 2005-01-24 22:28:06 [---] Can't parse workunit in state file
> I am planning to to send out another ten thousand account keys for
> Einstein@Home in the next day or so. I am not yet sure whether or not we
> should ask new users to use 4.16 or 4.17. So this thread is very useful to
> me: please post a short note saying if 4.17 did work for you or if it did
> not.
3 PC's upgraded without issues from 4.13 > 4.15 > 4.16 > 4.17
Two are P4's running Win98SE:
- one runs Einstein and SETI 50/50,
- the other runs CPDN/SETI/Einstein/ProPredictor equally
Third PC is a Dual P3/Xeon running NT4 workstation (an older but goody)
- this runs Einstein and SETI 50/50.
No WU's lost, no install hassles, everything really sweet.
> I am planning to to send out another ten thousand account keys for
> Einstein@Home in the next day or so. I am not yet sure whether or not we
> should ask new users to use 4.16 or 4.17. So this thread is very useful to
> me: please post a short note saying if 4.17 did work for you or if it did
> not.
>
> I am particularly interested in hearing from Linux and Mac OSX users.
>
The upgrade from 4.15 to 4.16 resulted in projects being reset and WUs lost. Upgrade from 4.16 to 4.17 no problems (so far).
just update my Athlon64
)
just update my Athlon64 3.200+ WinXP SP1, without any problems.
Greetings from Germany NRW
Ulli
Just upgraded from 4.16 to
)
Just upgraded from 4.16 to 4.17 on Intel 3.0 HT machine w/WinXPPRO. My upgrades went from 4.13 to 4.15 to 4.16 to 4.17 at present. I have had no problems except for the bug related to the 4.71 executable in terms of CPU Time but as soon as a 4.72 WU was crunched by 4.16 all was well. I followed this sequence to do the upgrade.
1. used File->Exit to stop the program.
2. downloaded the 4.17 boinc cc.
3. installed right over the 4.16 boinc cc.
4. ran the 4.17 boinc cc.
I observed that when I stopped the client that 1 seti and 1 einstein WU were running and when I restarted, after the speed test, it resumed operation like nothing has happened. At the moment, all is well.
I have 5 projects attached, SETI, Predictor, LHC, Einstein and climate. Each time I upgraded, the same procedure was used. And each time the upgrade went without a hitch. I did not detach and I did not uninstall.
Upgraded to v4.17 from v4.16;
)
Upgraded to v4.17 from v4.16; WinXP SP2. No problems!
- Marco
Team Canada
Just upgraded from Boinc
)
Just upgraded from Boinc v4.15 to Boinc v4.17 and I've got problem. When Boinc client was restarted, it dropped all work and restarted all projects. So I'm now restroing backup of Boinc v4.15. Please help me with upgrade.
P.S. In error log, there was somenthing like this after upgrade:
> 2005-01-24 22:28:06 [---] H1_0205.4__0205.8_0.1_T09_Test02: error in command_line element
> 2005-01-24 22:28:06 [---] Can't parse workunit in state file
> I am planning to to send
)
> I am planning to to send out another ten thousand account keys for
> Einstein@Home in the next day or so. I am not yet sure whether or not we
> should ask new users to use 4.16 or 4.17. So this thread is very useful to
> me: please post a short note saying if 4.17 did work for you or if it did
> not.
3 PC's upgraded without issues from 4.13 > 4.15 > 4.16 > 4.17
Two are P4's running Win98SE:
- one runs Einstein and SETI 50/50,
- the other runs CPDN/SETI/Einstein/ProPredictor equally
Third PC is a Dual P3/Xeon running NT4 workstation (an older but goody)
- this runs Einstein and SETI 50/50.
No WU's lost, no install hassles, everything really sweet.
Thanx for a good job !
Timbo
regards,
Tim
UK BOINC Team Founder
Join the UK BOINC Team: http://www.ukboincteam.org.uk/newforum
Just upgraded to the 4.17,
)
Just upgraded to the 4.17, everything went smooth so far. Let see if wu's finishes ok :)
Laryea
> I am planning to to send
)
> I am planning to to send out another ten thousand account keys for
> Einstein@Home in the next day or so. I am not yet sure whether or not we
> should ask new users to use 4.16 or 4.17. So this thread is very useful to
> me: please post a short note saying if 4.17 did work for you or if it did
> not.
>
> I am particularly interested in hearing from Linux and Mac OSX users.
>
The upgrade from 4.15 to 4.16 resulted in projects being reset and WUs lost. Upgrade from 4.16 to 4.17 no problems (so far).
XP Pro SP2/AMD XP 1700+
Seti Classic Final Total: 11446 WU.
No problems during install.
)
No problems during install. 4.13 > 4.15 > 4.16 > 4.17 Host running S@H, PP & Einstein. No errors. No completed WUs yet. No downloads or uploads yet.
Host 5392
Pentium II 600
Win 98 SE
128 MB
Coming soon... BOINC 4.18
)
Coming soon... BOINC 4.18 ;-)
Bug correction to the proxy setings.
Code to prevent/correct BOINC from spamming the Project Servers.
Professor Desty Nova
Researching Karma the Hard Way
> Coming soon... BOINC 4.18
)
> Coming soon... BOINC 4.18 ;-)
>
> Bug correction to the proxy setings.
> Code to prevent/correct BOINC from spamming the Project Servers.
>
this goes fast at these Days, every Day a new Version...
Greetings from Germany NRW
Ulli