No idea yet, sorry. When the project gets a chance (they\'re very undermanned).

Which projects have special 64-bit code (as opposed to renamed 32-bit code)? (I\'m aware of APS and PrimeGrid having 64-bit versions).

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

At the risk of repeating myself, see this. As you can see 14 BOINC projects send native 64-bit applications for at least one OS. Many of them with less funding than CPDN, but evidently with more enthusiasm and gratitude towards its volunteers.

HTH

---

Please see my post from last night here.

---

Cpdn news

...Many of them with less funding than CPDN...

Ha, that\'s amusing. CPDN is two people struggling to cope, the project regularly runs out of enough disk space to store the data. They only get enough time to firefight, and no time to work on features.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

Hey,
I went and checked through the message boards on the other projects I run to be certain of this. Apparently most of the projects I run DON\'T have true 64-bit apps. They have 32-bit apps disguised (and advertised) as 64-bit apps, so, I\'ve compromised. I\'ve re-installed the 32-bit client and will use it until my current model finishes. After that I\'m switching (since at least SIMAP DOES have a true 64 bit app), and if Climate Prediction doesn\'t have the servers upgraded I guess I won\'t be able to get more work until they find the time to upgrade.

Another thought. I seem to remember reading on the SETI site (at least I think it was SETI) that BOINC was originally intended to allow the project to use spare disk space on the client machines, I don\'t know whether this has been implemented, and there are probably people who don\'t want the project storing its files on their computers, but it might be worth investigating. Of course, there\'s that funny issue of finding time.

---

The problem was that people are happier to donate CPU time than disk space (and over time, disks are formatted / go bad / get \'cleaned up\'). So the project found that it had to collect all the output itself.

Hopefully the 64-bit support will be enabled sooner or later, I know they want to do it, but they\'re buried under a constant stream of firefighting.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

well i have been getting this error for work unit http://climateapps2.oucs.ox.ac.uk/cpdnboinc/workunit.php?wuid=5926462

climateprediction.net 28/10/2007 3:24:45 AM Reporting 1 tasks
climateprediction.net 28/10/2007 3:24:55 AM Scheduler RPC succeeded [server version 509]
climateprediction.net 28/10/2007 3:24:55 AM Message from server: platform \'windows_x86_64\' not found
climateprediction.net 28/10/2007 3:24:55 AM Reason: requested by project

so basically i was unable to talk to server (ie trickles up ect) therefore i have aborted work unit and detached from project

if someone could manually mark that work unit as client detached so work unit could be reissued or will that occur automatically on the 16 Mar 2008 11:54:25 UTC ?

When an Abort is issued, the model is marked immediately and automatically for re-issue.

When an Abort is issued, the model is marked immediately and automatically for re-issue.

so how exactly would that occur when you get this from server also if you check work unit you will notice these been no communication since the 19th of October
climateprediction.net 28/10/2007 10:24:45 PM Reporting 1 tasks
climateprediction.net 28/10/2007 10:24:55 PM Scheduler RPC succeeded [server version 509]
climateprediction.net 28/10/2007 10:24:55 PM Message from server: platform \'windows_x86_64\' not found
climateprediction.net 28/10/2007 10:24:55 PM Deferring communication for 1 days 0 hr 0 min 0 sec
climateprediction.net 28/10/2007 10:24:55 PM Reason: requested by project

in other words once a day my comp would had tried to talk to server and everyday server would tell my comp to wait 1 more day simply because server does not know about platform \'windows_x86_64\' or put much simpler server snobs XPx64 and does not allow any meaningful communications from client

There are 2 different types of \'messages\': zips and trickles.
For people with 64 bit systems, one gets accepted, and the other doesn\'t. I forget which is which.

If the model HASN\'T been automatically marked for re-issue after you aborted it, then no one will be doing this manually. The wu will just sit there for about 6 weeks, and then the server will mark it as abandoned.
And the labels on your account page will remain as they currently are until the one year dead line is up, and then one of the labels will change to something like: \"not heard from\".

There is a sticky at the top of all sections of this board regarding the non-availablity of 64 bit models from this project.
The problem with 64 bit computers not being able to return part of the work is well known, and is mentioned in several threads, along with the only work around. (Use a 32 bit version of BOINC on a 64 bit computer.)

along with the only work around. (Use a 32 bit version of BOINC on a 64 bit computer.)

well none of the workaround\'s i have read deal with the fact that the operating system is not supported and i fail to see what difference running a 32 bit version of boinc, would it not still report \"platform \'windows_x86_64\' not found\" ? and going back to 32 bit version of boinc would not allow me to run native 64 bit app from abc

ps i gained 802.19 million inter operations per second per core going from 32 bit to 64 bit operating system, why would i go back ?

\'windows_x86_64\' is a science application for Windows version of 64 bit BOINC.

If you have another project that you wish to run that uses 64 bit code, that\'s fine. You\'ve decided that\'s what\'s important to you, along with more integer operations.
Not that the number of int ops means anything for credits on these climate projects.

well none of the workaround\'s i have read deal with the fact that the operating system is not supported and i fail to see what difference running a 32 bit version of boinc, would it not still report \"platform \'windows_x86_64\' not found\" ? and going back to 32 bit version of boinc would not allow me to run native 64 bit app from abc

ps i gained 802.19 million inter operations per second per core going from 32 bit to 64 bit operating system, why would i go back ?

What is is about the explanations you don\'t/won\'t/refuse to/can\'t understand?

You \"read\" about workarounds. You \"fail to see\". What have you actually tried?

64-bit CPUs and OS work just fine in CPDN. Repeat, just fine. The servers have no problems with them.

If I were constrained by your illogic, none of my six boxes could communicate with the Project. All six have 64-bit CPUs; in Linux, all six run 64-bit OS; in Windoze, four of the six run 64-bit OS. In all 12 possibilities, they run 32-bit boinc.
If you glance to the left of this post, you might conclude from the numbers that they manage to crunch a bit here and there -- and make at least occasional successful contact with the servers.

CPDN Models are 32-bit clients; they gain NOTHING, repeat, NOTHING, from 64-bit at this time. (An upgrade was tried in Alpha Test some time ago but there was an atmosphere-ocean boundary problem and not enough staff time to sort it.)

You can harp all you want about your wondrous gain in integer count with 64-bit. This Project COMPLETELY IGNORES Benchmarks for credit --> besides, CPDN Models are floating point. Your Models won\'t process a bit faster if/when the server recognizes 64-bit boinc.

Les\' comments are on the mark. If you were to read and accept the assistance volunteers offered you, rather than trying to mold the Project to your wants, you could solve your problem. If not, there\'s nothing we can do to help.

If you are content with ABC\'s 64-bit client (assuming it is 64-bit, most of the Projects which recognize 64-bit boinc have 32-bit clients -- but, if memory serves, two of about 50 actually have them), then have at it. Your choice.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

If you are content with ABC\'s 64-bit client (assuming it is 64-bit, most of the Projects which recognize 64-bit boinc have 32-bit clients -- but, if memory serves, two of about 50 actually have them), then have at it. Your choice.

Your memory is slightly off here. There are only two projects so far that GAIN any significant processing speed from running a 64bit app, ABC and APS. There are a few more that have native 64bit apps but they do not make a difference.

There may be a new workaround in the 5.10.27 client. By adding an approiate <alt_platform> element to the cc_config.xml file you may be able to get 32bit apps from a server that does not recognize 64bit clients. I have not tested this though.

---

BOINC WIKI

BOINCing since 2002/12/8

well none of the workaround\'s i have read deal with the fact that the operating system is not supported and i fail to see what difference running a 32 bit version of boinc, would it not still report \"platform \'windows_x86_64\' not found\" ? and going back to 32 bit version of boinc would not allow me to run native 64 bit app from abc

ps i gained 802.19 million inter operations per second per core going from 32 bit to 64 bit operating system, why would i go back ?

What is is about the explanations you don\'t/won\'t/refuse to/can\'t understand?

You \"read\" about workarounds. You \"fail to see\". What have you actually tried?

i dont understand how a 64 bit app would be able to run in a 32 bit , silly old me but i sure you understand how it works and no i have not tried installing 32 bit version of boinc since i dont believe it is possible to run 64 bit in 32 bit

64-bit CPUs and OS work just fine in CPDN. Repeat, just fine. The servers have no problems with them.

If I were constrained by your illogic, none of my six boxes could communicate with the Project. All six have 64-bit CPUs; in Linux, all six run 64-bit OS; in Windoze, four of the six run 64-bit OS. In all 12 possibilities, they run 32-bit boinc.
If you glance to the left of this post, you might conclude from the numbers that they manage to crunch a bit here and there -- and make at least occasional successful contact with the servers.

you noticed how you said 32 bit boinc , i don\'t have it nor is that going to change i am very happy with 64 bit version of boinc

CPDN Models are 32-bit clients; they gain NOTHING, repeat, NOTHING, from 64-bit at this time. (An upgrade was tried in Alpha Test some time ago but there was an atmosphere-ocean boundary problem and not enough staff time to sort it.)

thats not what i have asked for nor will i

You can harp all you want about your wondrous gain in integer count with 64-bit. This Project COMPLETELY IGNORES Benchmarks for credit --> besides, CPDN Models are floating point. Your Models won\'t process a bit faster if/when the server recognizes 64-bit boinc.

most projects that i actively crunch from have server assigned credits so bench mark doesn\'t make any difference but i am sure increase in integer speed translates to faster run times of work units

Les\' comments are on the mark. If you were to read and accept the assistance volunteers offered you, rather than trying to mold the Project to your wants, you could solve your problem. If not, there\'s nothing we can do to help.

was this not my original question

if someone could manually mark that work unit as client detached so work unit could be reissued or will that occur automatically on the 16 Mar 2008 11:54:25 UTC ?

basically project did not want to play nice and i detached from project i thought i was doing the polite thing by asking someone to deal with this, apparently not.
as for me trying to mold this project, get a life

If you are content with ABC\'s 64-bit client (assuming it is 64-bit, most of the Projects which recognize 64-bit boinc have 32-bit clients -- but, if memory serves, two of about 50 actually have them), then have at it. Your choice.

abc uses 64 bit client not a re badged 32 bit version as for other projects even if it is a 32 bit app they still run in 64 bit environment

If you are content with ABC\'s 64-bit client (assuming it is 64-bit, most of the Projects which recognize 64-bit boinc have 32-bit clients -- but, if memory serves, two of about 50 actually have them), then have at it. Your choice.

That\'s not correct. You\'re entitled to your own opinions, but not to your own facts. See this thread for the facts.

There are 14 projects that provide native 64-bit applications. The overwhelming majority of projects support 64-bit clients with just a handful of projects that haven\'t upgraded the server software, including CPDN.

HTH

---

Your memory is slightly off here. There are only two projects so far that GAIN any significant processing speed from running a 64bit app, ABC and APS. There are a few more that have native 64bit apps but they do not make a difference.

This is not true. 64-bit applications typically experience an improvement of 10% due to the greater number of registers available, as I explained here.

You could say though that ABC, APS and SHA-1 gain SIGNIFICANT speed from 64 bits.

HTH

---