Ken, There is a change in the way that VNC Server 4 handles desktop switch events as compared to VNC Server 3. This appears to interact badly with x2vnc. The next VNC Server release will correct this behaviour.
Wez @ RealVNC Ltd. > -----Original Message----- > From: Ken Poole [mailto:[EMAIL PROTECTED] > Sent: 18 June 2004 20:06 > To: James Weatherall > Cc: [EMAIL PROTECTED] > Subject: Re: VNC 4.0 - mouse/kbd hang after unlock win2k box > > mouse/kbd stop responding to actions from x2vnc on "vnc > server" machine ... > > after the "unlock" (done by typing password and selecting > "ok" via x2vnc from solaris box), when I move the mouse or > type on the kbd from the solaris box , nothing happens on the > win2k vnc server If the screen was NOT locked, then it works > fine (win2k vnc server responds fine to kbd and mouse from x2vnc) ... > > local mouse/keyboard on server machine work in either case ... > > and this same version of x2vnc (1.6) worked with older vnc > servers fine > > ken > James Weatherall wrote: > > >Ken, > > > >You've described the steps to recreate the problem you're > seeing, but > >not what the actual problem is. What is the problem? > > > >Wez @ RealVNC Ltd. > >_______________________________________________ > >VNC-List mailing list > >[EMAIL PROTECTED] > >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 _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
