IR server Suite and Imon (1 Viewer)

[signuptrash]

awesome!

Do you have a dedicated post where you will post the files when you work it out?

Thanks for your advice and hard work in getting this going.



If you need any help testing, please let me know

 

[frankwaan]

Yeah, if you need anything Simone, just ask.
Also available for testing



Kind regards

 

[chemelli]

Yeah, if you need anything Simone, just ask.
Also available for testing



Kind regards

Do you have a copy of VisualStudio2005 ?

Simone

 

[onyx666]

i also have a firmware with version 0x380102 and cannot get it to work

 

[frankwaan]

Yes, only not in the Mediacenter PC where the problem occurs.
If needed, I can also install it there.

Frank

Yeah, if you need anything Simone, just ask.
Also available for testing



Kind regards

Do you have a copy of VisualStudio2005 ?

Simone

 

[chemelli]

no, not needed on MP itself.

just grab IRSS sources and try to compile them, once you succeed, I'll provide a patch to add more logging.
In the mean time I asked and-81 if I can provide a debug test version...

Simone

 

[frankwaan]

Thanks Simone, I'll try that.
In the meantime: is there some sort of documentation online how I should setup the development envoirement for MediaPortal SVN?

[edit]: I only need to build the .dll , right?

Greets, Frank

 

[Frantid]

I also have problems with the imon remote keys working, being recognized in IRSS. I help can test as well.


I wonder if this could help: (from here by and-81)

[cut]
I don't know how I didn't find this earlier...

Load "regedit.exe" and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da

Then delete the keys from "CodeSetNum0" to "CodeSetNum3".

To make sure you can recover these keys easily should you want to you should save them by using the export function in the file menu.

Once the registry has been changed you will need to reboot for the change to take effect.

This same process can be applied to disable automatic keyboard handling. Just look at the other registry sections under the "Remotes" sections.

Now if you ever want to re-enable the automatic handling of the MCE Remote and MCE Keyboard you just need to put those registry keys back.

EDIT:

You can recover those Registry keys by reinstalling the eHome driver, just go into device manager and uninstall the eHome receiver USB device and then go to the Action menu and select "Scan for hardware changes", this will bring back the driver and the registry keys with it.


If you're just here for the Vista replacement driver then I've forced you to read all that for nothing, just grab the attachment, it has what you want

EDIT:

The driver and source is now available from this location as well (doesn't require forum registration):
MEDIAPORTAL - free MediaCenter HTPC Software - MCE Remote Replacement Driver

I should also have mentioned that there are limitations that I've found with the Replacement Driver compared to the default eHome driver. Firstly, the Replacement Driver doesn't handle suspend/resume very well. And secondly, the Vista default driver is much better at dealing with learning and blasting IR. Thirdly, the replacement driver won't work with some of the newer Vista MCE remote devices.

[cut]

I wonder if removing these registry entries would cause the remote keys to be seen and not processed by Windows first?

Unfortunately, I can't use this because, my only keyboard (diNovoMini - wireless bluetooth mini-keyboard) gets disabled when I remove these registry keys. So I can't test it. I just thought it might help someone else or maybe give an idea where things are getting intercepted. My family is hooked on youtube & wikipedia on the htpc, so I need to use the keyboard.

frantid

 

[chemelli]

New version of IRSS posted: https://forum.team-mediaportal.com/337960-post583.html

Simone

 

[frankwaan]

Hello Simone,

Still having detection problems, logs are attached.

Greets, Frank