Richard Kay wrote: > The logs also show copies of the Windows dongle.bin and > dongle.bin.ver...
What do you mean by "Windows dongle.bin"? The dongle supplied by Hauppauge? > The display on the MVP it suggests that it is downloading the application > and then it seems to fail to contact the servers ( I guess for > the servers/services configured in the Windows specific dongle.bin ). My expectation is that the stock Hauppauge dongle would boot up normally, regardless of what server supplied it, but then complain later when it couldn't contact the media server. Perhaps that's just what you're seeing. > Attempts to contact 192.168.1.112 using telnet fail... As one would expect, if you aren't booting the mvpmc dongle that has an telnet daemon running. > Would supplying another dongle.bin and dongle.bin.ver from > Linux be likely to work ? Probably. > If so does a set of precompiled files which work on the H3 exist... Yes. Follow the links from mvpmc.org and you should find both a release version as well as a nightly build, both precompiled and drop-in replacements for the Hauppauge dongle.bin. See the wiki for instructions on generating the dongle.bin.ver file. > ...prior to my exploring the next stage which will involve supplying > a NFS aware client from Linux to the MVP ? What do you plan to use NFS for? -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
