Ever the optimist, I jumped feet-first into Windows 10 on the VCR, because there isn’t much documentation on the sorts of things I’m trying to do with Windows and the project. For the past couple of weeks, I’ve been blazing a trail through the digital wilderness trying to get peripherals and software working perfectly under the new OS, and I hate to say that I’ve run across some glaring dead-ends.
The first to go was the real support for my remote control. Because it uses the MCE protocol, which is no longer supported by Windows 10 (since they dispensed with MCE in a vaguely boneheaded move to sell more XBones? [Pun intended]). WinLIRC, which was already a finicky primadonna under 7 has simply refused to work more than once under Windows 10. The Xbox 360 remote still works (sorta), but I prefer to have the different protocols so I’m not transmitting odd signals to one machine or the other. I’ve been having to use a keyboard and mouse combo primarily for simple navigation, which is getting old, so I decided to give the gamepad a go. Which leads to dealbreaker number 2.
Either Logitech is not supporting its devices properly or Microsoft has decided to abandon support for generic X-Input devices. Probably both. Logitech has taken the official position that gamepads should use Direct-Input and map controls through their proprietary software which immediately does not work because I lose the programmable functionality of the “Guide” button which I will make extensive use of in future upgrades to the system.
It stands to be said that the only reason I am using Windows in the first place is for proper game support. Instead of a hacked-up solution involving WINE under Ubuntu, I would rather have the operating environment with minimal “intrusion”. Granted, for media and hardware support, I would rather be running under Ubuntu anyway, but I’ve got to sacrifice one to get the other.Also on: