EDIT: By the way I'm using Vi$ta 64bit.

Not an issue, this worked on Vista 64 in Beta testing, location looks normal.

Didn't come across this in beta testing, but looks like a permissions issue as stated by others. Please rerun Boinc Installer, which should fix any errant permissions on boinc folders, then rerun the Lunatics installer [Carefully double check folder on directory selection page ... maybe it is pointing somewhere else!] , and report success or failure here. While not its intended use, running the script from the command line within the project folder, with said files present, then it should work ... otherwise, logically, it doesn't have access to those files ... and 'something' has made it so.

---

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

OK. I did that, made certain that my user has full permissions on project directory and that the installer points to the project directory and it gives the same results. Tried running both installers as administrator and still no change.

---

OK. I did that, made certain that my user has full permissions on project directory and that the installer points to the project directory and it gives the same results. Tried running both installers as administrator and still no change.

Cause Unknown: Manual Install is the answer for you.

---

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

OK. I did that, made certain that my user has full permissions on project directory and that the installer points to the project directory and it gives the same results. Tried running both installers as administrator and still no change.

did the User Access Control (UAC) pop up asking for Permission?

---

Please consider a Donation to the Seti Project.

It's off.

I'll poke the script some more. If I find anything interesting, I'll let you know.

---

Oh dear, Yes thanks for the reminder Al. Depending on version of Windows, Administrator isn't Really 'Administrator' anymore, but some hybrid 'Power User'. When the Installer requests elevated privileges, they must be explicitly allowed by the user, or the install will not succeed. There may also be circumstances that prevent the mechanism to request elevated privileges from working (Such as Disabled security?). In those cases the installer would have no effective way to gain access... even though 'Run as' 'Administrator' .... make any sense at all? Basically Administrator ... isn't [Unless you click some button to say it can be for the operation].

---

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

Actually if you do turn off the User Access Control, everything should work as if it isn't there. Back in the days when Vista was new, the solution for all kinds of problems with setup programs were to turn the UAC off.


Anyway, I located the problem. FIND on my computer does not work as expected. When I try to pass it any command using /something it attempts to find directory named /something. If I find out why this is happening I'll let you know.

EDIT: I think I found the problem! It appears that I have on my computer installed Subsystem for UNIX-based Applications. The script works fine on a computer without it installed. When I installed Subsystem for UNIX-based Applications on that computer, script failed. It seems that the Subsystem for UNIX-based Applications replaces traditional find with its own version which has different behavior. Maybe a note should be posted on the download site for users which have Subsystem for UNIX-based Applications installed.

---

Anyway, I located the problem. FIND on my computer does not work as expected. When I try to pass it any command using /something it attempts to find directory named /something. If I find out why this is happening I'll let you know.

Thanks very much! very curious!

---

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

Once again, a big thanks to all you guys over at Lunatics for all your hard work on the optimised apps and for making them so easy to install with this app

Thanks alot guys

---

Oh dear, Yes thanks for the reminder Al. Depending on version of Windows, Administrator isn't Really 'Administrator' anymore, but some hybrid 'Power User'. When the Installer requests elevated privileges, they must be explicitly allowed by the user, or the install will not succeed. There may also be circumstances that prevent the mechanism to request elevated privileges from working (Such as Disabled security?). In those cases the installer would have no effective way to gain access... even though 'Run as' 'Administrator' .... make any sense at all? Basically Administrator ... isn't [Unless you click some button to say it can be for the operation].

I did run into a 32 bit program on the 64 bit vista machine that for some reason ran afoul of UAC... I never did the find the registry entery that prevented it from installing (suspect in the WMI database) How I got around it was running under compatbility setings to finally get it work.

---

Please consider a Donation to the Seti Project.

Anyway, I located the problem. FIND on my computer does not work as expected. When I try to pass it any command using /something it attempts to find directory named /something. If I find out why this is happening I'll let you know.

Thanks very much! very curious!

Hmmmmmm POSIX rears its ugly head?

---

Please consider a Donation to the Seti Project.

Glad my old P4 is out of work because i will be downloading the new unified installer. Thanks guys.
App info file says im using an anonymous platform. So looks like it installed ok. Now some AP work and ill be happy.

---

[/quote]

Old James

thank you for the installer, marvelous thing, it was not too difficult before and i had to learned it, which was good, being twenty years without computer,but this is great.

I would like to know what cosmetic changes are there in Multibeam 6.03, AKv8b?
______________

Does this version do for the Astropulse v 505 as I can only see v 503 on the site? Forgot I do not have CUDA so how can I use it?

---

Does this version do for the Astropulse v 505 as I can only see v 503 on the site? Forgot I do not have CUDA so how can I use it?

I used the link at the start of this thread. and then clicked on the 32 bit for windows unified ver 02 installer. and version 5.05 is there.

---

[/quote]

Old James

I would like to know what cosmetic changes are there in Multibeam 6.03, AKv8b?
______________

No problem. It remembers signal counts after checkpoint/restart and obeys checkpoint period better at some angle ranges (mostly applicable to slower machines)

---

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

Thanks for the info Jason. I shall change the application on all my machines to the newer version then.
______________