Posts by Link

1) Message boards : Wish list : Adreno iGPU support (Snapdragon laptops) (Message 8760) Posted 12 May 2026 by Link Post: Also, currently getting 18 concurrent tasks, all running, but they are stuck at 4,779% completion, why? Because that's how the application displays it. Let them run, they will progress in few huge steps.
2) Message boards : Number crunching : Testing Intel 18A / Xe3 (Arc B390) Throughput on RC5-72 (Message 8739) Posted 16 Jan 2026 by Link Post: This project does not support Intel GPUs as you can see on the applications page.
3) Message boards : Number crunching : No CPU work on AMD cpu, but plenty on Intel CPUs - why? (Message 8731) Posted 9 Dec 2025 by Link Post: My AMD 7800X3D is not getting any CPU-work. Is it not getting or not requesting any work? Post log of a scheduler request.
4) Message boards : Science : Current project status and progress updates (Message 8727) Posted 14 Nov 2025 by Link Post: Is there an estimate on when the current phase might be completed? Yes. You need to put this link in the server status. Actually better put it on the front page, in the "What is Moo! Wrapper?" section, there's no need to hide it any deeper.
5) Message boards : Number crunching : OpenCL errors with RTX 5xxxx series GPUs !? (Message 8723) Posted 19 Oct 2025 by Link Post: I doubt that the project administrator can do anything, since the distributed.net client does not support 64-bit GPU applications on Windows OS The distributed.net client is open source, so actually the project administrator of Moo! can do something about it. The Android version is not from distributed.net either, at least I don't see it anywhere on their page.
6) Message boards : Cafe : BOINC Census 2024 (Message 8716) Posted 22 Jul 2025 by Link Post: Nope, loads without any issues for me.
7) Message boards : Science : Current project status and progress updates (Message 8713) Posted 13 Jul 2025 by Link Post: Latest in 14,380 days at yesterday's rate. And the rate is increasing, the overall rate since the project started is just 220 blocks/sec, yesterday's rate was 759 blocks/sec. It was even higher in the past, than lower, but overall it's increasing with new hardware, so unless all users suddenly drop the project, it should be completed one day. It can be completed any moment actually, I mean it's not very likely that the right answer is in the last block.
8) Message boards : Number crunching : Task download failed (Message 8710) Posted 10 Jul 2025 by Link Post: Yes, the files are missing on the server. Admin needs to fix it.
9) Message boards : Number crunching : Only nvidia GPU tasks available? (Message 8707) Posted 25 Jun 2025 by Link Post: Looks like tasks are now handed out to ATI GPUs as well... CPU tasks may be requested in a few hours. I'm curious ;-) No "tiny" ones available, so that aspect can't be the whole story. Your ATI cards are getting the "huge" tasks with 768+ blocks, so yes, this was something else, that was not visible on the SSP.
10) Message boards : Number crunching : Only nvidia GPU tasks available? (Message 8705) Posted 24 Jun 2025 by Link Post: I know that running old dual core CPUs is mostly for fun but is going to be sad to lost one of the few projects where running these make any sense. An old dual core CPU can still run most of the projects, I was running myself a Core 2 Duo E7300 until a year ago as my main system and there were no real issues on the CPU side, it was crunching mostly either Einstein's FGRP5 or WCG's MCM. Both perfect projects for CPUs of nearly any age, even x86 single cores and with some real scientific value. Just the GTX 275 couldn't run anything else than Moo! in the end when Milkyway Separation ended (it was also able to run PPS sieve on Prime Grid, but the computer became unusable with it, so I have run Moo! instead). Is there any documentation somewhere explaining which clients are eligible for which task type? I'm wondering, because my AMD GPUs also didn't get any tasks, and having three out of four task types only handed out to nvidia GPUs seems a bit particular. I couldn't find anything that helped me understand things in the source repo nor the web site here. I don't think there's some real documentation, but IIRC I've read somewhere, that the server tries to send such size of tasks, that they complete within max of an hour or so. Of course it can't send smaller tasks than tiny.
11) Message boards : Number crunching : Only nvidia GPU tasks available? (Message 8702) Posted 24 Jun 2025 by Link Post: Well, seems the project is out of "tiny" tasks, see server status page.
12) Message boards : Wish list : WU size option (Message 8697) Posted 19 Jun 2025 by Link Post: I have no idea how you do that exactly on a Mac, but in general you go to your Moo! project dir and run the client from command line with the -bench command attached, so in your case it will be something like "dnetc518-macosx-amd64 -bench". To get correct values you need to limit Moo! crunching in BOINC to one core less than usual, but do not stop it completely. Eventually you might want to try how fast it is with different amount of cores in use, after all it's running in emulated environment.
13) Message boards : Wish list : WU size option (Message 8695) Posted 18 Jun 2025 by Link Post: My point was, that you won't get smaller WUs even if you choose manually the tiny ones since you already get them, so your feature request might not solve your "issue". However I have another hint for you: run the benchmark integrated in the dnet client, it detects your CPU as "Intel Xeon 56xx processor" and since you obviously don't have it, it's likely not choosing the optimal "core". Set than the fastest core in your Moo! Wrapper preferences.
14) Message boards : Wish list : WU size option (Message 8693) Posted 18 Jun 2025 by Link Post: Your Mac is getting the "tiny" WUs with just 12 blocks (used to be 9 in the past), there are no smaller WUs here. "Tiny" is 12 blocks, "small" is 32 blocks (IIRC sometimes up to around 36-38, my HD 3850 always got them), "normal" is 256+ blocks and "huge" is 768+ blocks. The automatic selection works actually pretty well here.
15) Questions and Answers : Web site : Email change keeps getting reversed (Message 8691) Posted 31 May 2025 by Link Post: A workaround would be in this case a security issue, so no, there is no workaround.
16) Questions and Answers : Web site : Email change keeps getting reversed (Message 8685) Posted 24 May 2025 by Link Post: IIRC you need to confirm the change via a link, that's send to the old email adress.
17) Questions and Answers : Android : Computation error (Message 8682) Posted 18 Apr 2025 by Link Post: My best guess from "Exec format error" is that the Moo! wrapper executable is made for 32-bit ARM and you are trying to run that on a 64-bit ARM system without 32-bit support. The dev will have to look into it, no idea if it's possible to install 32-bit libraries on a phone.
18) Message boards : Wish list : GPU applications for 64-bit Windows (Message 8680) Posted 31 Mar 2025 by Link Post: Necessary for those of us who need to use <no_alt_platform> in cc_config.xml to stop other projects from sending slow 32-bit CPU applications. I know that distributed.net doesn't have any native 64-bit GPU apps, but you might release the 32-bit GPU applications with different platform tag, Windows will run them anyway, at least in the next one or two decades. Eventually need to check that again when Windows 12 comes out, but nothing to worry at least until than.
19) Message boards : Science : Current project status and progress updates (Message 8678) Posted 13 Mar 2025 by Link Post: Is there an estimate on when the current phase might be completed? Yes.
20) Questions and Answers : Macintosh : MacOS Apple Silicon ARM support? (Message 8675) Posted 27 Feb 2025 by Link Post: But then you adapt to that new reality if/when it happens, right now there is a massive unused potential, cause Apple Silicon doesn't show up on the applications page Better change the description of the current application or add a copy of it with a different name, whichever is easier to do. But definitely not create something, that needs to be permanently watched as it will break one day. Most people won't care or even know that the project is using Rosetta 2, they just wanna run project that works But they do know, that they can run programs written/compiled for Intel Macs? So why schould this not work? And if they don't know that, than that's another good reason not to release an application for them, which will stop working one day.

Next 20