Ack. That's it. I never saw anything about registering it at all. You
actually have to dig very deeply on the web site to see that it even
needs registration. Couldn't they put that a bit more prominently?

Scott Best wrote:
> Walter:
> 
>       Heya. Have to ask ... is your echoServer registered? :) The  
> "disconnection"
> happens when the echoServer drops the data channel, and every 10 minutes
> is what the echoServer is supposed to do, in the unregistered state...
> 
> -Scott
> 
> On Aug 11, 2008, at 2:20 PM, [EMAIL PROTECTED] wrote:
> 
>> I've upgraded to echoserver 1.63 and EchoVNC 2.35 on client and  
>> server. I'm connecting today from a Windows XP Pro Box to a Windows  
>> XP Home box. I think they are fully patched except for service pack 3.
>>
>> What I've found is that I get these reconnect messages about every  
>> ten minutes. With past versions it would actually re-connect after  
>> 30 seconds or so. With the current versions it does not seem to ever  
>> reconnect and you have to close it out and re-start the viewer.
>>
>> However the every ten minute thing creates a bad problem for my home  
>> use. I have a set top computer that I watch internet television and  
>> movies (netflix instant watch) and computer format recorded shows  
>> on. Although I have not tested this out today, I imagine the problem  
>> is still there. When I am watching a full screen video and the  
>> Reconnecting... box comes up, the screen on the set top box freezes  
>> and audio continues. It does not seem to freeze if I am not watching  
>> full screen.
>>
>> I don't know if there are many people trying to use EchoVNC in this  
>> manner, but it makes it so that any computer in the house can  
>> function as a remote control for the set-top unit which you can  
>> imagine is very handy.
>>
>> Another factor I should mention is that the set top computer and  
>> usually the remote computer are connected over a wireless network. I  
>> just checked here at work and I'm getting the same ten minute  
>> Reconnecting with no reconnection problem over a wired network. The  
>> EchoVNC server in this case is 2.00 as the computer is running NT4.
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Echovnc-users mailing list
> Echovnc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/echovnc-users
> 
>    
> 
> 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users

Reply via email to