Glad to hear it works (didn't really expect that) and thanks for updating this thread - I hope it will help others!
I must have got the code from somewhere, I assume WinRing0 as it was open source like InpOut. I didn't write InpOut, only ported it to x64 and my driver experience is pretty much that!
By "Influence" I think you are referring to the almost impossible requirements to build drivers. They have to be signed with a driver code signing certificate - these are not available to hobbyists, only legally registered companies and cost quite a bit ($300+ a year). So it kind rules out these little projects. WinRin0 was killed when MS revoked their certificate meaning the driver will not install. That hasn't happened to InpOut yet but it could if someone were to abuse it like WinRing0 was used and abused (by malware developers). If/When that happens, InpOut will be dead unless someone manages to sign it with a new certificate - and take the risk that it will also be revoked (its a lot of pain, money and effort to get a certificate, to have it revoked because some random out there abuses the driver is not feasible).
So you could say Microsoft influenced it - but I can see why (if WinRni0 was used to bypass HDCP or other naughty things, they had every right to I guess).
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 500Gb NVME, 2x2TB WD Black (RAID1)