stottle wrote:BTW, I think it might be possible to create a small app that attaches to the Mce device and forwards the ir codes to EG. That way the app could be installed with higher rights and you wouldn't have to worry about having EG run as Admin and turning off UAC. I'm looking into it.
That's right and this is the way MediaPortal's IR Server Suite does workaround the issue.
With out EG's involvement, only Up, Down, Left, Right, OK and number keys work with XBMC, provided HID is not disable.stottle wrote:The MCE Remote is kind of made of two parts. The first part is the device itself, which receives ir codes from the remote. The second part is the Windows OS, which decodes the ir codes and sends keypresses to the active window. That's the way it works without EG being involved, and I imagine (although I haven't tested it) those keypresses work fine in XBMC.
When does this "registry change over" thing takes place - every time EG starts up or when it was installed in the first place? Also, does it also mean - as you said "EG changes the registry" - the remote can't be use, say for example with Windows Media Center once EG is installed without running EG?stottle wrote:EG isn't going to read all the keyboard messages as events, that doesn't make sense. It needs the ir codes. So the first thing it does is change the registry (if run as an Admin with UAC off). This only needs to be done once, and once done, the OS no longer runs the second step above..
So, MceIr.dll is doing the thing that was previously done by OS, right? Wondering why it's a problem now and the reason for the device to raise an alarm - am I missing something here?stottle wrote:But now EG still needs to attach to the device to get the ir codes. That's were this MceIr.dll comes in, and where the problem is. The device has raised security (my terminology is off, but you get the point).
I'm kinda lost here: Do you mean on Vista/Win 7 MceIr.dll (if I understood correctly) cannot work for Admin with UAC on? Still trying to understand if I get that properly. Or you talking about the OS?stottle wrote:On Vista or Win7, the driver can't connect to the device without UAC off and using an Admin account.
I completely new in the XBMC stuff and almost a starter when it comes to the Windows. Can you explain it a bit in detail please? What registry key you are talking about. I just install EG and then added MCE and XBMC plugin from the configure menu - that's all I did.[/quote]stottle wrote:If you've run the EG plugin, you need to re-install the registry keys to have the OS run the 2nd step if you want to use XBMC without EG running (which you can do from the MCE plugin's configuration). I doubt XBMC needs to run as Admin, I think its more likely the registry keys have been removed.
Okay, so is it possible to fix the "right privileges" for MceIr.dll if not running as Admin? In other words, if I need to run EG (which I think I have to) to operate the remote, then there is any way to run XBMC as standard user? Cheers!!!stottle wrote:As for why this all happens, it certainly is a PITA. Since the OS was installed with Admin privileges (obviously), the OS can use the driver. Any process that tries to attach to the driver without raised privileges will fail. The MceIr.dll, provided with the MceRemote plugin, doesn't have the right privileges unless you are running with Admin rights and UAC is turned off. That's just the way it is, and EG can't do anything about it.
humm.......stottle wrote:Right now, there's no way to run MceRemote without Admin privileges and UAC turned off.
Users browsing this forum: Bing [Bot], blackwind, Google [Bot], Google Adsense [Bot] and 1 guest