no points

[sc00p]

http://forum.folding-community.org/p...topic_id=20562

[embeejay]

Vijay Pande also says:

"Sorry for this problem. We've been making some mods for v6. Looks like the fixes broke some new things. We reverted our changes and all should be back to what it was again.

I want to stress that these changes are in how the stats are outputted -- the db itself is unchanged (and therefore safe). It's late, so I want to be conservative with our fixes. If this fix doesn't do it, I'd be surprised, but rest assured that the db (with the official numbers) is safe and we just need to fix the output scripts."

in the following thread: http://forum.folding-community.org/ftopic20505.html

so i guess we aren't really wasting cpu time atm - it's only the stats output thats screwed up

[angra]

I remain skeptical that my problem is on Stanford's end - stanford might be giving our team as a whole problems, but my errors sure do look like client errors...before any attempt is made to contact the mothership.

[12:45:41] Finished Work Unit:
[12:45:43] - Reading up to 6048840 from "work/wudata_03.arc": Read 6048840
[12:45:44] - Reading up to 20822132 from "work/wudata_03.xtc": Read 20822132
[12:45:44] goefile size: 0
[12:45:44] logfile size: 355728
[12:45:44] Leaving Run
[12:45:53] - Writing 27329432 bytes of core data to disk...
[12:47:11]   ... Done.
[12:49:05] 
[12:49:05] Folding@home Core ShuCoreStatus = 12 (18)
[12:49:09] Client-core communications error: ERROR 0x12
[12:49:09] Deleting current work unit & continuing...
[13:11:07] - Preparing to get new work unit...
[13:11:07] + Attempting to get work packet

[Sparky]

Hmm yeah I see what you mean angra. Unfortunately I haven't used the SMP client near enough to know how to help

[embeejay]

i have had problems with client/core comm probs, iirc they were O/C related - are you cpu's running hot/unstable?

oetherwise i'd try to completely delete the client and all work units then reinstall and see if it helps...