I've just noticed that BOINC (v36.6.36) run MW's WU at the lowest priority on my i7 965 system. I've Cosmology and Einstein attached on this machine. BOINC always give priority to the two other projects and only occasionally start MW's WUs. I've set the resource for MW to be 50% no significant change. I sometime have to suspend one of the other project to at least get BOINC to look at MW. Is this potentially a problem with v6.6.36?

It's just a problem with BOINC and the debt system it uses. Try increasing the MW resource share - or down grade to a non 6.6.x version of BOINC. I'm using 6.4.5 with MW at 50% and BOINC just keeps enough work cached for it but at least it is always trying to crunch MW. Some others have downgraded all the wasy to 5.10.45.

I've just noticed that BOINC (v36.6.36) run MW's WU at the lowest priority on my i7 965 system. I've Cosmology and Einstein attached on this machine. BOINC always give priority to the two other projects and only occasionally start MW's WUs. I've set the resource for MW to be 50% no significant change. I sometime have to suspend one of the other project to at least get BOINC to look at MW. Is this potentially a problem with v6.6.36?

It's just a problem with BOINC and the debt system it uses. Try increasing the MW resource share - or down grade to a non 6.6.x version of BOINC. I'm using 6.4.5 with MW at 50% and BOINC just keeps enough work cached for it but at least it is always trying to crunch MW. Some others have downgraded all the wasy to 5.10.45.

_3s WUs still get compute error. When BOINC client start to crunch a _3s WU, the GPU app stop crunching any other WU indefinitely (GPU time move but progress remain at 0%). I'll have to suspend all _3s in the list, close BOINC and restart to get GPU app to work on _2s WUs.

Also, after installation of 019f, my quad system will run only 2 other CPU WUs plus 2 GPU WUs or 4 CPU WUs and no GPU task. I'm using BOINC 6.6.36 on W7 and catalyst v9.5. This catalyst package install atical...64.dll files on my system and I make a copy and rename them to amdcal...64.dll and place them back on system32 folder, will this be sufficient?

After having a look to your host list (the Win7 hosts), the only compute errors showing up on your computers are caused by using the old 0.19e version. The Core2Quad still runs 0.19e. After you updated the Core2Duo to 0.19f, all appears to be okay. And if you specify the options "n2 w1.1 f20" on that C2D, you don't have to wonder why 2 WUs run. But that is competely okay as running more won't help the performance.

And why the BOINC-Client 6.6.36 is not starting the GPU tasks in parallel to CPU tasks, I simply don't now. You can play around with the avg_ncpu value in the app_info.xml or raise the number of processed WUs in the c_config.xml. I'm using the client version 5.5.45, 6.2.19 and 6.6.21 and it runs quite okay there.

I can tell I am taking this all too seriously now and I refuse to buy any more of these Guppie cards. Dam things need PCs which clutter up my garage. I have a lizard to put on ice. Laters gators.

This script works and gives you choices as to time between requests and number of requests .... works on XP .....

--------------------------------------------------------------------------
@echo off
Echo.
echo.
Echo Request Work From Milkyway Sever
echo.
Echo.
echo.
set /p xx= Server Request Work Interval - Enter Seconds :

cls
Echo.
echo.
echo Server Request Interval %xx% seconds.
Echo.
echo.
set /p zz= Enter the number of requests :


set /a Request_limit = %zz%
set /a seconds = %xx%
set /a looper = 0
set /a timecount = %zz%*%xx%

set /a h = %timecount%/3600
set /a m = (%timecount%-(%h%*3600))/60
set /a s = (%timecount%-(%h%*3600)-(%M%*60))


cls
echo.
echo.
echo. Milkyway - CPU ONLY
echo.
echo Sending %zz% requests - One Every %xx% seconds.

ping localhost -n 3 > NULL

goto main

:main


IF %looper%==%Request_limit% goto finish

goto app

:app

C:\PROGRA~1\BOINC\boinccmd.exe --passwd 11110 --project http://milkyway.cs.rpi.edu/milkyway update

ping localhost -n %xx% > NULL

goto nest

:Nest
set /a countdown = %timecount%-(%xx%*%looper%)
set /a h1 = %countdown%/3600
set /a m1 = (%countdown%-(%h1%*3600))/60
set /a s1 = (%countdown%-(%h1%*3600)-(%M1%*60))


SET /A looper=%looper%+1


cls
echo.
echo.
echo. Milkyway - CPU ONLY
echo.
echo Sending %zz% requests - Once Every %xx% seconds.
echo.
echo.
Echo %looper% of %Request_limit% Requests
echo.
echo.
echo Total Runtime of Batch File %h%:%m%:%s%
echo.
echo Time remaining %h1%:%m1%:%s1%

goto main

:finish

cls
echo.
echo.
echo.
echo.
Echo Milkyway Request Count total is %looper% of %Request_limit% - Completed Sequence
echo.
Echo Dos Windows Closing - Have a nice day

ping localhost -n 10 > NULL
exit
------------------------------------------------------------------------

Ah yeah. I mis-remembered this ATi webpage.