Is this project generating any work for windows machines? I've had a Windows 10 machine attached for several months and nada . . . I used to get work up until a year or so -- stopped getting work so removed the project from my four machines and put them to work on other things. Then reconnected one machine awhile back and still nada . . .

---

Is this project generating any work for windows machines? I've had a Windows 10 machine attached for several months and nada . . . I used to get work up until a year or so -- stopped getting work so removed the project from my four machines and put them to work on other things. Then reconnected one machine awhile back and still nada . . .

No Windows work units for a long time. Currently Mac with a side portion of Linux unless you spin up a vm to run the work in.

No Windows WU in the pipeline that anyone knows of, or has even heard rumors of.

Currently, there are no workunits at all, beyond the very occasional resend. The most recent batch was 32-bit MacOS/Intel workunits, and there are rumors of more 32-bit Linux WUs here in the near future. Either way, you're looking at a VM to do any of the work - though I think the Windows Subsystem for Linux 2 can do a lot of what's needed, if properly configured. I don't use Windows anymore, so I'm not familiar with details, but I believe there's a writeup somewhere around here. Make sure you install the 32-bit libraries!

For the MacOS units, (almost) everyone is using VMs to process them, because the last version of MacOS that supports them is Mojave, which is quite a few versions old now. Apple dropped 32-bit binary support after Mojave, so anything newer, and especially the M1s, won't run them at all. Annoyingly, it will try to run them, and they fail - there's no way to say "Only run on older versions of MacOS." Or, at least, no way that's being used - I don't know if BOINC supports that or not. So at least a few of us have Mojave VMs running on Linux or Windows (there are writeups on both), running those workunits.

Of course, the standard CPDN behavior of "Suspend/resume of tasks is flaky, you're far better off just letting tasks run non-stop until completion" is present too. Sometimes a task will suspend/resume on command, sometimes it will recover from an abrupt shutdown, often enough it won't. So it's best to only run CPDN on long-lived machines (you can suspend/resume the entire machine without problems, and I do that for my solar compute rigs, but the tasks never see that and just compute through to completion).

It's a bit of a fiddly project to contribute to lately...

Good to know -- I shall detatch it again. A shame . . .

---

No Windows WU in the pipeline that anyone knows of, or has even heard rumors of.

Yes, both Mac and N216 Linux have had testing batches running last week that completed OK. I am assuming these will lead to main site work but when is anybody's guess.

Yes, both Mac and N216 Linux have had testing batches running last week that completed OK.

Workunits, Grommit! We must have workunits!

I've got a new 3900X build up and online, ready for whatever comes down the pipeline. And I'll probably upgrade my homeserver's CPU once this batch of tasks is done (3700X to 3900X). Though that may chip in a bit less this summer, I'm getting into air conditioning season so I try to run a bit less random compute in the house in the hot months. I suppose I could find a way to schedule my VMs to start/stop based on temperature... hm. Overnight, cooling is free if the windows are open.