Apr 15 2008, 04:44 AM
Post
#1
|
|
|
Participant Group: New Members Posts: 10 Joined: 3-April 08 Member No.: 9,916 Card: None |
As you may or may not know, Hauppauge is selling a standalone MCE Remote kit that includes an MCE remote control, a USB IR receiver and an IR blaster. See http://www.hauppauge.com.sg/web-content/pa...s_mce_vars.html (at the bottom of the page). This remote is recognized as a "eHome Infrared Transceiver" by windows XP (non MCE) but alas, the driver referred to by the FAQ, namely http://burningzeroad.free.fr/MceIrApi.rar, cannot be used as the driver. At least, not without some alteration. It is my belief that other MCE remotes (that may not necessarily show as "eHome Infrared Transceiver") could be used as well.
All you have to do in order to use the replacement driver with said remote (and possibly others) is the following: DISCLAIMER: You're going to be messing with drivers, potentially ruining your computer, so do this at your own risk Option 1 - Python Script (You need to have python installed) 1. Download attached file (mcefix.zip) and extract to some empty folder 2. In the command line, go to that directory and type python mcefix.py X where X is how the remote shows in your device manager (use quotation marks if the description contains spaces). If no parameter is given, "eHome Infrared Transceiver" is assumed. 3. A file named mceir.inf will be created in that directory. Copy it over the one in the driver directory. Note: the script uses (and includes) USBDeview so if that creates a copyright problem tell me and I'll remove it from the archive, in which case it would have to be downloaded separately Option 2 - Manual 1. In the device manager, right click "eHome Infrared Transceiver" (or whatever the device shows as on your system)-> Properties 2. Go to the "Details" tab 3. Choose "Hardware IDs" In the drop down list 4. The bottom list should now show something like this: CODE USB\Vid_1784&Pid_0001&Rev_0000 USB\Vid_1784&Pid_0001 (This is what I see with my remote, but with other models it might vary) copy the line that looks like USB\Vid_1784&Pid_0001 in your case (you can simply select it on the list and press Ctrl+C) 5. Go to where you extracted the replacement driver and open mceir.inf with notepad (or any other text editor) 6. Find the [Microsoft] section 7. In the end of that section (i.e. after the line %USB\VID_0471&PID_0815.DeviceDesc%=MCEIR.Dev, USB\VID_1460&PID_9150) add the following line: %USB\VID_0471&PID_0815.DeviceDesc%=MCEIR.Dev, X, where X is the line you copied in step 4. So for example in my case, I would add %USB\VID_0471&PID_0815.DeviceDesc%=MCEIR.Dev, USB\Vid_1784&Pid_0001 8. Find the [Strings] section 9. Change USB\VID_0471&PID_0815.DeviceDesc="MCE Infrared Remote Control" to USB\VID_0471&PID_0815.DeviceDesc="X" where X is the name of your device, as it appears in the device manager. So for example, in my case the line would be USB\VID_0471&PID_0815.DeviceDesc="eHome Infrared Transceiver" 10. Change MCE.SvcDesc="MCE Infrared Remote Control" similarly 11. Save the file You can now (hopefully) use the driver with your remote and proceed as per the FAQ I hope it helps some people (maybe the admins can contact this guy and tell him about it, because he won't be showing up in the forum judging from his stats), It's the least I could do to show my appreciation to this great program (really, superb job btmi) Cheers Edit: I forgot to mention, I got all the info regarding inf files from this great site: http://www.osronline.com/ddkx/install/create-inf_4l47.htm so kudos go to them Edit 2: removed comment regarding steps 8-10, as they appear to be necessary after all - thanks Dahakk Edit 3: Rapidshare link for the script: mcefix.zip Edit 4: New Rapidhsare link: mcefix.zip
Attached File(s)
|
|
|
|
![]() |
Dec 7 2008, 04:13 AM
Post
#2
|
|
|
Participant Group: New Members Posts: 10 Joined: 3-April 08 Member No.: 9,916 Card: None |
Admins - I can't seem to upload it, it says: "Upload failed. Please ask the administrator to ensure the uploads directory is available"
I uploaded it to rapidshare, check original message |
|
|
|
t0xin Using the Replacement MCE Remote Driver (by Bruno FLEURETTE) with the Hauppauge MCE Remote Control Kit (and possibly other supposedly unsupported remotes) Apr 15 2008, 04:44 AM
btmi Thanks so much for taking the time to let us know ... Apr 15 2008, 10:21 AM
t0xin No problem at all, you and this community deserve ... Apr 15 2008, 11:53 AM
dbbd I want to join the thank you.
I wish you posted th... Apr 15 2008, 08:44 PM
t0xin I wrote a Python script that automates the procedu... Apr 16 2008, 05:29 AM
dbbd This is great!
I'd never laugh at code tha... Apr 16 2008, 10:10 PM
Dahakk QUOTE (t0xin @ Apr 14 2008, 11:44 AM) 8. ... Oct 14 2008, 03:14 AM
giskard314 QUOTE (t0xin @ Apr 14 2008, 01:44 PM) Opt... Dec 4 2008, 09:43 AM
denfrosnesko QUOTE (t0xin @ Apr 15 2008, 05:44 AM) As ... Dec 16 2008, 05:58 AM
t0xin QUOTE (denfrosnesko @ Dec 15 2008, 10:58 ... Dec 16 2008, 06:35 AM
freshjewbagel QUOTE (t0xin @ Dec 15 2008, 03:35 PM) I u... Dec 17 2008, 11:06 PM
t0xin I don't see your email on the profile
but just... Dec 18 2008, 06:17 AM
DHS t0xin is correct: tried the (manual edit) fix on t... Dec 5 2009, 11:17 AM
CyborgGold QUOTE (t0xin @ Apr 15 2008, 05:44 AM) As ... Jun 16 2010, 08:49 AM
t0xin QUOTE (CyborgGold @ Jun 16 2010, 01:49 AM... Jun 16 2010, 10:11 AM
bobmorton QUOTE (t0xin @ Jun 16 2010, 11:11 AM) htt... Nov 6 2010, 12:30 PM
david f A reasonable number of models of MCE Remotes do no... Nov 2 2012, 07:38 PM![]() ![]() |
|
Lo-Fi Version | Time is now: 20th June 2013 - 12:08 PM |