When will the 64 bit client be supported here at Climate Prediction? I upgraded the the new 64 bit client last week and lost the work I had been doing with the following error in Boinc:

5/10/2007 3:11:15 AM|climateprediction.net|Message from server: platform \'windows_x86_64\' not found


At first I thought it was a problem with the client, but I run other applications with the 64 bit client with no problems.

---

This project doesn\'t have a 64 bit application at present.
Perhaps next year, perhaps later.

You need to install the 32 bit files/programs on your 64 bit computer, so that it can access the 32 bit program here.

---

Backups: Here

There was a bug in a particular version of the beta Boinc manager (5.9.<something>) which was causing this error, I think it\'s been fixed in the latest one. But beta code will have bugs which will sometimes kill workunits, so it might be safer to use a released manager rather than a test manager.

---

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

The 5.9.10 client looks to be reasonably stable, although still not quite ready for release.

The server will still need to be updated before it will work. The version from 4/30/7 or later is required.

---

BOINC WIKI

BOINCing since 2002/12/8

This project doesn\'t have a 64 bit application at present.
Perhaps next year, perhaps later.

You need to install the 32 bit files/programs on your 64 bit computer, so that it can access the 32 bit program here.

I have been at this since the days of 8 bit software and the Intel 8088 processor that ran at a blistering 9 something megahertz and it seems that the entire industry has been asleep at the switch on 64 bit apps, driver, etc; including Microsoft (their own One Care Live application does not support the 64 bit version of Vista; go figure).

I for one am going to continue pushing in the 64 bit direction, I have one computer running 64 bit Vista Ultimate and plan to migrate another to 64 bit Vista Business this weekend. There are a few BOINC apps that support the 64 bit client, so my computers are not idle and I guess I will continue crunching them until my old favorite BOINC apps catch the 64 bit wave.

---

64 bit apps are not necessarily quicker than 32 bit apps (some will be quicker, some will be slower). AFAIK the only 64 bit Boinc app which is quicker than it\'s 32 bit equivalent is ABC. I\'m not aware of any Boinc applications which have a need to address over 4GB of RAM in their process address space.

In 1990, I was working on a 128-bit system (ICL\'s 3900 mainframe range), and there\'s no sign of PCs evolving to that point yet.

---

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

Any news on this topic? Boinc just released 5.10.7 as the official 64 bit recommended install. The tag sent for platform ID reads \"windows_x86_64\", which does not seem to be accepted at some servers, climateprediction amongst others.

I wouldn\'t like to go back, but I would also hate to loose two prediction sets at 70%, just because the standard host is not supported here. Any comment from the inside guys?

---

Any news on this topic? Boinc just released 5.10.7 as the official 64 bit recommended install. The tag sent for platform ID reads \"windows_x86_64\", which does not seem to be accepted at some servers, climateprediction amongst others.

I wouldn\'t like to go back, but I would also hate to loose two prediction sets at 70%, just because the standard host is not supported here. Any comment from the inside guys?

I\'m als using the 64-bit version of 5.10.7 and get the same error message. Sice I\'m running a 64-bit version of Vista don\'t really want to run mor 32-bit software than I have to.

---

Carl is working on a 64-bit climate model, probably won\'t reach beta for a year or so (it needs 64-bit because it uses 4.7GB of RAM).

See this thread: http://boinc.berkeley.edu/dev/forum_thread.php?id=1863

---

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

Updateing the scheduler to be based on the current head should enable the sending of 32bit models to 64bit machines until the 64bit model is ready.

In fact only 2 or 3 projects are actually sending 64bit tasks, most are using the new server code to automatically send 32bit tasks to 64bit clients.

---

BOINC WIKI

BOINCing since 2002/12/8

Carl is working on a 64-bit climate model, probably won\'t reach beta for a year or so (it needs 64-bit because it uses 4.7GB of RAM).

See this thread: http://boinc.berkeley.edu/dev/forum_thread.php?id=1863

Thanks for the Ref - the question however, is more one of accepting results from the current 32 bit application running on a 64 bit platform. Actually harnessing the 64 bit (as done by ABC@home) would be a boon, surely, though I would expect this to happen rather on the integer/float width end than on the memory allocation front, even at today\'s growth of memory for home PCs. And you surely cannot switch engines on a task already started, so you would want to finish the old runs anyway.
The main problem seems to be that the server needs to accept the \"windows_x86_64\" platform as a valid client. The data that comes up for this application here sees no change. But in parallel the willing user might spend fome Mips/Flops on a 64 bit task, while still crunching away on the trusty climate model (on the other CPU, or whatever).
So, is there any plan on updating the server anytime soon, now that Boinc went official on 64 bit?
Is it ok to keep crunching with the 64 bit variant, even if it meens stockpiling a number of trickles until they become \"legal\"?
I would just hate to see that server connecting up one day and declaring so many of hours of crunching illegal and just reset my tasks to zip because of that.

---

The only advantage 64-bit code has over 32-bit code is memory allocation, since you can use any size of ints/floats when running 32-bit code. In all the projects I\'ve worked on, it\'s been routine to use 64 or 80 bit floats rather than 32-bit floats.

My first full-time programming job, 17 years ago, was with a 128-bit instruction set (system programming on ICL\'s 3900 mainframes), PCs still haven\'t caught up to that :-)

The 64-bit work fetch code was updated on the most recent versions of the Boinc software recently (late 5.9 and 5.10 I think). This might be why you\'re having problems. The name used for 64 bit instruction sets was changed. I\'m not sure of the implications since I don\'t use the 64 bit client, but Keck\'s post above sounds like it should be resolved eventually.

http://boinc.berkeley.edu/dev/forum_thread.php?id=1742

---

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

From what I\'ve read elsewhere, SETI isn\'t using the \'normal\' naming idea for 64 bit programs, so If other projects do, then you\'ll still have to decide which to run, and which to drop.

From what I\'ve read elsewhere, SETI isn\'t using the \'normal\' naming idea for 64 bit programs, so If other projects do, then you\'ll still have to decide which to run, and which to drop.

I checked with SETI - they definitely accept the current client. I read somewhere else, don\'t remember where, some people started coding clients that send an \'AMD64\' platform ID, with some servers accepting these. So there seems to be some movement in that direction, though I sort of miss a coordinated effort. Just who says what is supposed to be \'normal\'?

---

A few projects and non-standard clients started using the \"AMD64\" platform ID before an official platform ID was created. When an official platform ID was created it used \"x86_64\". So that is the direction all projects will be heading eventually.

---

BOINC WIKI

BOINCing since 2002/12/8