Ah, but can this era of Mac run Windows 10? I feel like that's the real challenge!
Win10 in a virtual machine on a c2duo early intel is IMHO only proof of concept - or, wait, the calculator runs great ... 😄
I had a three 24" iMacs from 2009 (2,6 to 2,9GHz, 8GB RAM, SSD) to run Win10pro solely (drive fully MBR-partitioned, 'cause I didn't want the hassle of BootCamp and mixed MBR/GPT).
First impression was ok with browsing, Office2k, PDF-handling, light apps and BootCamp-add-ons.
After I've installed my mandatory database-suite-software for work (a horrible 32bit-patchwork that really needs to be revamped), which needs to deal with the connected database and embedded documents on a Win10pro-file-sever, fun was over. Working was still possible, but speed comparable to current browsing on PPC ... I finally replaced by mid-2012 nonRetina MBP9,1 (cloning Win10 and transfer of the Win-activation was a bit tricky but did work), sold the two 2,6GHz machines but kept the one 2,9GHz one for special tasks, where speed doesn't matter that much or for RDP to the server ...
Well, Win10pro on an early-intel is possible, but only on a MultiBoot-machine and with limited power ...
And mind the hassle about Win10 activation! On the faster mid-2012 MBP9,1 (one sports two SSD: one Win10/MBR, the other Mojave/GPT) I tried to open Win10 within VMware-Fusion and killed my Win10-Activation (something that was not supposet to happen, if you read the manual - but maybe I missed an important thing). Especially because of that Activation-thing, I'd keep Win10 on an separate drive, because swapping the compete hardware (the Mac) and transfer the Activation is a bit complicated, but possible.
Down the virtual road Win7 struggles (but is ok, like actual Win10 on an early-intel), WinXP is ok and Win2k runs like hell, even for runnung games of that time (as long, as they do not require 3D-grafic-support)