From: "Jamie Burns" <jamie.burns@dynamicexpression.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Code Copy / New Linux boot code
Date: Tue, 17 Feb 2004 00:10:49 -0000 [thread overview]
Message-ID: <003701c3f4ea$7fc57f00$6407a8c0@personal> (raw)
In-Reply-To: 1076963635.27070.22.camel@enterprise.local.lan
Well, whilst looking for some code examples for this kind of thing, I came
across:
http://ultravnc.sourceforge.net/
Which appears to be a version of VNC, which can export secific windows, and
is optimised heavily through use of Windows device driver hooks to be super
fast when sufficient bandwidth exists. On a local machine, it should be
plenty fast.
If nothing else, the concepts for hooking into GDI look interesting.
Thought that may be useful to those who thought it was an interesting idea.
Jamie.
----- Original Message -----
From: "Michael Torrie" <torriem@chem.byu.edu>
To: <qemu-devel@nongnu.org>
Sent: Monday, February 16, 2004 8:33 PM
Subject: Re: [Qemu-devel] Code Copy / New Linux boot code
> My apologies for my post, then, and for my other post! :) I agree that
> the usefulness of such a thing would extend far beyond Linux.
>
> On Mon, 2004-02-16 at 13:17, Lionel Ulmer wrote:
> > > No, Wine is an attempt to implement the Windows API on linux. What
I've
> > > described has nothing to do with that. Instead, you run Windows XP
(the
> > > real version) inside of the qemu virtual machine.
> >
> > Well, I perfectly understood what you meant and my post was more a joke
then
> > anything else.. But well, if you take Wine's GDI implementation, it
already
> > does exactly what you want : takes GDI commands and translate it into
X11
> > commands (except that the interface is done at the GDI32 level and not
at
> > the driver level as you would in your case).
> >
> > And after, the more integration you want (copy paste, systray, ...) the
more
> > DLLs you will have to thunk / rewrite and the more you will ressemble
Wine :-)
> >
> > But well, if it's feasable, it would really be a nice piece of work that
> > could even be used on real Windows to 'remote display' applications from
a
> > real Windows box instead of an emulated one.
> >
> > Lionel
> --
> Michael Torrie <torriem@chem.byu.edu>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-02-17 0:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 0:07 [Qemu-devel] Code Copy / New Linux boot code Fabrice Bellard
2004-02-16 0:27 ` Grzegorz Kulewski
2004-02-16 0:40 ` Fabrice Bellard
2004-02-16 0:52 ` Jamie Burns
2004-02-16 3:43 ` Ed Suominen
2004-02-16 7:27 ` Michael Torrie
2004-02-16 12:33 ` Lionel Ulmer
2004-02-16 18:02 ` Michael Torrie
2004-02-16 18:10 ` Rutger Nijlunsing
2004-02-16 20:25 ` Gabriel Ebner
2004-02-16 20:26 ` Michael Torrie
2004-02-29 21:24 ` Derrik Pates
2004-03-03 14:58 ` Artur Skawina
2004-03-05 8:23 ` John R. Hogerhuis
2004-03-08 23:23 ` Michael L Torrie
2004-02-16 20:17 ` Lionel Ulmer
2004-02-16 20:33 ` Michael Torrie
2004-02-17 0:10 ` Jamie Burns [this message]
2004-02-17 0:23 ` Michael Torrie
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='003701c3f4ea$7fc57f00$6407a8c0@personal' \
--to=jamie.burns@dynamicexpression.co.uk \
--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).