From: Lindsay Mathieson <lindsay@softlog.com.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] VNC Patch - 6th version
Date: Thu, 19 Aug 2004 17:14:15 +1000 [thread overview]
Message-ID: <41245347.3090402@softlog.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0408171559470.6186@wgmdd8.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
>Unfortunately, for some systems (e.g. Windows 98), you have to calibrate
>the mouse. For that, you have to move (somehow) the mouse pointer to an
>empty spot on the desktop (with space above it), and then press and
>release Ctrl+Shift. Your mouse cursor should go a little bit upwards and
>then jump back. After that, the mouse pointer movements should be
>consistent with the host pointer.
>
>
Got it running:
- still have to manually edit keyboard_rdesktop.c and hardcode the
prefix path for keycode to load
- the mouse does seem to track now, though it is extremely jerky and erratic
The session keeps disconnecting, it seems to make a difference choosing
different compression ratios, also screen res in the guest makes a real
difference as well.
e.g connecting with UltraVNC on AutoSpeed selection to win98 at 800x600,
the client disconnects immediately.
From my console log:
19/08/2004 16:29:00 rfbProcessClientNormalMessage: ignoring unknown
encoding type 9
19/08/2004 16:29:00 rfbProcessClientNormalMessage: ignoring unknown
encoding type 8
19/08/2004 16:29:00 Using compression level 6 for client 192.168.5.69
19/08/2004 16:29:00 Enabling X-style cursor updates for client 192.168.5.69
19/08/2004 16:29:00 Enabling full-color cursor updates for client
192.168.5.69
19/08/2004 16:29:00 Using image quality level 0 for client 192.168.5.69
19/08/2004 16:29:00 rfbProcessClientNormalMessage: ignoring unknown
encoding type -65530
19/08/2004 16:29:00 Enabling LastRect protocol extension for client
192.168.5.69
19/08/2004 16:29:00 Enabling NewFBSize protocol extension for client
192.168.5.69
19/08/2004 16:29:00 WriteExact: select: Interrupted system call
19/08/2004 16:29:00 rfbSendUpdateBuf: write: Interrupted system call
19/08/2004 16:29:00 Client 192.168.5.69 gone
19/08/2004 16:29:00 Statistics:
19/08/2004 16:29:00 key events received 0, pointer events 1
19/08/2004 16:29:00 framebuffer updates 2, rectangles 4, bytes 22303
19/08/2004 16:29:00 cursor shape updates 2, bytes 24
19/08/2004 16:29:00 hextile rectangles 1, bytes 17283
19/08/2004 16:29:00 ZRLE rectangles 1, bytes 4996
19/08/2004 16:29:00 raw bytes equivalent 921624, compression ratio
41.367386
--
When life hands you lemons, ask for a bottle of gin and tonic.
next prev parent reply other threads:[~2004-08-19 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 23:47 [Qemu-devel] VNC Patch - solved Lindsay Mathieson
2004-07-28 8:57 ` [Qemu-devel] " Johannes Schindelin
2004-08-17 14:04 ` [Qemu-devel] VNC Patch - 6th version Johannes Schindelin
2004-08-19 6:48 ` Lindsay Mathieson
2004-08-19 7:14 ` Lindsay Mathieson [this message]
2004-08-19 10:21 ` Johannes Schindelin
2004-08-19 12:02 ` Lindsay Mathieson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41245347.3090402@softlog.com.au \
--to=lindsay@softlog.com.au \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).