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. This data is taken from http: This is the option I would recommend for people with Windows XP and the Philips SRM because if you just use the eHome drivers, the typematic keypress rates are not correct. Thanks to the many people who put effort into discovering these numbers. The only raw input messages likely to be useful are:. If the eHome device does not appear you aren’t using the eHome driver and you should read no further.

Uploader: Bragami
Date Added: 24 February 2009
File Size: 30.41 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 55118
Price: Free* [*Free Regsitration Required]

Views Read View source View history. This thread is locked.

The 7 bytes would be:. Goobus, Jan 31, I have used one day to find a driver to this device, but all I have tried not working! This means that there is no byte available to specify the key modifiers, so you cannot combine a multimedia keypress with ctrl, shift, alt, etc.

The following table lists all the known button numbers. I have the same question This page was last edited on 4 Mayat ShowKey will show you what keypresses or AppCommand messages are being sent, and KeyMapEdit is a utility for editing the keyboard.


Navigation menu Personal tools Log in. The above example is from Windows 7. Navigation menu Personal tools Log in Request account.

Using a Microsoft remote control in Windows

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. MyNews, Jan 29, This is the easiest and most effective solution, assuming someone has gone to the trouble of editing the eHome drivers and making them available for your MCE Remote.

You’ll need to choose a username for the site, which only take a couple of moments here. 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.

It’s an arbitrary code selected by MS. Ask a Question Want to reply to this thread or ask your own question? Thanks to the many people who put effort into discovering these numbers.

What is “eHome Infrared Receiver” | PC Review

When I look in the device manager, I can see that the “eHome Infrared Receiver” not could be recognised correctly! Trnasceiver us about your experience with our site.


If byte 4 is set to 01 the eHome driver may generate a multimedia keyboard keypress.

Images and video may be under a different copyright. Jike edited the drivers to fix this and other little things.

The normal keys have the “HID usage page” set to Infrred on this page is available under Attribution-ShareAlike 3. They are the keys with the “HID usage page” set to 0C. You can do this either when it is first plugged in, or once it has appeared in the Device Manager as an unknown device just double click on it and go to the drivers tab.

Thanks for marking this as the answer. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service px.

How satisfied are you with this response? Did this solve your problem? Navigation Main page Recent changes Random page Help.