And now I suppose I know what this "CreateProcess() failed" means.
x86 OS and x64-only provided installer.
So, if you see such error on CPU app download x86 build from my cloud and manually revert back to proper binary:
https://cloud.mail.ru/public/3nxq/SgQBZXcM7

I offered a copy from my website yesterday.
But it seems it has been ignored.

---

With each crime and every kindness we birth our future.

And now I suppose I know what this "CreateProcess() failed" means.
x86 OS and x64-only provided installer.
So, if you see such error on CPU app download x86 build from my cloud and manually revert back to proper binary:
https://cloud.mail.ru/public/3nxq/SgQBZXcM7

I offered a copy from my website yesterday.
But it seems it has been ignored.

Seemed (at the time) to be something broken we didn't understand yet Mike, because the CPU seems to support SSE3. As Raistmer picked up on, probably the problem was OS was 32 bit, while the apps in the installer were 64 bit.

---

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

Your (everyone's) advice for corrective options was not ignored. I'm currently running speed testing with different command lines so I don't want to make any changes yet.

I'm willing to try a new installer, but that will be in about 12 hours before I finish.

I know now all I have to do is read Mikes aisub, and point it to the right app (which I should have).

EDIT: BTW I don't have a WOW tag in my registry on this computer, so you should get nothing returned.

And now I suppose I know what this "CreateProcess() failed" means.
x86 OS and x64-only provided installer.
So, if you see such error on CPU app download x86 build from my cloud and manually revert back to proper binary:
https://cloud.mail.ru/public/3nxq/SgQBZXcM7

I offered a copy from my website yesterday.
But it seems it has been ignored.

Seemed (at the time) to be something broken we didn't understand yet Mike, because the CPU seems to support SSE3. As Raistmer picked up on, probably the problem was OS was 32 bit, while the apps in the installer were 64 bit.

Or probably missed in the noise of me responding to all of the off topic posts.
Sorry again.

---

Grant
Darwin NT

And yes, the CPU apps in the installer labelled 64 bit are 64 bit. The GPU apps are 32 bit, because there's no need to waste precious memory bandwidth on 64 bit transfers.

Since this thread is really about testing the installer, other deployment methods, and the behaviour of the applications after installation, are somewhat besides the point.

They do take forever to complete and so prevent the host machine from doing more productive tasks.

Then how one defines productivity of task ?
It's very important question - to establish correct metric.
(1)Productivity - bigger credit per hour?
(2)Productivity - hotter GPU?
(3)Productivity - better chance to achieve project goal?

Well, in ideal would be good if all these 3 metrics (there can be another too like less lags, more task number per hour and so on) would match.
Unfortunately, in current state of affairs these 3 metrics don't match.
So one should make educated choice what metric one will follow.

As was said many times already, GBT data represent results of targeted search. Chances to catch smth unusual much bigger than you specially stare for unusual not just glimpse between other observations.
So, productivity of "GUPPI VLAR" under metric (3) is much higher than any other task. Order of magnitude? Two orders? - hard to give quantative estimate but apparently much higher.

That's why worth to tolerate decrease in other metrics in my point of view.
Also of these 3 metrics (1) is mostly self-made one. CreditScrew is broken, period.
Metric (2) of course is important one. Would be good to have it as high as possible for all tasks, VLAR included. But, again, currently it happens to be lower for VLAR. Optimizations possible to improve it over time (also, optimizations possible to improve it overal again as was made with each new opt apps release).
But, all this secondary to single most important metric - how closer we to project goal. And with starting processing of targeted observations we much closer.

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.

Also, would be nice to add (x64) for application name on choice panel.
If one missed x64 in installer filename there is no other possibilty to understand one going wrong route until installer finished and too late to save cache.
Having SSE3 x64, SSE2 x64 will make it much more fool-proofed.

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

. . That's the one :)

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

. . Oops. Sorry.

Coming soon:



Yay!

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.

I've found these keys helpful for determining the OS architecture.
HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP\Hardware Abstraction Layer\ACPI x64 platform
HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP\Hardware Abstraction Layer\ACPI x86 platform

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

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 - I'm not sure whether it will fly or not.

This installer has been updated for NVidia only so far - DO NOT USE IT if you are currently running stock applications for ATI/AMD or intel GPUs.

This is basically the v0.44 installer (64-bit only, to start with), with the following changes....

Beta2 now available, in both 64-bit and 32-bit versions. Pick the right one, or test out my new dialogs...

Now includes new r3430 ATI and intel_gpu versions, with extra app_version entries to correspond with the new stock applications deployed on 19 May.

ReadMes not yet updated: we polish those up last, to take account of feedback received from testers.

Not extensively tested yet: that's your job. I'm going out for a walk.

While you download from https://onedrive.live.com/redir?resid=8D83BF774A4A86F5!979&authkey=!AK7t-36P9nAec2Y&ithint=folder%2cexe

Very nicely done!

Strong waiting for guppis wus to download, but nothings there !?

Have they been excluded ?

But fastest wu ever for me.

http://setiathome.berkeley.edu/result.php?resultid=4970345911

Edit:

ok, first guppi is here , lets see...

---

I'm sorry, I don't really understand your question. But for me, guppi.VLAR tasks are still being allocated and downloaded - they tend to come in batches, with batches of Arecibo tasks in between.

Thanks for the reply, first guppis are here, lets see...

---

Beta2 now available, in both 64-bit and 32-bit versions.

Selected and ran 64bit installer.

Win10 64bit, re-selected CPU AVX application, selected NVidia GPU SoG application (was running CUDA50).
Installed, restarted BOINC.
No problems.
Crunching resumed, cache intact.

---

Grant
Darwin NT

I installed the Beta on my main machine on the 29th.

Now I usually only look at my RAC once a week or less.

Imagine my surprise when I looked today



That is just a quick edited screenshot from Boinc Tasks but the upturn starts on the 29th/30th.

I wasn't expecting shuch a sharp rise.

I have just installed the 32 bit version on my other cruncher, that only has a GTS 450 so be interesting to see how that performs

---

Woah! Those are some impressive results. I haven't been following this as closely as I should have, though I have seen that there were discussions of many options settings, and as such I figured that I would hold off till it had a little more time to bake, and would jump on it when it was released. Looking at these results, I think I might take a stab at it, but how much configuring does it need? Or is it fairly automated? I've got a lot of balls in the air right now, and don't want to have to spend a ton of time fiddling with it. What's your experience been with it so far?

---

I installed the Beta on my main machine on the 29th.

Now I usually only look at my RAC once a week or less.

Imagine my surprise when I looked today



That is just a quick edited screenshot from Boinc Tasks but the upturn starts on the 29th/30th.

I wasn't expecting shuch a sharp rise.

I have just installed the 32 bit version on my other cruncher, that only has a GTS 450 so be interesting to see how that performs

. . I replied to ask about Boinc Tasks but learned something along the way about how to add images to messages. They must be uploaded to a web location then referenced with a URL. Hmmm .. something else to master.

. . You seem very comfortable with Boinc Tasks so is it alright if I try and pick your brains about it? One thing I do not like about it's graphs is the way they keep using strange values as reference lines, I mean why not use rounded number reference lines like 11000, 11500 etc :)