As per other users, I'm also a very happy user of the 0.38 Installer. I'm only using it as it came, 'out of the tin', but it did what I was a little wary of doing....namely, installing the relevant applications in the right place. The installation was simple and painless and done at the same time as installing the latest version of BOINC. At last, the HD4890 (one of the 1 GHz core capable RV790 GPUs) in my main PC can do some useful work, even if its full potential is probably not being realised. I've not even tried to tweak the ATI GPU applications, as it is working very well as it is - any speed increase over the Lunatics CPU applications I was already using, is very welcome! From me, a very big thumbs-up and an even bigger 'thanks guys' to The Lunatics team and all the testers, particularly, Raistmer, who has done a brilliant job, in spite of Open CL!

---

Don't take life too seriously, as you'll never come out of it alive!

I had not had any problems using .37 with my radeon 6970. All was working just went ahead and upgraded to .38 last night came down this morning and has the BSOD rebooted came back and it was locked up again. I did not mess with the config file or anything just install and go with the new ati options. Any ideas?

I had not had any problems using .37 with my radeon 6970. All was working just went ahead and upgraded to .38 last night came down this morning and has the BSOD rebooted came back and it was locked up again. I did not mess with the config file or anything just install and go with the new ati options. Any ideas?

Did you check the temps of the GPU ?

Which drivers are you running?
Did you upgrade drivers?
If so which one was used before ?

Do you have knowledge with appinfo.xml ?

I guess you had driver restarts so we could start changing period_iterations first.

---

With each crime and every kindness we birth our future.

I had not had any problems using .37 with my radeon 6970. All was working just went ahead and upgraded to .38 last night came down this morning and has the BSOD rebooted came back and it was locked up again. I did not mess with the config file or anything just install and go with the new ati options. Any ideas?

Did you check the temps of the GPU ?

Which drivers are you running?
Did you upgrade drivers?
If so which one was used before ?

Do you have knowledge with appinfo.xml ?

I guess you had driver restarts so we could start changing period_iterations first.

IIRC, LI0.37 hadn't ATI/AMD GPU apps included.
The ATI/AMD GPU apps are now new in LI0.38 .

So before your GPU hadn't calculated WUs.
So it's normal that you hadn't probs with your HD6970 and with LI0.37 . ;-)

In the 'Lunatics ReadMe' file is an explanation how to edit the app_info.xml <cmdline> entries:

(...)
Tuning cmd line parameters:
For AP: If you get lags or worse driver restarts, decrease unroll. If you run
stable you can try to increase it. ffa_block should be a multiple of ffa_block_fetch.
Start low e.g. -ffa_block 4096 -ffa_block_fetch 2048 and try increasing if it runs
fine. Sticking to the power of 2 line at first can help.
The will be a system specific best combination - too low slows you down, too high
slows you down as well.
Remember AP runtimes depend on blanking % so only compare runtimes on similar
blanking %.
For MB: other way round - if you experience lag or driver restarts increase
-period_iteration_num
(...)

- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

I had not had any problems using .37 with my radeon 6970. All was working just went ahead and upgraded to .38 last night came down this morning and has the BSOD rebooted came back and it was locked up again. I did not mess with the config file or anything just install and go with the new ati options. Any ideas?

Did you check the temps of the GPU ?

Which drivers are you running?
Did you upgrade drivers?
If so which one was used before ?

Do you have knowledge with appinfo.xml ?

I guess you had driver restarts so we could start changing period_iterations first.

IIRC, LI0.37 hadn't ATI/AMD GPU apps included.
The ATI/AMD GPU apps are now new in LI0.38 .

So before your GPU hadn't calculated WUs.
So it's normal that you hadn't probs with your HD6970 and with LI0.37 . ;-)

In the 'Lunatics ReadMe' file is an explanation how to edit the app_info.xml <cmdline> entries:

(...)
Tuning cmd line parameters:
For AP: If you get lags or worse driver restarts, decrease unroll. If you run
stable you can try to increase it. ffa_block should be a multiple of ffa_block_fetch.
Start low e.g. -ffa_block 4096 -ffa_block_fetch 2048 and try increasing if it runs
fine. Sticking to the power of 2 line at first can help.
The will be a system specific best combination - too low slows you down, too high
slows you down as well.
Remember AP runtimes depend on blanking % so only compare runtimes on similar
blanking %.
For MB: other way round - if you experience lag or driver restarts increase
-period_iteration_num
(...)

- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

I think i figured out the problem. I had left my "Trading Paints" application for my iRacing running. It seems to reek havoc on the GPU when it tries to minmize the screen saver to show the upadates. It kinda ends up with the same result as the Freeze during a youtube video. I apreciate the help.

With a non-FERMI-equipped machine & 0.38g installed, the newly-downloaded CUDA units are showing in the cache as CUDA_FERMI, whereas understandably they didn't before. Is this likely to lead to errors once the card comes across them or is it nothing to worry about?

With a non-FERMI-equipped machine & 0.38g installed, the newly-downloaded CUDA units are showing in the cache as CUDA_FERMI, whereas understandably they dind't before. Is this likely to lead to errors once the card comes across them or is it nothing to worry about?

It's nothing to worry about, there's extra enties in the app_info to cover multiple different configurations, so work isn't lost,

Claggy

With a non-FERMI-equipped machine & 0.38g installed, the newly-downloaded CUDA units are showing in the cache as CUDA_FERMI, whereas understandably they dind't before. Is this likely to lead to errors once the card comes across them or is it nothing to worry about?

It's nothing to worry about, there's extra enties in the app_info to cover multiple different configurations, so work isn't lost,

Claggy

To add to Claggy's reply just a little. The 6.10 (cuda- fermi) app is listed first in the app_info. The work is all the same so it just picks the first name it comes to. It is running the work you already had as whatever version you had asked for when you got them. If those other versions were not included in the app_info you would have lost all that earlier work. All the work from now on will be marked as 6.10.

---

PROUD MEMBER OF Team Starfire World BOINC

THX for the new apps,

CPU-apps work fine, but all my ati-apps fail immediate.

Stderr output

<core_client_version>6.12.33</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>

Edit: I've installed the version for HD5xxx cards

does not say much, MW and Collatz run both fine. Any ideas?

---

After completing about 5500 tasks, I got one down-clock after the folowing task:

http://setiathome.berkeley.edu/result.php?resultid=1964766177

Had to re-boot to re-apply the overclock.

Only other observation is that my DCF has stayed in the 1.2-1.3 range since using the 0.38 binaries.

---

THX for the new apps,

CPU-apps work fine, but all my ati-apps fail immediate.

Stderr output

<core_client_version>6.12.33</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>

Edit: I've installed the version for HD5xxx cards

does not say much, MW and Collatz run both fine. Any ideas?

The error code doesn´t say much.

"The application failed to initialize properly"

I´d suggest a clean install of the drivers.

---

With each crime and every kindness we birth our future.

I am crunching for quiet some time but just on a low level. I am not very much into this stuff.
I am still running an old version of Seti Enhanced from Crunch3r on a 32bit System with NVIDIA Graphic card but do not have a GPU.
As I had to modify the app_info, would it be possible for me to switch to lunatics by simply running the 'Windows Installer v0.38 32 bit'? Or should I select an older version?

The old Crunch3r app did not run Astropule tasks. Is Astropuls included when I use the installer?

---

Sure, you can use the installer but in your task list i see you already have a lunatics app installed.

I´d suggest to run GPUz to see what extensions your CPU supports.

Then run installer to choose wich apps you want to install.
Second page is useless for you since you have no usable GPU installed.

Mike

---

With each crime and every kindness we birth our future.

I am crunching for quiet some time but just on a low level. I am not very much into this stuff.
I am still running an old version of Seti Enhanced from Crunch3r on a 32bit System with NVIDIA Graphic card but do not have a GPU.
As I had to modify the app_info, would it be possible for me to switch to lunatics by simply running the 'Windows Installer v0.38 32 bit'? Or should I select an older version?

The old Crunch3r app did not run Astropule tasks. Is Astropuls included when I use the installer?

The 0.38 installer has Multibeam apps for CPU, Nvidia Cuda, and ATI OpenCL, and Astropulse apps for CPU, ATI OpenCL (for HD4*** and later) and ATI Brook+ (For HD3*** and earlier)

Claggy

And as we have noticed if you are running an onboard gpu its most likely a rebranded lesser GPU(ie 4250 is really a 3XXX) so ask for help if you attempt to install for one of those

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

Thanks to everydody.
I will check it out.
If it works it will maybe give me a little bit tailwind or at least a slight breeze.

---

Thanks to everydody.
I will check it out.
If it works it will maybe give me a little bit tailwind or at least a slight breeze.

You need to check first what setiathome_enhanced version number is being displayed in BOINC Manager. With an application (and hence an app_info.xml file) as old as that, it's possible that your cached tasks are flagged as something like v5.28

The new installer will preserve any cached tasks branded v6.03, but will discard any other brandings (for CPU work). If BOINC Manager shows you anything except 6.03, set 'No new tasks' and run down your cache before upgrading.

You need to check first what setiathome_enhanced version number is being displayed in BOINC Manager. With an application (and hence an app_info.xml file) as old as that, it's possible that your cached tasks are flagged as something like v5.28

The new installer will preserve any cached tasks branded v6.03, but will discard any other brandings (for CPU work). If BOINC Manager shows you anything except 6.03, set 'No new tasks' and run down your cache before upgrading.

Richard,
Thanks for that. You are right. They are branded v5.28
I already have blocked new work. It will take me some time to run dry.
Do you think the update will improve my speed (even a little bit)with a Core 2 Duo CPU E8400@3.00GHz and no GPU?

---

You need to check first what setiathome_enhanced version number is being displayed in BOINC Manager. With an application (and hence an app_info.xml file) as old as that, it's possible that your cached tasks are flagged as something like v5.28

The new installer will preserve any cached tasks branded v6.03, but will discard any other brandings (for CPU work). If BOINC Manager shows you anything except 6.03, set 'No new tasks' and run down your cache before upgrading.

Richard,
Thanks for that. You are right. They are branded v5.28
I already have blocked new work. It will take me some time to run dry.
Do you think the update will improve my speed (even a little bit)with a Core 2 Duo CPU E8400@3.00GHz and no GPU?

Actually, there won't be much difference (if any) between your current built 41 and the build 76 for CPU work in the installer. You're probably as well off just leaving things alone this time round.

BUT, we're expecting a new 'Version 7' of seti@home in the next few months - no release date even pencilled in yet. That one will definitely be a 'required upgrade', so keep watching this space.

I will do. Thanks again for your perfect support.

Frank