Type: New Feature
Resolution: Won't Fix
Fix Version/s: None
There is a project called One-Core-API, this is a compatibility layer for WinXP/2003 to implement NT6 application compatibility. Author and main programmer is a guy called Samuka. Personally, I am a tester/contributor of this project. Our plans is to make NT5.x OS'es be compatible with most NT6-only applications.
This is not just a wrapper, this is a compatibility layer, it replaces native system files with our ones and we use native system files as a source of already implemented functions and all other dependencies. For example, our kernel32.dll(vernel32.dll) has a dependency of native kernel32.dll which has to be renamed to kernelfull.dll. Yes it is rough enough, but it provides the best handling.
DX10-11 is a WineD3D with some rough D3DKMT unimplementations, small enhancements and native d3d10.dll from Vista, which is not good
We have some neat results of NT6-only apps being worked. Tropico 5, Sony Vegas 13, Adobe Photoshop CC 2015, PES2016 etc.
As it is based on ReactOS you guys can check this out and maybe transfer some implementations to ReactOS in future, because our implementations are mostly tested on real apps and it will be mature enough to use it as base in future ReactOS releases.
Our task for now is to make later Chrome version work on XP/2003, we already found a reason why it doesn't work, we need to implement Windows Integrity levels feature in our layer, if someone has any ideas we will hear him with pleasure.
Here is even a Chromium commit that broke XP compatibility: https://chromium.googlesource.com/chromium/src/+/f9b843b964801440b50e74b072c70e7ecb0f1921
Here are the sources:
Compilation only possible for now with VS2010 and maybe later versions.
Participants are welcome!