I see the new app is ready to go, and have not closed any doors, but I only receive camb_legacy 2.17 work units, so I can't help.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Hi Adrian, the camb_boinc2docker and planck_param_sim jobs require a 64bit machine, the one I'm seeing under your account is 32bit.

Fair enough.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I researched this a little. This machine has a Core 2 processor, which, according to Wikipedia, is a 64bit chip. https://en.wikipedia.org/wiki/Intel_Core_2

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Ah you're right. The problem is though that you have a 32-bit OS, which we don't currently support for the VM jobs. However, I believe technically you should be able to run 64-bit VMs on a 32-bit OS as long as you have VT-x turned on (and looks like your processor does support VT-x).

It just requires that we release an app_version which includes the 32-bit vboxwrapper. That should give access to the small (but perhaps not too small) minority of you guys who have a 64-bit machine with a 32-bit OS. In fact I realize now that I though we were supporting you, but didn't realize we weren't.

Let me get the bugs sorted out of this new planck_param_sim release, and then I will try to get to this, possibly early next week.

It still crunches the old app, and is connected to more than a dozen BOINC projects, so as long as the camb_legacy jobs are useful, it will work them. Be nice to get it fixed, but don't bust a gut over getting it done.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

The machine has been updated, now running a 4GHz i7 under Windows 10. Still only seeing 2.17 jobs.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

The machine has been updated, now running a 4GHz i7 under Windows 10. Still only seeing 2.17 jobs.

Are you still on a 32bit OS? I have not gotten around to implementing it to work there yet (but I've started!). Otherwise, can you check the usual suspects, i.e. did you forget to enable VT-x or maybe you've been bitten by this bug?

It runs Windows 10, an update from Windows 8.1. I've looked for that option in the BIOS but not found it yet, ASUS Sabertooth Z170 Mark 1 board - has a flashy BIOS interface, can't find ANYTHING yet!

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

It runs Windows 10, an update from Windows 8.1. I've looked for that option in the BIOS but not found it yet, ASUS Sabertooth Z170 Mark 1 board - has a flashy BIOS interface, can't find ANYTHING yet!

Ah sorry I see you're running a 32 bit OS, which, despite the 64 bit processor, is not yet supported by either the camb_boinc2docker or planck_params_sims jobs.

The good news is that eventually we will support your setup, but I have not had time to do so yet. I'll make sure to post back here when I get around to it, which should be in the next few months.

I have the 64 bit media, I'll install it when I get a moment.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

... but Windows 10 refuses to read the disk, it says it is not possible.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Reformatted. Now runs 64 bit Windows 8.1.

Another question, is there a way I can limit the number of threads the application spins?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Reformatted. Now runs 64 bit Windows 8.1.

Another question, is there a way I can limit the number of threads the application spins?

Yes, see http://www.cosmologyathome.org/faq.php#limit-cpu

Thanks, I'll write an xml file to limit it.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Doesn't seem to work. I allowed Cosmo to download wu's and watched to make sure it was playing nice, but when a work unit started, other BOINC task went into waiting and vboxheadless was using 98-99% CPU. I've set no new tasks again.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Can you double check the stuff mentioned in the "notes" in the link? This solution has definitely been confirmed to work by multiple users.

Checked, I see nothing there that would apply. I can definitely confirm to not work by one. Don't worry about it, I'll detatch.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.