> This was more of a fun proof of concept rather than something usable. Virtually nothing can run due to critical missing files such as common dialog boxes and common controls.
[0]: https://x.com/XenoPanther/status/1983579460906487835?t=7jLSz...
Similarly, this is still windows 7.
Besides this old debate is pretty silly because I doubt anyone could propose (and get a majority of us to agree on) a formal definition of an operating system that would allow us to unambiguously say "that's an OS competent", "that's an OS", and "that's just software that ships with the OS" across a suite of OS's.
"Windows 7" brings a lot of connotations, including the ability to run Windows 7 software. Without that what makes it different to Windows XP?
https://github.com/shorthorn-project/One-Core-API-Binaries
That adds various NT 6 APIs and even compatibility modes for various newer versions of Windows up to Windows 11. At a glance, it appears to have support for Vulkan, Direct3D 10 and Direct3D 11 through software rendering, with the option of using WineD3D to get hardware accelerated Direct3D 10 and 11. I assume old WineD3D-PBA binaries run very nicely on that.
Interestingly, the developer suggests that installing graphics drivers from newer versions of Windows might be possible at some point, which I assume would provide native hardware acceleration for newer graphics APIs and support for recent graphics cards:
> WDDM is not impossible, only very hard. Currently initializes and the subsystem runs, but every driver fails to communicate with it's internal hardware due 2000/XP/2003 doesn't have support for MSI/MSI-X interrupt, required to WDDM drivers works;
https://github.com/shorthorn-project/One-Core-API-Binaries/i...