vnc2swf-users

[Vnc2swf-users] RFB protocol error: Illegal encoding

[Karnowski, D. <dka...@et...>]

Hello,

While recording I fairly consistently get an "RFB protocol error" window =
pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex =
number is different I think, but can't be sure). At that point my =
recording stops and I have to start over. It doesn't always happen, but =
normally does at some point. The longer I record the more likely it is =
that I'll experience it. The error normally occurs after something =
fairly dynamic occurs on the screen (opening a new window say).

I'm running the 0.7.1 Python version of vnc2swf, but it also used to =
happen with version 0.6.3 which I just upgraded from. My Python version =
is 2.4, I'm running RealVNC v4, and I'm on Windows 2000 Service Pack 4.

Any help appreciated.

thanks,
David

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[Yusuke S. <yu...@cs...>]

Yes, I've experienced this problem a couple of times, but didn't
know the exact condition when it happens. There's no solution
right now, but I hope I can investigate this problem.

Yusuke

"Karnowski, David" <dka...@et...> wrote:
> Hello,
> 
> While recording I fairly consistently get an "RFB protocol error" window pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex number is different I think, but can't be sure). At that point my recording stops and I have to start over. It doesn't always happen, but normally does at some point. The longer I record the more likely it is that I'll experience it. The error normally occurs after something fairly dynamic occurs on the screen (opening a new window say).
> 
> I'm running the 0.7.1 Python version of vnc2swf, but it also used to happen with version 0.6.3 which I just upgraded from. My Python version is 2.4, I'm running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> 
> Any help appreciated.
> 
> thanks,
> David

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[<lfk...@ya...>]

Hi,

The recorder could be parsing the wrong number of bytes for some king of
message that rarely happens. When it happens the recorder may not get the
number of bytes as expected and then when it tries to decode the next message,
the stream pointer is not at the expected position.  I'm just trying to guess
it, of course.
Maybe David could try to record it using the "vnc" method and then try to
convert it later. If the problem occurs then we can use that file to check
what's going wrong.  Just a suggestion!

Luis Fernando

--- Yusuke Shinyama <yu...@cs...> escreveu:

> Yes, I've experienced this problem a couple of times, but didn't
> know the exact condition when it happens. There's no solution
> right now, but I hope I can investigate this problem.
> 
> Yusuke
> 
> "Karnowski, David" <dka...@et...> wrote:
> > Hello,
> > 
> > While recording I fairly consistently get an "RFB protocol error" window
> pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex
> number is different I think, but can't be sure). At that point my recording
> stops and I have to start over. It doesn't always happen, but normally does
> at some point. The longer I record the more likely it is that I'll experience
> it. The error normally occurs after something fairly dynamic occurs on the
> screen (opening a new window say).
> > 
> > I'm running the 0.7.1 Python version of vnc2swf, but it also used to happen
> with version 0.6.3 which I just upgraded from. My Python version is 2.4, I'm
> running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > 
> > Any help appreciated.
> > 
> > thanks,
> > David
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 



	



	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[<lfk...@ya...>]

Also try using debug to check the last messages before the error.  
They can give you a great hint on which message is causing the problem.


--- lfk...@ya... escreveu:

> 
> Hi,
> 
> The recorder could be parsing the wrong number of bytes for some king of
> message that rarely happens. When it happens the recorder may not get the
> number of bytes as expected and then when it tries to decode the next
> message,
> the stream pointer is not at the expected position.  I'm just trying to guess
> it, of course.
> Maybe David could try to record it using the "vnc" method and then try to
> convert it later. If the problem occurs then we can use that file to check
> what's going wrong.  Just a suggestion!
> 
> Luis Fernando
> 
> --- Yusuke Shinyama <yu...@cs...> escreveu:
> 
> > Yes, I've experienced this problem a couple of times, but didn't
> > know the exact condition when it happens. There's no solution
> > right now, but I hope I can investigate this problem.
> > 
> > Yusuke
> > 
> > "Karnowski, David" <dka...@et...> wrote:
> > > Hello,
> > > 
> > > While recording I fairly consistently get an "RFB protocol error" window
> > pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex
> > number is different I think, but can't be sure). At that point my recording
> > stops and I have to start over. It doesn't always happen, but normally does
> > at some point. The longer I record the more likely it is that I'll
> experience
> > it. The error normally occurs after something fairly dynamic occurs on the
> > screen (opening a new window say).
> > > 
> > > I'm running the 0.7.1 Python version of vnc2swf, but it also used to
> happen
> > with version 0.6.3 which I just upgraded from. My Python version is 2.4,
> I'm
> > running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > > 
> > > Any help appreciated.
> > > 
> > > thanks,
> > > David
> > 
> > 
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server.
> Download
> > it for free - -and be entered to win a 42" plasma tv or your very own
> > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > _______________________________________________
> > Vnc2swf-users mailing list
> > Vnc...@li...
> > https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> > 
> 
> 
> 
> 	
> 
> 
> 
> 	
> 		
> _______________________________________________________ 
> Yahoo! Acesso Grátis: Internet rápida e grátis. 
> Instale o discador agora!
> http://br.acesso.yahoo.com/
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Vnc2swf-users mailing list
> Vnc...@li...
> https://lists.sourceforge.net/lists/listinfo/vnc2swf-users
> 



	



	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/

Re: [Vnc2swf-users] RFB protocol error: Illegal encoding

[Yusuke S. <yu...@cs...>]

I noticed this happens only if you use GUI mode.  I set the socket
timeout in RFBNetworkClientWithTkMixin, and this is probably the
cause of the bug, as it might abort data transfer in the middle.
So the current workaround would be using command line mode for a while.
I think I can fix this before long.

Thanks
Yusuke

lfk...@ya... wrote:
> 
> Hi,
> 
> The recorder could be parsing the wrong number of bytes for some king of
> message that rarely happens. When it happens the recorder may not get the
> number of bytes as expected and then when it tries to decode the next message,
> the stream pointer is not at the expected position.  I'm just trying to guess
> it, of course.
> Maybe David could try to record it using the "vnc" method and then try to
> convert it later. If the problem occurs then we can use that file to check
> what's going wrong.  Just a suggestion!
> 
> Luis Fernando
> 
> --- Yusuke Shinyama <yu...@cs...> escreveu:
> 
> > Yes, I've experienced this problem a couple of times, but didn't
> > know the exact condition when it happens. There's no solution
> > right now, but I hope I can investigate this problem.
> > 
> > Yusuke
> > 
> > "Karnowski, David" <dka...@et...> wrote:
> > > Hello,
> > > 
> > > While recording I fairly consistently get an "RFB protocol error" window
> > pop up with the message "Illegal encoding: 0x6699cc" (sometimes the hex
> > number is different I think, but can't be sure). At that point my recording
> > stops and I have to start over. It doesn't always happen, but normally does
> > at some point. The longer I record the more likely it is that I'll experience
> > it. The error normally occurs after something fairly dynamic occurs on the
> > screen (opening a new window say).
> > > 
> > > I'm running the 0.7.1 Python version of vnc2swf, but it also used to happen
> > with version 0.6.3 which I just upgraded from. My Python version is 2.4, I'm
> > running RealVNC v4, and I'm on Windows 2000 Service Pack 4.
> > > 
> > > Any help appreciated.
> > > 
> > > thanks,
> > > David
> >