I know, I know, I should be working more on DW3, but I've been setting up my new HTPC lately and came across the need to remap the keys on my remote controls (TinyTwin remote, VisionPlus remote, and SunWave SMR-140). Problem was, the remote recievers for these remotes are HID keyboard devices, so pressing keys on the remote is just like pressing keys on the keyboard.All the key handling applications I tried (EventGhost, Girder, and HIP) were unable to tell the difference between the remote controls and the main keyboard (which I still wanted to be able to use).

So what do you do when you can't find an an application to do what you need? You write your own of course. It's taken me about a month to get to the point where I'm happy enough with the code to share it, but I'm finally there. I wrote more about the development process and how it works on the website.

nate, this looks like a great development. I will try it over the weekend when I get home and report back.I have always felt that the remote supplied with DNTV Live tuners were the weak link, now it appears that your application has plugged the gap. Like you, I had tried EventGhost and HIP to no avail.

That's one weird screenshot. I've no idea why it looks like that. The only thing i can think that might make the gui look odd is using a font DPI other than 96, but I haven't tested this to know for sure. That shouldn't stop the tree view on the left showing up though.

Can you check if there's an exception.log file for me? If it exists it'll be in your %allusersprofile%\KeyboardRedirector\ folder.It's possible W7 has new restrictions on windows hooks that XP and Vista don't.

I run the same resolution as you on my htpc so that's not a problem. I don't have a W7 system at the moment so i can't test that out, but I should have one in a few weeks.

In the meantime I wonder if it's worth trying some of the compatability options (in the property pages of the KeyboardRedirector.exe)

As an aside, I've been crook today so I spent most of the day on the couch using the remote. I only had to restart KBR once after one of the remote keys got stuck down and the Raw Input messages stopped being recieved. So, still a few problems to work out but it's been fairly reliable for me today at least.

No, not self inflicted, and still hanging around so it's not just the weekend. I think I must have caught something on the bus ride I took from Albury to Melbourne on Saturday. The bus was packed with tourists heading from Sydney to Melbourne.

I changed my font size from 125% to 100% and can see KeyboardRedirector fully.

While mapping and changing buttons on my HP remote (non-RC6 sadly) the program occaisionally locked-up. Killed it and restarted OK, and I continued. I've used it in 7MC, but it causes a lock-up there too. If I kill KR, 7MC works straight away.

Any ideas? Is there possibly a text box or something opening under the main window?

There's no error log in KR user directory.

I was hoping to use KR as a "HIP replacement". If I start MC via HIP it doesn't always have focus, which it does when I use KR, even though I start it with the executable not key stroke in both.

I know how to cause it, I don't know if you can (or even want to) fix it. I'm guessing it's not been a problem for you.

As an example, my HP remote has a button, which is the TAB key, according to KBR. When I remap it as Ctrl+D in ehshell, it causes a lock-up of MC until I kill KBR. I tried it with TAB on the keyboard, and it does the same. I also tried it for notepad, same result.

As test, I remapped them as TAB, it didn't lock-up. But it did do TAB twice in MC, but not notepad. I noticed a couple of times when it was remapped as Ctrl+D, it did TAB, then Ctrl+D in MC (on the occasions it didn't lock).

A couple of other remote buttons I've tried do the same. Strangely the button I've remapped to "LWin+Alt+Enter" hasn't caused a lock-up.

Does this only happen with ehshell? I don't have WMC installed at the moment so can't test that, but I've tried out your scenario with a few others apps and haven't had any problems.

I do very occasionally have a lockup on my htpc, but no really repeatable. I did notice one time a problem occured due to an application having it's cpu priority set to high and taking up 100% of the cpu. KBR, having a lower cpu priority, couldn't process the key presses, so input to the application appeared to hang. You could try using task manager to increase the priority of KBR. If this works I could add an option to increase it by default when it starts.

If that doesn't work, it might help if I can get logs of what's happening when the hang occurs.Can you please

Does this only happen with ehshell? I don't have WMC installed at the moment so can't test that, but I've tried out your scenario with a few others apps and haven't had any problems.

I do very occasionally have a lockup on my htpc, but no really repeatable. I did notice one time a problem occured due to an application having it's cpu priority set to high and taking up 100% of the cpu. KBR, having a lower cpu priority, couldn't process the key presses, so input to the application appeared to hang. You could try using task manager to increase the priority of KBR. If this works I could add an option to increase it by default when it starts.

If that doesn't work, it might help if I can get logs of what's happening when the hang occurs.Can you please

Go to this folder. %allusersprofile%\KeyboardRedirector\

Close KBR

Delete the log files (main.log, and exception.log if it exists)

Start KBR.

Swtich to ehshell, press tab to cause the hang.

Kill KBR

Post the contents of main.log, and exception.log if it exists.

No, the lockups also occur in notepad, which I used to test if it was only ehshell or not.

Increasing priority to high didn't help.

I've done as you asked, but after restarting I set TAB as Ctrl-d (HP remote), so maybe you can see it in the log.

I've attached the new main.log, a new execption.log file wasn't created, I've attached the one that was already there. I had to rename them as ".txt" before it woud allow me to upload them.

This means before the crash KBR was getting messages from the raw input API, but wasn't getting any messages from the keyboard hooks. I suppose this could happen if the application in focus was intercepting the hook events before KBR could see them. Which application were you using at the time? Maybe you could see if that's a one off occurance or if you can get a repeatable scenario where the hook messages are missing.

As to the crash, I don't see anything obvious, but then we need to work out the above issue before I can really get useful information from the logs.