At the very moment of writting this note, the only two projects working are Seti and CPDN, and when I say working I mean sending out units. The other are at a stand by position, solving and/or arrangeing things so that we might have more units to crunch in the future. Both projects are running fine with 4.14 CC on WXP - p4 - 2.66GHz
> After switching to version 4.14 this afternoon my CPDN project on a WinNT
> aborted !!
Legolas, did you use Task Manager to make sure the CPDN science tasks where actually killed when you suspended/quit BOINC 4.13? Apparently, sometimes one of them remains alive and that would corrupt your data.
I upgraded 4.13 to 4.14 on one machine, my CPDN is doing just fine. I'm about to upgrade the other machine.
I upgraded two of my machines so far w/no problems, including CPDN. Both of these systems are currently attached to all 6 projects. I stopped all BOINC processes before upgrading, but I *DID* install over the previous 4.13 without uninstalling.
-Gene
[edit] still running 4.65 WU's, got some 4.71's upcoming.
> > After switching to version 4.14 this afternoon my CPDN project on a
> WinNT
> > aborted !!
>
> Legolas, did you use Task Manager to make sure the CPDN science tasks where
> actually killed when you suspended/quit BOINC 4.13? Apparently, sometimes one
> of them remains alive and that would corrupt your data.
>
> I upgraded 4.13 to 4.14 on one machine, my CPDN is doing just fine. I'm about
> to upgrade the other machine.
>
> - Marco
>
>
>
Marco, thank you for your advice to kill all CPDN tasks before updating. Unfortunately it came too late for me (after 6 weeks crunching on this wu), but on CPDN I will not loose the already granted credits.
Hoping your advice will help others (and me in future upgrades) :-)
At the very moment of
)
At the very moment of writting this note, the only two projects working are Seti and CPDN, and when I say working I mean sending out units. The other are at a stand by position, solving and/or arrangeing things so that we might have more units to crunch in the future.
Both projects are running fine with 4.14 CC on WXP - p4 - 2.66GHz
Patience is a virtue
HM, I just upgraded my faster
)
HM, I just upgraded my faster machines to cc 4.14; until now, all seems to work fine. Crossing fingers ...
With 4.14, I could succesfull download some P@H-WUs, even a test-unit from E@H came through. Until now, all looks fine.
All my clients are crunching CPDN / E@H / P@H / some are crunching S@H
Supporting BOINC, a great concept !
> After switching to version
)
> After switching to version 4.14 this afternoon my CPDN project on a WinNT
> aborted !!
Legolas, did you use Task Manager to make sure the CPDN science tasks where actually killed when you suspended/quit BOINC 4.13? Apparently, sometimes one of them remains alive and that would corrupt your data.
I upgraded 4.13 to 4.14 on one machine, my CPDN is doing just fine. I'm about to upgrade the other machine.
- Marco
- Marco
Team Canada
I upgraded two of my machines
)
I upgraded two of my machines so far w/no problems, including CPDN. Both of these systems are currently attached to all 6 projects. I stopped all BOINC processes before upgrading, but I *DID* install over the previous 4.13 without uninstalling.
-Gene
[edit] still running 4.65 WU's, got some 4.71's upcoming.
> > After switching to
)
> > After switching to version 4.14 this afternoon my CPDN project on a
> WinNT
> > aborted !!
>
> Legolas, did you use Task Manager to make sure the CPDN science tasks where
> actually killed when you suspended/quit BOINC 4.13? Apparently, sometimes one
> of them remains alive and that would corrupt your data.
>
> I upgraded 4.13 to 4.14 on one machine, my CPDN is doing just fine. I'm about
> to upgrade the other machine.
>
> - Marco
>
>
>
Marco, thank you for your advice to kill all CPDN tasks before updating. Unfortunately it came too late for me (after 6 weeks crunching on this wu), but on CPDN I will not loose the already granted credits.
Hoping your advice will help others (and me in future upgrades) :-)
Legolas13