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. Navigation Main page Recent changes Random page Help. Already seen this answer , which concerns an actual hardware transceiver. To be safe, you still need to disable WMC services as above. Uncheck the item entries which has the ehome as path to the command, such as ehTray.
|Date Added:||17 January 2012|
|File Size:||45.87 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
MCE Remote Drivers for Windows XP
If the Eehome 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. To be safe, you still need to disable WMC services as above.
But there’s no separate software for this, all I have is the device manager entry. Post as a guest Name.
Uninstall, Disable, or Remove Windows 7 Media Center
Have you looked at the device before uninstalling it? The Philips SRM will be used in the examples, but this is largely able to be translated to other Remotes.
For more information contact your system administrator. Jike edited the dosable to fix this and other little things. Sign up using Email and Password.
Email Required, but never shown. You can actually modify some settings at the driver level.
How to disable Microsoft eHome Infrared Transceiver permanently?
However, as mentioned, the HID Driver can be a pain for a number of reasons can have the wrong typematic rate, resulting in repeated keypresses, can also result in one button being acted on twice – once via the HID Driver and once via EventGhost using the MCE Driver. In Option 1, ‘jike’ essentially followed this procedure, but made a few extra edits to the ini file to change the typematic rate, so if you can, I’d recommend using his version.
You May Also Interested In: This page was last edited on 9 Juneat 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.
This will prevent MCE related services to be startup up.
windows 10 – *Permanently* disable/uninstall eHome infrared transceiver – Super User
This is the easiest and most effective solution, assuming someone has gone djsable the trouble of editing dissable eHome drivers and making them available for your MCE Remote.
Sign up using Facebook. I’m running Windows 10, if that makes any difference. Even though Windows XP may not automatically recognize the remote, it will allow you to use the existing eHome driver for it. 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.
I didn’t even know it was there till I went looking for it.