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 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 ?

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.

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

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

Does suspending CPDN help? (I can\'t remember if it suspends the uploads or not, I\'m not near a PC with Boinc).

Resolving the problem involves ordering new disks and installing them into the servers, I know the disks were ordered a few days ago but don\'t know when they\'re arriving / being fitted. Hopefully very soon.

It will do no harm at all just to suspend boinc network activity and let these 10-year zip files wait a day or two to upload.

well i have had six trickles and no credits whatsoever, still i see some sign of credits i will leave work units suspended

edit credits are not showing up here or else where

Do you have your Network settings allowed to upload in BOINC Manager?
BOINC Manager->Activity->??? What is it set to?

If Network activity suspend, you won\'t upload trickles. So they won\'t register anywhere.