I did some googling around and found plenty of instances of the same
problem with the windows software. Eventually I ended up at:
http://www.shspvr.com/smf/index.php?topic=8389.0
There's nothing in the changelog that indicates a remote fix so it
would appear that they are as clueless about it as we are. Is this a
different chip than in the 350? Because the 350 seemed stable with
the 2.0 drivers. I used it all the time. It was just that I wanted to
use the 150 IR Blaster for my digital settop box instead of the
analog cable directly
There are "I2C fixes" for the blaster listed inside the zip, but there
are various pointers to it for fixing the remote as well and people who
claim that it has done so. Given that it only happens when watching TV,
presumably some of the other I2C traffic causes it to crash. Whether
they did or didn't fix it I'm not sure, I'll have a play with the
Windows box at the weekend and see if I can find anything out.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
