Ok, there is some new info because testing is not still finished. It looks like there is need to install VirtualBox otherwise it can't create an instance of VBox. But there is also other problem with new version of VirtualBox, so I've been solving it. I thought that it could be ready on Monday but I need more time to testing.

Found link from orbit website, sounds interesting so I'm going to try it out! T4T had some quirks (a lot of quirks) in the beginning with vbox, but has been running smooth for months now. I'm running Win7-64, Boinc Mgr 7.0.25 and just downloaded the newest vbox 4.2.0 r80737. Added project ... now what? Do we need to setup vbox manually, or is there a wrapper like T4T that gets automatically downloaded and then launches when Boinc starts the task?

I only have one computer available right now, hope this vbox setup works out for the project! Haven't rec'd any tasks yet, so I'll keep checking forums for updates.

---

After some more testing I've found out that if BOINC is installed like Protected Service then it has no rights to start virtual machine and I couldn't figure out how to solve it. I tried changes rights in exe files or registry keys but nothing. The other problem is that if it worked a normal user wouldn't do such things to get it work. It seems to me that I will have to continue with making native app afterall. There are still some troubles with windows so I am very sorry that the windows app isn't still prepared.

...It seems to me that I will have to continue with making native app afterall. There are still some troubles with windows so I am very sorry that the windows app isn't still prepared.

Thanks, Kyong, for trying and doing what you can to make a Windows app available. As for me, I'm building a new host and may load it with a Linux distribution so I can participate in those projects which have only Linux apps.

---

After some more testing I've found out that if BOINC is installed like Protected Service then it has no rights to start virtual machine and I couldn't figure out how to solve it. I tried changes rights in exe files or registry keys but nothing. The other problem is that if it worked a normal user wouldn't do such things to get it work. It seems to me that I will have to continue with making native app afterall. There are still some troubles with windows so I am very sorry that the windows app isn't still prepared.

On Windows BOINC must be installed using the default installation settings which means that in the third (maybe fourth?) screen in the installer the user must not click Advanced button and select Protected Application Execution. If BOINC is already installed with Protected Application Execution option selected then the user must reinstall BOINC and make sure that option is not selected. It's actually very easy.

At the Test4Theory project we found that most Windows users use the default installation and thus have no problem. Those who do not have the default installation are very willing to redo the install and select the default. Most users just use the defaults so it's not a big problem.

Another way to avoid the problem is to run the VM in headless mode which means do not allow it to start it's own screen/window. Then BOINC (the wrapper) can run the VM even if BOINC is installed with Protected Application Execution option turned on. Of course the user cannot see what is going on inside the VM but if the VM is stable then there is little need to see inside it.

Have you discussed the wrapper with Rom Walton? Rom and a few of us did some extensive testing of a VM wrapper about a year ago at a special test project. Few, if any, of the methods/concepts learned from the test project were incorporated into the Test4Theory wrapper and that is why the Test4Theory wrapper is basically still a mess today. I advise to not let the experiences from Test4Theory influence you. Most of their troubles are caused by their steadfast refusal to incorporate tested improvements into their own wrapper. You can do better than that :-)

Hi everyone,

Listen, I have had no great success with vmbox in any environment.....

If you want the most volunteers, you have to run windows applications period.

I am running 4 boxes with Windows 64 environment and one box with Linux 64 variations.
And I am not running single cores........
You want lots of GFLOPS, run Windows Applications FINALLLLLLL>>>>>>>>>>>......... Need I say More......

Hope it happens soon....,
Qubity.

On Windows BOINC must be installed using the default installation settings which means that in the third (maybe fourth?) screen in the installer the user must not click Advanced button and select Protected Application Execution. If BOINC is already installed with Protected Application Execution option selected then the user must reinstall BOINC and make sure that option is not selected. It's actually very easy.

PAE/Daemon isn't good for several projects already. WCG still use their own version of Boinc where PAE is enabled by default (security reasons). If PAE is in use you will have to uninstall Boinc and then reinstall it; you can't just reinstall and unselect it because it's greyed out.

---

.

I am announcing that there will be native windows application released on friday or saturday probably. After many problems the app is ready, just a few more tests must be done.

I am announcing that there will be native windows application released on friday or saturday probably. After many problems the app is ready, just a few more tests must be done.

Great news! I look forward to giving it a try once it's released. :-)

---

I attached my Acer notebook running Windows. If it can run on that it will run on anything.

Great news! When you launch the windows app, please send an announcement via BOINC Notices. I'll be anxiously awaiting a chance to crunch for Asteriods@Home. Rick

---

Finally, the windows app is released. But I noticed that the noticing to BOINC manager is not working, I will have a look at it.

Thanks so much for making asteroids@home available for us Windows users. I've already finished 9 WU's and have more in the que. How do I donate to your worthy cause? Could not find a link on your home page. Thanks again. Rick

---

Thanks so much for making asteroids@home available for us Windows users...

+1

---

Hello,

With this apps you can really make your advanced calculations because the majority of people are on windows ....

---

Thanks so much for making asteroids@home available for us Windows users. I've already finished 9 WU's and have more in the que. How do I donate to your worthy cause? Could not find a link on your home page. Thanks again. Rick

Donation is not available at this moment but I am considering it.

Yes!!! Thanks for all the effort to get a Windows app going!!! Add another cruncher and some quad-cores to your volunteer list :D

---

What are the minimum requirements for the Windows app? I have a VERY old Sony notebook (263MHz, 128MB Ram) I still use for crunching wu's. Still works great for WCG, Seti@Home, and Quakecatcher. I'd like to add Asteroids@Home, but can't find the specs anywhere in the message boards. If anyone knows, please answer. Thanks in advance, Rick

---

Wow! It's hard to find them that old and still working. It's a perfect crash test dummy :-)

The app is using slightly less than 7 MB RAM on both my Linux and Windows hosts. On Linux it's using ~21 MB swap. That's less than a few project apps that I have come to think of as "small", ABC@home's app for example.

Given the CPU speed your other concern would be deadline. It looks to be 14 days so I would say there's a good chance you would be able to complete one. DCF for this project is close to 1 on my hosts so tasks are giving good duration estimates here. Usually that means if the scheduler figures it'll be OK it usually is.

Thanks for the reply. When I added Asteroids I got this message in the event log, "Period Search Application needs 244.14 MB RAM but only 127.49 MB is available for use. " The same message showed up in the client "Notices". Strange requirement, if it only uses 7 MB. Comments anyone? Rick

---