So triple 4870's are out of the question for now I see :)
I have an linux box with a 3870 and Ubuntu 64bit with Cat 9.1 set up when you get around to a linux app.

So triple 4870's are out of the question for now I see :)
I have an linux box with a 3870 and Ubuntu 64bit with Cat 9.1 set up when you get around to a linux app.

But the good thing is that a single HD4870 has almost the speed of a triple GTX280 system here at MW :D
I just imagine what quad HD4870X2 system would be capable of (if one finds an appropriate power supply). That wouldn't be pretty anymore ;)

Let's hope nvidia improves their double precision performance for their next generation, ATI won't get slower.

I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future!

Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point.

---

I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future!

Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point.

Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again.

EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how?

---

I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future!

Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point.

Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again.

EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how?

Could you post the content of the stderr.txt (shown under task details) please? I have not found it in your host list (already purged?).

If "No compatible GPU found!" is the only error there, the app does not find the CAL (Compute Abstraction Layer) libraries, which are installed as part of the driver since 8.12. If the libs would be there and one has an unsupported card, it would tell you something about double precision not supported.
The error you are seeing hints at an incorrectly installed or too old driver. The alternative would be a missing brook.dll, but I guess you checked that already.

Or are you trying to run it when accessing the machine via a remote desktop connection? That is also not working, because Win uses some kind of a virtual framebuffer driver for that (you don't have the Catalyst as display driver in a remote session). You could use VNC and check "disable mirror driver".

Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again.

EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how?

Could you post the content of the stderr.txt (shown under task details) please? I have not found it in your host list (already purged?).

If "No compatible GPU found!" is the only error there, the app does not find the CAL (Compute Abstraction Layer) libraries, which are installed as part of the driver since 8.12. If the libs would be there and one has an unsupported card, it would tell you something about double precision not supported.
The error you are seeing hints at an incorrectly installed or too old driver. The alternative would be a missing brook.dll, but I guess you checked that already.

Or are you trying to run it when accessing the machine via a remote desktop connection? That is also not working, because Win uses some kind of a virtual framebuffer driver for that (you don't have the Catalyst as display driver in a remote session). You could use VNC and check "disable mirror driver".

I'll have to run another WU or two to get another stderr, but other than the XML formatting and the error code, that's all that was there.

Like I said, it was a fresh install of Cat 9.1 straight off ATI's website, and the only thing I deselected during installation were the Catalyst Registration and the WoW trial. Is there any way I can find out manually if I have the CAL libraries installed?

---

Is there any way I can find out manually if I have the CAL libraries installed?

Look into the Windows\system32 folder. There should be the files "amdcalcl64.dll", "amdcaldd64.dll" and "amdcalrt64.dll".

Is there any way I can find out manually if I have the CAL libraries installed?

Look into the Windows\system32 folder. There should be the files "amdcalcl64.dll", "amdcaldd64.dll" and "amdcalrt64.dll".

Well, that explains some stuff... They don't exist in the Win7 installation, but they do in the Vista installation. So it does seem Catalyst for Win7 doesn't have Stream support yet. Still doesn't explain why Vista fails.

---

I've been using the gpu app for almost 2 weeks now and just wanted to give a little feedback. I've rolled back my driver to the 8.12 version from 9.1 yesterday. I was running 8.12 fine but wanted to get the latest driver installed when it came out. After the upgrade i had a lot of pc responsiveness issues and a bsod every few days. Since then my computer has ran much smoother. I'm not sure why the newer driver just didn't seem to perform as well as 8.12. I should mention i'm running gpu version 0.17.

I have the next alpha version ready, still limited to Win64 and running on ATI HD38x0 and HD48x0 cards with Catalyst driver 8.12 or 9.1. But this time it should be able to handle again all WUs flying around, also those with more than one stream. They should take about 50% longer (there is one stream more to calculate). I have squeezed the code a bit, it should need now about 0.1 seconds less for the single stream WUs ;) But there is not much left what one could get out of it performance wise. Don't expect major speed gains for the future!

Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point.

Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again.

EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how?

Hi,
Same problem for me with Vista64 + Catalyst 9.1

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
Fonction incorrecte. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
No compatible GPU found!

</stderr_txt>
]]>

Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point.

Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again.

EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how?

Hi,
Same problem for me with Vista64 + Catalyst 9.1

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
Fonction incorrecte. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
No compatible GPU found!

</stderr_txt>
]]>

The screenshot and two videos posted in this thread are done on Vista64. There are quite some people where it runs. So please check again the points already mentioned here in the forum:
- driver correctly installed (three amdcal??64.dll files present in Windows/system32 folder)
- you are not accessing the machine over a remote desktop connection (use VNC and disable mirror driver)
- the card should be active (monitor connected to it)

Works fine on my E7200 2.53 GHz & HD4850. I get about 300 credits per hour, with four workunits at the same time (Core2Duo).

Works fine on my E7200 2.53 GHz & HD4850. I get about 300 credits per hour, with four workunits at the same time (Core2Duo).

Thanks for the feedback on the Vista64 issue.
The credits you get are less than a Quadore with an optimized CPU app gets (432credits/hour). Furthrmore you can't let it run for 24h a day. After about 6 hours you have used up your WU limit of 1000 WUs per day and core and that will earn you less than 2000 credits a day.
So you should definitely run another project at the same time. The MW GPU app uses only one core no matter how many WUs run concurrently. The work done for MW won't change, if you run it only with 50% resource share (2 WUs at the same time). Just try it!

Works fine on my E7200 2.53 GHz & HD4850. I get about 300 credits per hour, with four workunits at the same time (Core2Duo).

Thanks for the feedback on the Vista64 issue.
The credits you get are less than a Quadore with an optimized CPU app gets (432credits/hour). Furthrmore you can't let it run for 24h a day. After about 6 hours you have used up your WU limit of 1000 WUs per day and core and that will earn you less than 2000 credits a day.
So you should definitely run another project at the same time. The MW GPU app uses only one core no matter how many WUs run concurrently. The work done for MW won't change, if you run it only with 50% resource share (2 WUs at the same time). Just try it!

Thank you very much for this information ^^

I tried a few hours ago to (re)join my main project (World Community Grid), but I stopped when I saw "only" two MW workunits instead of 4 before ^^ But the 1000 Wu limit per day change everything ^^

Question : if the GPU app uses only one core, is it possible to use the other core for a CPU-optimized app ? Or use all the cores with the GPU ?

---

Star Wars BOINC Team

Just a quick note that it still crashes on my machine. I'm going to try and clear out at least the Milkyway tasks I have left, then see if it works on my Vista x64 installation. It's possible ATI's 8.12 drivers for Win7 don't have Stream support yet, which is my suspicion at this point.

Well, Vista x64 gives a better error: "No compatible GPU found!" I know I have a Radeon HD4870 1GB though, so I'm not sure what's causing this. Right now, I'm running with Cat 8.12. I'll update to Cat 9.1 and try again.

EDIT: Same result with Cat 9.1. Are you checking for a compatible GPU, and if so, how?

Hi,
Same problem for me with Vista64 + Catalyst 9.1

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
Fonction incorrecte. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
No compatible GPU found!

</stderr_txt>
]]>

The screenshot and two videos posted in this thread are done on Vista64. There are quite some people where it runs. So please check again the points already mentioned here in the forum:
- driver correctly installed (three amdcal??64.dll files present in Windows/system32 folder)
- you are not accessing the machine over a remote desktop connection (use VNC and disable mirror driver)
- the card should be active (monitor connected to it)

- driver installed yesterday, the 3 files are in System32 (amdcalcl64.dll ,amdcaldd64.dll and amdcalrt64.dll)
- i didn't use any remote protocol, it's my main PC
- the card was active, there is only one.

How have you guys installed the BOINC client?
In the protected mode under Vista the application may not have the necessary access rights. CUDA apps also fail when tried to run in such a scenario. On XP64 and Server2003 it should also run in the protected mode.

If also the people where it runs could report on this?

How have you guys installed the BOINC client?
In the protected mode under Vista the application may not have the necessary access rights. CUDA apps also fail when tried to run in such a scenario. On XP64 and Server2003 it should also run in the protected mode.

If also the people where it runs could report on this?

Default options for me on Vista64, so I think I used the protected mode. It worked very fine until the 2000 WU limit. I earned 1939 credits in 6 hours. Only three WU went wrong during the initial tests, but it was my fault ^^

How have you guys installed the BOINC client?
In the protected mode under Vista the application may not have the necessary access rights. CUDA apps also fail when tried to run in such a scenario. On XP64 and Server2003 it should also run in the protected mode.

If also the people where it runs could report on this?

Hmm, that makes sense... I think I did a service install, which would be that. Unfortunately, I won't have access to the machine for at least a week, so I can't test what the other install would do. I can try it after I have access again though.

---

How have you guys installed the BOINC client?
In the protected mode under Vista the application may not have the necessary access rights. CUDA apps also fail when tried to run in such a scenario. On XP64 and Server2003 it should also run in the protected mode.

If also the people where it runs could report on this?

I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support

I reinstalled Boinc this morning with default value, and now all seems to work, some freeze on the screen but some tuning needed, i suppose. Thanks for your support

Isn't the default the protected mode?

The experience of some users indicate the lags or short (one or two seconds) freezes are caused by either GPU-Z or the Catalyst Control Center. If these tools are closed it normalizes within a minute or so.