From: Hetz Ben Hamo <hetzbh@gmail.com>
To: sol10x86@cox.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] WinXPHome update failed
Date: Thu, 7 Apr 2005 14:14:46 +0200 [thread overview]
Message-ID: <41e41e7a05040705146e557ae@mail.gmail.com> (raw)
In-Reply-To: <20050407114954.IHFD3789.lakermmtao05.cox.net@smtp.east.cox.net>
Hi,
Which version of QEMU?
Leonardo mentioned few days ago that there seems to be a problem in
the emulation with 1 or more instructions (if my memory served well).
Could you test it on Linux X86 with kqemu?
Thanks,
Hetz
On Apr 7, 2005 1:49 PM, Ben Taylor <sol10x86@cox.net> wrote:
> I was running Windows update for XPHome hosted by Solaris
> 10, and got the following message last night:
> --
> The instruction at "0x00fbdffb" referenced memrory at
> "0x01b70094" The memory could not be "read".
>
> Click OK to terminate program
>
> <OK>
> --
> The program was called setup_wm.exe and appears to be
> the Windows Media Player 10 update. Ideas?
>
> Ben
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
prev parent reply other threads:[~2005-04-07 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 11:49 [Qemu-devel] WinXPHome update failed Ben Taylor
2005-04-07 12:14 ` Hetz Ben Hamo [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=41e41e7a05040705146e557ae@mail.gmail.com \
--to=hetzbh@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sol10x86@cox.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 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).