I just released a new version of separation today that is compiled against older glibc versions. The actual version number is 2.11 for glibc. This is the oldest that Ubuntu currently has on an active LTS. Users who experience errors due to the fact that their glibc versions are older than this should send me a message and I will give them instructions on how to compile the program for their own machines using their version of glibc. Otherwise, I changed the plan class we are using for our GPU versions to enforce a minimum OpenCL version. This will keep CAL cards from getting GPU work units from the server and reduce error rates and thus validation issues.

Sorry for the wall of text but essentially we have an older glibc and a new method for sending out GPU work units.

If there are any issues with this release please post them here and I will try to get back to you quickly.

And the feeder is still not running. I've got eight or ten MilkyWay tasks ready to report, and can neither send them nor get new ones to crunch on. My second machine ("Luddite") is still happily working on stuff it downloaded a couple days ago (1.6 GHz single core Athlon XP 2000+), but my main system ("Kubuntu64") hasn't had anything to crunch on other than GPU tasks for Einstein since sometime last night.

Sorry about the delayed response. Thank you for all of the reports. Looks like we need to change a few things on the server to get the feeder back up and running. Will try to have it done by the end of the day today. If not then by the end of the day tomorrow. Until then I'm sorry about the inconvenience.

Jake, with all the problems going on with the modfits, someone should have alerted you to this and maybe you could update us as to what is going on. My GPU just spits 99% of these tasks back. I also unchecked modfit in the preferences but that does not seem to stop your servers from sending me modfit tasks. I don't understand this! I even reset the project and the first modfit died immediately and another ran about 8 minutes and then starts the exit 0 status loop. I aborted everything else. So why is your server sending me modfit tasks when I said not to? And why are they always dying on my system?

Hello Jake, all the modfit 1.34 files are not being processed. That figure is running around 30-50 files in a 24 hour period. Exact number is not known. All other files are fine, including those of Cosmology@home and SETI@home files. I'd like to help you more. -Mike
____________

In the last couple of days I have had 24 Modfit 1.34 tasks downloaded to my computer. So far one has yet to run, and the other 23 failed immediately (0.00 sec CPU time) with "Unknown error - exit code -1073741515".

I am using a Dell XP machine with a 2-core processor. I don't think MOdfit 1.34 likes my computer!

If I'm the only one having problems with the Sep Modfit 1.34 files then my comment might be superfluous, but I am deleting ~20 to ~30 files in a 24 hour period. I feel I must because if I allow them to run, they will crash at the end. That means hours of CPU time lost to other programs. Not so efficient. The other files process just fine with no problems. I don't see any other chatter on the topic so I can see if there is something I can do to remedy this issue.
Any suggestions?
-Mike

Soon is today sorry. We try to do releases at the beginning of the week so they're easier for us to support and easier for you guys to check for errors if they're on machines you may not be able to access on the weekends. Sorry for the delay.