Posts by DoctorNow
|
1)
Message boards : Number crunching : Cobblestones ( Message 4283 )Posted 3278 days ago by 
DoctorNow
I claim considerably less than benchmarks would demand. It's quorum=1, but no benches. Hm, then why do your results always getting what they are claiming? It's the same for me - claim = grant, so it must be benchmark-depending. ;-) And I note down my WUs in an Excel-worksheet. The average per hour for the last WUs was always the same. With fixed credits it would have varied. ;) |
|
2)
Message boards : Number crunching : Cobblestones ( Message 4281 )Posted 3278 days ago by
DoctorNow
We definitely need to give you all more credits!!! Yes, agreed. The current ones are benchmark-depending because of quorum 1, that's a nice and easy way for cheaters to use optimized clients. Think about some fixed credits maybe. My puter has this C/h rates for various projects (decending order): Obviously you haven't crunched Cosmo for a while, Saenger. They fell down to a level under SETI! ;) |
|
3)
Message boards : Number crunching : New CHARMM version and work-units ( Message 4251 )Posted 3284 days ago by
DoctorNow
12/08/2008 20:54:00|Docking@Home|[error] Checksum or signature error for logo.jpg Yes, getting the same here. Strange thing is: it caused all WU-downloads to fail and they won't start on crunching... Is the screensaver using the jpg so that they can't run without it? Edit: I just de- and re-attached again. This time it downloaded fine. If someone did something meanwhile, then thanx. ;-) |
|
4)
Message boards : Number crunching : Test WUs ( Message 3793 )Posted 3453 days ago by
DoctorNow
Hello! An hour ago I got a big bunch of the new WUs under openSuse 10.2 64-Bit. But as the very first one started some minutes ago it errored out, the complete rest did follow. That is the text from the result files: <core_client_version>5.10.39</core_client_version> <![CDATA[ <message> process exited with code 131 (0x83, -125) </message> <stderr_txt> Calling BOINC init. Starting charmm run (initial or from checkpoint)... SIGSEGV: segmentation violation Stack trace (3 frames): [0x83699a5] [0x83e0de0] [0xffffe500] Exiting... </stderr_txt> ]]> |
|
5)
Message boards : Cafe Docking : Massive censorship at Predictor !!! ( Message 2740 )Posted 3792 days ago by
DoctorNow
Predictor@home is censoring massively at their boards and is restricting the freedom of opinion of their registered users in an inappropriate manner. After a discussion had started about the attitude of the project administration towards a big cheating issue in this thread that thread was closed immediately to avoid any different opinion. After that any new discussion thread and any question concerning "censorship" were "answered" with the immediate deletion of the postings/threads. Even accounts were fully blocked for posting (in the case of my team member until the year 2038!!). I think it is not acceptable that the freedom of opinion is restricted in that way and I want to ask the BOINC community members to form an opinion about this. Try for yourself and start asking about this all at the P@H message boards! In between even account creation was disabled to prevent the "bad users" from posting further questions. After that didn't help meanwhile whole IP ranges are blocked from access to the complete Predictor homepage! There's an ongoing discussion over at the BOINCstats forum, where also the beginning of this whole mess is to be found. See: Trojan boinc installation by rogue member |
|
6)
Message boards : Number crunching : Who is overclocking their machine? ( Message 2174 )Posted 3857 days ago by
DoctorNow
My Host ID: 651 No overclocking here, it's an AMD Athlon XP 2200+ with Windows XP Pro SP2. Not crunched much unfortunately since I'm here... only finished 2 results some days ago. |
|
7)
Message boards : Number crunching : "Incorrect function (0x1)"? ( Message 1405 )Posted 3921 days ago by
DoctorNow
Hello! The same happens to me... I've joined yesterday and downloaded 2 wu's. Both errored out with those messages: <core_client_version>5.4.9</core_client_version> It was WU 13411 and 13412 ... Unfortunately one of them ran over 7 hours... I have an AMD Athlon XP 2200+ with Windows XP Pro on it... |