By the way, I have a Polish name, but neither I, my parents nor my grandparents speak/spoke it.

temporarily down for maintenance ?

The abacus is the key to getting work. Unfortunately it is only a single precision abacus.

Can anyone tell me how i can see if my card is being found by mw or boinc
I have 2 x 4770 ati cards but they are only be able to install with cat 9.4 or 9.5

<core_client_version>6.4.6</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home ATI GPU application version 0.19e by Gipsel
CPU: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (4 cores/threads) 2.39898 GHz (549ms)

CAL Runtime: 1.3.145
Found 1 CAL device

Device 0: ATI Radeon HD 3800 (RV670) 512 MB local RAM (remote 28 MB cached + 512 MB uncached)
GPU core clock: 669 MHz, memory clock: 829 MHz
320 shader units organized in 4 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

1 WUs already running on GPU 0
Starting WU on GPU 0

main integral, 160 iterations
predicted runtime per iteration is 408 ms (33.3333 ms are allowed), dividing each iteration in 13 parts
borders of the domains at 0 123 246 369 492 615 738 861 984 1107 1230 1353 1476 1600
Calculated about 3.70012e+012 floatingpoint ops on GPU, 6.34181e+007 on FPU. Approximate GPU time 85.2656 seconds.

cut number 0, 40 iterations
predicted runtime per iteration is 51 ms (33.3333 ms are allowed), dividing each iteration in 2 parts
borders of the domains at 0 200 400
Calculated about 1.15629e+011 floatingpoint ops on GPU, 5.38792e+006 on FPU. Approximate GPU time 2.64063 seconds.
Calculated about 2.48101e+009 floatingpoint ops on FPU (stars).

WU completed.
CPU time: 15.4375 seconds,  GPU time: 87.9063 seconds,  wall clock time: 286.817 seconds,  CPU frequency: 2.40012 GHz

</stderr_txt>
]]>

;).

priz-by-low

Why would he bother with it at all?
It only means that much more science is getting done that much faster.

It appears that the mystery packets are coming in "new not syn", which is said most likely to be caused by a broken TCP implementation. They are all part of the exchange with the server but for some reason come in with no sync bit. I doesn't seem to cause any stutters in the overall transaction, I can upload, report, and if there's work available, download it. I read a couple articles that claimed that MS IIS strayed from accepted TCP protocols and use the 'new not' syn' scenario as some sort of speed up mechanism for it's servers.

But now it's Friday evening, the Cubs are on, as is my low alcohol light. So I officially make this a "tomorrow problem". :)

I'll be done with my part hopefully tonight or tomorrow. Then it's up to Travis to get the apps up. I'm not sure if he's done with them yet but hopefully they're ready for alpha testing.