We're just guessing at the requirements for this version, so point me at any hosts that are repeatedly failing with this app version.

---

my host already failed.
Look for E-mail. it got absolutely wrong binary under plan class ati_opencl_sah.

I've released 6.99 which should have the correct binary. Sorry about that.

---

I've released 6.99 which should have the correct binary. Sorry about that.

I have one ati_opencl_100 running at the moment, should be done in 30 minutes. I have suspended all other ati_opencl_100, so when that one is finished, my first ati_opencl_sah should start. I received 47 ati_opencl_sah tasks

Did I also get the wrong binaries? I got:

setiathome_6.98_windows_intelx86__opencl_ati_sah.exe
setiathome_6.98_windows_intelx86__opencl_ati_sah.pdb
MultiBeam_Kernels_r1643.cl

If those are wrong, what should I do with the tasks I have?

Yes, now binary is correct. Task running.

I've released 6.99 which should have the correct binary. Sorry about that.

I have one ati_opencl_100 running at the moment, should be done in 30 minutes. I have suspended all other ati_opencl_100, so when that one is finished, my first ati_opencl_sah should start. I received 47 ati_opencl_sah tasks

Did I also get the wrong binaries? I got:

setiathome_6.98_windows_intelx86__opencl_ati_sah.exe
setiathome_6.98_windows_intelx86__opencl_ati_sah.pdb
MultiBeam_Kernels_r1643.cl

If those are wrong, what should I do with the tasks I have?

You should do project reset for SETI beta.
[And for now suspend all ATi 6.98 work until you will finish other beta work]

I've released 6.99 which should have the correct binary. Sorry about that.

I have one ati_opencl_100 running at the moment, should be done in 30 minutes. I have suspended all other ati_opencl_100, so when that one is finished, my first ati_opencl_sah should start. I received 47 ati_opencl_sah tasks

Did I also get the wrong binaries? I got:

setiathome_6.98_windows_intelx86__opencl_ati_sah.exe
setiathome_6.98_windows_intelx86__opencl_ati_sah.pdb
MultiBeam_Kernels_r1643.cl

If those are wrong, what should I do with the tasks I have?

You should do project reset for SETI beta.

So, I did get the wrong binaries? Is that what you say?

Yes, you have 6.98, you need 6.99

Claggy

Yes, you have 6.98, you need 6.99

Claggy

How sad. Ok, I will reset.

Yes, you have 6.98, you need 6.99

Claggy

How sad. Ok, I will reset.

Not your fault anyway.
But the light side - when you will get 6.99 it should really work :)

Yes, you have 6.98, you need 6.99

Claggy

How sad. Ok, I will reset.

Not your fault anyway.
But the light side - when you will get 6.99 it should really work :)

Well, I got the 6.99 binaries, but the tasks were resent and are still named 6.98. But maybe that's what to expect.

Yes, you have 6.98, you need 6.99

Claggy

How sad. Ok, I will reset.

Not your fault anyway.
But the light side - when you will get 6.99 it should really work :)

Well, I got the 6.99 binaries, but the tasks were resent and are still named 6.98. But maybe that's what to expect.

What happens if you restart Boinc? I've seen funny after effects after having tasks resent before,

Claggy

Yes, you have 6.98, you need 6.99

Claggy

How sad. Ok, I will reset.

Not your fault anyway.
But the light side - when you will get 6.99 it should really work :)

Well, I got the 6.99 binaries, but the tasks were resent and are still named 6.98. But maybe that's what to expect.

What happens if you restart Boinc? I've seen funny after effects after having tasks resent before,

Claggy

Hmm, next request renamed them to 6.99. Funny effects indeed :-)

Any info on GPU support for OSX? Any updates as to support since both CUDA and Open CL are supported.

Well, my first result went inconclusive, even though the visible results in stderr, was the same as my wingman.

Spike count: 10
Autocorr count: 0
Pulse count: 3
Triplet count: 0
Gaussian count: 0

There has to be some difference though between our results.

wuid=4153634

Edit: Second one validated fine though:

wuid=4153648

First task is running...

Well, my first result went inconclusive, even though the visible results in stderr, was the same as my wingman.

Spike count: 10
Autocorr count: 0
Pulse count: 3
Triplet count: 0
Gaussian count: 0

There has to be some difference though between our results.

wuid=4153634

Edit: Second one validated fine though:

wuid=4153648

Despite my requests CUDA app still has no found signal printing in stderr so it's not possible to say what was wrong w/o offline task redone.
Pity.

We're just guessing at the requirements for this version, so point me at any hosts that are repeatedly failing with this app version.

The app is fully OpenCL 1.0 compatible.

I tested on HD 4770 (RV 770) HD 4850 with driver 12.1.

Work group size 256 required.

I suggest driver version 12.1. and newer.

Running Windows XP driver 12.1 is the last driver with OpenCL support.

Mike

---

With each crime and every kindness we birth our future.

We're just guessing at the requirements for this version, so point me at any hosts that are repeatedly failing with this app version.

The app is fully OpenCL 1.0 compatible.

I tested on HD 4770 (RV 770) HD 4850 with driver 12.1.

Work group size 256 required.

I suggest driver version 12.1. and newer.

Running Windows XP driver 12.1 is the last driver with OpenCL support.

Mike

And I'm running my HD4850 on Vista with driver version 12.4, which also is an OpenCL 1.0 driver on the 4850. Apparently HD4850 doesn't support other than OpenCL 1.0, so no matter which newer driver you install, you will not get anything more than OpenCL 1.0 on that card.

But you knew that already Mike, I'm just a bit chatty :-)

Any info on GPU support for OSX? Any updates as to support since both CUDA and Open CL are supported.

Current situation with porting ATI OpenCL windows apps to Linux and OSX : Working on it, but at the moment too many wrong signals for a beta version.

---

_\|/_
U r s