usagent27
Junior Member Posts: 5 Joined: Apr 2012 Reputation: 0 |
2012-05-02 01:24
Post: #31
following the steps above worked! the info button works! how do i get the red button to bring up the context menu? just enter "C" on the remap page?
|
| find quote |
jhsrennie
Team-XBMC Developer Posts: 7,237 Joined: Nov 2008 Reputation: 117 Location: Chester, UK |
2012-05-02 11:19
Post: #32
If you used the mapping file from the post I linked to your red button will be sending the keypress ctrl-alt-1 so you need to add a mapping for this. Grab KeyMapEdit from http://xbmcmce.sourceforge.net/. Run KeyMapEdit, select "detect keypress" from the KeymapMenu and press the red button and you should see the add key dialog. Set the action to "ContextMenu" then close KeyMapEdit and save the changes.
|
| find quote |
jsmith432
Junior Member Posts: 5 Joined: May 2012 Reputation: 0 |
2012-05-07 02:12
Post: #33
Hi all,
I just bought a Nano AD10. I am not able to use the onboard CIR receiver as the driver is not installing on my Windows 7 SP1 64 bit. I am using the dongle that came with the box, and everything is working on XBMC except the color keys and the info key. After importing the reg file that is posted on this thread, I tried to use showkey.exe to see what is being sent, but when I press the colored keys or the i key, nothing happens, it is like I didnt press any buttons. Do you guys have any idea how to work around that using the "dongle" that comes with the AD10? XBMC rocks and I just want to have most used features like info and subtitle menu on the remote control, that would be perfect. Regards, Johnny |
| find quote |
jhsrennie
Team-XBMC Developer Posts: 7,237 Joined: Nov 2008 Reputation: 117 Location: Chester, UK |
2012-05-07 10:17
Post: #34
The .reg file only works if the receiver is using the eHome driver. See http://wiki.xbmc.org/index.php?title=Usi...in_Windows for how to check this.
|
| find quote |
jsmith432
Junior Member Posts: 5 Joined: May 2012 Reputation: 0 |
2012-05-07 19:32
Post: #35
Hi jhsrennie, I knew my attempt to put the .reg file using the dongle was a long shot. The dongle is not eHome driver.
Any suggestions to do this without this driver? |
| find quote |
jhsrennie
Team-XBMC Developer Posts: 7,237 Joined: Nov 2008 Reputation: 117 Location: Chester, UK |
2012-05-08 11:39
Post: #36
I thought the AD10 receiver was an eHome device. Maybe the attempt to install the CIR driver has messed things up. You could try a from scratch reinstallation of Win7 and see if the IR receiver is correctly detected. I can't comment any further without an AD10 to test.
|
| find quote |
usagent27
Junior Member Posts: 5 Joined: Apr 2012 Reputation: 0 |
2012-05-09 13:09
Post: #37
from what i know the usb reciever is not compatable. disconnect it and the reg file works. hope this helps
the internal is the one using ehome driver |
| find quote |
jsmith432
Junior Member Posts: 5 Joined: May 2012 Reputation: 0 |
2012-05-11 04:38
Post: #38
Yeah, the internal is not working for me... I think it is a driver issue. I can't get it to install.
Can someone that has the ad10 with the internal working send me a screenshot of the device manager with Human Interface Devices, Keyboards, and Mice and other pointing devices expanded? I am trying to install the drivers manually but the inf files have several. |
| find quote |
jsmith432
Junior Member Posts: 5 Joined: May 2012 Reputation: 0 |
2012-05-15 22:20
Post: #39
Nevermind, got it to work. Thanks.
|
| find quote |
Broken9754
Junior Member Posts: 40 Joined: Jun 2012 Reputation: 0 |
2012-06-12 02:33
Post: #40
(2012-05-15 22:20)jsmith432 Wrote: Nevermind, got it to work. Thanks. Mind posting how? I just picked this unit up, and can't get any response from the internal IR receiver, which is enabled in bios. I (think I) even managed to manually get the drivers installed, as I now have something that says "microsoft ehome" in driver manager which installed itself after I manually installed the ITECIR infrared receiver driver to the HID device that is located on PCI standard ISA bridge... But it still doesn't work, like at all. The USB extension works in that it responds to key presses, but then infinitely loops whatever I just hit. No combination of any of the various driver options has gotten the internal receiver working for me. I'm about to just cave and buy a separate remote here... EDIT: And through the magic of, "as soon as you post something asking for help it'll just suddenly work," as soon as I posted this it just suddenly worked.
(This post was last modified: 2012-06-12 03:26 by Broken9754.)
|
| find quote |

Search
Help