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
