More MCE info

[stottle]

There have been a number of posts about MCE remotes not working. I took a look at the registry on a Vista machine that had an MCE remote and found the following keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57db
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57dc
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57dd
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57de

All of the info I've seen about getting MCE remotes to work talks about changing subkeys under ...da. Apparently that works for most, but I didn't understand what the entries ending with db, dc, dd, and de were for. I think I figured it out, they are for different types of MCE input. Besides the CodeSetNum0/1/2/3, there's also a RemoteName key. ...da says RC6 based MCE remote - which makes sense, when the CodeSetNum keys are removed, EG sees RC6 encoded IR signals.

The other ones are:
...db ==> Samsung MCE remote
...dc ==> MCIR Standard Keyboard Remote
...dd ==> MCIR Japanese Keyboard Remote
...de ==> MCIR Three Button Mouse Remote

My guess is that those who are having trouble are using Samsung MCE remotes. And, for the case of kneighbour, I'm wondering if only a subset of these keys were added to the registry.

I've created an updated MCE __init__.py file that removes the CodeSetNum keys from all 5 keys (rather, any that exist. It only throws device not present if none of the 5 keys are present).

Will those having trouble give this version a try and let me know how it works?

Thanks,
Brett

[kneighbour]

>Will those having trouble give this version a try and let me know how it works?

By "give this versions a try", what do you mean? What do I do with this python file?

[stottle]

Each plugin in EventGhost is stored in its own directory under the EventGhost directory, in a "plugins" sub-folder. So go to the plugins->MceRemote directory, move the existing __init__.py file to __init__.py.bac, then copy the file above to that directory. When you restart EG, it will use the beta version above, which hopefully fixes the trouble you are having.

Brett

[Melloware]

I am having similar issues but with windows 7 and the MCE Remote.

http://www.eventghost.org/forum/viewtop ... f=2&t=1669

When I delete the Codeset0-3 the HID signals stop completely.

[stottle]

@Melloware -

I posted this in your other thread, but thought it would be good to have the info here as well.

I was able to get EG events from an MCE remote in Win7 by turning off UAC. Obviously that's not a good long term answer. If you find a better way, please let me know. I'll post back here if I find anything else that works.

[edit: I was surprised to not see any events, but also not see any indication of UAC stopping the events. I would have expected UAC to ask and then allow events]

Brett

Has anyone ever looked at creating a wrapper for a process that asks UAC for raised privileges from EG?

Brett

[Melloware]

@Melloware -

Has anyone ever looked at creating a wrapper for a process that asks UAC for raised privileges from EG?

Brett

I think it might actually be a bug. Because I have users that reported running the app As Administrator and they were still not receiving any HID ouput from the remote. So maybe it is that its not just elevated privileges but turning UAC off entirely?

[stottle]

I was running as administrator as well and still needed to turn off UAC. As I understand it, running as administrator means that you run with the privileges of a regular user, but if you try to run something that needs higher privileges you can be automatically elevated (once you hit the ok button on the UAC prompt). Otherwise it will ask you to authenticate. That's why I was asking about having a process that requests elevated privileges. I think the process needs to let the OS know it needs elevated privileges before it asks (I could be wrong, I'm not a UAC expert).

Brett

[Melloware]

I was running as administrator as well and still needed to turn off UAC. As I understand it, running as administrator means that you run with the privileges of a regular user, but if you try to run something that needs higher privileges you can be automatically elevated (once you hit the ok button on the UAC prompt). Otherwise it will ask you to authenticate. That's why I was asking about having a process that requests elevated privileges. I think the process needs to let the OS know it needs elevated privileges before it asks (I could be wrong, I'm not a UAC expert).

Brett

Hmmm that makes more sense. i was under the impression that Run As Administrator meant automatically raise your priviledges without the UAC even asking you since you are an Admin. It sounds like I am wrong if you have confirmed that behavior.

[stottle]

This has been downloaded, but other than the Win7 comments, I haven't heard if this helped fix any of the problems people were having. Any feedback?

Thanks,
Brett

[pinkieiknip]

With Windows 7 build 7100 (RC1 that is), I now get the following error when EventGhost 0.3.7r1030 has been installed and tries to start for the first time:

"Unable to elevate priviliges."
or something in that sense.

And, as I was before, I can only get input from my remote when I start EventGhost as an administrator. As I really like this program and the way it is set-up, I would like to see this to be fixed, so I can run EventGhost at startup, which it now does not, since I would get an UAC report (and I do not intend turning it off).