A very old subject I think, but new to me. I have an XPC-RC01 remote for accessing media center on my windows 8.1 HTPC.
I can't seem to capture the codes with my MX-3000 and make them work. I understand there is an enabledebounce setting in the registry that might need to be reset to a 0 from a 1, but I can't find that DWORD. I get to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\ but can't find Remotes listed.
Am I hunting in the wrong place?
I've tried the pre-programmed codes in the library using AUX\Microsoft\Library#1 and all the rest of the libraries and they don't work either. The XPC-RC01 remote works fine, but I can't get ANY response from the MX-3000.
Any suggestions???

Update:
I did find Remotes under the following: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da

I edited the enabledebounce to a zero and restarted the computer. Still no activity with the library of Microsoft codes.. I'm baffled..

Really, nobody has any ideas? I'm sure with all the awesome talent that uses these forums, somebody has crossed this bridge successfully.

That particular remote uses a one of a kind protocol that's very hard to learn and is nothing like Microsoft (MCE or RC6) codes. So none of those codes will work. No built-in codes will work. No registry changes can make them work. I highly recommend you get a different remote and dongle that specifically says it uses MCE, RC6 or Ortek protocol. If you can afford an MX-3000, you can certainly afford a decent MCE dongle.

The JP1 community (Vicky) figured out this protocol a few years ago which turned out to be close to a Mitsubishi protocol but not quite, hence throwing off your remote's learned signal analysis. Details are in the thread below. But I wouldn't waste any time or effort trying to convert it to pronto hex.

[Link: hifi-remote.com]

If you insist on making your old dongle work, you'll have to figure out how to create an IRP for it in order to use IRScrutinizer to generate the pronto hex. That part is way over my head, but if you post in the thread above, someone may be able to help you figure it out.

Thank you so much for the response. Certainly, another remote is easy to acquire. Knowing that this protocol is unusable is what I needed to hear. I'd tried everything that I could think of. It was a remote that I had lying around from before I set up my HTPC. I'll switch to another with MCE coding now that I know that is the problem. Again, thanks for the reply.

mdavej,
If you've got a moment, can you lead me a bit on this. I purchased a Rosewill
RRC-126 for the HTPC I referenced above. It is an MCE/RC6 remote. It controls the PC fine but once again, I am not able to learn the commands into my MX-3000. What am I doing wrong?? I've learned a lot of remotes over the years, but these latest attempts are making me wonder what the heck I'm doing wrong. Any thoughts or suggestions??

Sorry, I have no idea how to learn on a MX-3000, but I would be very surprised if it didn't have MCE codes built in. If it doesn't, just import pronto hex:

[Link: cetoncorp.com]

mdavej

For closure on this issue. First, thanks for the HEX codes. I ported them to CCF files and imported into the MX-3000. No luck. Then I imported the HEX codes directly into the MX-3000 with the universal browser. Still no luck. Then the thought occured that maybe my 3000 built-in IR blaster wasn't working. I connected a bug to my RF module and placed it on the receiver and bingo! The 3000 had its RF and IR turned on for all codes, but somehow the blaster had failed and wasn't transmitting anything. Now all codes (including the pre-programmed Microsoft codes in the database all work fine. Also had to add three repeats and edit the debounce registry setting (both of which I had tried before the bug ir bug fix). Geez..... It's the simple things in life, huh???
Thanks for reaching out to me.

Sure thing. Glad you figured it out.