This page largely summarizes the 11 forum pages at the MediaPortal-Forum and information from elsewhere , but there is a bit more information in the above link for people with other versions of Windows bit, etc. If byte 4 is set to 03 the eHome driver will generate a “Raw Input” message, see http: Byte 4 determines what the eHome driver will do when the button is pressed. The key codes for the multimedia keys are also listed in http: The exceptions I know about are:.
|Date Added:||8 May 2015|
|File Size:||24.31 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
If the HID Driver works properly for you, and you are satisfied with the limited selection of buttons that are converted into simulated keypresses, then all you need is the Remote’s drivers installed – you don’t even need EventGhost. You can find a list of the codes in http: Windows will react as if a key had been pressed on the keyboard.
Installing an eHome Infrared Transceiver
The Philips SRM will be used in the examples, but this is largely able to be translated to other Remotes. This site in other languages x.
Note that the standard MS remote uses number 12 for this button. There is no guarantee that the behaviour will be the same on all platforms. To fix it, download the setup from this link: Hi everyone, On my computer there running Windows XP, I can see that the guide came up and tell me that my computer have found new hardware a device called eHome Infrared Receiver”, but what is this? Images and video may be under a different copyright.
MyNews, Jan 29, Very thanks for the answer.
This page was last edited on 9 Juneat Views Read View source View history. I have used one day to find a driver to this device, but all I have tried not working!
Ejome for marking this as the answer.
Using a Microsoft remote control in Windows – Official Kodi Wiki
They are the keys with the “HID usage page” set to 0C. I will be very happy, if a person could tell me where I can find the correct driver to Windows XP, and tell me what ” “eHome Infrared Receiver” is!
Eome 4 determines what the eHome driver will do when the button is pressed.
For most people this will be fine, and in that case you don’t need to do anything further. To give a specific example, suppose you want to configure the Play button to send the Media Center keyboard shortcut for midrosoft, the 7 bytes would be:. Procedure from the MediaPortal-Forum.
The eHome driver can be configured by modifying the registry details below.
If you’re happy with binary numbers you’ve probably spotted that bit 0 specifies Control, bit 1 specifies Shift, bit 2 specifies Alt and bit 3 specifies the Intrared key. The exceptions I know about are:. Tell us about your experience with our site.
MCE Remote Drivers for Windows XP – EventGhost
It’s an arbitrary code selected by MS. Channel up button on the universal remote. This results in HID Devicein a brief button press mcrosoft the remote having the effect of it being constantly held down. Ask a Question Want to reply to this thread or ask your own question? This is not the case – they can be used easily and happily in Windows XP.
The only reason for continuing with this article is if you want to customise the Microsoft remote to change the actions of any of the buttons or to make the Info and coloured buttons work. When I start up my Windows 7-installation there run on the same computer, I can see that Windows 7 has recognised the device as the “Microsoft eHome Infrared Transceiver”, and here the driver is installed fine.
The data has been reproduced here just in case Microsoft ever remove the link to the tranlate. This thread is locked.