All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Johansson" <esj@harvee.org>
To: Mark Williamson <maw48@hermes.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: running Windows (albeit slowly)
Date: Wed, 24 Nov 2004 09:15:28 -0500	[thread overview]
Message-ID: <41A49780.7020505@harvee.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0411241301070.23620@hermes-1.csi.cam.ac.uk>

Mark Williamson wrote:
>> Under the opinion that there is no crime if optimization fails on 
>> incorrect code, would it not be appropriate to do all the things 
>> necessary to run Windows unmodified albeit poorly slash slowly?
> 
> 
> It's not just that the modifications improve performance, guests 
> actually need to be modified to work on Xen at all.

I'm sorry.  I misunderstood what was written.  I was under the 
impression that to run Windows or unmodified operating systems quickly 
required a great deal of complexity on the order of vmware and that you 
could run Windows slower (under certain circumstances) with "simple" 
emulation features

> If you want a free means of running a Windows virtual machine your best 
> bet right now is probably QEmu.  Faster than Bochs although with less 
> complete machine emulation.  The author intends to enhance it further to 
> eventually get VMWare levels of performance (although that's a 
> non-trivial undertaking!).

I was under the impression that the performance degradation for qemu was 
on the order of 3x native which would be a bit problematic for speech 
recognition.  Is this impression wrong as well?


> Yeah, speech recognition on Linux (and others) is a bit of a pain. There 
> are a few open source products (e.g. sphinx, perlbox) but I doubt 
> they're usuable for dictation, if that's what you want.  Out of 
> interest, does Wine have any success at running NaturallySpeaking / 
> ViaVoice / whatever?

tell me about it.  I am heavily involved in the Open Source Speech 
Recognition Initiative (www.ossri.org) and just trying to figure out 
what's necessary to make NaturallySpeaking work on wine is a handful 
because we need to make it tremendous number of assumptions about 
NaturallySpeaking.  Scansoft, the current owner of the desktop speech 
recognition monopoly, views customers as a hostile necessity and doesn't 
provide any support to anybody for any reason unless you show up with a 
big fat checkbook.

The open source speech recognition engines are "cute research projects". 
  To get something useful will take approximately five to eight years of 
work and $40 million.  in other words, we're going to need some major 
grants.

as for wine and NaturallySpeaking, we can't get past install.  Again we 
are going to hunt for grants sometime after the first of the year to pay 
for the evaluation and development.  It wouldn't be entirely fair to go 
to the wine community without some compensation for their efforts.

---eric


-- 
"Part of the problem with the Wal-Mart business model is that it
requires more poverty in order to grow."

http://www.salon.com/mwt/feature/2004/11/22/wal_mart/print.html


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-24 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 12:38 running Windows (albeit slowly) Eric S. Johansson
2004-11-24 13:09 ` Mark Williamson
2004-11-24 14:15   ` Eric S. Johansson [this message]
2004-11-24 16:36     ` M.A. Williamson
2004-11-24 14:50   ` Dave Feustel
2004-11-24 17:08   ` David Hopwood
2004-11-24 13:27 ` Steven Hand

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=41A49780.7020505@harvee.org \
    --to=esj@harvee.org \
    --cc=maw48@hermes.cam.ac.uk \
    --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.