2013-01-12, 15:30
All the above problems are due to the change in mce remote codes. Just uninstall xbmclauncher to return to your previous mce settings.Then install without the mce remote option.
(2013-01-12, 15:30)baijuxavior Wrote: All the above problems are due to the change in mce remote codes. Just uninstall xbmclauncher to return to your previous mce settings.Then install without the mce remote option.
(2013-01-13, 21:36)jordandk Wrote: I have justed updatet to 3.1 a couple a days ago.
When using the XBMC shell now, because you have done it awsome so I now can use UnifiedRemote at the same time.
My problem are, I have lost my Hibernation now, I have in powercontrol set it, to 20 minutes, then it would hibernate if there's no activity. But it never does that now, is there anyway that I can do to fix it again or do I really need to turn back to windows shell?
(2013-01-13, 23:33)costi Wrote:(2013-01-12, 15:30)baijuxavior Wrote: All the above problems are due to the change in mce remote codes. Just uninstall xbmclauncher to return to your previous mce settings.Then install without the mce remote option.
That did not help, I'm afraid. My guess is that the registry changes were not reverted back on uninstalling (the "Install MCE Remote Control registry code" checkbox). Does anyone have the .reg file, or can point me to where the MCE remote settings are, and what they should contain originally?
(2013-01-14, 15:34)baijuxavior Wrote: ^^ Not sure what causes that problem. In xbmc try options like 'Use a full screen window rather than true full screen'.
(2013-01-18, 02:23)Vidman Wrote: Is it possible to start xbmc when a WOL packet is received with xbmclauncher?
if not now could this feature be added?