Did you try holding down "C" on power-on to boot from the Windows DVD? If not, give it a shot. That's Apple's "Boot from optical media" incantation. Also, if you've only tried with a 64-bit Windows 10 ISO, try a 32-bit one. It should be a 64-bit capable CPU, but I think your era only boots 32-bit media - the transition to a 64-bit UEFI was with the transition to unibody, if I remember properly.

I don't want 32bit windows, that won't run the programs I need. It is trying to boot from the DVD, I get a DVD icon on the screen, it just locks the machine when I click it.

But you don't seem to care about actually accomplishing the task you've stated you want to accomplish. Just whining about Apple hardware and being smug about how you're so much better than Apple users. So good luck.

I want to accomplish it without going insane trying 100 different methods. Linux is happy, I'll stick with that. I hate Linux, but I don't have to interact with it, it's controlled remotely from Boinc over here in Windows on my main computer.

Sorry. Microsoft is the one who, rather late to the game, created the filesystem you're whining about. Nobody else thought it was a decent filesystem, either - at the time or at any time since.

And the hardware. Motherboards physically couldn't handle large disks, for any OS. There are similar limitations with RAM size.

Likely because they're booting in legacy BIOS modes, not UEFI. Different boot methods, different ways of dealing with volumes.

The Macbook refused to boot a legacy Windows from USB. The same stick I used for old PCs which had never heard of UEFI, and the one where somehow UEFI is broken - it's almost the same (actually one model newer) than another xeon server motherboard which is ok with UEFI. BIOS bug I think.

I'm not convinced WCG can be blamed for this outage (or other hardware-related problems), and I sometimes wonder what sort of [software] bag of nails IBM handed over :-)
Cheers - Al.

I think the root cause of WCG's problems are due to the grid configuration. It serves no real benefit. Put MCM, SCC, OPN, etc on their own BOINC servers and most issues will vanish.

If your GPUs need something to do you might consider mining Dynex (DNX). It's a distributed neuromorphic computing project. It's still a work in progress. https://dynexcoin.org/

---

I'm not convinced WCG can be blamed for this outage (or other hardware-related problems), and I sometimes wonder what sort of [software] bag of nails IBM handed over :-)

I don't know that it was so much it being a bag of nails but that it was very heavily customised to the point where the BOINC server manual probably covers less than half of it. That and Krembil has only a fraction of the resources IBM was putting into it. I am pretty sure if they had the same number of programmers and hardware resources IBM had, they would have resolved most of the problems, though it can certainly be argued that they might have been better starting from scratch with a default BOINC server setup but migrating their forums and other stuff would have created its own problems.

IBM had plenty of problems with their grid and needed a team constantly putting on band-aids. TN-Grid, Denis, etc seem to run fine with just one person at the helm.

---

I'm not convinced WCG can be blamed for this outage (or other hardware-related problems), and I sometimes wonder what sort of [software] bag of nails IBM handed over :-)
Cheers - Al.

I think the root cause of WCG's problems are due to the grid configuration. It serves no real benefit. Put MCM, SCC, OPN, etc on their own BOINC servers and most issues will vanish.

If your GPUs need something to do you might consider mining Dynex (DNX). It's a distributed neuromorphic computing project. It's still a work in progress. https://dynexcoin.org/

https://www.virustotal.com/gui/file/ace9dd93beae65218cfc7abdbaf6d22e58e0075ed9b1cbf3fd76c153cd1c0eeb

https://medium.com/@ares_61826/why-we-believe-the-dynex-cryptocurrency-is-a-scam-from-sec-sanctioned-daniel-mattes-561bbabbd89a

Dynex is a scam.