All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Williamson" <mark.williamson@cl.cam.ac.uk>
To: Mikhail Ramendik <mr@ramendik.ru>
Cc: maw48@cantab.net, xen-devel@lists.sourceforge.net
Subject: Re: win4lin-like porting of win98 to xen?
Date: Sun, 10 Oct 2004 23:41:02 +0100	[thread overview]
Message-ID: <200410102341.03482.mark.williamson@cl.cam.ac.uk> (raw)
In-Reply-To: <1097437140.2679.195.camel@localhost.localdomain>

> This approach would enable running Win4Lin. My idea would be, instead,
> to replace Win4Lin entirely.

That suggests using some kind of Xen-compatible kernel that can provide the 
DOS syscalls Win 9x needs to run.  Maybe this could be a (perhaps suped-up) 
FreeDOS, as you suggest, if someone were to port it to Xen.  I don't know if 
FreeDOS can host Win 9x currently...

OTOH, maybe its still possible to use a ported Win4Lin kernel patch to allow 
Win 9x to be hosted on a XenLinux kernel.  Instead of using the Win4Lin 
virtual device drivers, you'd want to write some Xen-compatible ones for 
Win9x to talk to the block / net backends.  You'd also need to figure out a 
suitable solution for display virtualisation.  This approach would avoid you 
using the parts of Win4Lin that are non-free.

There was another thread involving porting ReactOS (GPL licensed Windows 
clone) to Xen, recently.  Something like this would be another option for 
Windows compatibility, although for now ReactOS is probably less compatible 
with Windows apps than Win 9x is ;-)

HTH,
Mark


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

  reply	other threads:[~2004-10-10 22:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 16:17 win4lin-like porting of win98 to xen? Mikhail Ramendik
2004-10-10 16:32 ` M.A. Williamson
2004-10-10 19:39   ` Mikhail Ramendik
2004-10-10 22:41     ` Mark A. Williamson [this message]
2004-10-11  0:05       ` David Hopwood
2004-10-11  0:33         ` Brian Wolfe
2004-10-11  0:38         ` Mark A. Williamson
2004-10-11  1:03           ` Avery Pennarun
2004-10-11  9:05             ` Mikhail Ramendik
2004-10-11  9:21               ` Steven Hand
2004-10-11  1:52           ` David Hopwood
2004-10-11 11:33 Tom Cranbrook

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=200410102341.03482.mark.williamson@cl.cam.ac.uk \
    --to=mark.williamson@cl.cam.ac.uk \
    --cc=maw48@cantab.net \
    --cc=mr@ramendik.ru \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.