2010-06-18, 04:15
jhsrennie Wrote:The ReportMappingTable registry entry is just a long stream of bytes. In my .reg file I split it up into lines of seven bytes to make it more readable. The listing of your registry is laid out as eight bytes per line, but if you rewrite it as seven bytes per line you'll find it matches what is in my .reg file.
So it looks as if the registry has been set correctly, which means the problem must lie elsewhere. You say "I altered the file". Does this mean you edited the .reg file? In that case try with the original unedited .reg file. Also try Remote-XBMC.reg and see if that works. Use the Showkey app to see what if any keystrokes the remote is sending.
I'd be nervous of 3rd party drivers for the remote. Win7 should detect it automatically without needing extra drivers.
JR
Thanks for clarifying the reportmappingtable, I was a little confused.
I didnt edit the .reg file, as in altered i mean i ran the remote-XBMC-asrock.reg file. After doing that though none of the keys would register. I used showkeys to check but there was no commands coming from the remote. I tested with the keyboard to see if the app was receiving properly and it was.
Before running the remote-XBMC-asrock.reg I tested the showkey app and the buttons were registering. some buttons were registering win shortcuts and others were displaying APPCOMMAND.
Pressing play displays WM_APPCOMMAND 46
Pressing the OK button displays the keyboard Return button.
The Nuvoton driver that is installed, which came with the asrock and is also posted as the CIR driver for download on the asrock website is:
Nuvoton W836x7HG CIR Device Driver (for Win 7 64bit)
I noticed just now that this driver and the EHome are both installed. I might uninstall the 3rd party driver see what happens. See if I get any response from the remote with showkeys. If I do I'll have another go at using the remote-XBMC.reg, I wont try the remote-XBMC-asrock.reg first up since you didnt suggest trying that one. If it all works i'll let you know.