Sounds about right, However I think Raistmer has updated his combined cudaMB+AP package with spliced app_info's that may make things easier if you are unsure.

Discussion of that, and appropriate links, are in his thread Modified SETI MB CUDA + opt AP package for full GPU utilization

Note that I'd provide a link to his thread on Lunatics with the download, but it seems to be down right now.

Jason

[Edit: modified the link to point to the right message]

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I will give it a go tonight...

Cheers

---

I realized after all 600+ of my WU's went comp error that this is a 32 bit app. Ugh /me must read what I'm doing and remember I'm on x64

---

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

I realized after all 600+ of my WU's went comp error that this is a 32 bit app. Ugh /me must read what I'm doing and remember I'm on x64

But the 32 bit App runs fine on x64 - does for me!!

Are you sure it wasn't a c**k-up in the app_info.xml??

F.

---

nope didnt work editted the app_info and checked it 2X before I installed it. reinstalled the old version and it worked fine

---

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

nope didnt work editted the app_info and checked it 2X before I installed it. reinstalled the old version and it worked fine

Well, the stderr out's say something different, MB & AP both say:

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
No main program specified
</message>
]]>

It means there wasn't an entry in your app_info for the work you already had,
ie: 500 for AP, 603 for MB.

Claggy

we need an app_info.xml

like this, the old one

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSSE3x.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8_win_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r69_SSE3.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r69_SSE3.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>

edit update with an Editor

Greetings from Germany NRW
Ulli

we need an app_info.xml

like this, the old one

That looked like a paste from Internet Explorer.

Internet Explorer adds the dashes you saw before some tags, and adds extra spaces inside some tags. That file wouldn't have worked without re-editing.

Always use a simple text editor like Notepad or Wordpad when preparing app_info.xml files.

Edit - the updated version looks much better. Thanks for re-posting.

update app_info.xml

Greetings from Germany NRW
Ulli

I have repackaged the combined packages with the new app and hopefully they will have them up soon.

Any idea when these may show?

---

Alright, well so far, it appears that I have dropped from 45-48 hours to under 40.

Great job to all involved!

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

First AP on rev 103 came in at 11.3 hours. They had been around 16 to 18 hours.

Good job on the new version.

---

It will be a little while before my Windows machine get to my AP units, will see if I get any improvement on the 18 hours that r69 took on a E6550(2.33)

---

r103 takes about 6.45 instead of just over 9 hours on my 4ghz quad.
Thank you.

Anyone had any luck with r103 on the new Boinc 6.6.2? When I tried it last night, Boinc Manager wouldn't load properly (sometimes but, eventually all the time), Boinc Manager wouldn't shut down the connected client, and machine responsiveness slowed to a crawl. It did work fine for about an hour before I had occasion to do a warm re-boot; that was when the trouble started.

Even when it was running with the app_info (confirmed by checking the tasks shown in Windows Task Manager) there was no mention of "Anonymous Platform" in the 6.6.2 Messages.

After several re-starts of Boinc and several complete re-boots of the box had not fixed this, I removed the app_info (trashed the cache) and all is now back to normal... Apart from the fact that the only way I can stop it continuously downloading new work is to suspend network access!!

F.

Q9450 o/c
GTX 295
Vista Home Premium x64

---

I am running the new BM and r103 and everything is crunching fine, though it did take an age to download all the WU's, I think it downloaded the maximum possible for each day in my cache regardless of processor speed.
The Manager is very buggy, but it doesn't seem to have affected my crunching...

---

Yeah, the real numbers for CPU seconds are in now.

r69 was about 165,000 - 174,000
r103 is now showing between 141,000 - 157,000

Of course I was playing some games during the crunching, too, so that skews the results a bit.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I went from 17.88 hours down to 12.56 hours, that is a big boost on my system.

---

Revision 103 is primarily a minor performance update,...snip

Jason, I think that could now be officially classified as a classic understatement!

Revision 103 is primarily a minor performance update,...snip

Jason, I think that could now be officially classified as a classic understatement!

I nearly didn't upgrade because of that statement, but to go from 13.5/14 hrs/task down to 9.5/10 hrs/task is not a minor performance upgrade.