From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] x86 on x86 instruction error bug report
Date: Thu, 24 Feb 2005 18:56:47 +0400 [thread overview]
Message-ID: <421DEB2F.4030104@wasp.net.au> (raw)
G'day all,
I get this when trying to run the Office97 installer on Windows XP
http://www.wasp.net.au/~brad/office97-2.png
It appears to be an emulation issue. It occurs exactly the same running with/without kqemu.
Of course Win2k/WinXP on the bare metal runs it fine.
Is there anything I might be able to do to assist in debugging this issue?
Regards,
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next reply other threads:[~2005-02-24 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 14:56 Brad Campbell [this message]
2005-02-24 23:30 ` [Qemu-devel] x86 on x86 instruction error bug report Andrew Francis
-- strict thread matches above, loose matches on Subject: below --
2005-02-24 17:50 Hans Christian Studt
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=421DEB2F.4030104@wasp.net.au \
--to=brad@wasp.net.au \
--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).