Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1138393" data-attributes="member: 82144">To be clear: this is what I mean...You physically remove all tuners and Hauppauge software and drivers (recommended: HCWClear).Reboot.Then you connect the HVR-1600 and 950Q and install their drivers.Reboot.Then you connect the Colossus and install its driver.Reboot.Finally you install IRBlast.You should not install IRBlast until all the tuners and their drivers have been installed.Did you do this?AFAIK the blaster config shows up differently depending on whether a blaster cable is connected or not. So, this may have happened because the blaster driver selected the HVR-1600 (...which had no blaster connected to it). That's why I keep suggesting to try swapping the blaster cable from the Colossus to the HVR-1600. It shouldn't matter which card the blaster is plugged into. You might just have to go with the one that the blaster driver latches onto.When he did this previously, logs made it look like the Rosewill blaster was working (with IRSS and TV3 Blaster plugin). I have the impression that the only thing missing was the physical blaster cable (ie. the IR emitter) from the Rosewill kit.Yes, the Hauppauge blaster driver can only work with one tuner/card per PC. With the exception of the HVR-22** cards (which can support 1 blaster per tuner for a total/maximum of two blasters), that means one Hauppauge blaster per PC... even if you have 50 Hauppauge tuner cards connected. In other words, it wouldn't be possible to have 2 Colossus with a blaster each... or a Colossus and HVR-1600 with a blaster each. The difficulty is controlling/predicting which product/card/tuner the blaster driver latches onto.</blockquote>

[QUOTE="mm1352000, post: 1138393, member: 82144"] To be clear: this is what I mean... You physically remove all tuners and Hauppauge software and drivers (recommended: HCWClear). Reboot. Then you connect the HVR-1600 and 950Q and install their drivers. Reboot. Then you connect the Colossus and install its driver. Reboot. Finally you install IRBlast. You should [B]not [/B]install IRBlast until all the tuners and their drivers have been installed. Did you do this? AFAIK the blaster config shows up differently depending on whether a blaster cable is connected or not. So, this may have happened because the blaster driver selected the HVR-1600 (...which had no blaster connected to it). That's why I keep suggesting to try swapping the blaster cable from the Colossus to the HVR-1600. It shouldn't matter which card the blaster is plugged into. You might just have to go with the one that the blaster driver latches onto. When he did this previously, logs made it look like the Rosewill blaster was working (with IRSS and TV3 Blaster plugin). I have the impression that the only thing missing was the physical blaster cable (ie. the IR emitter) from the Rosewill kit. Yes, the Hauppauge blaster driver can only work with one tuner/card per PC. With the exception of the HVR-22** cards (which can support 1 blaster per tuner for a total/maximum of two blasters), that means one Hauppauge blaster per PC... even if you have 50 Hauppauge tuner cards connected. In other words, it wouldn't be possible to have 2 Colossus with a blaster each... or a Colossus and HVR-1600 with a blaster each. The difficulty is controlling/predicting which product/card/tuner the blaster driver latches onto. [/QUOTE]

Verification