Well, after some additional crappy support from Netraverse, I decided to dig deeper into the whole mouse synchronization problem. At first, all the information I found about it indicated the problem to be with the emulated video driver (from what I understood, anyway) and that the solution would be found there and required fixing the video driver. I decided to email the folks at RealVNC to see if maybe there was just something going on with the VNC server/client--since QEMU/Bochs work fine from the console, it made sense that there may be something missing or wrong with the VNC software (I happen to use the free RealVNC). They responded...
They suggested that RealVNC Personal or Enterprise would correct the problem, so I grabbed the free trials of Enterprise. It actually resolved the issue--there's a feature called Relative Pointer Motion that, when enabled, syncs the local cursor perfectly to the cursor in QEMU and Bochs. I thought this one might be useful to others having the same problem. ~ Tom Tom Smith wrote: >Man, I tell you what... > >Bochs built correctly and the RFB stuff worked... Sort of. There seems >to be an issue with both QEMU and Bochs when used via VNC. Both of them >were fairly easy to setup and get running and they work fine when I'm >sitting at the console. The problem is when I try to use them over a VNC >session on a virtual console (using vncserver). From what I can find, >there's an issue with mouse synchronization--an issue that pretty much >excludes these great products from being used in a Terminal Server-like >environment. > >Neil Bothwick wrote: > > > >>On Wed, 18 Jan 2006 14:52:26 -0700, Tom Smith wrote: >> >> >> >> >> >>>Well, I tried that and get the same error--">>PANIC<< bochsrc.txt: >>>display library 'rfb' not available". >>> >>> >>> >>> >>OK, so this isn't one of "most ebuilds" >> >> >> >> >> >>>So I tried to edit the ebuild file and add "--with-rfb" and get the >>>emerge error: >>> >>>"!!! Digest verification Failed: >>>!!! /usr/portage/app-emulation/bochs/bochs-2.2.1-r1.ebuild >>>!!! Reason: Filesize does not match recorded size" >>> >>>Is there a way I can override this behavior? (The file size obviously >>>doesn't match because I added an additional ./configure option to it. >>> >>> >>> >>> >>Add --digest to the emerge command. >> >> >> >> >> >>>>EXTRA_ECONF="--foo" emerge bar - works with most ebuilds. >>>> >>>> >>>> >>>> >> >> >> >> -- gentoo-user@gentoo.org mailing list
