Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1167654" data-attributes="member: 82144">Many happy returns to you! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Yes, that's exactly the right thing to do. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />Excellent.P.S. Sorry, no news from Hauppauge yet about a driver update. They've been able to reproduce the problem outside MediaPortal (a good thing). Now we just have to be patient and hope that they'll be able to schedule time for their developers to find and fix the problem. From what I've been told, all HVR-22** series tuners - 2200, 2205, 2210, 2215, 2250, 2255 etc. - are affected.</blockquote>

[QUOTE="mm1352000, post: 1167654, member: 82144"] Many happy returns to you! :) Yes, that's exactly the right thing to do. (y) Excellent. P.S. Sorry, no news from Hauppauge yet about a driver update. They've been able to reproduce the problem outside MediaPortal (a good thing). Now we just have to be patient and hope that they'll be able to schedule time for their developers to find and fix the problem. From what I've been told, all HVR-22** series tuners - 2200, 2205, 2210, 2215, 2250, 2255 etc. - are affected. [/QUOTE]

Verification