You are welcome Jord.
I see you catched V8 tasks already.

All looks good.

---

With each crime and every kindness we birth our future.

Still have 45 v7s and 6 APs to go through before I hit upon the v8s. If I game a little less Far Cry 3, perhaps Wednesday. :)

---

off-topic: sovietWomble (from England, lol) has been streaming Farcry 3 play on Twitch lately. Funny stuff when he screams like a girl as tigers run at him.

---

"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.

off-topic: Better than those irritating eagles and honey-badgers in Far Cry 4. :)

---

(Reposted from here.)

Hi.

Both my Macs received the new v8.0 apps this morning.

All the tasks on the PowerPC machine are erroring immediately.

<core_client_version>6.12.35</core_client_version>
<![CDATA[
<message>
process got signal 5
</message>
<stderr_txt>
dyld: Library not loaded: /sw/lib/libfftw3f.3.dylib
  Referenced from: /Library/Application Support/BOINC Data/slots/4/../../projects/setiathome.berkeley.edu/setiathome_8.00_powerpc-apple-darwin
  Reason: image not found

</stderr_txt>
]]>

That error was reported to Eric during Beta testing, and he acknowledged it on 26 December. A new Beta version was deployed on 29 December (Beta applications), but apparently not tested. I'll draw his attention to the problem here after the weekend (let the guy have a break, eh?)

No need -in the mean time and because we were chatting anyway- both Jason and I have done so already, also to Charlie. :)

---

No need -in the mean time and because we were chatting anyway- both Jason and I have done so already, also to Charlie. :)

Not sure whether Charlie has a hand in the PPC builds - I think he's an Intel guy, using a newer toolchain. Best to check with Eric too, just to be sure.

Beta message 55493:

Since Charlie uses xCode projects, he doesn't put much effort into being able to compile through autoconf.

Don't ask me whether xCode was ever released for PPC.

Eh, we're both at least part dutch, so used the shotgun approach and did both.

---

"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.

Ah look, that's what you use for option two. (secret code). :)

---

Hi all, finally i realized that was a issue caused by Comodo Internet Security 2015.

Marco.

---

Ah look, that's what you use for option two. (secret code). :)

I have no idea what you are talking about.

---

"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.

Hi all, finally i realized that was a issue caused by Comodo Internet Security 2015.

Marco.

Could be that or could be network drivers it relies on

---

"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.

Hi all, finally i realized that was a issue caused by Comodo Internet Security 2015.

Marco.

Ah, that makes sense. Thanks for reporting back.

I wonder what AV/security product Brent Norman - Canada uses?

Edit - I assume that taking Comodo out into the back yard and forcefully re-educating it has allowed SETI v8 to run normally?

I wonder what AV/security product Brent Norman - Canada uses?

Edit - I assume that taking Comodo out into the back yard and forcefully re-educating it has allowed SETI v8 to run normally?

I use Comodo
EDIT: Why do you ask this Richard?

I wonder what AV/security product Brent Norman - Canada uses?

Edit - I assume that taking Comodo out into the back yard and forcefully re-educating it has allowed SETI v8 to run normally?

I use Comodo
EDIT: Why do you ask this Richard?

You and Marco both reported the same error - the new v8 application continually re-starting every 40 seconds, but making no progress and producing no diagnostic files, until eventually being killed by BOINC for "Too many Exit(0)".

Marco says he traced the problem to Comodo - I presume preventing the application from launching. Could you test whether making a security exclusion in Comodo allows yours to run, too?

I only had the first file experience that restart issue, other seem to be running fine.

Before that happened, I have had BOINC and TThrottle excluded ... all those reads/writes scanning seemed to improved system stability.

Am I understanding correctly that the v8 app_info text - presented in the read-only thread at the top of the fora - should be inserted into the existing app_info.xml in order to avail oneself of the stock Seti@Home v8 WU, in addition to any available v7 Seti@Home WU? When an optimized Lunatic's for v8 AP is released, the proprietary Lunatic's app_info.xml will reflect that change?

Right?

'Cause that's all my app_info.xml has are references to Lunatic's AP v7.00, 7.01, 7.03, and Seti@Home v7.00

[quote]Since Charlie uses xCode projects, he doesn't put much effort into being able to compile through autoconf.

Don't ask me whether xCode was ever released for PPC.

I'm doing command line compiles through autoconf for the PPC version. I had two executables available, one statically linked to fftw, one dynamically linked. I thought I had picked the right one. I had even used "otools -L" to show the dynamic library list, but I apparently got the wrong one anyway. I'll fix it as soon as I can.

---

@SETIEric@qoto.org (Mastodon)

Am I understanding correctly that the v8 app_info text - presented in the read-only thread at the top of the fora - should be inserted into the existing app_info.xml in order to avail oneself of the stock Seti@Home v8 WU, in addition to any available v7 Seti@Home WU? When an optimized Lunatic's for v8 AP is released, the proprietary Lunatic's app_info.xml will reflect that change?

Right?

'Cause that's all my app_info.xml has are references to Lunatic's AP v7.00, 7.01, 7.03, and Seti@Home v7.00

Exactly so - that's what it's there for.

Note that when you join the two files together, there should be exactly one

<app_info>

at the very top, and exactly one

</app_info>

at the very bottom. None in the middle where the two files join.

Comodo needs to be told that the new Seti image is trusted; it gets sandboxed and depending on how that's confingered prolly won't fly right. Unless you tell it in the alert not to isolate, that's prolly going to abend.

Furthermore, you may need HIPS rule for the image. I've set up a file-group for BOINC_projects that contain paths to:

BOINC_Data\projects\*\*
BOINC_Data\slots\*\*

and have given the file-group 'installer or updater' predefined policy access rights / permissions. Work good last long time.