Using GBPVR With "Fake MCE Remote

[Melloware]

Depends on your remote but I may be able to get it supported in my Intelliremote software. Check out this thread for possibly supporting it....

http://forum.melloware.com/viewtopic.php?f=1&t=6180

[carpeVideo]

I would try eventGhost - I have it working with an iones libra remote transceiver and my hauppauge remote. For some reason I noticed the libra receives the hauppauge signals and gives EG an MCE code for each key.

[bluphant]

Dunno what I did right, but got XP to recognize my remote, at least in driver. Now I've gotta work with HIP.... tonight

[bluphant]

Fighting with HIP. Apparently I have a v1 remote, so I can't use the alternative driver. Working through the configuration, right now I'm getting double keystrokes. But, it's closer than it's been. Kudos to the wiki people for a very informative article on how to get this working. Appreciate the efforts!

-Blu

[Loomy]

It most definitely has a mouse control pad.

Not sure if everyone knows this or not, but if they don't: Real MCE remotes do the same thing in windows. People who use mce remotes with custom software install a custom driver which intercepts and kills those mouse/keyboard commands, so that macro programs can use the input alone. There is an alternative workaround which involves keeping the default windows driver, and disabling the usb input device driver that is installed, which kills the initiation of the keyboard/mouse commands, but leaves the device as interceptable by macro software. Both the replacement driver and the default driver workaround for the real mce remote can be found here: http://forum.team-mediaportal.com/mce-re...ete-29024/

[bluphant]

Yeah -- mine is apparently an early version of the MCE remote that cannot use the replacement drivers (v1 or some mess) BUT! I did find a solution that seems to work top notch. My remote uses Irbus.sys for the driver.

I'm using HIP, with MCE Remote for input and keyboard output. This worked fine, but I had the standard doubling of most (all?) commands. So I made my own variation on the recently updated advice at ByRemote I went in to the registry

Code:

Load "regedit.exe" and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da

Then delete the keys from "CodeSetNum0" to "CodeSetNum3". To make sure you can recover these keys easily should you want to you should save them by using the export function in the file menu.   Once the registry has been changed you will need to reboot for the change to take effect.

This same process can be applied to disable automatic keyboard handling. Just look at the other registry sections under the "Remotes" sections.

Now if you ever want to re-enable the automatic handling of the MCE Remote and MCE Keyboard you just need to put those registry keys back.

I repeated this process (after doing a backup of this branch of my registry) for each remote in the tree, not just the one specified.

Rebooted, and all is well, everything works great!

-Blu

[webserverdude]

Depends on your remote but I may be able to get it supported in my Intelliremote software. Check out this thread for possibly supporting it....

http://forum.melloware.com/viewtopic.php?f=1&t=6180

I did check out your software and it only seemed to recognize the "media keys" (play/pause, stop, next track, previous track) I am trying to use HIP, but I cannot get it to start on system boot (my system runs GBPVR from a shell and automatically logs in.)

[webserverdude]

Not sure if everyone knows this or not, but if they don't: Real MCE remotes do the same thing in windows. People who use mce remotes with custom software install a custom driver which intercepts and kills those mouse/keyboard commands, so that macro programs can use the input alone. There is an alternative workaround which involves keeping the default windows driver, and disabling the usb input device driver that is installed, which kills the initiation of the keyboard/mouse commands, but leaves the device as interceptable by macro software. Both the replacement driver and the default driver workaround for the real mce remote can be found here: http://forum.team-mediaportal.com/mce-re...ete-29024/

I could not kind the registry keys specified in the given link post. Read my above post to see the "solution" I have resorted to.

[bluphant]

Update: Windows XP Professional Service Pack 3 includes the eHome Receiver drivers by default. It will detect it as unrecognized, select choose driver, and select Microsoft eHome Receiver.

I did a OS wipe/restore now that I have my new box (Dell GXPro 270) - much, much easier this time. By the way, GBPVR works a lot better going from 1gHz celeron to 2.6gHz P4 w/ Hyperthreading

Regards,

-Blu