Can MCE remote work without MCE?

[Mucaro]

Sonoma03, I started re-reading this thread, trying to understand why you are still having problems. Soon I realized that you have "an MCE compatible remote and receiver", not the "regular" MS MCE remote/receiver. :eek: (Initially I thought you had a Hauppauge card with an MS remote/receiver combo)

Sorry for misleading you into trying the replacement (MS) MCE remote driver. The replacement driver is for the Microsoft MCE remote's receiver only.

I'm glad you are close to solving your issues.

[Squid]

Just to follow up, I have been exchanging email messages with Hauppauge technical support. The support person told me that the SMK remote receiver that I have is for Vista only,

I tried that and didn't have the patience to get that far.

Congratulations

[dhbernard]

I was able to get the MCE remote control and reciever that comes with the PVR-500 MCE Kit to work with the eHome Infrared Receiver driver from Microsoft and Hip. Through trial and error over several days I was able to collect the following information that allowed the receiver to work with the native MS eHome drive and not have the 'Sticky Key' issue. Here is what I did.

1) obtained the MS eHome IR driver (see post #15 and others.)
2) Extract the files and modify the inf file to add the RX0000-0141E's VID and PID.

%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0609&PID_0334

3) install the driver by pointing to the inf file you modified.
4) once the driver is loaded you will need to make some registry changes.
This information can be found here. http://forum.team-mediaportal.com/mce_re...ent+driver

<QUOTE>
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.
<QUOTE>

I then use the attahced HIP config.

I can now use the MCE remote to fully control GBPVR with out the sticky key issue.

[Melloware]

For an easier solution to map your MCE remote or Creative remote to use GBPVR you might want to look at Intelliremote. It is vastly simpler than EventGhost and Hip yet much more powerful and easy to configure. Want to start GBPVR with the Green Button? No problem. Want to have one set of remote mappings for GBPVR and a completely different set when you are in Itunes? No Problem. Intelliremote will even notice when you change applications and switch remote profiles for you.

Check it out...

http://www.intelliremote.com

[Squid]

Woo! Thanks dhbernard. I had given up and I was *so* close. My plan was to modify the codesertnumx keys to remove the sticky key problem, but I just couldn't make heads or tails of it and I couldn't figure out how to "sniff" what the remote was sending.

Thanks again for posting your solution.

[dtronvig]

1) obtained the MS eHome IR driver (see post #15 and others.)

Hey dhbernard,

Thanks for working this out. Simple Plug'n'Play, right?

I'm not sure what file I should download from where to get the driver. Post #15 doesn't appear to give a link. All I can find are references to the rollups KB905213 and KB912024. These download as exe files. Can I somehow extract the relevant file(s) from those? If not, I'd love to get a link to the right file.

Thanks,
Drew

[kayleigh]

You can use a command line to extract the files from any MS KB file. Use the command:

KBhotfixNumber.exe /X:C:\path\to\files

[dtronvig]

Will try.

Thanks,
Drew

[dtronvig]

Sorry if I'm a little dense on some of this stuff, but I think I need a little orientation.

1) obtained the MS eHome IR driver (see post #15 and others.)

This would be just KB912024, yes? That update looks like it completely supercedes KB905213.

2) Extract the files...

With 7-Zip I can extract _sfx_.dll, _sfx_0000._p through _sfx_0015._p, and _sfx_manifest_. The manifest file apparently gives the filename and the path inside the Windows directory for each ._p file. I'm not sure what the filenames to the right of the ._p entries mean.

...and modify the inf file to add the RX0000-0141E's VID and PID.

%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0609&PID_0334

That would be irbus.inf? Modify the inf file using what? I've Googled onto the CMAK Wizard and Autorun.inf Editor. I can't figure out where to download CMAK Wizard, and I'm guessing that Autorun.inf Editor is kind of oriented towards autorun.inf files. Could I maybe just get a modified version of the relevant inf file from someone?

3) install the driver by pointing to the inf file you modified.

Would that be pointing to it in Device Manager or what? Honest, I don't know.

I really appreciate the solution, but this is new territory for me.

Thanks,
Drew

[dtronvig]

Okay, I finally did the "KBhotfixNumber.exe /X:C:\path\to\files" operation, and I see how that extracts the files with the right names in the right folders. I should put that file and folder structure into the Windows root folder, yes? That takes care of the first half of part 2.

That helps a lot, but I'm still unclear on the rest.

Thanks for any help,
Drew