Reply to thread

Message

<blockquote data-quote="ting" data-source="post: 13492" data-attributes="member: 11449">pvr150 bugI think i maybe have a few thoughts on this:In the begining of february i had a problem with the ir driver, were &quot;failed to initialize infrared&quot; etc... error message appeared, and a reboot was nececarry to regain controll. The ir would stop working after a few minutes of use. A new driver, dated 04.02.2005 cleared up the problem.These topics are about the problem:<a href="http://www.hauppauge.co.uk/board/showthread.php?t=1761&amp;page=1&amp;pp=10" target="_blank">http://www.hauppauge.co.uk/board/showthread.php?t=1761&amp;page=1&amp;pp=10</a><a href="http://www.shspvr.com/forum/viewtopic.php?t=6703&amp;postdays=0&amp;postorder=asc&amp;start=0" target="_blank">http://www.shspvr.com/forum/viewtopic.php?t=6703&amp;postdays=0&amp;postorder=asc&amp;start=0</a>To sum it up, I think hauppauge changed the function which mpod mentioned in his post with the &quot;IR_NOKEY&quot; frase.&nbsp; I think this is a hauppauge work around or something.I konow nothing about programming, but I think this command keeps the remote in focus.Anyway: My sugestion to other pvr150 users:For those who do NOT have an nforce based motherboard: use drivers dated before 04.02.2005.*(hauppauge’s system of driver naming is rather weird, so im mentioning the date as stated in the device properties)If It works, post it, and perhaps mpod cand find a “work around” for the “work around”…. :?</blockquote>

[QUOTE="ting, post: 13492, member: 11449"] [b]pvr150 bug[/b] I think i maybe have a few thoughts on this: In the begining of february i had a problem with the ir driver, were "failed to initialize infrared" etc... error message appeared, and a reboot was nececarry to regain controll. The ir would stop working after a few minutes of use. A new driver, dated 04.02.2005 cleared up the problem. These topics are about the problem: [url]http://www.hauppauge.co.uk/board/showthread.php?t=1761&page=1&pp=10[/url] [url]http://www.shspvr.com/forum/viewtopic.php?t=6703&postdays=0&postorder=asc&start=0[/url] To sum it up, I think hauppauge changed the function which mpod mentioned in his post with the "IR_NOKEY" frase. I think this is a hauppauge work around or something. I konow nothing about programming, but I think this command keeps the remote in focus. Anyway: My sugestion to other pvr150 users: For those who do NOT have an nforce based motherboard: use drivers dated before 04.02.2005. *(hauppauge’s system of driver naming is rather weird, so im mentioning the date as stated in the device properties) If It works, post it, and perhaps mpod cand find a “work around” for the “work around”…. :? [/QUOTE]

Verification