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

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

Yes, running in "CUI" mode seems to have worked around it. I'm yet to =
experience a similar failure since running in CUI mode.

How do I end the CUI recording? I've been using <Ctrl>C which seems to =
work OK, but I'm guessing there maybe less brutal method?

Luis mentioned a couple of other things to try:
1) Running the "vnc" method. I'm yet to try this and won't since I have =
a workaround now unless you think it will be beneficial in resolving the =
original problem. But from Yusuke's email below I assume you're already =
on top of it.
2) Run (the GUI) in debug mode. Does this print the debug info to =
stdout/stderr? I ask because it didn't seem to display much more info =
than not running in debug mode. Anyway, here's the output in a GUI run =
that produced the error:
C:\Program Files\DesktopRecorder>python.exe =
C:\Progra~1\pyvnc2swf-0.7.1\vnc2swf.py -d -d -d -d -d -d -d -d -d -d
 Using pygame 1.7.0
 Connected: 127.0.0.1:5900, preferred_encoding=3D(0,)
 VNC Screen: size=3D800x600, name=3D'JFK1-35XMN0VDJV'
 Output movie size: 800x600
 Creating movie: 'C:/David/work/ireport_variables.swf': version=3D5, =
size=3D800x600, framerate=3D12.0, compression=3DNone
 start recording
 Ignored msg=3D'\xff'
 Ignored msg=3D'\xff'
 Ignored msg=3D'\xff'
 Illegal encoding: 0xffffff


Many thanks to Yusuke & Luis for your responses. I don't personally need =
any further responses as the workaround is sufficient for now.

regards,
David

-----Original Message-----
From: Yusuke Shinyama [mailto:yu...@cs...]
Sent: Thursday, November 10, 2005 11:46 AM
To: Karnowski, David; lfk...@ya...
Cc: Vnc...@li...
Subject: Re: [Vnc2swf-users] RFB protocol error: Illegal encoding


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:
>=20
> Hi,
>=20
> 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!
>=20
> Luis Fernando
>=20
> --- Yusuke Shinyama <yu...@cs...> escreveu:
>=20
> > 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.
> >=20
> > Yusuke
> >=20
> > "Karnowski, David" <dka...@et...> wrote:
> > > Hello,
> > >=20
> > > 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).
> > >=20
> > > 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.
> > >=20
> > > Any help appreciated.
> > >=20
> > > thanks,
> > > David
> >=20