From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Qemu Bugreport <qemubugreport@yahoo.com>
Subject: Re: [Qemu-devel] problem with qemm in dos and avg antivirus in xp
Date: Sat, 22 Jul 2006 22:27:31 +0100 [thread overview]
Message-ID: <200607222227.32891.paul@codesourcery.com> (raw)
In-Reply-To: <20060722211716.33778.qmail@web39808.mail.mud.yahoo.com>
> It says it might lock up and to reboot, which I do, and every time it moves
> on to the next step and locks up again. Eventually qemm thinks it has
> solved all of the problems and the install process finishes and it adds
> itself to autoexec etc, but the problem is still there. I guess this crash
> is not one that it expects, so is probably qemu specific. I have also had
> problems with programs that have built in extended memory managers (the emm
> seems to run, then the program claims a lack of memory).
It's possible it requires segment limits be enforced. qemu does not currently
do this.
Paul
next prev parent reply other threads:[~2006-07-22 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 21:17 [Qemu-devel] problem with qemm in dos and avg antivirus in xp Qemu Bugreport
2006-07-22 21:27 ` Paul Brook [this message]
2006-07-22 22:34 ` Nigel J. Terry
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=200607222227.32891.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=qemubugreport@yahoo.com \
/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).