• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Remote/IR Receiver from MCE-edition Hauppauge PVR-150 doesn't work with MCE?

MichaelD

Lifer
While spec'ing out my new HTPC I was very careful to choose compatible components. I purchased WinXP MCE 2005 and a Hauppauge PVR-150 MCE edition DVR card. It came with the MCE remote and a USB IR receiver box and an IR blaster.

And I can't get the receiver box to work; I get the same error in Device Manager that the other guys get. I literally spent all day yesterday (12+ hours) reloading the OS and Googling for answers.

I found this and this and about a dozen other threads with the identical info and that fix does NOT work. I tried everything I know and then some.

I have an email into Hauppauge for the problem.

Anyone else run into this? What good is the PVR card if I can't control my set top box w/it?
---------------------------------------------------------------------------------------------------------

*EDIT 29 JAN 08*

HOLY COW, I fixed it! 😀 This was my first IRB.inf file hack and I guess beginner's luck had a lot to do with it. In Device Manager I noticed that whenever I'd plug the IR receiver in, I'd get the "Unknown E-home IR transcevr" error. But in the PROPERTIES page, it showed "Unknown device//USB\VID_0609&PID_0334//some-alphanumeric-string." <--This VID/PID was NOT in the original irb.inf folder.

/gears turning

So, I copy/pasted a line from the HW section to the end of the list and changed the data after the comma to reflect ^^that VID/PID. Saved the file and rebooted. When I plugged the receiver in this time I got the Found New Hardware box as usual, but this time it said "Compliant IR Receiver Device." I told it to search the net for drivers. It found them. It repeated this no less than 8 times. I now have more HID Devices/USB Devices/Keyboard Devices/Mouse Devices.

Each time I told it to go to the net and it found them. All the drivers are dated "Microsoft/2001" by the way.

Hopefully this can help somebody else. 🙂
 
Anyone? I haven't heard back from Haugpaugge either. 🙁

I tried that "irb.inf" file hack again and to my surprise, my "beanbag" receiver is listed. It's branded as "SMX" on the bottom, and it's listed about line four in the file. Yet it doesn't work.

I wonder if it's got anything to do with my case having a built-in IR receiver? Hmmm. I may have to disable it and check.
 
The SHSPVR guys seem pretty confident that it's an INF problem. Are you sure one of the PNP IDs listed in the INF file match the PNP ID for the receiver?
 
Originally posted by: ViRGE
The SHSPVR guys seem pretty confident that it's an INF problem. Are you sure one of the PNP IDs listed in the INF file match the PNP ID for the receiver?

Hi Virge. How can I tell if it matches? I've been wondering how they get the Vendor ID from the name. 😕

The little receiver box only has markings on the bottom. It says :

SMK
Model: RXX6000-0141E

And that's it. Do I change the .inf file to read the exact model number? Thanks much!

*edit*
Here's the entire MicrosoftHW section. Note there are two entries for "SMK". They have the same VID (expected) but very different PIDs. What nubers do I put in for my black box?

[MicrosoftHw]
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V1, USB\VID_045E&PID_006D ; Microsoft SB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_045E&PID_00A0 ; Microsoft BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_045E&PID_00DA ; Microsoft SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_107B&PID_3009 ; Gateway BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1509&PID_9242 ; FIC BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_03EE&PID_2501 ; Mitsumi BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0471&PID_0815 ; Philips BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0609&PID_031D ; SMK BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_2040&PID_6310 ; Hauppauge BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1009&PID_000E ; eMuzed BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1019&PID_0F38 ; ECS BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_03F3&PID_0094 ; Adaptec BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0FB8&PID_0002 ; Wistron BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_04E8&PID_7061 ; Samsung BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1460&PID_9150 ; Tatung BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_03EE&PID_2502 ; Mitsumi SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_0609&PID_0322 ; SMK SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1308&PID_C001 ; Shuttle BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0768&PID_0023 ; Ricavision BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_0471&PID_0608 ; Philips SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_043E&PID_9803 ; LG BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_179D&PID_0010 ; Ricavision BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_179D&PID_0020 ; Ricavision SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_1784&PID_0001 ; Topseed BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_1784&PID_0002 ; Topseed SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_17B8&PID_1100 ; Trojan SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_17B8&PID_044C ; Trojan SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_17B8&PID_04B0 ; Trojan BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_15B1&PID_8090 ; Mitac SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_147A&PID_E015 ; Formosa21 BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_147A&PID_E016 ; Formosa21 SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_051C&PID_C001 ; Shuttle BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_051C&PID_C002 ; Shuttle SF
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_V2, USB\VID_0C16&PID_0081 ; Gyration BB
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus_RX, USB\VID_0C16&PID_0080 ; Gyration SF

*edit*
Windows TOLD ME what numbers to put in for the black box. 🙂 See OP, above.

This could be a good "resource thread" for others experiencing the same problem. From what I've seen during my couple of days of Googling for answers, I'm far from the only one that runs into this issue. Hauppauge should be ashamed!
 
:thumbsup: Here's a thumbs up for you....

Guess I am lucky, never had any problems with my PVR-150.
But, just in case, I've got this saved.....
 
Originally posted by: MichaelD
*EDIT 29 JAN 08*

HOLY COW, I fixed it! 😀 This was my first IRB.inf file hack and I guess beginner's luck had a lot to do with it. In Device Manager I noticed that whenever I'd plug the IR receiver in, I'd get the "Unknown E-home IR transcevr" error. But in the PROPERTIES page, it showed "Unknown device//USB\VID_0609&PID_0334//some-alphanumeric-string." <--This VID/PID was NOT in the original irb.inf folder.

/gears turning

So, I copy/pasted a line from the HW section to the end of the list and changed the data after the comma to reflect ^^that VID/PID. Saved the file and rebooted. When I plugged the receiver in this time I got the Found New Hardware box as usual, but this time it said "Compliant IR Receiver Device." I told it to search the net for drivers. It found them. It repeated this no less than 8 times. I now have more HID Devices/USB Devices/Keyboard Devices/Mouse Devices.

Each time I told it to go to the net and it found them. All the drivers are dated "Microsoft/2001" by the way.

Hopefully this can help somebody else. 🙂
Looks like the SHSPVR guys were right then. Welcome to the world of driver hacking.😉
 
Yeah I've had this problem since I had my faulty TVcard (bad picture quality) replaced with a PVR 150. Since the ir receiver didn't work with the previous TVcard it has to be a driver issue.
 
Back
Top