It won't make any difference - at least it didn't for me. I removed all other GPU projects from my machine and the tasks still won't start. I then removed ALL other BOINC projects with only Moo remaining and still a no go.

Good luck with your attempts....

What worked for me in that situation is an app_info.xml file. I too had one pc that just would NOT run Moo tasks at all, every other one of my pc's was fine but that ONE PC just would not! I too am using AMD gpu's and it now works fine. The app_info.xml file goes in the Moo directory and therefore only affects Moo. Here is a copy of the one I use:

<app_info>
<app>
<name>dnetc</name>
<user_friendly_name>Distributed.net Client</user_friendly_name>
</app>
<file_info>
<name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc518-win32-x86-stream.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc-gpu-1.3.ini</name>
</file_info>
<file_info>
<name>job-ati14-1.00.xml</name>
</file_info>
<app_version>
<app_name>dnetc</app_name>
<version_num>102</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.050000</avg_ncpus>
<max_ncpus>0.895864</max_ncpus>
<plan_class>ati14</plan_class>
<flops>1157115231469.729200</flops>
<api_version>7.0.8</api_version>
<file_ref>
<file_name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc518-win32-x86-stream.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-gpu-1.3.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-ati14-1.00.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.000</count>
</coproc>
<gpu_ram>262144000.000000</gpu_ram>
</app_version>
</app_info>

IF you decide to try it MAKE SURE you copy and paste it into NOTEPAD in Windows as word processing programs add stuff and it won't run! The file should be placed in the directory c:/Program Data/Boinc/projects/moowrap.net and then Boinc should be stopped and then restarted. It should make Moo crunch one unit on EACH gpu and since that is DIFFERENT than when you last asked for units all of your current units might error out. But if they aren't running anyway what good are they. Near the bottom of the file is a line <gpu_ram....> this is TOTAL gpu ram in the machine, so adjust it as you need to.

I previously saw this file, but I am not using AMD GPUs. I have dual NVIDA GeForce GTX 550 Ti cards. Can I just replace the ATI/AMD references with CUDA or NVIDIA? I no longer have any other tasks that require the GPU besides 90+ Moo! Wrapper tasks due 9/22-9/25.

---

David - KC2WUF

I previously saw this file, but I am not using AMD GPUs. I have dual NVIDA GeForce GTX 550 Ti cards. Can I just replace the ATI/AMD references with CUDA or NVIDIA? I no longer have any other tasks that require the GPU besides 90+ Moo! Wrapper tasks due 9/22-9/25.

No I don't think it is a direct replacement, but yes sort of. In my file there are things like this:
<plan_class>ati14</plan_class>
<flops>1157115231469.729200</flops>
<app_name>dnetc</app_name>
<version_num>102</version_num>

and probably some other AMD specific things. Look around and you should see someone using both Nvidia cards and using the anonymous drivers and they should have one you could start out with, the top crunching users might be a good place to start.

I reviewed the Top 200 computers and the first one with multiple NVIDIA GPUs was running BOINC V6.12; while the second one was using BOINC V7.0.28, it had a single AMD GPU as well. All other computers with NVIDIA GPUs were single cards and therefore wouldn't have my problem.

Since I can run GPU tasks on the other BOINC projects, I'll check in every month or so and see if anyone has had success either through a configuration file, new version of the Moo! Wrapper app, or a new version of BOINC.

---

David - KC2WUF

I reviewed the Top 200 computers and the first one with multiple NVIDIA GPUs was running BOINC V6.12; while the second one was using BOINC V7.0.28, it had a single AMD GPU as well. All other computers with NVIDIA GPUs were single cards and therefore wouldn't have my problem.

Since I can run GPU tasks on the other BOINC projects, I'll check in every month or so and see if anyone has had success either through a configuration file, new version of the Moo! Wrapper app, or a new version of BOINC.

That sounds reasonable, good luck!

Just joined today and my XP machine with one usable gpu started processing right off the git go. My win 7 machine with two gpus refused to run any until I put in the first app info xml, here is the startup log after putting in the xml:

2/18/2013 5:54:45 PM | | log flags: file_xfer, sched_ops, task, coproc_debug, scrsave_debug, task_debug
2/18/2013 5:54:45 PM | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
2/18/2013 5:54:45 PM | | Data directory: C:\ProgramData\BOINC
2/18/2013 5:54:45 PM | | Running under account Darrell
2/18/2013 5:54:45 PM | | Processor: 2 AuthenticAMD AMD Athlon(tm) II X2 250 Processor [Family 16 Model 6 Stepping 3]
2/18/2013 5:54:45 PM | | Processor: 1.00 MB cache
2/18/2013 5:54:45 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
2/18/2013 5:54:45 PM | | OS: Microsoft Windows 7: Professional x64 Edition, Service Pack 1, (06.01.7601.00)
2/18/2013 5:54:45 PM | | Memory: 7.75 GB physical, 15.50 GB virtual
2/18/2013 5:54:45 PM | | Disk: 931.41 GB total, 844.43 GB free
2/18/2013 5:54:45 PM | | Local time is UTC -6 hours
2/18/2013 5:54:45 PM | | VirtualBox version: 4.2.4
2/18/2013 5:54:45 PM | | CAL: ATI GPU 0: ATI Radeon HD 5800 series (Cypress) (CAL version 1.4.1741, 1024MB, 991MB available, 4176 GFLOPS peak)
2/18/2013 5:54:45 PM | | CAL: ATI GPU 1: ATI Radeon HD 2300/2400/3200 (RV610) (CAL version 1.4.1741, 256MB, 224MB available, 56 GFLOPS peak)
2/18/2013 5:54:45 PM | | OpenCL: AMD/ATI GPU 0: ATI Radeon HD 5800 series (Cypress) (driver version CAL 1.4.1741 (VM), device version OpenCL 1.2 AMD-APP (938.2), 1024MB, 991MB available, 4176 GFLOPS peak)
2/18/2013 5:54:45 PM | | No NVIDIA library found
2/18/2013 5:54:45 PM | Moo! Wrapper | Found app_info.xml; using anonymous platform

After getting the tasks to run, I have gone back and put back the exclude gpu in the config file to restrict moo's use to gpu #1 as I want to use gpu #0 for those projects that run opencl. Really was hoping to stay away from using any app info files, but is apparently the only way to get your tasks to work on muligpu system.

Just joined today and my XP machine with one usable gpu started processing right off the git go. My win 7 machine with two gpus refused to run any until I put in the first app info xml, here is the startup log after putting in the xml:

2/18/2013 5:54:45 PM | | log flags: file_xfer, sched_ops, task, coproc_debug, scrsave_debug, task_debug
2/18/2013 5:54:45 PM | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
2/18/2013 5:54:45 PM | | Data directory: C:\ProgramData\BOINC
2/18/2013 5:54:45 PM | | Running under account Darrell
2/18/2013 5:54:45 PM | | Processor: 2 AuthenticAMD AMD Athlon(tm) II X2 250 Processor [Family 16 Model 6 Stepping 3]
2/18/2013 5:54:45 PM | | Processor: 1.00 MB cache
2/18/2013 5:54:45 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
2/18/2013 5:54:45 PM | | OS: Microsoft Windows 7: Professional x64 Edition, Service Pack 1, (06.01.7601.00)
2/18/2013 5:54:45 PM | | Memory: 7.75 GB physical, 15.50 GB virtual
2/18/2013 5:54:45 PM | | Disk: 931.41 GB total, 844.43 GB free
2/18/2013 5:54:45 PM | | Local time is UTC -6 hours
2/18/2013 5:54:45 PM | | VirtualBox version: 4.2.4
2/18/2013 5:54:45 PM | | CAL: ATI GPU 0: ATI Radeon HD 5800 series (Cypress) (CAL version 1.4.1741, 1024MB, 991MB available, 4176 GFLOPS peak)
2/18/2013 5:54:45 PM | | CAL: ATI GPU 1: ATI Radeon HD 2300/2400/3200 (RV610) (CAL version 1.4.1741, 256MB, 224MB available, 56 GFLOPS peak)
2/18/2013 5:54:45 PM | | OpenCL: AMD/ATI GPU 0: ATI Radeon HD 5800 series (Cypress) (driver version CAL 1.4.1741 (VM), device version OpenCL 1.2 AMD-APP (938.2), 1024MB, 991MB available, 4176 GFLOPS peak)
2/18/2013 5:54:45 PM | | No NVIDIA library found
2/18/2013 5:54:45 PM | Moo! Wrapper | Found app_info.xml; using anonymous platform

After getting the tasks to run, I have gone back and put back the exclude gpu in the config file to restrict moo's use to gpu #1 as I want to use gpu #0 for those projects that run opencl. Really was hoping to stay away from using any app info files, but is apparently the only way to get your tasks to work on muligpu system.

Not any more!!! You can now use an "app_config.xml" file instead of an an app_info file. Here is an example of one:
<app_config>
<app>
<name>moo</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

You can see by the line "<gpu_usage>0.5</gpu_usage>" that it is running 2 units at one. IF you want to run for instance 4 units at once you would put 0.25 instead of 0.5. The number you use is a percentage of 1, so running 3 units would 0.33.

This ONLY works for people running Boinc version 7.0.40 or above, which you are. It eliminates the need to keep changing the file as the different projects change their file names, as this file doesn't use them.

ALSO I don't remember if this one works OR if you have to change the moo to dnetc. Try it the way it is and if it doesn't work change the moo to dnetc. ALSO any current units you have could be lost, so be aware of that. They will just be sent to someone else so don't worry too much about them, but it is best to run the cache dry before making any changes. Oh and put the app_config file in the same place as the app_info file, but be sure to remove or rename the app_info file so Boinc doesn't find both.

Just joined today and my XP machine with one usable gpu started processing right off the git go.

One thing to be careful of is remember NOT to upgrade the XP machine too often for the AMD Driver. As you can see on this chart:
http://www.hal6000.com/seti/boinc_ati_gpu_cheat_sheet.htm

They stopped making drivers that support XP after version 12.1. Your XP pc is okay as it is still using version 11.5. Your Win7 pc is using at least version 12.6, they seem to have stopped upgrading the numbers after that, I am using version 13.1 on some pc's and it shows the SAME numbers!

Yes, I have tried 11.9 to 12.1, but amd made some sort of change to the cal routines that causes boinc to see no usable gpus. After 12.1 amd dropped the cal routines for XP completely in favor of open-cl. It's just strange that they keep the cal routines for win7. I will give the app config a try later on today, will probably wipe out the five tasks waiting to run, but on the integrated hd3000 in my win7 machine, the tasks are taking about 15-18 hours to complete and to wait for them all to complete will take days. Thanks for the info, Mikey.

Yes, I have tried 11.9 to 12.1, but amd made some sort of change to the cal routines that causes boinc to see no usable gpus. After 12.1 amd dropped the cal routines for XP completely in favor of open-cl. It's just strange that they keep the cal routines for win7. I will give the app config a try later on today, will probably wipe out the five tasks waiting to run, but on the integrated hd3000 in my win7 machine, the tasks are taking about 15-18 hours to complete and to wait for them all to complete will take days. Thanks for the info, Mikey.

Anytime, please come back and let us know how it works out for you.

Anytime, please come back and let us know how it works out for you.

The app_config.xml does work and the app name does have to be set to dnetc. Did not lose any tasks from changing from app info to app config, however there are two tasks that have gone missing from the que when I first put in the app info xml. Now it's a matter of using it with other projects to fine tune the system.

Anytime, please come back and let us know how it works out for you.

The app_config.xml does work and the app name does have to be set to dnetc. Did not lose any tasks from changing from app info to app config, however there are two tasks that have gone missing from the que when I first put in the app info xml. Now it's a matter of using it with other projects to fine tune the system.

Now THAT is a wonderful idea and what most of us gpu crunchers have been doing for a awhile now!! Welcome to the wonderful world of fiddling with your pc!!!

Not any more!!! You can now use an "app_config.xml" file instead of an an app_info file. Here is an example of one:
<app_config>
<app>
<name>moo</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

You can see by the line "<gpu_usage>0.5</gpu_usage>" that it is running 2 units at one. IF you want to run for instance 4 units at once you would put 0.25 instead of 0.5. The number you use is a percentage of 1, so running 3 units would 0.33.

This ONLY works for people running Boinc version 7.0.40 or above, which you are. It eliminates the need to keep changing the file as the different projects change their file names, as this file doesn't use them.

ALSO I don't remember if this one works OR if you have to change the moo to dnetc. Try it the way it is and if it doesn't work change the moo to dnetc. ALSO any current units you have could be lost, so be aware of that. They will just be sent to someone else so don't worry too much about them, but it is best to run the cache dry before making any changes. Oh and put the app_config file in the same place as the app_info file, but be sure to remove or rename the app_info file so Boinc doesn't find both.

The app_config.xml does work and the app name does have to be set to dnetc.

Just wanted to say I tried this maybe a week ago and since then my computer has returned to chewing through WUs via my GPUs like crazy, as it did before with BOINC 6. Thank you so much for posting this solution! It's great to have my machine being significantly productive again!

Just wanted to say I tried this maybe a week ago and since then my computer has returned to chewing through WUs via my GPUs like crazy, as it did before with BOINC 6. Thank you so much for posting this solution! It's great to have my machine being significantly productive again!

No problem, I am glad it helped and you are now crunching like crazy!