Seti@Home optimized science apps and information
Optimized Seti@Home apps => Windows => Topic started by: Geek@Play on 18 Jun 2010, 10:01:43 am
-
Overnight this computer has downloaded 15 version 603 MB work units. All errored out with the same fault code of -177 (0xffffffffffffff4f). I have now removed version 603 MB from my app_info so that no more will be requested. I would be happy to add the 603 info back into the app_info again if anyone has any trouble shooting they want to do.
Of the 15 errored out work units, 10 failed at a run time of 0.00. 3 errored with a run time of exactly 1,533.89. 1 errored out at exactly 1,534.45 and 1 errored out at exactly 1,534.22 seconds.
This all concerns this computer (http://setiathome.berkeley.edu/show_host_detail.php?hostid=3378680) only.I am convinced that this is NOT a problem on my end. 3 errors at exactly the same time and 10 errors at exactly the same time? Not a hardware problem here. And again this computer was successfully crunching 603 work units before the server changes earlier this week.
Again if anyone at Berkeley is interested, I'm still here. I have copy's of the error's that report to Microsoft available if intersted.
More info here (http://setiathome.berkeley.edu/forum_thread.php?id=60396&nowrap=true#1005337) from yesterday.
For anyone here, I consider this to be a problem for Berkeley and post it here if anyone is interested.
-
I have a bunch of these errors last night - error out after 2+mins. After i removed the flops in the app_info, all wu resumed to normal crunching.
-
Why would those of us that are using optimized apps and the app_info file have more -177 problems than those users who are running stock?
-
Why would those of us that are using optimized apps and the app_info file have more -177 problems than those users who are running stock?
As seen in the BOINC server code respository at
http://boinc.berkeley.edu/trac/changeset/21806
and qioted on the main board this morning
http://setiathome.berkeley.edu/forum_thread.php?id=60427&nowrap=true#1008076
David wrote bad code (his words were "messed up") and hasn't worked out how to fix it yet.
-
OK......Guess I was asking for that.