I don't know which version the system has on it right now, but I am not getting work even when it is available. All I get when BOINC tries to get tasks is the following message -
"Wed Nov 5 09:04:19 2008|ralph@home|Sending scheduler request: Requested by user. Requesting 214616 seconds of work, reporting 0 completed tasks
Wed Nov 5 09:04:24 2008|ralph@home|Scheduler request succeeded: got 0 new tasks
Wed Nov 5 09:04:24 2008|ralph@home|Message from server: platform 'x86_64-apple-darwin' not found

BOINC 5.4.9, Ralph 5.16
GenuineIntel Intel(R) Pentium(R) M processor 1.86GHz
Microsoft Windows XP Professional Edition, Service Pack 2, (05.01.2600.00)
Memory 2039.37 MB
cash 76.56 KB
swap space 932.3 MB
65.54 GB

resultid=125665 -
ERROR:: Unable to obtain sequence information. fasta file must be provided.
ERROR:: Exit at: .initialize.cc line:236
resultid=125589 -
ERROR:: Unable to obtain sequence information. fasta file must be provided.
ERROR:: Exit at: .initialize.cc line:236
resultid=125413 -
ERROR:: Unable to obtain sequence information. fasta file must be provided.
ERROR:: Exit at: .initialize.cc line:236

The machine is also running Rosetta

Regards
Phil

Found these two running tonight when I got home. These are each roughly double my normal Mem usage showing 300+MB each on a dual CPU. One later dropped to 250MB which is still quite high.

MAPRELAX_TEST_hom004_1fna
MAPRELAX_TEST_hom005_1fna
http://www.geocities.com/feet1st/Ralph515.html

Thread on Rosetta indicates problems with 5.07 WUs ending due to disk space

Aborting result
JUMP_CLOSE_CHAINBREAK_ALLBARCODE_1q7sA_SAVE_ALL_OUT_472_6802_0: exceeded disk limit: 101466227.000000 > 100000000.000000

Aborting result JUMPTEST_CLOSECHAINBREAKS_1tul__469_2429_0: exceeded disk limit: 100308693.000000 > 100000000.000000

Yet both machines have plenty of disk space available. Is there some built-in limit of 100MB for a WU?? And how would a WU exceed that?

I'm thinking perhaps there are cases where the more frequent checkpointing can require more storage than expected perhaps?

I believe that the credits should be granted in this case !
*No error in my part.

RALPH@home is the official alpha test project for Rosetta@home. New application versions, work units, and updates in general will be tested here before being used for production. The goal for RALPH@home is to improve Rosetta@home.

Please consider the following before deciding to join:

Since this project is a testing environment, applications and work units may be unstable at times.
Credits and other competitive statistics do not mean anything in this test project. Credits may be lost due to instabilities and may be reset at any time for testing.
There will not be a continual flow of work units. Work units will be issued only when necessary for testing.
We urge participants to not abort work units to help with testing.
Please set the resource share low for this project compared to other production projects in your RALPH@home preferences.

Is anyone out there running with a Mac? Are your jobs from 5.02 or 5.03 running?

We've tried to make the watchdog a little less aggressive about aborting, and are having it give
us back the reason for aborting. Let us know if
you think these jobs are getting killed too soon, or
too late. Thanks!

Before people perform an upgrade to their BOINC software, could you please provide some information as to the impact this may have on other projects they may be running. Many of the users are running multiple projects, and this kind of an upgrade could have serious implications for those other efforts.

In particular people running CPDN and Predictor may have some issues.

There are no implications I upgrade my BOINC client whenever ROM and the team bring out a new version, to help test if for bugs, in the many months I have been upgrading to various clients I have never had a trashed WU.

Besides if people wish to help RALPH solve the 1% bug they have no choice this is the only BOINC client that handles what RALPH needs for the error reporting