Thank you, kgschlosser, inline
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
te36 wrote: Mon Jan 21, 2019 3:24 am
made it sound to me as if i can just use the MCE remote plugin and everything will be fine. Aka: i would NOT need to jump through hoops making EG autostart as admin so that it will work correctly with that plugin.
OK there is no jumping through hoops. You do not have to autostart EG as an administrator. You only have to start it as an administrator a single time to install the AlternateMCEIRService. The link you provided for the MediaWiki is for directions to the MCE Remote plugin and not the MCE Vista+ plugin. the MCE Remote plugin does not have an alternateMCEIRSeervice. So you are referencing documentation for the wrong plugin.
My first question explicitly referred to the MCE Remote plugin, not the MCE Vista+ plugin. I am trying to first understand what is required to make the MCE Remote plugin work. Does it require administrator to run or not ? For me, it only works as Administrator on Windows 10. Does it work for others on WIndows 10 without Administrator ? Then i would like to figure out whats wrong on my system.
There is no wiki entry for the MCE Vista+ plugin AFAIK. Once i understand how all this stuff works, i would really love to fixup that wiki FAQ to explain whats the state of things for both plugins.
So, it would be really great if you could tell me whether the MCE remote plugin is expected to require admin privileges to run.
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
te36 wrote: Sat Jan 19, 2019 5:14 am
Been using EG forever on win 7 pro with MCE remote via AlternatMceIrService.
You are the one that stated that you were using the MCE Vista+ Remote plugin because you stated that you were using thee AlternateMCEIRService. Not I. the MCE Remote plugin is for Windows XP MCE remotes which use keyboard emulation, Starting with Windows Vista that system was depreciated and is not commonly used. (Unless you have an old remote for XP).
I use the MCE Vista+ plugin on my windows 7 kodi system because the MCE Remote plugin does for me also require to start as admin, and it was easier to simply install the AlternateMCEIRService on windows 7 and then run EG without admin. That was just me explaining my history. For my new windows 10 system i am trying to figure out which plugin would work easisest.
Wrt. windows XP MCE remotes: Hah! this is getting more complex
). Yes, i guess my remotes come from the time of windows XP. I do not even have the original remote anymore, just the code set on my logitech harmonies. But i am using an IR receiver i bought just a few years ago. So when i try with that receivers original (uncomfortable
remote, then i do not get codes in EG from MCE Remote plugin. Only from the old XP remotes commands. Interesting. Before i disabled HID service i think i would have gotten from HID keyboard commands from both the old and the new remotes. what is this? RC5 on XP, RC6 on newer remotes ? And the IR receivers and the windows 10 MCE remote driver does support for RC5/RC6 as well as the HID module, but the MCE Remote plugin in EG only supports the RC5 ?? Could this be any more confusing ?
)
I only tried the XP RC5 remote when i had the AlternateMceIrService active. Maybe thats the reason why it didn't work ? Or is AlternateMceIrService also supporting the older XP remote command codes ?
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
I am not the one that wrote the code for Windows 10. I am not the one that brought a plethora of changes that made things to be a pain to do. I am the one that has had to spend a lot of time figuring out how to make the various components of EG work properly with Windows 10. You can send an E-Mail to Microsoft and I am sure they will simply ignore it.
Indeed. Hope my questions don't sound offensive, thats far from what they are meant to be. Windows 10 looks to me like an improved version of windows 7 with some microsoft version of android dropped on top of it to mess everything up (win
, and then beaten up with a hammer to make it work somewhat better (win 10).
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
You cannot use the Task Scheduler to start EG. it will not run correctly. There are components of EG that require the Windows GUI to be loaded. Even if you have it set up to start EG at user login. EG can get started before the Windows GUI has fully loaded. This can cause phantom like problems.
Hah. I thought i had it running as admin from task scheduler, but you're right, it does not work, even though i can see in task manager that it's running elevated. Seems like yours is the explanation. *sigh*. But i totally don't understand this logic. I can also start kodi from task scheduler. How mure windows GUI than kodi would EG need ? Really strange.
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
te36 wrote: Sat Jan 19, 2019 5:14 am
Now installed new Win 10 Pro system and can not get EG 0.4.1.r1722 to work:
which means you were running eg 0.4 at the time. and EG 0.4 has not had an update to it in 3 years. so the MCE Vista+ plugin is going to be horribly out of date. we did upgrade the version of the plugin in EG 0.5 However once we move on to making a newer version of EG we will no longer update the plugins in EG 0.5 so it can become out of date once again.
I think my xmbc system ran maybe 8 years on XP, then got a bit of an upgrade on win 7. I don't think i ever needed to upgrade EG in between.
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
As far as the funky setup process for the remote. with the pressing a key while it installs the drivers. You are just going to have to trust me on it. I know if sounds really goofy. but if you read other posts in that same thread you will see people commenting that it does in fact get rid of abnormal remote behavior including the remote not functioning at all. It took me almost 2 years to figure that out. I had the exact same problem you are having now. Everything was done and installed but no matter what I did I could not get any events in EG from pressing a button on the remote. Chances are you had the IR Receiver plugged in when you first booted Windows 10. because of the 50 other drivers Windows 10 was installing at that time the remote probably went to sleep. this is going to cause the drivers for the remote to not install 100%. Be glad that you have a solution if that is in fact the problem. I searched the internet for a very long time and never found a solution. I spent 100's of hours to be able to give you that solution.
Ok, i'll take this into advise, but: The remote was not plugged into the system when it was installed. I do have two MCE remotes (old one from XP time and new one i mentioned above). In experimenting even with MCE Remote and admin, one time everything stopped to work, and i got it back to work with MCE Remote though uninstalling the driver and let it reinstall when re-plugging the IR receiver after reboot.
So, i'll see...
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
All I am trying to do is help you. The links I gave you are for you to use to get a working remote in EG WITHOUT the need to Autostart it as an administrator. They outline each and every single step required to get the remote to work.
And help very much appreciated. I think the confusion comes from me first wanting to understand what exactly the deal is with the (old) MCE remote plugin, whereas you immediately jumped to explaining the MCE Vista+ plugin. I really want to understand if there is ANY way to get an autostarting system with just the MCE remote plugin. If it requires admin privileges, which it seems it require, then it looks to me as if there is no reasonable way to get an autostarting system.
kgschlosser wrote: Mon Jan 21, 2019 1:20 pm
You can most likely skip the step with disabling the blocking of unsigned drivers. Tho I am going to tell you you should do it. There are still way to many drivers out there that are not signed for Windows 10. If you have a piece of hardware that does not have any available drivers for Windows 10. you can go ahead and install the Windows 8 ones. and they will appear to be working and you will get no errors. but the device will not function. Those directions are how you go about getting drivers that are not Windows 10 signed to work. and it does it without having any kind of a watermark on the lower right hand corner of your desktop. It is my recommendation that you do it to save yourself some aggravation in the future. But it is up to you.
Slow.. Where does a driver come into player ? The AlternateMceIrService itself is not a driver right, so the only driver is the driver for the IR receiver ??? I did not have to install any driver for the two MCE IR receiver is have. I just plugged in and they worked to the extend described. I wouldn't even know where to find drivers. I guess i can check out the USB IDs and search the internet for new drivers, but its unclear to me how to first figure out that the driver does not work perfectly and that instead the problem is instead in EG and AlternateMceIrService.
I'll go back and examine this all, but how do you think someone without this whole email thread should be getting an MCE remote to work with EG ? Can this not all be put accordingly into the "Install Service" script of the AlternateMceIrService ?
I had also asked a few questions where i think i am missing answers:
-> Are the latest versions of the AlternateMceIrService binaries (exe/msi) in the latest EG on github ? If not, why not ?
-> If i click on "Install Service" in MCE Vista+ plugin, everything looks fine, but i do not get an Ok button, only Cancel. Is this an indication that the Service is not running correctly, or that the MCE remote driver is not correctly installed, or what ???