...@ssl.berkeley.edu] On Behalf Of Filip
Rydlo
Sent: Thursday, May 26, 2016 10:32 AM
To: BOINC-dev email list <boinc_dev@ssl.berkeley.edu>
Subject: Re: [boinc_dev] problem with check pointing
Now that you mention checkpointing problem .
I remember that I have detected it too.
Migh
ch gets read/used FIRST by a program instead
> of the ProgramData data, apparently for compatibility reasons related to
> running in compatibility mode)... has caused problems for BOINC in the past.
>
>
>
>
>
>
>
> > Date: Thu, 26 May 2016 19:32:11 +0200
> > From: filip.ry..
in compatibility mode)... has caused problems for BOINC in the past.
> Date: Thu, 26 May 2016 19:32:11 +0200
> From: filip.ry...@gmail.com
> To: boinc_dev@ssl.berkeley.edu
> Subject: Re: [boinc_dev] problem with check pointing
>
> Now that you mention checkpointing problem
Now that you mention checkpointing problem .
I remember that I have detected it too.
Might have the same cause!
In my case on Win7 x64 prof.EN , on latest betaver. boinc .29+ :
Project: Asteroids@home
Symptom: every time I restarted my PC (I closed Boinc manually way before
the
I've noticed that sometimes when the client starts a fresh work unit, it will
read the check point file of a previous work unit. Not sure how/why this is
happening, but this is obviously not a good thing. One way I can fix this is to
use a checkpoint filename unique to the WU (up until now all
