My AD12 was a pain to setup but here are some tips based on what worked for me:
First you need to find the right registry location for your remote :
- install XBMC MCERemote (Program Add-ons) - it contains a file 'D:\Users\Shared\AppData\Roaming\XBMC\addons\plugin.program.mceremote\resources\data\CreateTestConfig.reg' (you can uninstall it after)
- get ShowKey from here - http://xbmcmce.sourceforge.net/
- backup your HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\HidIr\Remotes
- Update CreateTestConfig.reg to match the remote ID in your registry.
- Save and merge the registry and restart you computer
- use ShowKey to see if your keys were remapped - all possible keys would have been re-mapped, keys that before didn't function in ShowKey should at least now register some keyboard sequence - if nothing has changed repeat above for the other remote IDS until you find the correct one.
So now using ShowKey and the backup version I was able to cross reference the pressed keys against the entries. For example let's say I pressed the red colored button and ShowKey displayed shif-alt-0 - that means in the test config - FB,00,00,00,04,06,27 in the backup original reg file I would find the entry FB,00,00,00,xx,xx,xx and change the xx,xx,xx to whatever I wanted it to map (use the CreateTestConfig.reg file for reference). However this didn't work for one keys for me, it just didn't match what ShowKey was saying - to track that one down I went through the original registry file and mapped each unknown key , rebooted, and tested in ShowKey one by one to find it. The key in question is to the right of the [T] key and I mapped it to the right click context menu.
You can see my AD12 remote registry file here: http://danielsokolowski.blogspot.ca/2013...emote.html
Joined: Jan 2013
2013-01-19 10:07 Post: #11
(This post was last modified: 2013-01-19 10:08 by danielsokolows.)
Joined: Nov 2012
2013-01-19 13:17 Post: #12
(2013-01-19 10:07)danielsokolows Wrote: My AD12 was a pain to setup but here are some tips based on what worked for me:
Thank you for your tips, Daniel. But I've the same problem Zissakos reported in your blog. I guess the big difference between ZBox Nano AD10/AD12 and non-Nano ZBoxes, is the integrated IR receiver on the Nanos. I guess you have to enable it in BIOS, and then install ITECIR driver from Zotac (Version: v188.8.131.52 for Lenovo v1.00 Beta01, Driver Date: 07/13/2010, Release Date: 04/06/2011). So when non-Nano users just use the external IR receiver, the mapping for the remote is different. Can you confirm you're using ITECIR driver?
I've grabbed CreateTestConfig.reg and I'll do some testing.
Please notice this subject has been quadruple posted, although most useful information is in this thread and the first one listed below:
Zotac Nano AD10 remote issues
Zotac ZBOX Nano AD10 remote is driving me crazy !! (this thread)
Zotac Zbox AD10 Remote problems