Reply to thread

Message: <blockquote data-quote="luiciphier" data-source="post: 56293" data-attributes="member: 19880">I think your problem is slightly different from mine - I finally got a reply from a Hauppauge guy a few days ago, and he informed me that the drivers I had installed (he was assuming I'd installed the MCE versions) weren't compatible with my XP setup. I actually got error messages (not surprisingly) when trying the MCE drivers and have been happily using the standard XP drivers (minus the IR Blaster functionality) since installation. My probem therefore maybe does make some sense as the XP drivers would be looking for the blaster in the wrong physicaly place.Note: I'm using XP drivers that expect a connection on the TV card for the blaster and thus had error messages. I did ask whether one could 'fudge' the system by mixing drivers/configs to get the best of both worlds but haven't had a reply yet.When I installed Media Portal RC4, it informed me my drivers were out of date, prompted me to download new ones and after this, the annoying "What bloody blaster?" boot message has disappeared. Still doesn't work when I go to the Hauppauge Blaster config but better nevertheless. I'm now pondering whether MyBlaster will ignore the actual connection (USB in my case as opposed to TV Card Phone plug) and let me config my controls anway? Once my one year old stops throwing my remotes (anything but my Philips Pronto!) down the toilet, I may have a chance to find out.So, you seem to have a whole new problem - I would try the usual: Download the latest drivers, uninstall the current, switch off, remove the card, reboot, switch off. plug in card, redirect the installer to your new drivers, etc. My setup couldn't even find drivers and I had to copy irbus.sys and irbus.inf from another setup to get the basic blaster (remote) to work. Your setup should already have this.Initially, I was under the impression that there were varying versions of these drivers, but then, as the drivers and hardware are Microsoft designed/approved, it probably couldn't care less about where the blaster connection is (Card or USB) so this removes another possibility from the puzzle, but doesn't really help.The Hauppauge guy stated that the remote and blaster were entirely Microsoft's bag but I reckon this can't be entirely true as Hauppauge's standard (non MCE) card has the blaster connection in a different place  - did Microsoft plan for this or did Hauppauge work around it?Hope it all works out for you - as soon as anything changes, I'll post again.</blockquote>

Verification