It looks like this problem ("running in standalone mode") is present in all the results from App 4.38 and Core Clients 4.43, though it doesn't always lead to Client Errors.
I (and probably the BOINC people, too) would be really curious to know whether the problem with the old Client still occurs with the 4.49 App currently in Beta test, which has been built with a more recent version of the BOINC library.
BM
I'll run it out of a directory in my own account as not to screw up my regular install.
So I'll do CC 4.43 and E@H 4.38 as well as 4.49.
[edit]Oye, I forgot where everything in the old manager was. Off to get my account key.[/edit]
RE: It looks like this
)
I'll run it out of a directory in my own account as not to screw up my regular install.
So I'll do CC 4.43 and E@H 4.38 as well as 4.49.
[edit]Oye, I forgot where everything in the old manager was. Off to get my account key.[/edit]
[edit2]The instance of the host is here.[/edit2]
Kathryn :o)
Einstein@Home Moderator
RE: So I'll do CC 4.43 and
)
Two tasks complete. One and two. They're waiting on the wingman.
Sorry about the aborts. I'm not sure where the general prefs are coming from and what they're set to.
E@H 4.49 currently running and it doesn't look good. Same behavior. No CPU time counting.
Kathryn :o)
Einstein@Home Moderator
RE: E@H 4.49 currently
)
Two results finished with 0 CPU time. Waiting on the wingman for validation. One and two.
Kathryn :o)
Einstein@Home Moderator
RE: RE: So I'll do CC
)
And both validated.
Kathryn :o)
Einstein@Home Moderator