2013-07-17, 20:08
Hi,
it took me quite some time to figure out how the VC-1100 remote actually behaves under Windows 8: while I had success making the green start button work using this tutorial in Windows 7, it seemed not to work at all under Windows 8. Why? Well, I don't know why, but under Windows 8, this remote sends a keystroke on the Green Button press:
L-Win + L-Alt + Enter
So I basically followed this tutorial here:
http://xbmccustomregis.sourceforge.net/r...art_Button
But I changed the script to monitor to the correct key-sequence, because they assume that the Green key causes Alt + Ctrl + Enter to be pressed, so you have to change this line in the .ahk-file:
^!Enter:: ;Ctrl-Alt-Enter is the shortcut for greenbutton_Win64bit
to
#!Enter:: ;Ctrl-Alt-Enter is the shortcut for greenbutton_Win64bit
(note: ^stands for Ctrl, # for WIN in the Autohotkey-script language).
I also set the path in the script correctly to match my XBMC installation directory, and added -fs -p parameters for running it in portable mode.
That was all. Worked for me, maybe it helps somebody who faces the same problems with that very special remote
it took me quite some time to figure out how the VC-1100 remote actually behaves under Windows 8: while I had success making the green start button work using this tutorial in Windows 7, it seemed not to work at all under Windows 8. Why? Well, I don't know why, but under Windows 8, this remote sends a keystroke on the Green Button press:
L-Win + L-Alt + Enter
So I basically followed this tutorial here:
http://xbmccustomregis.sourceforge.net/r...art_Button
But I changed the script to monitor to the correct key-sequence, because they assume that the Green key causes Alt + Ctrl + Enter to be pressed, so you have to change this line in the .ahk-file:
^!Enter:: ;Ctrl-Alt-Enter is the shortcut for greenbutton_Win64bit
to
#!Enter:: ;Ctrl-Alt-Enter is the shortcut for greenbutton_Win64bit
(note: ^stands for Ctrl, # for WIN in the Autohotkey-script language).
I also set the path in the script correctly to match my XBMC installation directory, and added -fs -p parameters for running it in portable mode.
That was all. Worked for me, maybe it helps somebody who faces the same problems with that very special remote
