ISSUE RESOLVED.

Instead of just suspending Primegrid I removed it and got some MB WU's.

All is well

so you're saying you had to completely detach your client from the Primegrid project, or else you couldn't get any S@H MB GPU tasks? what a PITA in comparison to only having to suspend Primegrid.

It's usually best to try and work out why something isn't working as expected, rather than just hitting it with a sledgehammer.

ISSUE RESOLVED.

Instead of just suspending Primegrid I removed it and got some MB WU's.

All is well

so you're saying you had to completely detach your client from the Primegrid project, or else you couldn't get any S@H MB GPU tasks? what a PITA in comparison to only having to suspend Primegrid.

It's usually best to try and work out why something isn't working as expected, rather than just hitting it with a sledgehammer.

Yes, but it's more fun that way and requires less thought from the wielder.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

It's usually best to try and work out why something isn't working as expected, rather than just hitting it with a sledgehammer.

exactly my thoughts...

...i'm sure you remember the hassle i went through trying to get my 5870 GPU to crunch both S@H and MW@H tasks without errors...granted, i never had problems getting work like Blurf is (i just had problems getting tasks to not error out), but i never had to completely detach from S@H to make MW@H run properly, or vice versa. yes, i did have to close BOINC, make a minor edit to the cc_config.xml file, and restart BOINC when switching from S@G to MW@H (or vice versa), but i never had to detach from either project.

i'm curious to see if there isn't a simpler solution to Blurf's problem...

---

i'm curious to see if there isn't a simpler solution to Blurf's problem...

Miep asked the right question, and Claggy supplied a good part of the answer.

i'm curious to see if there isn't a simpler solution to Blurf's problem...

Already done that, see earlier post.

Claggy

i'm curious to see if there isn't a simpler solution to Blurf's problem...

Already done that, see earlier post.

Claggy

oops didn't even see your post until now...thanks.

---

i'm curious to see if there isn't a simpler solution to Blurf's problem...

Already done that, see earlier post.

Claggy

oops didn't even see your post until now...thanks.

But strangely enough, Blurf has got both CPU and ATI MB work,

Claggy

oops didn't even see your post until now...thanks.

But strangely enough, Blurf has got both CPU and ATI MB work,

Claggy

Please remember I have one dual core (non-GPU) running MB units only.

My big rig now has a bunch of MB work.

As to the sledgehammer approach I apologize-as you'll see by the thread in the Cafe I'm dealing with some health issues w/ my wife and am running on empty as far as sleep and coherence.

---

oops didn't even see your post until now...thanks.

But strangely enough, Blurf has got both CPU and ATI MB work,

Claggy

Please remember I have one dual core (non-GPU) running MB units only.

My big rig now has a bunch of MB work.

As to the sledgehammer approach I apologize-as you'll see by the thread in the Cafe I'm dealing with some health issues w/ my wife and am running on empty as far as sleep and coherence.

The point was, on your ATI host, with the <app_info> start tag being in the wrong place, i would have only expected you to get CPU MB work on that host,
and you wouldn't have got any ATI MB work on that host because all the references to the ATI MB app are before the <app_info> start tag,

Don't know what that's got to do with your other host, the one without a GPU.

Claggy

Finished my new build, i7-2600, 8GiGDDR3 1333MHz, P67 Chipset and INTEL board,
DP67BG. And 2 EAH5870 GPU's.
Even with HT on MFLOPS value is 3345M Whetstone, per core.

Tied to run Prime GRID, if they've send the wrong app. I don't know but all ~100 WU's errored within seconds.

Well SETI stock and MW, as a test.
Here's a
link to the host 5884985.

Now I'm going to run ATI MB and AP, but there also has to be some SSSE3 optimization for CPU, if a VLAR is crunched, The Set Up is somewhat different
then, if nVIDIA cards are used. (But it is a budget-cruncher and did cost me €450,75 also had one 5870, a PSU (Coolermaster) and a case, too.

First I'm gonna install V0.37 and replace some executables and edit the app_info.xml, only the CPU part has to be in place, then the ATI cards
and their app.s



maybe a c_config.xml

---

The point was, on your ATI host, with the <app_info> start tag being in the wrong place, i would have only expected you to get CPU MB work on that host,
and you wouldn't have got any ATI MB work on that host because all the references to the ATI MB app are before the <app_info> start tag,

Don't know what that's got to do with your other host, the one without a GPU.

Claggy

I'll fix the app info that when I get home Claggy...I appreciate the help.

Sorry to confuse the issue further.

---

oops didn't even see your post until now...thanks.

But strangely enough, Blurf has got both CPU and ATI MB work,

Claggy

Please remember I have one dual core (non-GPU) running MB units only.

My big rig now has a bunch of MB work.

As to the sledgehammer approach I apologize-as you'll see by the thread in the Cafe I'm dealing with some health issues w/ my wife and am running on empty as far as sleep and coherence.

When going through other peoples work, at least my approach is to bring up their public account page (via the name link) and click on view computers, which brings up the list of systems, and there on 'tasks' or 'details' for one computer depending on what information you are looking for (like boinc version run). So you get computer specific task lists. That's why we were wondering, what the problem was [you had tons of MB tasks when I posted] and later why it was working when the app_info had syntax errors.

As I wrote before 'sledgehammer' works, but as we (i.e. Claggy, Richard and I) alpha test both on BOINC and Lunatics, we like to get to the bottom of a problem, preferably with full logging details, to work out whether the observed behaviour is a bug or a feature and ultimately to be able to reproduce and bugreport if necessary.

There are still a few unresolved issues that people keep reporting, but we are unable to chase them as we never get enough information. This problem is likely to be compounded, when 6.12.x comes out as recommended and you need to ask 'which boinc version' as well...

Could you all keep in mind, that we try to do our best to help and solve your problems, but it is really frustrating if people don't seem to properly read your advise or further information request, because they don't seem to act on it. When I have to repeatedly ask or say the same thing I get the strong urge to hit the person in question over the head with a rolling pin. And that goes for both developers and users...

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

[offtopic]
Moderator's rolling pin can really hurt[/offtopic] LoL ;)

I'm familiar putting together a new cruncher, but unfortunatly, I've, except BASIC
never worked with code for an application, f.i. in CUDA, OpenCL, BROOK,
C++ etc.
Also make too ofeten mistakes in the app_info.xml file.
(But one is never too old to learn :) )

---

Sorry offtopic again: Huge thanks to Raimster. My hd 4870 gpu running MB tasks fine now. Already tested Astropulse 516 rev. Also astropulse tasks running fine.

Also thanks to Claggy: If he would not published in this topic app_info code, I'd have been in big trouble.

[offtopic]

Sorry offtopic again: Huge thanks to Raimster.

LoL, he didn't participate. Only I and other Lunatics ;)
[/offtopic]

FYI I finally had a moment to switch the tag, Claggy so it is listed properly now. Thanks

---

[offtopic]

Sorry offtopic again: Huge thanks to Raimster.

LoL, he didn't participate. Only I and other Lunatics ;)
[/offtopic]

Sorry for that. I mean Raistmer.

Any reason why the Pendings from the MB WU's on my rig with this app don't appear in Pendings but the ones from my Dual-Core do?

---

Any reason why the Pendings from the MB WU's on my rig with this app don't appear in Pendings but the ones from my Dual-Core do?

Quite possibly because your Dual-Core computer is running a much older version of BOINC (v5.10.41). It would be interesting if somebody else could confirm that - it's not been mentioned so far in all the discussions about changes to the pendings list.