Has anyone fixed the text input in mce with the ATI remote yet? I can't seem to find a solution for it... tried mapping it to numpad keys,regular numbers and all combinations of ctrl, alt and shift with no luck.

 

Any ideas?

To be able to find out the right way to send these numpad keys, I think the best thing would be to run a Windows message "spy" utility (like Spy++ bundled with Visual Studio) on a system equipped with the standard MCE remote control. Unfortunately, this rules out the systems owned by most people interested in this thread.

Anyway, then it would be possible to see what WM_xxx messages, and with what parameters, are being sent to ehShell.exe and we could try to duplicate the behaviour.

//Mike

You're right... maybe someone with an MCE remote could do this for us and post his or hers findings here... anyone interested??

 

Thanks in advance!

I am having trouble with play\pause and stop - media playpause do not work, when I push them a little box pops up at the bottom left corner of the screen as say media playpause but it doesn't. If I fast forward or rewind I can't get it to play again.

I realized I had a friend at work using the standard remote with his MCE system. Running Spy++ on his system and typing "4" twice (to get an "h") revealed the following:

<00258> 000301DC P WM_KEYDOWN nVirtKey:'4' cRepeat:1 ScanCode:05 fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<00259> 000301DC P WM_CHAR chCharCode:'4' (52) cRepeat:1 ScanCode:05 fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<00260> 000301DC P message:0x0402 [User-defined:WM_USER+2] wParam:00000000 lParam:00000000
<00261> 000301DC P message:0x00FF [Unknown] wParam:00000000 lParam:006802E9
<00262> 000301DC P message:0x0402 [User-defined:WM_USER+2] wParam:00000000 lParam:00000000
<00263> 000301DC P WM_KEYUP nVirtKey:'4' cRepeat:1 ScanCode:05 fExtended:0 fAltDown:0 fRepeat:1 fUp:1
<00264> 000301DC P message:0x00FF [Unknown] wParam:00000000 lParam:006902E9
<00265> 000301DC P message:0x0402 [User-defined:WM_USER+2] wParam:00000000 lParam:00000000
<00266> 000301DC P WM_KEYDOWN nVirtKey:'4' cRepeat:1 ScanCode:05 fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<00267> 000301DC P WM_CHAR chCharCode:'4' (52) cRepeat:1 ScanCode:05 fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<00268> 000301DC P message:0x0402 [User-defined:WM_USER+2] wParam:00000000 lParam:00000000
<00269> 000301DC P message:0x00FF [Unknown] wParam:00000000 lParam:006A02E9
<00270> 000301DC P message:0x0402 [User-defined:WM_USER+2] wParam:00000000 lParam:00000000
<00271> 000301DC P WM_KEYUP nVirtKey:'4' cRepeat:1 ScanCode:05 fExtended:0 fAltDown:0 fRepeat:1 fUp:1
<00272> 000301DC P message:0x00FF [Unknown] wParam:00000000 lParam:006C02E9
<00273> 000301DC P message:0x0402 [User-defined:WM_USER+2] wParam:00000000 lParam:00000000

The 0x00FF message is particularly interesting as this is the WM_INPUT message and tells us that MCE is using raw input (an application needs to ask for it to get these messages). Within this message there is information about what type of device generated the input (RIM_TYPEHID, RIM_TYPEKEYBOARD, RIM_TYPEMOUSE) where RIM_TYPEHID means "other Human Interface Devices".

My guess is that MCE only does the text message style input when input is coming from something that looks like a remote control, or at least isn't the keyboard. The next step in this adventure should be to write a little utility that registers for raw input and writes out the interesting fields so we can see how these fields are actually set. I can arrange to try it on my friend's system and then compare the raw data with the one from my Remote Wonder. So, any volunteers for this?

If we can verify the above, the fix would then be to get RwKeyMaster (or something similar) send its keystrokes in "HID" style.

WM_INPUT docs: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/userinput/rawinput/rawinputreference/rawinputmessages/wm_input.asp

Raw input docs: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/userinput/rawinput.asp

//Mike

Any chance of getting this effort resurrected?  I would really be thrilled if I could get my Remote Wonder II to input letters instead of just numbers from the number pad.  I unfortunately no nothing about programming so I am not much of a help but with the information from the last post hopefully someone could come up with a solution!

perhaps you should watch here,

(probably you allready did )

http://remotew.free.fr/plugins.htm

 

any progress yet

Perhaps I am missing it.  But I have the things Mike Suggested and installed.  But When I try to run My MCE 2005 TV setup it is saying unable to find IR device.  which this is because the Remote Wonder I have is RF..  Is there a way to get it to recognize this???

 

Here is my DX Diag Details:

 

---

here are 10 types of people in the world; Those who understand binary, and those who don't.Tr

The Remote Wonder setup installation outlined in my post has nothing to do with any IR device. The remote's RF signal enters the computer through a USB device (ATI Wireless Remote Receiver V2.36 in my Device Manager) and RwKeyFactory then translates this into keyboard input. So MCE will never see any IR input, it will believe you are using the keyboard (and mouse).

The only reason I can think of why MCE would complain about IR during TV setup is if you are receiving your TV signal through a set-top box. In this case MCE wants an IR Blaster to change channels on the box (this blaster is bundled with the MCE remote AFAIK).

//Mike

Hello,

Thanks you for this great topic. It almost works on my HTPC.

In fact, I have only one problem with the remote. The numbers 0 to 9 do not work as expected. They do nothing. Only the 6 act as channel-.

Does somebody know why this can happen ?

Elgarv

Sounds like the wrong keycodes are sent for the numerical buttons. Verify by pressing the keys while Notepad has focus and see what is typed into the editor. If numbers are not inserted in the editor, then check your RW Key Factory settings. For "0" my setting is:

Number 0 | Simple: Action=On, Modifiers=-None-, Key=0 | Enabled=Yes

//Mike

nice job on the Ati... Is there a way to build the Nvidia remote into a MCE remote?

---

GRRrrRR @ MCE

Thanks mikewse for your quick and useful answer.

Effectively, when tested in Notepad, I found that the keys returned for numbers was the keys without Shift key on my "french" keyboard (I forget to tell you that I am French).

So it has been very simple to correct my problem by adding a Shift flag for all number keys.

I think I will post my french configuration file to the RW Key Factory web site.

Elgarv

Well, the Nvidia remote is an X10 device very similar to the Remote Wonder I, right? If RW Key Master isn't doing the trick for you (maybe only compatible with the ATI version?) then I would recommend trying other generic X10 applications, like x10rc.

Note that you will want to run the X10 device driver delivered with your Nvidia remote but NOT the separate application communicating with this device and sending the appropriate key presses to Windows. The latter will probably have a tray icon and its own process.

All this stated without ever trying an NVIDIA remote

//Mike

Thnx for the tip... its just I dont really get what your saying... I have to have another program that sends keystrokes to windows instead of the NVremote?
if so...
How do I seperately delete the driver?

and I don't see a tray icon because the driver is installed along with the forceware programs. And I seriously doubt if it will recognise my tv tuner without those

---

GRRrrRR @ MCE