I experienced similar problems, but I was running vmware on 2k and had Solaris in the vm. The easy fix for my problem was to just minimize the vm, or move the mouse away from the vmware window. But reading below I think if you remove the toolbox for the guest OS, you might not have this prob.
Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Gehl Sent: Wednesday, December 19, 2001 11:10 AM To: [EMAIL PROTECTED] Subject: VMWare & VNC cursor registration Trying to run VMWare inside a Xvnc server and get cursor registration problems. I've gone over a number of posts on this issue and have not found a solution. A post off google seemed to describe the problem... ----->> We've used VNC with VMware on Linux and had some problems when we startup X on the guest Linux and run that through VNC. Basically, VNC loses track of the cursor in the guest Linux. Instead, VNC makes the inside (VNC) cursor match the position of the outside (real X server) cursor. I've talked with the VMware folks about this and they indicate the problem is as follows: VMware doesn't have a cursor. It emulates a PS/2 mouse, which only reports relative motion. It takes the X (or VNC if running under VNC) cursor motion events and turns them into mouse moves for the VM. With any X server, this is fine until the cursor hits the root window border. Then it can no longer get motion events in that direction. To get around this, VMware warps the X cursor (using the XWarpPonter call) to the middle of the screen when it gets near a border. This should work when using VNC as VMware's X server, since it'll also keep the VNC cursor within its window. However, VNC essentially ignores the XWarpPointer call, because it always resets its cursor position to match the real X server's cursor. The result is that VMware gets some strange cursor movements and when you move the mouse in the same direction for a while, VNC releases the X cursor and VMware stops getting motion events. When VMware is running with the toolbox so it knows the guest operating system's cursor position, it can release the X cursor when the guest's cursor goes out of the display (plus a force threshold to make it stickier). I think VNC should work like that. The way it works now breaks XWarpPointer(), which is useful for things like moving the cursor to the middle of a dialog box when it pops up. Anyway, I consider it a VNC bug, since it doesn't support one of the standard X protocol calls. (On the other hand, any X server using an absolute-coordinate pointing device (like a tablet) will behave in the same way, so it's hard to say. I guess VMware, because it's emulating a mouse, just doesn't work well when the physical pointing device uses absolute coordinates.) -----<< Anyone have any ideas on this? Thanks. --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
