First, it will check if XBMC is already running. I wrote a little application to launch XBMC. If, for some reason, XBMC was taken out of the foreground, it wouldn’t come back. That was great, but it still had a weakness. They then used a batch-to-exe converter to make it an executable and replaced ehshell.exe.
I then saw some people had written some batch files that launched XBMC. This key combination is bound to launching “C:\Windows\ehome\ehshell.exe.” The quickest workaround to the problem is to change ehshell.exe to something that launches XBMC. Turns out, the behavior of that “Start” or “Green” button on the media center remote is to cause a special key combination to be pressed. I looked around the ol’ Internet for a solution to this problem. However, the “start” button on the media center remote still had the nasty habit of launching the Windows 7 Media Center app instead of launching XBMC. People have already provided premade media center remote configurations for XBMC. Luckily, some excellent work has been done on that front. One such challenge is getting the Windows Media Center remote to work in a nice way.
The point here is that switching to XBMC from Windows Media Center has a few challenges. But, my reasons for switching are not the point of this post. I found XBMC easier to get working with obscure encodings of video files (it uses mplayer instead of the normal codec engine).
#KODI XBMC FOR WINDOWS 10 SOFTWARE#
I recently took up the task of switching my media center software from Windows 7 Media Center to the Windows version of XBMC. I’ve also moved the source to a subversion repository. Big thanks to Joshka for showing me a neat registry trick that allowed me to create the installer. Updated : Based on some comments, I’ve released a new version with an installer and file for defining custom parameters.
0 kommentar(er)
