[OBSOLETE] MCE Replacement Driver (1 Viewer)

[Darth Androi]

The keyboard doesn't work out-of-the-box with the replacement driver, and you have to configure the remote in IR Server with the replacement driver; that's why and-81 is advocating using the standard driver.

and-81: Supposedly lirc for linux has support for my remote. I plan to go test it out in a few minutes. Here's the driver that they use: SourceForge.net Repository - [lirc] View of /lirc/drivers/lirc_mceusb2/lirc_mceusb2.c
Hope it helps shed light on this situation.

 

[and-81]

Darth Androi:

Let me know how it goes ... you still might have a faulty remote ...

I'll look at the lirc code and see if there is anything I can use ...

Thanks,

 

[stprules1]

thanks for your help guys. It turns out that I had the vista remote package and not the "XP Media center package". Big difference. Hey by the way I am using the wireless keyboard now, It's great.

 

[limpwhizkid]

Hello,

Since I am running Mediaportal now on XP SP2 (NON MCE)..
I find it impossible to get the remote to work .. it seems to only work for an MCE edition of XP.

Does anyone know if this package for download in this thread does the trick ?

I have 2 remotes now

both usb receivers.. one says it is BB+ dongle (e.d.)
and the other one says (emulator 2006 device (or something)..

As I have read several forums and threads.. the drivers seem to be in an MCE remote update rolluppackage.. what doesnt help me very much since I like to run XP normal version

Thanks!

 

[Darth Androi]

You can download the updates manually from mocrosoft's website. Just find the name of the package you need and then search MS's site for it.

 

[limpwhizkid]

You can download the updates manually from mocrosoft's website. Just find the name of the package you need and then search MS's site for it.

They actually do install .. on normal XP.. i am very surprised.. ..

I actually did not expect that.. so never tried.. but your post made me try.. just to get a screenshot of the expected " youre not running Media center edition blabla" which never came..
so thanks !

 

[bandyTA]

Hi Guys!

I'm a bit confused. I have an MCE remote clone, but it has an RF-USB interface, not IR. The device works great with MS own MCE front-end, but not well with MP. The best I can do, is check the HID device in MP config, and use not of all button on the remote. The My videos, My music, etc. won't work. More button won't work, and the colored buttons won't work to. What can I do? I check the USB input the OS has see there is some signal, but can’t assign any command for those buttons. This is a CONCEPTRONIC RF MCE remote….. Thanks any help!

Conceptronic.net

 

[nobbly]

Sorry mate, I really can't offer any advise in regards to Girder. I don't use girder. The only thing I can suggest is to use the mce replacement driver plugin for girder but with the modified registry settings with the default driver. If you haven't already tried that.

Perhaps I didn't make it clear in my above post the reason why I was posting. To put it bluntly, your statement that 'the Replacement Driver is obsolete' appears to be incorrect. In your original 'unedited' initial posting, which detailed the first method (which was then edited out by you and replaced with the second method), you made it very clear that the method worked with Girder and HIP when using Bruno Fleurette's MceIr.dll. In that original posting you provided a zip file entitled 'Why the MCE Replacement Driver is now obsolete.zip'. Within this zip file was a text file in which you stated:

Once you've disabled the automatic handling you will need some other software
to pick up the task. Most third party remote handling programs (like HIP,
Girder and EventGhost) should have no problem with this because they access
the device directly instead of going through the HID driver.

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 as I write this HIP, Girder and EventGhost can't
use the default Windows eHome driver in Vista. On Windows XP these programs
are fine because they use Bruno Fleurette's MceIr.dll, 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.

However neither the first method or the second method (of just removing the registry entries and rebooting) work with Girder when using Bruno Fleurette's MceIr.dll. And I suspect that these methods also do not work with HIP (unless you know better). I would have thought that if it had been so easy as to just remove the three registry settings, that Bruno Fleurette would have sussed this out rather than go to all the trouble of creating the replacement driver.

I originally posted above to point out that your methods do not work in Girder, as you did state that they would.

The only statement that appears to be correct and currently verifiable, is that for your own application (which looks very promising) you no longer need to use the replacement driver. What I am really rather disappointed at is that you appear to then jump from this and state that all the other remote control applications no longer need the replacement driver, when actually it appears that they still do need the replacement driver.

In fact, the replacement driver is far from obsolete for those that do not use your software. For many who use Girder and HIP etc, the replacement driver is essential as there appears to be no other way to bypass the eHome driver.

The only way of getting your second method to work in these applications, is to use their built in HID support. But this is wholly different to using the replacement driver as you can no longer use different remotes and have to use the original MCE handset. The benefit of the replacement driver is that you can use many other remotes including the original MCE handset.

To conclude, I think it is only fair to those that have read your statements and then spent some time trying to get your methods to work and then only to find that they don't (such as myself) that you:

1. Explain fully why you have made the statement that your methods work with the applications, when it appears that at least in Girder they do not (and I suspect they do not in any other application you quote);
2. That you re-edit your first posting to make it clear that the replacement driver is only obsolete when it comes to using your own software, and that the replacement driver is still probably needed for all other remote control software such as Girder/HIP etc.

Of course, if I am completely wrong in this, and your methods do actually work as you state in Girder/HIP etc, then please let me know (or anyone else who has tried to get these methods to work, please post!).

PROBLEM SOLVED!

The reason why the method of using the ehome driver and registry modifications with Bruno Fleurette's original MceIr.dll and Girder did not work on my system was that apparently the original MceIr.dll has a bug which means it tries to communicate with a couple of USB DVB-T boxes I have installed (Nebula DigiTV units), and I quote from http://www.digitv-forum.co.uk/viewtopic.php?t=2153:

"There is a bug in an earlier version of the MCEir.dll (ie nothing whatsoever to do with DigiTV), that causes it to try to talk to the DigiTV USB device, rather than talking to the MCE IR receiver. This causes bad things to happen. I (HR) fixed the MCEir.dll code a while ago (thankfully the source was available, and thanks to Anarchi who reported the problem) and provided the updated version to the author of HIP."

I can confirm that it is also a problem when using Girder as the version I have (3.3.10) also uses the same MceIr.dll as HIP (http://www.byremote.com.au/HIP/Default.htm). The problem disappears when the USB DVB-T units are disconnected and then the 'ehome driver method' works exactly as if the replacement driver were being used.

The updated MceIr.dll by HyperReality (HR) is available from here:

http://www.byremote.com.au/downloads/default.asp?SCLASS=HIP EXTRA

This works in Girder and allows the 'ehome driver method' to work when the USB DVB-T units are connected.

This bug could be unique to when these specific USB DVB-T units are attached, although if anyone else is having the same problem of not being able to get the 'ehome driver method' to work then it could possibly be due to the bug in the original MceIr.dll causing problems with similar USB devices attached. If so, then use the updated MceIr.dll from HyperReality in the link above.

P.S.: Apologies to and-81 for my rather harsh second posting!

 

[flippado]

Hi folks!

Could someone help out bandyTA!??

I have a similar problem, only my remote is SL-6399 from Speed-Link (USB connected, I think it simulates a keyboard, but you should know better than me…)

It worked fine with windows XP MCE 2005, now I have only have windows XP with MP installed, and only some buttons work…

Pleeeeeeeaaaaasssssssssseeeeeee!! HELP! I’m tired of reading posts in forums!

Btw I would like to use the remote also on BSPlayer, but that’s another story… But if someone recommends a better player to use… an easier one to use the remote on!

Speed-Link SL-6399

 

[and-81]

bandyTA & flippado:

I believe both of you have remotes that are "mce compatible" in so far as they will work with the Media Center software, but they are completely incompatible as far as the hardware/driver are concerned.

They work with Windows Media Center because they simulate the keyboard button presses the same way the genuine MCE remote would... but that is where the similarity ends unfortunately.

To get them working with MediaPortal your best bet is to try the HID input plugin. Alternatively you could try one of the third party apps like HIP, Girder, EventGhost and IR Server Suite and see if you can get them to work. Just don't expect the MCE Remote support in any of those applications to help you, you'll more likely get it working with HID or "Keyboard" input support.

As this does not relate to the MCE Replacement Driver (which only works with compatible hardware) please create new posts outside of this thread if you'd like to continue discussing these remotes. I know you can't of know they were incompatible before, so please don't think I'm giving you a dressing down.

nobbly:

Interesting, it must be due to the way the mceir.dll addresses the device (conflicting GUID's or some such thing) ... I'll look into it further and try to find out exactly what HyperReality did to fix it in his copy ... Given that Bruno's code was open source I expect HyperReality will have released his source modification ...

Cheers,