Search the Community

First of all, I blame myself for not researching this receiver more. I bought another receiver a while back and it "just worked" with my WMC remotes, so I expected Flirc would, too. I didn't realize that it merely mapped IR signals to keystrokes. I have a WMC remote that, I think, came with one of my Hauppauge tuners. (It's been years.) The keys are the same as the Rosewill RHRC-11002, but its shape is more like the Adesso ARC-100 remote (but it's black). Keys http://amazon.com/gp/product/B005ZAK50K Shape http://www.amazon.com/Adesso-Media-Center-remote-control/dp/B000XVNJRM It was nice to get an e-mail about the product before I had even received it. It gave me the feeling that Flirc was truly interested in providing a good customer experience. I like the simple setup and driver installation that automatically updates the firmware (if necessary). The key-mapping portion is very easy to use as well. I suggest improving the method of selecting the configuration though because it's not obvious at startup that the user should do that first. Maybe a panel could be added on the side that lists the available configurations and highlights the selected one. Unfortunately, after installing and configuring my Flirc, there are a few problems with the way I want to use it. 1. Using the WMC configuration, there are a number of missing (and important) buttons: Windows button ("The Green Button") Record Standby Go to TV recordings Go to Guide Go to Live TV Go to DVD Player I don't know if there are equivalent keystrokes, so I'm not sure if it's possible to map these, but it'd sure be nice. The Green Button is weird, because it seems to work sometimes. That might be related to point #2 below, but I haven't had a lot of time to experiment yet. I'll update this post with more info if I have any. 2. I must press a button on my remote twice in order for WMC to respond. This is , pretty obviously, a deal-breaker, and I think, regardless of its support for WMC remotes, this is something Flirc needs to fix (or tell me what I'm doing wrong, which is certainly probable). :-)