home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Event Ghost Plugin For Mediaportal
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="druid9" data-source="post: 425153" data-attributes="member: 28347"><p>Thought this might explain - from the IRSS documentation</p><p></p><p>"With IR Server Suite there is no reason to use the MCE Replacement Driver.</p><p></p><p>By default Windows will handle most of the MCE Remote buttons, the arrow buttons, number buttons, etc ...</p><p>But I've now figured out a way to stop this behaviour ...</p><p></p><p>To handle the MCE device Windows loads a series of device drivers onto the system.</p><p>The main driver is the USB device driver, it provides access to the MCE device. Without it you can't use the device at all.</p><p></p><p>There are also a series of Human Interface Device (HID) drivers that are there to translate raw information from the USB device into remote button presses, keyboard and mouse inputs.</p><p></p><p>You can't disable the HID drivers but you can alter their settings to prevent them from acting on the button presses coming from the remote.</p><p></p><p>This process should work on all version of Windows that support the Microsoft eHome Infrared Transceiver. I've tested on Windows XP Pro and Windows Vista Home Premium and it worked on both.</p><p></p><p>However, please note that HIP, Girder and EventGhost can't use the default Windows eHome driver in Vista. On Windows XP these programs are fine, but these programs need the Replacement driver for Vista and I haven't been able to get the Replacement driver to work on 64-bit Vista yet, only 32-bit Vista."</p></blockquote><p></p>
[QUOTE="druid9, post: 425153, member: 28347"] Thought this might explain - from the IRSS documentation "With IR Server Suite there is no reason to use the MCE Replacement Driver. By default Windows will handle most of the MCE Remote buttons, the arrow buttons, number buttons, etc ... But I've now figured out a way to stop this behaviour ... To handle the MCE device Windows loads a series of device drivers onto the system. The main driver is the USB device driver, it provides access to the MCE device. Without it you can't use the device at all. There are also a series of Human Interface Device (HID) drivers that are there to translate raw information from the USB device into remote button presses, keyboard and mouse inputs. You can't disable the HID drivers but you can alter their settings to prevent them from acting on the button presses coming from the remote. This process should work on all version of Windows that support the Microsoft eHome Infrared Transceiver. I've tested on Windows XP Pro and Windows Vista Home Premium and it worked on both. However, please note that HIP, Girder and EventGhost can't use the default Windows eHome driver in Vista. On Windows XP these programs are fine, but these programs need the Replacement driver for Vista and I haven't been able to get the Replacement driver to work on 64-bit Vista yet, only 32-bit Vista." [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Event Ghost Plugin For Mediaportal
Contact us
RSS
Top
Bottom