The new version for cmsearch XXL and S for Windows32 and Windows64 has the following new feature:
- disabled heartbeat to avoid missing heartbeat errors
- writes not every time, that check pointing isn't working on Windows. Instead this is written only once.

yoyo

yoyo,
Is it possible to switch to 0.32 for a workunit that I am currently crunching that is using 0.31? The first time I got a heartbeat error it was @ about 1100 hours. I read up on the error and saw that NTP could be a cause on older versions of BOINC, so I disabled NTP on my Win7 x64 machine.
I have since gotten about 5 heart beat issues and have not gotten back above a couple hundred hours. The heartbeat resets coincide with kernel messages informing me that the system time has been updated.
If it's not possible to switch the cmsearch app on a workunit I am crunching is there any way to know that I would be using the 0.32 on a new XXL work unit that I started crunching?

That helped ... my ISP hung, the IPs could not be retrieved from the server names and this caused my core clients to be completely unresponsive. All other projects suffered from the heartbeat bug - but my 8 days old cmsearch task continued without any flaw :-)

Thanks !