Socket disconnects

[tkgafs]

If you have a chance, you're the first person I know that has actually connected via crossover, could you tell me if mvpmc's native internet radio streaming works? Use the Filesystem option and go to /usr/playlist and select default.m3u. I'm not sure how the dns or routing will work so I'm not optimistic.

Thanks,

Martin

Radio streaming seems to work fine although I only tried a couple of stations which didn't say they needed realplayer or vlc

I seem to remember that resolv.conf points correctly at the other end of the crossover cable [192.168.0.1] but I didnt actually check !

Tkgafs

[mvallevand]

Radio streaming seems to work fine although I only tried a couple of stations which didn't say they needed realplayer or vlc

I seem to remember that resolv.conf points correctly at the other end of the crossover cable [192.168.0.1] but I didnt actually check !

Tkgafs

Great thanks, one working was good enough for me. I can use this as a test that ICS/DNS, and DHCP are set up properly.

Martin

[mvallevand]

I'm probably going to stop looking into this for now. Hauppauge tells me they do nothing on the mvp and we use the same kernel, so I think this could be a Windows issue more than mvpmc

I did find that I could greatly extend the time that mvpmc stayed connected, I got the logs rolling mesage for the first time, by adding the registry key eepAliveTime and setting it to 1800000 (half an hour).

This link has info on this setting as well as many others.

http://support.microsoft.com/kb/314053

Martin

[tkgafs]

I'm probably going to stop looking into this for now. Hauppauge tells me they do nothing on the mvp and we use the same kernel, so I think this could be a Windows issue more than mvpmc

I did find that I could greatly extend the time that mvpmc stayed connected, I got the logs rolling mesage for the first time, by adding the registry key eepAliveTime and setting it to 1800000 (half an hour).

This link has info on this setting as well as many others.

http://support.microsoft.com/kb/314053

Martin

Martin

can I check what exactly you did as the following seems to say that the default for KeepAliveTime is 7,200,00 [two hours] so in effect you seem to be reducing the time between the keepalive transmissions

the following is extracted from the microsoft page Martin mentions above

KeepAliveInterval
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 1000 (one second)
Description: This parameter determines the interval that separates keepalive retransmissions until a response is received. After a response is received, KeepAliveTime again controls the delay until the next keepalive transmission. The connection is aborted after the number of retransmissions that are specified by TcpMaxDataRetransmissions are unanswered.

KeepAliveTime
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
Description: The parameter controls how frequently TCP tries to verify that an idle connection is still intact by sending a keepalive packet. If the remote computer is still reachable and functioning, the remote computer acknowledges the keepalive transmission. By default, keepalive packets are not sent. A program can turn on this feature on a connection.

Tkgafs

[mvallevand]

can I check what exactly you did as the following seems to say that the default for KeepAliveTime is 7,200,00 [two hours] so in effect you seem to be reducing the time between the keepalive transmissions

I'm using the following setting right now, As for the default the documentation isn't clear since it also says "By default, keepalive packets are not sent."

========================================
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime "=dword:001b7740
========================================

Martin

[mvallevand]

I suggest applying this new patch from sub. I just ran 14 hours straight with it.

http://forums.gbpvr.com/showpost.php?p=1...stcount=31

This patch also clears up a minor annoyance on startup where mvpmc shows the screen but gbpvr thinks that it is in screen saver mode although the jump to screen saver can be abrupt.

Martin

[sub]

I suggest applying this new patch from sub. I just ran 14 hours straight with it.

http://forums.gbpvr.com/showpost.php?p=1...stcount=31

Thanks for the confirmation. Sometimes I wonder if anyone even downloads my patches

[mvallevand]

Well I just did good thing I've backup the two files because when I run this patch I loose a great share of my RAM..
Services Running look huge

I let LiveTV run for about an hour and didn't see anything close to the those numbers. 18MB for dormant session 22-34 for the running one. Also I don't think you use mvpmc do you?

Martin

[sub]

Services Running look huge

Actually those can be fairly normal numbers if you're running any plugins. Some plugins like Weather etc consume heaps of memory. Try temporarily removing all the files from you plugins directory. This patch wont have affected this.

[Lindsay]

Thanks for the confirmation. Sometimes I wonder if anyone even downloads my patches

What a sad statement I have downloaded the patch, along with pretty much all the others, so I hope you feel a little better