Hello,
After three years of pain staking self teaching on MediaPortal I am 95% complete in having my dream Home PVR solution, I am now running a dual tuner, dual STB client/server configuration (3 x clients, 1 x server), My TV Series, Moving Pictures, all PVR clients utilising the same model of MCE compatible remote.
One last hurdle which I cannot figure, I am hoping some IR Server knowledge expert can help?
On the TV Server I am using the HP Media Center beanbag transciever model OVU400102/71 3139 228 64141, part number HP Part No 5187-4593. Now I am at a stage where I need to utilise both the IR sender bug ports (1 for a V+ box, and one for a EuroVox PVR 5100).
If I use port #2 on the bean bag it all works fine, however port #1 never works, even though it shows up in the TV Server Blaster Plugin as port that can be used. As I have three bean bag transceivers I have tried all three, all with the same effect. Apart from installing IR Server Suite 1.4.2.3158, I have not made any registry changes or used the obsolete MCE driver replacement as I think all these issues where sorted in XP Professional SP2. In any event the transceiver sends and receives just fine if using port #2.
I have searched and searched and Googled, and Yahooed but can I find a reason as to why port #1 does not work which applies, no :-(
The transceiver is detected by Windows XP Professional fine (eHarmony USB driver).
I read some posts on the GB PVR forum about Hauppage software installations breaking software communication with port #1 on MS transceivers, which the fix was to install the XP MCE 2005 eHome Update Rollup 2 (using a WinTV PVR 250 and 350). I have tried the XP MCE 2005 eHome Update Rollup 2 method, but this does not allow for installation as it reports I already have a later version SP then expected, am I doing it wrong, should I be performing a manual update rather then using the XP MCE 2005 installer, would XP SP3 not have the update rollup included?
Any help/ideas would be of great assistance! Im betting it is a known issue and that I have missed something...
Thanks.
Gary.
After three years of pain staking self teaching on MediaPortal I am 95% complete in having my dream Home PVR solution, I am now running a dual tuner, dual STB client/server configuration (3 x clients, 1 x server), My TV Series, Moving Pictures, all PVR clients utilising the same model of MCE compatible remote.
One last hurdle which I cannot figure, I am hoping some IR Server knowledge expert can help?
On the TV Server I am using the HP Media Center beanbag transciever model OVU400102/71 3139 228 64141, part number HP Part No 5187-4593. Now I am at a stage where I need to utilise both the IR sender bug ports (1 for a V+ box, and one for a EuroVox PVR 5100).
If I use port #2 on the bean bag it all works fine, however port #1 never works, even though it shows up in the TV Server Blaster Plugin as port that can be used. As I have three bean bag transceivers I have tried all three, all with the same effect. Apart from installing IR Server Suite 1.4.2.3158, I have not made any registry changes or used the obsolete MCE driver replacement as I think all these issues where sorted in XP Professional SP2. In any event the transceiver sends and receives just fine if using port #2.
I have searched and searched and Googled, and Yahooed but can I find a reason as to why port #1 does not work which applies, no :-(
The transceiver is detected by Windows XP Professional fine (eHarmony USB driver).
I read some posts on the GB PVR forum about Hauppage software installations breaking software communication with port #1 on MS transceivers, which the fix was to install the XP MCE 2005 eHome Update Rollup 2 (using a WinTV PVR 250 and 350). I have tried the XP MCE 2005 eHome Update Rollup 2 method, but this does not allow for installation as it reports I already have a later version SP then expected, am I doing it wrong, should I be performing a manual update rather then using the XP MCE 2005 installer, would XP SP3 not have the update rollup included?
Any help/ideas would be of great assistance! Im betting it is a known issue and that I have missed something...
Thanks.
Gary.