VNC 4.0 - mouse/kbd hang after unlock win2k box

[Ken Poole]

Wez,

thanks for the info ...

I had a report of a problem from a co-worker who uses x2vnc, and thought 
I was seeing the same issue/behavior when I was connecting via the viewer

I have since installed x2vnc 1.6, and see that the cursor doesn't blink ...

and after checking with the co-worker, came up with his original 
complaint, and a way to recreate it:

1 - have a win2k computer with the 4.0 server on it
2 - lock the computer (ctl-alt-del, select "lock computer")
or have the server in "When last client disconnects - lock"
3 - connect via x2vnc to the win2k box
4 - enter password to "unlock" computer
5 - try to move mouse or do keyboard inputs ...

this works with previous versions (3.3.3r7, 3.3.3r9 )of the VNC server 
(i.e. doesn't lock up)

ken p.



James Weatherall wrote:

>Ken,
>
>The mouse flicker that you describe is an artefact of a more complete
>capture method used by VNC Server 4.0, which ensures that alpha-blended
>windows & menus are displayed.
>
>What is puzzling is that you say that you get this problem with x2vnc.  The
>mouse will only flicker when there are clients connected that are requesting
>display updates.  Since x2vnc never displays any graphics, it should never
>request a graphical update.  So it sounds as though x2vnc is broken.
>
>Cheers,
>
>Wez @ RealVNC Ltd.
>_______________________________________________
>VNC-List mailing list
>VNC-List "at" realvnc.com
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
>  
>

-- 
Ken Poole
Software Engineer
DSP Development Tools Product Line
Analog Devices, Inc.
Phone: 781-461-3634
Fax: 781-461-4284
http://www.analog.com
***********************************************
CROSSCORE, Analog Devices DSP Development Tools