If you check my host details you will see i`ve finnished a couple thousand APs already with dozen different app variants.
I never had such a problem.
Sorry.

Boinc api bug is pretty new to me.
Evenso the app is running fine on your other rigs.

You can still try unroll and block_fetch settings Claggy and some others suggested.

---

With each crime and every kindness we birth our future.

If you check my host details you will see i`ve finnished a couple thousand APs already with dozen different app variants.
I never had such a problem.
Sorry.

Boinc api bug is pretty new to me.
Evenso the app is running fine on your other rigs.

You can still try unroll and block_fetch settings Claggy and some others suggested.

Per Richard's suggestion, I'll take this discussion to the other thread and review more of what has been said there. It is vexing that the same app would run just fine on some of my rigs and not of some others with similar architecture and GPUs.

Your input is appreciated of course, Mike. It's obvious you have put a lot of time and effort into testing. Just wish the app would screw up for YOU....LOL.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Sorry if this was answered and I missed it, or maybe it was in a different thread and I missed it.

I just installed the new package on my XP GPU-only box.

(Before I started it, I changed all the counts in app_info.xml to .5 and it still only ran one, but I found the answer to that, downloaded and installed the app_config.xml, and then had to stop and restart Boinc; just reading the file didn't make it start a second task.)

The question is, did I miss a recommended minimum driver version for nvidia? I currently have 310.70 and I see 320.18 is available. Should I install it? Should I NOT install it? Or am I fine either way, Boinc-wise?

My first task has already completed and been reported, but I don't know how to read the stderr to see if it's okay. I don't see any red flags, but I don't know.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Sorry if this was answered and I missed it, or maybe it was in a different thread and I missed it.

I just installed the new package on my XP GPU-only box.

(Before I started it, I changed all the counts in app_info.xml to .5 and it still only ran one, but I found the answer to that, downloaded and installed the app_config.xml, and then had to stop and restart Boinc; just reading the file didn't make it start a second task.)

The question is, did I miss a recommended minimum driver version for nvidia? I currently have 310.70 and I see 320.18 is available. Should I install it? Should I NOT install it? Or am I fine either way, Boinc-wise?

My first task has already completed and been reported, but I don't know how to read the stderr to see if it's okay. I don't see any red flags, but I don't know.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

As to the drivers, to run Cuda 50 on your 630, the minimum is listed as 306.23 and you are on 310.70, so you should be good to go there.
On your 440 rig, Cuda 42 should be the best. Minimum driver is listed as 301.48, and you are on 301.42, so you might want to update that one.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Uhh, this AP GPU app still isn't happy, even though on my quad core dual 560 rig I updated the driver, have a core free and set my count back to 1.
It is still ditching AP tasks.

I am out for the evening, but what would be the next suggestion?

EDIT...
Sorry, I forgot about the priority thingy. Will give that a whirl next.

EDIT2
OK, the AP GPU app is now set to high priority on the 3 rigs that were giving the most trouble.

Do you Overclock?

Set to default speeds and see if it works.
And run app at default settings as well.

I am not about to change my clock speeds on either CPU or GPU just to accommodate a fragile application. These rigs are stable on everything else, and have been for some time.
The app settings are whatever the Lunatics installer supplied with the app, I have not changed a thing there. I have set them to high priority using Fred's priority tool.

There is a fatal flaw in the manner in which this application wraps things up after the WU is completed. I am sorry if that statement offends some, but I think I have verified what others have seen before me.

And, as I appear to be able to reproduce the problem willingly or unwillingly, I could test any new version if a bug fix can be found.

Why I suggested settings to default was because I ran Oc'd for aboy 2.5mounths and then by "mistake" setted clocks to default and then ran for about 24hours without problem. I can't Oc my ATI cards with SETI ap but with all other projects I can.
It was merely a suggestion from my own experiences.
It may not be what you need to be able to run.

//TQ

(Before I started it, I changed all the counts in app_info.xml to .5 and it still only ran one, but I found the answer to that, downloaded and installed the app_config.xml, and then had to stop and restart Boinc; just reading the file didn't make it start a second task.)

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

N9JFE, The app_config.xml won't do anything on your hosts, Boinc 7.0.40 or later required, you're running Boinc 6.10.58 and .60

Claggy

Sorry if this was answered and I missed it, or maybe it was in a different thread and I missed it.

I just installed the new package on my XP GPU-only box.

(Before I started it, I changed all the counts in app_info.xml to .5 and it still only ran one, but I found the answer to that, downloaded and installed the app_config.xml, and then had to stop and restart Boinc; just reading the file didn't make it start a second task.)

The question is, did I miss a recommended minimum driver version for nvidia? I currently have 310.70 and I see 320.18 is available. Should I install it? Should I NOT install it? Or am I fine either way, Boinc-wise?

My first task has already completed and been reported, but I don't know how to read the stderr to see if it's okay. I don't see any red flags, but I don't know.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

As to the drivers, to run Cuda 50 on your 630, the minimum is listed as 306.23 and you are on 310.70, so you should be good to go there.
On your 440 rig, Cuda 42 should be the best. Minimum driver is listed as 301.48, and you are on 301.42, so you might want to update that one.

Okay, thanks for the advice, Mark. So there's no known reason NOT to go to 320.18?

Between the 8 and 2 halves Einstein units and 23 MBs left to run, the i7 still has 2-3 days left to clear out its cache. (On both machines, I put Einstein on NNT as well as Seti so they wouldn't load up on Einsteins and then have to run through it all before starting on the new Setis and seeing how they perform. On the P4, I let it get some Seti and then opened up Einstein and it didn't ask for any. But even though there's a Seti task 30% finished after 1 hour, it still thinks it has 3.5 days left to run. And 23 days for an AP. That should settle down soon, I hope.)

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

(Before I started it, I changed all the counts in app_info.xml to .5 and it still only ran one, but I found the answer to that, downloaded and installed the app_config.xml, and then had to stop and restart Boinc; just reading the file didn't make it start a second task.)

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

The app_config.xml won't do anything on your hosts, Boinc 7.0.40 or later required, you're running Boimc 6.10.58 and .60

Claggy

Then why didn't the app_info.xml edits do the trick and app_config did?

I suppose I should mention that before I installed Lunatics, I exited Boinc Manager, but the installer told me the other Boinc apps were still running and it would have to stop them. Then when the installer finished, rather than go looking for Boinc Manager I just started Boinc Tasks. After adding the app_config, I told it to read that file and nothing happened, so then I had it stop everything and exited and restarted Boinc Tasks. That's when it started running 2 at once.

But the next time I have to restart the computer, it'll automatically start boinc manager.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

I have a AMD Phenom 2 1100T

Question is with this app
mb7_win_x86_sse2_cpu_r1717_nonipp_fftw

Would it better to run this app with the amd chip or the sse2 app in the installer
for cpu MB tasks

I am just not sure

I have a AMD Phenom 2 1100T

Question is with this app
mb7_win_x86_sse2_cpu_r1717_nonipp_fftw

Would it better to run this app with the amd chip or the sse2 app in the installer
for cpu MB tasks

I am just not sure

The SSE2 app in the installer is faster.

---

With each crime and every kindness we birth our future.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

No good reason unless you want to have a backup project on standby in case SETI runs out of work. 6.12.34 would be a good choise for that since that's the first (stable) version, that has a usable backup project support.

---

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

No good reason unless you want to have a backup project on standby in case SETI runs out of work. 6.12.34 would be a good choise for that since that's the first (stable) version, that has a usable backup project support.

And it's also the last version which supports running GPUs when installed as a service - under Windows XP only.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

No good reason unless you want to have a backup project on standby in case SETI runs out of work. 6.12.34 would be a good choise for that since that's the first (stable) version, that has a usable backup project support.

And it's also the last version which supports running GPUs when installed as a service - under Windows XP only.

I run Einstein as more than a backup project, I let it do some work. It gets about 29% of my resources.

Richard, if you're saying that later Boinc versions don't run GPU tasks as a service, I definitely don't want it for my GPU only machine. If you're saying that version and earlier don't do it on win7, I've noticed that.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

No good reason unless you want to have a backup project on standby in case SETI runs out of work. 6.12.34 would be a good choise for that since that's the first (stable) version, that has a usable backup project support.

And it's also the last version which supports running GPUs when installed as a service - under Windows XP only.

I run Einstein as more than a backup project, I let it do some work. It gets about 29% of my resources.

Richard, if you're saying that later Boinc versions don't run GPU tasks as a service, I definitely don't want it for my GPU only machine. If you're saying that version and earlier don't do it on win7, I've noticed that.

Nothing does it on Windows 7.

v6.12.34 is the last version before the BOINC developers prevented GPUs running in service mode, for no good reason. Well, they did it because something ATI did made things crash when BOINC did the necessary 'what have you got?' detection at startup. Which sounds like 'no good reason' to a NVidia user.

Sorry if this was answered and I missed it, or maybe it was in a different thread and I missed it.

I just installed the new package on my XP GPU-only box.

(Before I started it, I changed all the counts in app_info.xml to .5 and it still only ran one, but I found the answer to that, downloaded and installed the app_config.xml, and then had to stop and restart Boinc; just reading the file didn't make it start a second task.)

The question is, did I miss a recommended minimum driver version for nvidia? I currently have 310.70 and I see 320.18 is available. Should I install it? Should I NOT install it? Or am I fine either way, Boinc-wise?

My first task has already completed and been reported, but I don't know how to read the stderr to see if it's okay. I don't see any red flags, but I don't know.

Oh, and is there a really good reason why I should update Boinc from 6.10.58?

No good reason for to update Boinc as far as I am concerned.

As to the drivers, to run Cuda 50 on your 630, the minimum is listed as 306.23 and you are on 310.70, so you should be good to go there.
On your 440 rig, Cuda 42 should be the best. Minimum driver is listed as 301.48, and you are on 301.42, so you might want to update that one.

301.42 and 301.24 both support cuda 4.2 out of the gate Mark, just in case you didn't know.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

301.42 and 301.24 both support cuda 4.2 out of the gate Mark, just in case you didn't know.

I was only going by the information given in the installer.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

301.42 and 301.24 both support cuda 4.2 out of the gate Mark, just in case you didn't know.

I was only going by the information given in the installer.

as per readme (*) in some cases there may be beta, day 0, or day 1 drivers supporting the cuda revision described. In most cases except if there is some specific reason I specifically avoid an implied recommendation of using boxed or beta drivers, and state the developer driver shipped with the Cuda toolkit instead. early 300.x 301.10 are problematic, 301.24 being first Kepler beta that didn't have major issues (though it has some subtle ones underneath)

---

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

301.42 and 301.24 both support cuda 4.2 out of the gate Mark, just in case you didn't know.

I was only going by the information given in the installer.

as per readme (*) in some cases there may be beta, day 0, or day 1 drivers supporting the cuda revision described. In most cases except if there is some specific reason I specifically avoid an implied recommendation of using boxed or beta drivers, and state the developer driver shipped with the Cuda toolkit instead. early 300.x 301.10 are problematic, 301.24 being first Kepler beta that didn't have major issues (though it has some subtle ones underneath)

Since no one has directly answered the question, I'm now assuming there is no reason not to install 320.18.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

301.42 and 301.24 both support cuda 4.2 out of the gate Mark, just in case you didn't know.

I was only going by the information given in the installer.

as per readme (*) in some cases there may be beta, day 0, or day 1 drivers supporting the cuda revision described. In most cases except if there is some specific reason I specifically avoid an implied recommendation of using boxed or beta drivers, and state the developer driver shipped with the Cuda toolkit instead. early 300.x 301.10 are problematic, 301.24 being first Kepler beta that didn't have major issues (though it has some subtle ones underneath)

Since no one has directly answered the question, I'm now assuming there is no reason not to install 320.18.

IIRC nobody has yet reported problems with that driver, which isn't quite the same. Monitor the rig and the tasks and be prepared to drop back down to a 'known good' driver. If problems occur report on the board ASAP.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

I downloaded and installed the app_config.xml file and it started ripping thru the V7 GPU wus nicely at two @ a time. The it started doing APs on the GPU and suddenly the room cooled down again (humour there.. is winter in Aus so like the heat *grin*)

SO, what should I add to the app_config.xml file so that it crunches two APs at a time or is this stretching it?

(And yes, am aware that it'll be a simple answer, but it is the simple answers that sometimes lead to greater questions.)