qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dan Sandberg <dan.sandberg@medsci.uu.se>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] win98 slow with kqemu
Date: Mon, 08 Jan 2007 11:11:31 +0100	[thread overview]
Message-ID: <45A218D3.2050801@medsci.uu.se> (raw)
In-Reply-To: <200701061743.11495.mr@ramendik.ru>

...also make sure that you have installed the CPU usage reduction fix 
for Windows 98, se manual: 3.11.2.2
(The link in the manual seems to be dead, but working ones can be found 
using Google.)

/Dan


Mikhail Ramendik wrote:

>On Tuesday 02 January 2007 12:54, Dan Sandberg wrote:
>
>  
>
>>On the other hand, if for instance VMware is able to run Windows 98 much
>>faster (I do not have it so I can't test this) then my guess is that
>>kqemu is the guilty part and does something wrong with 16-bit code.
>>    
>>
>
>Thanks. Will test with VMWare and report.
>
>  
>

      reply	other threads:[~2007-01-08 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 18:09 [Qemu-devel] win98 slow with kqemu Mikhail Ramendik
2007-01-02 12:54 ` Dan Sandberg
2007-01-06 17:43   ` Mikhail Ramendik
2007-01-08 10:11     ` Dan Sandberg [this message]

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=45A218D3.2050801@medsci.uu.se \
    --to=dan.sandberg@medsci.uu.se \
    --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).