Posts by Link

\n studio-striking\n
1) Questions and Answers : Web site : Email change keeps getting reversed (Message 8691)
Posted 16 days ago by Link
Post:
A workaround would be in this case a security issue, so no, there is no workaround.
2) Questions and Answers : Web site : Email change keeps getting reversed (Message 8685)
Posted 23 days ago by Link
Post:
IIRC you need to confirm the change via a link, that's send to the old email adress.
3) 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.
4) 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.
5) 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.
6) 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.
7) Questions and Answers : Macintosh : MacOS Apple Silicon ARM support? (Message 8673)
Posted 23 Feb 2025 by Link
Post:
These were running under Rosetta 2 though, so not native, but still, it works, which means you can add MacOS ARM to the Applications page :)
Better not, now you can run it as alternative platform when it is indeed available and when it is not available, nothing happens. If you add the current application as ARM, it will crush all tasks in case Rosetta isn't available, for example if Apple decides that their users don't need it anymore.
8) Questions and Answers : Web site : Feeder offline for 2 days (Message 8671)
Posted 30 Jan 2025 by Link
Post:
I also reset about 50 completed CPU and GPU tasks, deleted the project, and added it again, thinking it would help.
How exactly was that supposed to start the feeder on the project server?
9) Message boards : Number crunching : Suggested Settings (Message 8652)
Posted 30 Dec 2024 by Link
Post:
No, I mean the benchmark of the distributed.net client. To run it, disable GPU computing in BOINC (but let the usual amount of CPU tasks run), go to Moo! Wrapper project dir and run for example "dnetc521-win32-x86-opencl.exe -bench" from the command line. It will tell you, which "core" is the fastest for your current setup. Repeat for different amout of used CPU cores or additional GPU tasks to find the best config for your system. Even different CPU projects might have effect on which core is the fastest and how many CPU cores you need to leave free to feed the GPU. You schould get something like this:

distributed.net client for OpenCL on Win32 Copyright 1997-2016, distributed.net
Please visit http://www.distributed.net/ for up-to-date contest information.
Start the client with '-help' for a list of valid command line options.


dnetc v2.9112-521-GTR-16021317 for OpenCL on Win32 (WindowsNT 6.2).
Please provide the *entire* version descriptor when submitting bug reports.
The distributed.net bug report pages are at http://bugs.distributed.net/

[Dec 30 09:25:02 UTC] RC5-72: using core #0 (CL ANSI 1-pipe).
[Dec 30 09:25:08 UTC] RC5-72: Benchmark for core #0 (CL ANSI 1-pipe)
                      0.00:00:04.01 [1,101,718,290 keys/sec]
[Dec 30 09:25:08 UTC] RC5-72: using core #1 (CL 1-pipe).
[Dec 30 09:25:13 UTC] RC5-72: Benchmark for core #1 (CL 1-pipe)
                      0.00:00:02.85 [1,572,042,516 keys/sec]
[Dec 30 09:25:14 UTC] RC5-72: using core #2 (CL 2-pipe).
[Dec 30 09:25:20 UTC] RC5-72: Benchmark for core #2 (CL 2-pipe)
                      0.00:00:04.10 [1,080,195,879 keys/sec]
[Dec 30 09:25:20 UTC] RC5-72: using core #3 (CL 4-pipe).
[Dec 30 09:25:27 UTC] RC5-72: Benchmark for core #3 (CL 4-pipe)
                      0.00:00:04.12 [1,068,081,893 keys/sec]
[Dec 30 09:25:27 UTC] RC5-72 benchmark summary :
                      Default core : #-1 (undefined) 0 keys/sec
                      Fastest core : #1 (CL 1-pipe) 1,572,042,516 keys/sec
[Dec 30 09:25:27 UTC] Compare and share your rates in the speeds database at
                      http://www.distributed.net/speed/
                      (benchmark rates are for a single processor core)
10) Questions and Answers : Android : Computation error (Message 8651)
Posted 30 Dec 2024 by Link
Post:
If you've checked the other threads, you would have noticed, that anything newer than Android 9 or so doesn't work.
11) Message boards : Number crunching : Suggested Settings (Message 8648)
Posted 24 Dec 2024 by Link
Post:
The best suggested settings for this project and for your computer you will get from the build-in benchmark, which you should run with CPU tasks running.
12) Message boards : Wish list : Windows 11 ARM and Intel ARC GPU support (Message 8645)
Posted 15 Dec 2024 by Link
Post:
It doesn't seem to find any info about the GPU, so this is worse than this. No idea than, only someone from distibuted.net can help you but I've really no idea how to contact them and if they are doing any maintanance of the code anymore or provide any support, there's no forum, only some stone age stuff like mailing lists and IRC. ;-)

Probably submitting that as a bug / feature request into their bug database is the only thing you can do, but I wouldn't hold my breath while waiting for their response.
13) Message boards : Wish list : Windows 11 ARM and Intel ARC GPU support (Message 8643)
Posted 15 Dec 2024 by Link
Post:
Hmm... the good news is, that the wrapper still tried to run the client after it didn't find any Nvidia GPU, it just wrote it to the log as a warning.

What does the client print with "-gpuinfo"?
14) Message boards : Wish list : Windows 11 ARM and Intel ARC GPU support (Message 8639)
Posted 14 Dec 2024 by Link
Post:
Like this, without the ATI part. Try this:

<app_info>
 <app>
  <name>dnetc</name>
  <user_friendly_name>Distributed.net Client</user_friendly_name>
 </app>
 <file_info>
  <name>dnetc_wrapper_1.5_windows_x86_64.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>dnetc521-win64-amd64.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>dnetc_wrapper_1.5_windows_intelx86__opencl_nvidia_101.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>dnetc521-win32-x86-opencl.exe</name>
  <executable/>
 </file_info>
 <file_info>
  <name>dnetc-cpu-1.4.ini</name>
 </file_info>
 <file_info>
  <name>dnetc-gpu-1.5.ini</name>
 </file_info>
 <file_info>
  <name>job-win64-521.1.xml</name>
 </file_info>
 <file_info>
  <name>job-win32-opencl-521.1.xml</name>
 </file_info>
 <app_version>
  <app_name>dnetc</app_name>
  <version_num>105</version_num>
  <file_ref>
   <file_name>dnetc_wrapper_1.5_windows_x86_64.exe</file_name>
   <main_program/>
  </file_ref>
  <file_ref>
   <file_name>dnetc521-win64-amd64.exe</file_name>
   <copy_file/>
  </file_ref>
  <file_ref>
   <file_name>dnetc-cpu-1.4.ini</file_name>
   <open_name>dnetc.ini</open_name>
   <copy_file/>
  </file_ref>
  <file_ref>
   <file_name>job-win64-521.1.xml</file_name>
   <open_name>job.xml</open_name>
   <copy_file/>
  </file_ref>
 </app_version>
 <app_version>
  <app_name>dnetc</app_name>
  <version_num>105</version_num>
  <avg_ncpus>1.00</avg_ncpus>
  <max_ncpus>1.00</max_ncpus>
  <plan_class>opencl_nvidia_101</plan_class>
  <coproc>
   <type>intel_gpu</type>
   <count>1</count>
  </coproc>
  <file_ref>
   <file_name>dnetc_wrapper_1.5_windows_intelx86__opencl_nvidia_101.exe</file_name>
   <main_program/>
  </file_ref>
  <file_ref>
   <file_name>dnetc521-win32-x86-opencl.exe</file_name>
   <copy_file/>
  </file_ref>
  <file_ref>
   <file_name>dnetc-gpu-1.5.ini</file_name>
   <open_name>dnetc.ini</open_name>
   <copy_file/>
  </file_ref>
  <file_ref>
   <file_name>job-win32-opencl-521.1.xml</file_name>
   <open_name>job.xml</open_name>
   <copy_file/>
  </file_ref>
 </app_version>
</app_info>

Coproc type might be wrong, check what name other tasks for that device use if you get some error messages regarding this. Files you need to download are in the other thread.

The main question is, how the wrapper application will react if there's no Nvidia GPU in the system, the other system had one, the wrapper was trying to use it, but the dnet client was running the tasks on Intel GPU for some reason, so that's a different situation.
15) Message boards : Wish list : Windows 11 ARM and Intel ARC GPU support (Message 8633)
Posted 15 Nov 2024 by Link
Post:
There are no distributed.net clients for those platforms yet (and considering the latest clients are from 2018 I wouldn't expect them to release anything new soon), but you might want to try using the AMD or Nvidia OpenCL clients with annonmous platform on your Intel GPU, at least in one case it worked.
16) Message boards : Number crunching : Gt 730 runtime and points (Message 8627)
Posted 18 Oct 2024 by Link
Post:
I still don't see it as coprocessor, please post the startup messages from BOINC's log.
17) Message boards : Number crunching : Gt 730 runtime and points (Message 8621)
Posted 14 Oct 2024 by Link
Post:
Your GT 730 is not even recognized as a coprocessor, 1327991 has only AMD AMD Radeon RX 7800 XT (16368MB) OpenCL: 2.0 visible to BOINC. Or it's messed up somehow, after all it's requesting tasks for it.

At first use this as cc_config.xml (if you don't have one already, otherwise just add the <use_all_gpus> tag):
<cc_config>
 <options>
  <use_all_gpus>1</use_all_gpus>
 </options>
</cc_config>

If after that BOINC still won't see the card, you probably need to update the drivers for it. Download them from Nvidia's site, not via Windows Update as those not always come with OpenCL support. If successful, you should see both GPUs as coprocessors in the details of that computer, like here for example.
18) Message boards : Number crunching : Automatic Selection of Fastest Core doesn't work correct (Message 8606)
Posted 22 Jun 2024 by Link
Post:
There are 12 different CUDA cores, you should run the complete benchmark on each of your cards and than it might be enough to use the four different venues (default/home/work/school) to assign all of them the best cores, your cards are just from 3 different generations. The cores with lower numbers are for old cards, I guess the 2-pipe or 4-pipe cores should perform best (either #5 or #8 in particular, but that's just a guess).
19) Message boards : Number crunching : Try using "ATI Stream Client core" selection to select OpenCL core (Message 8600)
Posted 7 May 2024 by Link
Post:
Yes, this seems to work, at least on the iGPU of my Ryzen CPU.

dnetc_r72_1714231152_13_819_0, run time 2 hours 15 min 54 sec with automatic core selection:
<core_client_version>7.24.1</core_client_version>
<![CDATA[
<stderr_txt>

17:58:00 (5640): wrapper v1.5 build 20 for AMD/ATI OpenCL starting (BOINC Wrapper v7.13.26016)
17:58:00 (5640): device: OpenCL: AMD/ATI GPU 0: AMD Radeon(TM) Graphics (driver version 3444.0 (PAL,HSAIL), device version OpenCL 2.0 AMD-APP (3444.0), 12367MB, 12367MB available, 2048 GFLOPS peak)
17:58:00 (5640): checkpoint interval: 0h15m00s00 (task 1146600 GFLOPS, 0h09m19s86 per packet)
17:58:00 (5640): wrapper: running dnetc521-win32-x86-opencl.exe (-ini dnetc.ini -runoffline -multiok=1) - attempt 1/10

dnetc v2.9112-521-CTR-16021318 for OpenCL on Win32 (WindowsNT 6.2).
Using email address (distributed.net ID) '<censored>                              '

[Apr 27 15:58:01 UTC] Automatic processor type detection did not
                      recognize the processor (tag: "gfx90c (AMD Radeon(TM) Graphics)")
[Apr 27 15:58:20 UTC] RC5-72: using core #2 (CL 2-pipe).
[Apr 27 15:58:20 UTC] RC5-72: Switched to random subspace 1343 (stored)
[Apr 27 15:58:20 UTC] RC5-72: Loaded 5D:EAE55B49:00000000:64*2^32
[Apr 27 15:58:20 UTC] RC5-72: 12 packets (755.00 stats units) remain in
                      in.r72
                      Projected ideal time to completion: 0.02:31:00.00
[Apr 27 15:58:20 UTC] RC5-72: 0 packets are in out.r72
[Apr 27 15:58:20 UTC] 1 cruncher has been started.
[Apr 27 16:07:13 UTC] RC5-72: Completed 5D:EAE55B49:00000000 (64.00 stats units)
                      0.00:08:52.60 - [516,096,999 keys/s]
(...)


After running the benchmark integrated in dnetc521-win32-x86-opencl.exe:
dnetc_r72_1715073438_13_823_0 run time 38 min 59 sec using core #1 set via the settings for ATI Steam:
<core_client_version>7.24.1</core_client_version>
<![CDATA[
<stderr_txt>

11:52:34 (10888): wrapper v1.5 build 20 for AMD/ATI OpenCL starting (BOINC Wrapper v7.13.26016)
11:52:34 (10888): device: OpenCL: AMD/ATI GPU 0: AMD Radeon(TM) Graphics (driver version 3444.0 (PAL,HSAIL), device version OpenCL 2.0 AMD-APP (3444.0), 12367MB, 12367MB available, 2048 GFLOPS peak)
11:52:34 (10888): checkpoint interval: 0h15m00s00 (task 1152200 GFLOPS, 0h09m22s59 per packet)
11:52:34 (10888): wrapper: running dnetc521-win32-x86-opencl.exe (-ini dnetc.ini -runoffline -multiok=1) - attempt 1/10

dnetc v2.9112-521-CTR-16021318 for OpenCL on Win32 (WindowsNT 6.2).
Using email address (distributed.net ID) '<censored>                              '

[May 07 09:52:35 UTC] RC5-72: using core #1 (CL 1-pipe).
[May 07 09:52:35 UTC] RC5-72: Switched to random subspace 1343 (stored)
[May 07 09:52:35 UTC] RC5-72: Loaded 5E:0D31F809:00000000:64*2^32
[May 07 09:52:35 UTC] RC5-72: 12 packets (759.00 stats units) remain in
                      in.r72
[May 07 09:52:35 UTC] RC5-72: 0 packets are in out.r72
[May 07 09:52:35 UTC] 1 cruncher has been started.
[May 07 09:55:35 UTC] RC5-72: Completed 5E:0D31F809:00000000 (64.00 stats units)
                      0.00:02:59.34 - [1,532,685,269 keys/s]
(...)
As you see, no automatic detection and using the selected core instantly.

To run the benchmark, suspend GPU processing in BOINC (not CPU if you run CPU tasks), open command line, navigate to your moowrap.net directory and execute
dnetc521-win32-x86-opencl.exe -bench


Try and report your results here, that's probably as close to OpenCL core selection as we can get here.
20) Message boards : Number crunching : Ignore Opencl and force CUDA version (Message 8597)
Posted 1 May 2024 by Link
Post:
Probably it's enough if you clean up all AMD drivers and eventually reset Moo!, unlikely that you need to reinstall Windows for that.


Next 20


 
Copyright © 2011-2025 Moo! Wrapper Project