@java_guru: try the solution described here.

http://blog.mattgoyer.com/categories/mediaCenter/2004/12/14.html#a3856

I had problems with my MCE remote working with my STB. This helped my issue.

hth,
slang

 

Ok - I will have a test build of HIP for everyone tomorrow, but to assist me in getting the configuration right can anyone tell me:

1) What is the default installation path of EShell.exe

2) Using the programs already available, does the numeric repeat that transposes numbers for characters (like in SMS ie 2,A,B,C) work with the library as it is?

BurningZeRoad - I have another challenge for you once we have this build working.  What would even be way cooler, would be for the dll to allow the input from ANY remote (and not just the MCE remote).  I don't know if that is possible, but presumably if you drop the MCE-specific error checking, and the work out a formula that can produce a unique WParam and LParam values for any remote then we are in business.  Also for my web site, once this build has been road-tested, I would like to give you the appropriate credit and so if you want me to include your real name then PM me, otherwise I will use your tag.

---

Peter (BTMI)

Click here for HIP, the free alternative to control your PC via remote control

1) The default path is C:\Windows\ehome (but mines @ D: )

2) Couldnt tell you. Which programs are you referring to? I assume you arte talking about useing the MCE remote?

Cheers

This deveopement you guy are making, would it in any way enable a USB-Uirt to work in windows MCE as the blaster device? Say if you already have it and you don't have the MCE unit.

Is there anything you guys are stumpling on that would allow HIP to be detected by MCE as a valid blaster in the setup??

Thanks guys!

These developments are strictly for the MCE remote, but HIP already has USBUIRT support and works just fine under MCE for receiving and sending, and I remember reading some mention that the developer of the USBUIRT is working on a direct MCE solution.

---

Peter (BTMI)

Click here for HIP, the free alternative to control your PC via remote control

But when MCE gets to the point where it detects the MCE blaster/remote, since I don't have one it gets stuck. Does your software solve this issue?

Yeah, he told me he's fighting a learning curve. But I guess he'll solve it sometime. What I describe is what he's dealing with too.

First, this is excellent that you guys are solving this problem!  I have been following this thread with amazement.

I for one am excited about being able to control my other AV equipment through my PC using the Microsoft MCE remote.

Unfortunately I have not been able to make it work using your program.

I have MCE2005 and tried installing your MCEremoteTest program.  When I run the program I get:

"Error reading IR"

I also tried installing the drivers to replace my "Microsoft e-home infrared transceiver", from your drivers directory, but got the message

"specific location doesn't contain information about your hardware". 

What am I doing wrong?

A.

@MainDane : MCERemoteTest requires MCEIR.sys driver... I think you don't have exactly the same MCE remote model as mine.
Can you check it in USB driver details that you get something different than USB\VID_0471&PID_0815\PH0014M7 ? If this is the case, just post your device ID here and I will update the MCEIR.inf so you can properly install MCEIR driver... then you play with your remote !

@BTMI : PM in progress... right after this reply !

I think you are right.  I believe I have the Microsoft remote for MCE 2005 (which I thought was identical to the cheaper Philips, but with a 20ft instead of a 10ft range). The driver details in the device instance ID is

IRBUS\VID_0471&PID_0815\6&204FC6A8&0&0001

A.

Your remote shows the same device id but you are trying to update the IRBUS driver (in HID section). You will find the one you should update in the Universal Serial Bus Controllers section.

Hi BurningZeRoad

Is the command line version still available eg MceIrPlay.exe & MceIrRec.exe? I tried the ones your original post refered to but could not get them to work.

Mike

Well, what do you know. It works.:  Thanks!  Sometimes stupidity IS and excuse.

A.

The story so far...

To save people reading the entire post, and to try and explain things in terms that even I can understand (and hopefully be corrected if I get it wrong), this is what this post is all about

XP Media Centre Edition (MCE) has a remote control (a bit like the one that controls your TV). Both the remote and the operating system can be purchased separately and the remote will work to some degree with std XP (although I found that without service pack 2 it was not recognised). The remote allows you to control the PC (which is cool) and you can even teach it the TV on/off and volume up and down buttons so you can perform those functions from the MCE remote (in theory, it did not work for me with my TV).

Some of the buttons send normal keystrokes like {enter}, {up} and {down} which work in any application.

It is also supplied with two "Blasters". These are deigned to allow the PC to send commands to other devices (such as a TV) by simulating a remote control and sending the infra red signals that it (the TV) understands. So if you have a cable, freeview or other kind of set top box, you can get the PC to change the channel of the other set-top-box (provided it is on the Microsoft list). You program the computer to record a program, and the PC will make sure that the set-top-box is tuned to the right channel).

This thread is about using the MCE remote to do more.

1. Use it to control other applications on the PC - If you want to use different DVD player program, you can launch it and control it with the MCE remote.
2. Use it to control other devices, so that you could change the TV power on button to turn on the TV and set it to the correct input for the PC, or set it so that you can change the channel on the TV by pressing the channel buttons on the MCE remote). This would make use of the blaster - you would record the "off" signal that you TV remote sends, and then program the PC to send that same signal if you pressed a certain key on the MCE remote.

All this would be possible with standard XP as well as MCE XP

BurningZeRoad has developed a new driver. A driver is the program that makes hardware (in this case the remote) work. The Microsoft driver sends the remote signals to the Microsoft application that controls media centre. BurningZeRoad's version replaces the MS version and instead allows you to send the "signals" to whichever program you want. He has also created a program (a "dll") that allows other programs to receive the signals, store them and then re-send them via the blaster. The files can by downloaded from http://www.burningzeroad.free.fr/MceIrApi.rar, but these include the source code, which you probably don't need.

Of course a program needs to know what to do with them. Btmi has a program called HIP that is designed to capture the signals from an input device and translate those signals to a message to a program, or to re-send them to a defined device using the supplied blaster. So the plan is that Btmi will change HIP to use the driver and dll create by BurningZeRoad so that you can control what key press does what, and appropriate signal on to a different device (eg a TV)

If you go to http://www.zinfonia.com/hip/mceremotetest.zip you can download the latest solution. This download includes the latest driver as well. You need to update the driver for the remote by following the instructions below (provided earlier by Btmi)

Make sure the MCE remote is installed.

In the Control Panel/System, select the Device Manager button on the Hardware Tab.

In the Universal Serial Bus Controllers section, locate the entry for the remote, right click and select "Update Driver"

- Select "No, not at the time" for the Window Update prompt.

- Select "Install from a list or specific location"

- Select "Don't search. I will choose the driver to install"

- Select the "Have Disk" button and enter the location of the supplied drivers.

- Select the MCE Infrared Remote Receiver option and the rest should be self explanatory.

Easy mistakes to make are

- The remote is listed as an input device as well, but you need to change the driver for the USB device
- To find the driver you need to navigate right to the driver folder and select the "mceir.inf" file.
- Follow the instruction entirely - if you don't the system will most likely find the std MS driver.

Please note that as you are no longer using the MS driver, any keypresses will not control the PC

If you want to go back to the normal driver, just repeat the above but instead of "No, not at the time" click "yes, this time only" and it should find the original driver.

Hi Pallismn !

Your post was too early : I just found the way to do EXACTLY the same things using the original MS driver ! looooooooooollllllll
This just means that this thread can leave the hacks category...
and also that you can remove all the driver stuff from the long story !

I also have integrated the Girder API in the dll so it can be used as a Girder plugin (as receiver only ! not yet blaster...)

@btmi: I will provide you a new MceIrApi.dll tomorrow evening (CET!). I'm too tired to produce robust code for now... I think it's better your beta runs with my own driver (swapping to MS driver won't change a single line in your code).

OK Folks..Here was you need to do..

1) Follow palissmn's excellent post about installing the different drivers and test program to make sure that works (this will not be necessary when we have a new dll to play with)

2) Download and run the following 4.7Mb file http://www.zinfonia.com/hip/HipInstallCompleteTest.EXE

3) During the installation make sure you select the MCE IR Plugin option in the Components page (you will have to scroll down to see it)

4) After installation is complete, start HIP, and Open the Configuration (Ctrl-O) called MCEIR.Hip.  This file contains all of the default key assignments you should need (the Hip Control window is set on the RED button).  You can of course change this to suit your own setup.

5) On the main screen, check that the ehshell program is pointing to the correct directory (if it is not, it will be displayed in gray text, and you should select the folder icon alongside to point this to the correct location).

6) Open up the Preferences (Ctrl-P) and check that the Alternate Input tab is using the MCE Plugin (if it is not, it has not been installed). Click on the Device Configuration button to change any of the driver settings and click OK.

7) Move to the IR Output page which should have the "Use Input Device for IR Output checked". The "Edit IR Codes" button here is where you can learn IR Commands.  To do this, after opening the window you must first click on the "Add Remote" button and enter a definition for the remote you wish to use.  Then you can use the Add IR button to learn a command (you must also select a button from the list to help in identification).  Once entered you can use the Test button to check it out, and the value in the Panel above the Remotes selection displays the command that you need to insert into HIP to send an IR command (you can also copy this directly using "Send IR" button on the Keyboard Editor window available when entering commands).

Save all of the changes, and run HIP and you should be away to go. You can also add other applications and key assignments.

Problems and questions here....

---

Peter (BTMI)

Click here for HIP, the free alternative to control your PC via remote control