AK_v8b_win_SSSE3x.exe has just gotten to bodgy and calculates its score as 1.293091 which is close though I'd rather the first difference were in the 6th significant digit than the 5th.
If you are too, I'm content to call this one "remaining chirp annoyances, with added yet to be divined nVidia Gaussfit implementation vagaries"
...Am I finding what you guys are looking for or wasting your time? If these don't help let me know more of what I should look for. ...
Got the same count as this 460 running x38g but still went to inconclusive.. http://setiathome.berkeley.edu/workunit.php?wuid=771572553
Hi Jason,took x39e now for seti main on my GT540M (1GB), but get no work till now.As soon as I have work, i will post again.heinz
...Only issue every time when a seti wu will start the machines clock down again on my GT540M.I run it together with primegrid....
Quote from: _heinz on 01 Jul 2011, 03:06:13 am...Only issue every time when a seti wu will start the machines clock down again on my GT540M.I run it together with primegrid....OK heinz, I think that no other project has the application fixes for newer Cuda drivers yet. If you suspend primegrid for a while & verfiy you see no more downclocks, then I'd suggest if you want to run that then either go back to a Cuda 3.2 driver (until primegrid fixes their application) or encourage them to apply the boincapi fixes necessary in an application update.Jason
from where I can download the boincapi fixes ? If I get them, I can compile a new pg version, to see if that fixes the issue.thanks
May want to see this one too. http://setiathome.berkeley.edu/workunit.php?wuid=771931438 First three to run it got -12s I completed and a 6.03 completed with the same count I had. Still got sent out to another.