I'd rather abort any that I find on My 580 gpu.

Better not to crunch at all than to abort.

Well I aborted all the cuda guppi's/vlar's, it's done...

So sue Me.

The only effect of the Guppies on my systems is they take forever to finish & don't pay much credit.

So it would be better just to block all those that abort from using the project. They have the option of not using the GPU in their settings.


EDIT-
Just in case you didn't get around to reading the initial post in this thread, i'll repost the first couple of lines.

"As the title says. Beta test only, try at your own risk.

I think we should dig out the old Advanced Users only tag for this one"

. . Sorry Grant,

. . Unlike yourself that is exactly what frustrates and annoys many other contributors. They do take forever to complete and so prevent the host machine from doing more productive tasks.

. . As you fully know disabling GPU processing on a host completely would remove a valuable resource from the project, and there is NO option to allow GPU crunching on other tasks while excluding Guppis.

. . While you are correct about the caveat on the Lunatics Beta release the problem with Guppis is not a Lunatics issue in any way, the installer works fine, it is an issue probably more suited to the SoG thread.

The only effect of the Guppies on my systems is they take forever to finish & don't pay much credit.

So it would be better just to block all those that abort from using the project. They have the option of not using the GPU in their settings.

Fine then more people will leave, vlars it was agreed would not be on the gpu again We were told, promised really, sounds like that was an empty(hollow) promise...

. . I don't think people need to leave. But it would be nice if we could find a Guppi tamer to get these critters to behave and play well with Nvidia cards.

I don't suffer from lag here, I have an i7 3820 and the coolest 580(temperature wise) gpu, a PNY LC 580.

I'm not a programmer, I'm a hardware guy, but it would be nice if running vlars could be optimized.

I'm also going to apologize for what I said when I was having hardware problems, I have severe anxiety problems, the pc hardware I could replace and I've done so, it just required time and money, the severe anxiety problems I can do nothing about.

. . Exactly, it just requires time and money, resources that contributors donate to the project and which should be respected.

Anybody got an incompatibility wizard I can use to detect a 32-bit operating system from a 32-bit application (the installer itself), to say "Hi. I'm a 64-bit application really"?

Something simpler than https://msdn.microsoft.com/en-us/library/windows/desktop/ms684139(v=vs.85).aspx?

Fine then more people will leave, vlars it was agreed would not be on the gpu again We were told, promised really, sounds like that was an empty(hollow) promise...

That was MB data & that is still the case. There are still no MB VLARs going to GPUs.

. . It seems strange to me that such a commitment is being honoured when Guppis which are at the very least as demanding as MB VLARs are being distributed as GPU tasks. Anyone else see a pradox there?

I don't suffer from lag here, I have an i7 3820 and the coolest 580(temperature wise) gpu, a PNY LC 580.

I'm not a programmer, I'm a hardware guy, but it would be nice if running vlars could be optimized.

If you run the stock application then it will (eventually) select the application that gives the best throughput.


If you choose to run something that is only at the Beta stage of release- not yet close to general release- then it's up to you to select the application & then tweak it to give the best results. The information you provide back will allow those developing the applications to make the release version better. Unfortunately the documentation on what each variable is & does & what's best & not best doesn't really exist- this is still a Beta release remember.
But there are people around that can help.

. . Sadly that is true of most of the documentation available.

I run Lunatics 0.44...

I tried 0.45, opencl and Me aren't compatible, since most of opencl seems to be cpu work, I opencl you'd think would work on the gpu like cuda does.

. . While I share your allergy to Guppis, unless you are running a very, very old graphics card it should support OpenCL language. I am probably not the first to respond to this but most Nvidia cards less than 5 years old support OpenCL 1.2, and the Intel integrated GPUs support OpenCL 2.0 (at least my HD530 does).

I run Lunatics 0.44...

I tried 0.45, opencl and Me aren't compatible, since most of opencl seems to be cpu work, I opencl you'd think would work on the gpu like cuda does.

. . While I share your allergy to Guppis, unless you are running a very very old graphics card it should support OpenCL language. I am probably not the first to respond to this but most Nvidia cards less than 5 years old support OpenCL 1.2, and the Intel integrated GPUs support OpenCL 2.0 (at least my HD530 does).

The PNY LC GTX 580 supports OpenCL 1.1, runs like a slightly run away freight train, yet very cool in temps.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Anybody got an incompatibility wizard I can use to detect a 32-bit operating system from a 32-bit application (the installer itself), to say "Hi. I'm a 64-bit application really"?

I'm glad we have the experts around here to identify the error code ID10T :)

Thanks for looking into it everyone.

There are a few things mixed up here.
Strong opinions about what guppi runs well on or not etc.

Maybe some facts should be collected first, instead of blaming one thing or the other or demanding one thing or the other.

I run Lunatics 0.44...

I tried 0.45, opencl and Me aren't compatible, since most of opencl seems to be cpu work, I opencl you'd think would work on the gpu like cuda does.

. . While I share your allergy to Guppis, unless you are running a very very old graphics card it should support OpenCL language. I am probably not the first to respond to this but most Nvidia cards less than 5 years old support OpenCL 1.2, and the Intel integrated GPUs support OpenCL 2.0 (at least my HD530 does).

The PNY LC GTX 580 supports OpenCL 1.1, runs like a slightly run away freight train, yet very cool in temps.

. . :)

Fine then more people will leave, vlars it was agreed would not be on the gpu again We were told, promised really, sounds like that was an empty(hollow) promise...

That was MB data & that is still the case. There are still no MB VLARs going to GPUs.

. . It seems strange to me that such a commitment is being honoured when Guppis which are at the very least as demanding as MB VLARs are being distributed as GPU tasks. Anyone else see a pradox there?

No.
MB VLARs caused significant system usability issues. Guppie VLARs don't. Since they don't, why wouldn't they be run on GPUs?

---

Grant
Darwin NT

There are a few things mixed up here.
Strong opinions about what guppi runs well on or not etc.

Maybe some facts should be collected first, instead of blaming one thing or the other or demanding one thing or the other.

. . Well Guppis definitely run well on CPUs, on my core i5-6400 they actually take slightly less time then normal MB tasks.

. . And they definitely have a hate/hate relationship with Nvidia GPUs. In fact they are total brats.

. . Anything else? :)

Fine then more people will leave, vlars it was agreed would not be on the gpu again We were told, promised really, sounds like that was an empty(hollow) promise...

That was MB data & that is still the case. There are still no MB VLARs going to GPUs.

. . It seems strange to me that such a commitment is being honoured when Guppis which are at the very least as demanding as MB VLARs are being distributed as GPU tasks. Anyone else see a pradox there?

No.
MB VLARs caused significant system usability issues. Guppie VLARs don't. Since they don't, why wouldn't they be run on GPUs?

. . Now that is a scary thought, so MB VLARs on GPUs actually cause more system disruption than Guppis do?

. . That could cause me nightmares.

. . Now that is a scary thought, so MB VLARs actually cause more system disruption than Guppis do?

What system disruption do the Guppies cause on your system?

The only issue everyone else appears to be having is they take considerably longer than their estimated time to crunch.

---

Grant
Darwin NT

...the installer works fine...

That's about the only on topic post you've made here today. Would you please take the non-installer issues elsewhere. I'm getting quite tired of coming back to this thread when I see new posts, expecting to get the latest info on the installer, and finding post after post that are totally unrelated. Thank you.

I'm getting quite tired of coming back to this thread when I see new posts, expecting to get the latest info on the installer, and finding post after post that are totally unrelated. Thank you.

Sorry.
I try to ignore the off topic posts, but often can't help myself.

---

Grant
Darwin NT

Anybody got an incompatibility wizard I can use to detect a 32-bit operating system from a 32-bit application (the installer itself), to say "Hi. I'm a 64-bit application really"?

Something simpler than https://msdn.microsoft.com/en-us/library/windows/desktop/ms684139(v=vs.85).aspx?

x64 Windows should have a registry key in its default registry hive to do with WoW32 node, which wouldn't be present on x86

[Edit:] https://msdn.microsoft.com/en-us/library/windows/desktop/ms724072(v=vs.85).aspx

HKEY_LOCAL_MACHINE\Software\Wow6432Node

The applications for x64 usually have x64 or Win64 in the filename

[Edit2:] There is one complication in that NSIS installers i believe are still natively (and sensibly) 32 bit, so you see the 32 bit hive by default. Back in the day I did put logic near the top of the NSiS script to switch hives during Boinc client location detection. Don't know if that still works the same way, but if still present can set a flag there somewhere.

---

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

HKEY_LOCAL_MACHINE\Software\Wow6432Node

That sounds like a goer. I can ask for something universally present, like

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\CurrentVersion

and if I get an answer, I'm on a 64-bit machine? Silence means 32-bit? I'll give it a try. Thanks.

HKEY_LOCAL_MACHINE\Software\Wow6432Node

That sounds like a goer. I can ask for something universally present, like

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\CurrentVersion

and if I get an answer, I'm on a 64-bit machine? Silence means 32-bit? I'll give it a try. Thanks.

Sounds right, give it a go [failure would mean just rethinking the key]. NSIS always was deceptively powerful, which is why I chose it back then.

[Edit:] note there would be far reduced necessity now to separate 64 and 32 bit than there would have been when I was making them. Substantial customers were on dialup back then. Perhaps simplicity of combining to a single installer is justified now ?

---

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