Can climatprediction.net run on Apple Macintosh OSX v10.4.11 ?
I have a lot of old running systems.

Possibly, if there were any.
But there's only been Linux tasks for a long time now.

However, I discovered this


Meaning : "mac only" (??)

and also


Meaning : that's the only work available (!!)

So I tried my luck : no luck.

Sam 5 fév 11:30:08 2022 | climateprediction.net | Message du serveur: Ce projet ne supporte pas les ordinateurs de ce type x86_64-apple-darwin

How can that be ??

(this is the machine)

How can that be ??

(this is the machine)

I can confirm that the current batch of hadcm3s tasks are Mac only. I am not sure why your machine isn't getting any. I don't know if the recent problem with Windows machines and security certificates affected Apple machines or not - the message you are getting doesn't suggest that but Macs being an alien species to me I don't have any other ideas. Ian another moderator has gotten at least one task on his Mac so you may have to wait till he or someone with experience of Macs sees this.

Thanks for your quick answer.

The server had delayed next contact to one day.
I tried a manual update, I got the exact same message

Sam 5 fév 13:10:57 2022 | climateprediction.net | Message du serveur: Ce projet ne supporte pas les ordinateurs de ce type x86_64-apple-darwin

+ another day delay

Sam 5 fév 13:10:57 2022 | climateprediction.net | Project requested delay of 86400 seconds

I'm afraid it doesn't like my Mac :(

type x86_64-apple-darwin

The programs are 32 bits, and I think that Apple has moved away from this.

type x86_64-apple-darwin

The programs are 32 bits, and I think that Apple has moved away from this.

Got an idea there may be a workaround somewhere on the BOINC forums but I didn't find it when I had a quick look.

I found this :

including this point : "Yes, it's possible to run 32-bit apps with a 64-bit kernel."

but maybe it's more complicated than it seems ?

cpdn needs "certain 32 bit libraries" to work.
I don't know which ones they are, but my Linux Mint machines have always loaded everything needed, so I've never looked into it.

I'm not sure what's going on. But with with the upgrade to "Catalina" (OS X version 19.x) a couple years ago, 32-Bit Apps 'Not Optimized for Your Mac' No Longer Working on macOS Catalina.

Dave, did you see any computers with Darwin versions 19 and above with successes in the previous batch?

Okay, I went through the first 100 successes, of which about 75 were on Macs. Of the successes, 100% of those were on Darwin 18.7 or older.

On the successes, I looked for failures on those work units from other Macs, and every Darwin 19 or 20 PC was receiving the bad CPU type errors.

Edit...I've alerted Sarah and Andy about this.

Thanks a lot for all your investigations !

Wikipedia has a Darwin release history , 18.7 is not mentioned there but 18.0 is "mojave" (back in 2018) and I must confess it had been a very very long time that I had not participated to CPDN (much more years than 2018 I think) and I cannot remember on which machine / OS (even mac ?) I was then.

Hopefully your devs find a cure to this :)

Darwin 19 starts with macOS 10.15.2, so that all ties up with Charlie's note "allow 32-bit applications only if OS X version < 10.15".

With a suggestion from Sebastien at l'AF I added <alt_platform>i686-apple-darwin</alt_platform> in my cc_config and got the project to give me tasks but they immediately fail

process exited with code 255 (0xff, -1)</message>
<stderr_txt>
Process creation (../../projects/climateprediction.net/hadcm3s_8.36_i686-apple-darwin) failed: Bad CPU type in executable (errno = -1)
</stderr_txt>

and what Richard wrote makes sense.

I assume this confirms some dev must be done to the app ? Hopefully they can !

With a suggestion from Sebastien at l'AF I added <alt_platform>i686-apple-darwin</alt_platform> in my cc_config and got the project to give me tasks but they immediately fail

process exited with code 255 (0xff, -1)</message>
<stderr_txt>
Process creation (../../projects/climateprediction.net/hadcm3s_8.36_i686-apple-darwin) failed: Bad CPU type in executable (errno = -1)
</stderr_txt>

and what Richard wrote makes sense.

I assume this confirms some dev must be done to the app ? Hopefully they can !

That would mean the UK Met Office re-writing their code to use 64 bit instead of 32.
The data generated by them has been across many decades, and changing anything will give slightly different results, making comparison across those decades harder than it already is.

Well. I hope my Mac's not the only one here still running Mojave. It would take a while to get through the 2247 tasks still waiting to be sent! ;)

---

NG

Well. I hope my Mac's not the only one here still running Mojave. It would take a while to get through the 2247 tasks still waiting to be sent! ;)

Not unless you have 316 tasks on your computer(s) at the moment.

Andy says,

Thank you George. Yes we are sadly aware of this, that 32 bit runs will not be able to run on post Catalina Macs.
We will however have the OpenIFS app which won't this issue.

Just hope Windows don't go down the route of not allowing 32bit programs. Major Linux distributions seem to be saying 32bit libraries will continue to be available for the medium term at least.

Hi Nigel

I'd join you, except my MacBook Air, Mountain Lion, 10.8, stopped attaching to secure sites last year.
"Safari can't establish a secure connection to ...."

A site that has tips for this says at one point to click on the lock symbol, and change some setting.
But none of the secure sites HAS the lock symbol on the Mac, even though it appears when using my Linux desktop.

Have you had this problem?

Les Bayliss wrote:

Have you had this problem?

Hi Les.

I had to give up Einstein@home on my old PowerMac (Mac OS X 10.5 Leopard) some years ago because Leopard could no longer handle the SSL connections to EAH's server(s).

I've just tried connecting to my CPDN account page using the Safari on my now semi-redundant MacBook Pro (macOS 10.11 El Capitan) and was presented with a display saying "This Connection Is Not Private". Clicking the "Show Details" button in the display got me the explanation that the site's certificate was invalid — although of course it was that Safari's data that were out of date. There was a link at the end to visit the site anyway and after I clicked that, OK-ed an "Are you sure?" dialog, and entered my machine user password into a security dialog, Safari updated itself to accept the CPDN certificate and connected to my account page. I had to repeat the process to connect to CPDN's front page, but not to connect to the fora.

If you already have BOINC installed on your MacBook Air, I think you should be able to attach to your existing CPDN account from BOINC Manager. But you'll probably need to follow the above procedure if you have to download BOINC in the first place!

My iMac is comparatively young and it's just fortuitous that I chose not to upgrade it beyond Mojave because of other 32-bit software that I want to keep using for now. In view of the revelation that CPDN tasks can't run on later systems, I've temporarily suspended work fetch for my other BOINC projects in order to take up some of the slack. I've also just re-enabled CPDN on the MacBook Pro, which I haven't done up till now because the tasks are likely to take a week or more of continuous running on it and I've been reluctant to have it working so hard for so long at its age. I'm currently waiting to see if it manages to get any tasks and how it gets on with them.

---

NG