All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Ramendik <mr@ramendik.ru>
To: Avery Pennarun <apenwarr@nit.ca>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: win4lin-like porting of win98 to xen?
Date: Mon, 11 Oct 2004 13:05:59 +0400	[thread overview]
Message-ID: <1097485559.3234.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20041011010303.GD11053@worldvisions.ca>

Avery Pennarun wrote:

> A free win4lin (ie. rewriting all those drivers) would be a *massive* amount
> of work.  Fun, but a lot of work.  And it gets more and more obsolete each
> day.  Lots of stuff still runs under win98, but it's certainly not a target
> platform for modern developers.

Actually I thought that, perhaps, much of the work from the WinXP port
could be adapted to a Win98 snap-in port? 

(As I understand, the WinXP structure is so different that a snap-in
port for it without breaking some MS license would be impossible.
Otherwise you'd have done it already ;).

The main idea behind any win9x port is end-user value. ReactOS is an
attempt to recreate the Win32 API, like Wine (but with a different
method). Wine's main problem from the user side is the presence of
various "quirks", minor differences between its implementation and the
Microsoft one; they cause applications to misbehave strangely. 

ReactOS might have the same problem, and thus, its end-user value, under
Xen or alone, might be significantly less than that of Win4Lin (or a Xen
XP, if that were available to the users).

Of course I understand that for end-user value alone, the presence of a
proprietary solution is sufficient. And, Win98 support is indeed getting
obsolete. 

So the only thing that Xen would get from this kind of support would be
an expanded user base. Not a "first-of-a-kind" value, not technical
advantage, only user adoption.

The only people qualified to decide whether this is needed are those who
know how hard it is - i.e. what actually is in the WinXP port and how
easy would it be to move it to win98.

Yours, Mikhail Ramendik




-------------------------------------------------------
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-11  9:05 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
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 [this message]
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=1097485559.3234.11.camel@localhost.localdomain \
    --to=mr@ramendik.ru \
    --cc=apenwarr@nit.ca \
    --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.