Reply to thread

Message

<blockquote data-quote="bert_r" data-source="post: 500777" data-attributes="member: 90426">You can change when an episode will be marked as 'watched' (configuration dialog, display tab, 'an episode is watched after x%'). If you set this low enough (the default setting of 90% is sufficient for me) an episode will be set to watched even when you press stop before the ending.But I'll see anyway if it is possible to implement a 'play next' function. I had such a function on my old media player (a TViX) and used it constantly.The reason why retrieving fanart and most themoviedb data works is probably because they probably use another protocol (TCP) than AniDB (which uses UDP). Can you try if other AniDB UDP clients (like <a href="http://www.bjecas.org/anihash/" target="_blank">AniHash</a>) have the same problem?Still, the only thing I can find is that this is most likely caused by a corrupted winsock stack. If the 'netsh winsock reset' trick didn't solve it, you could either try a tool like <a href="http://www.spychecker.com/program/winsockxpfix.html" target="_blank">this one</a> (note that I didn't test this tool myself, I just found it by googling around) or reinstall windows...</blockquote>

[QUOTE="bert_r, post: 500777, member: 90426"] You can change when an episode will be marked as 'watched' (configuration dialog, display tab, 'an episode is watched after x%'). If you set this low enough (the default setting of 90% is sufficient for me) an episode will be set to watched even when you press stop before the ending. But I'll see anyway if it is possible to implement a 'play next' function. I had such a function on my old media player (a TViX) and used it constantly. The reason why retrieving fanart and most themoviedb data works is probably because they probably use another protocol (TCP) than AniDB (which uses UDP). Can you try if other AniDB UDP clients (like [URL="http://www.bjecas.org/anihash/"]AniHash[/URL]) have the same problem? Still, the only thing I can find is that this is most likely caused by a corrupted winsock stack. If the 'netsh winsock reset' trick didn't solve it, you could either try a tool like [URL="http://www.spychecker.com/program/winsockxpfix.html"]this one[/URL] (note that I didn't test this tool myself, I just found it by googling around) or reinstall windows... [/QUOTE]

Verification