From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: W2K SP0 Status - mmx build
Date: Mon, 17 Jan 2005 22:10:53 +0100 [thread overview]
Message-ID: <pan.2005.01.17.21.10.50.899610@reply.to> (raw)
In-Reply-To: f3798e1205011712384bebf166@mail.gmail.com
Le Mon, 17 Jan 2005 15:38:02 -0500, Joe Bogner a écrit :
> I'm having trouble executing qemu after compiling on w2k pro. I downloaded
> the 0.6.1 source and followed the porting instructions. Everything
> compiled (although I had to use SDL-1.2.8-devel because SDL wouldn't
> compile). I'm getting a segfault when I run the compiled binary. The
> official release of 0.6.1 works fine on my machine (with the same image).
> The version I compiled won't even show the BIOS before crashing...
>
> Here's the GDB results:
>
> $ gdb qemu.exe
> GNU gdb 5.2.1
> Copyright 2002 Free Software Foundation, Inc. GDB is free software,
> covered by the GNU General Public License, and you are welcome to change
> it and/or distribute copies of it under certain conditions. Type "show
> copying" to see the conditions. There is absolutely no warranty for GDB.
> Type "show warranty" for details. This GDB was configured as
> "i686-pc-mingw32"... (gdb) set args -L c:/progra~1/qemu/bios -hda
> c:/virtual/temp.img (gdb) r
> Starting program: c:\dev\qemu\qemu-0.6.1\i386-softmmu/qemu.exe -L
> c:/progra~1/qe
> mu/bios -hda c:/virtual/temp.img
>
> Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? ()
> (gdb) backtrace
> #0 0x00000000 in ?? ()
> #1 0x0044e414 in cpu_x86_exec (env1=0x0)
> at c:/dev/qemu/qemu-0.6.1/cpu-exec.c:540
>
>
> I also had the same results with the CVS source. My goal is to enable MMX
> in the windows build so I can attempt to install MDAC/.NET Framework on my
> windows 2000 pro image. My image works great except that I get an access
> violation when attempting to install the .NET framework. I read on here
> that lack of MMX support could be at fault.
>
> Does anyone have any suggestions on what I should try? I've been fighting
> with this for at least 5 hours.... Or, I'd be grateful if someone could
> just create a windows build with MMX enabled (as specified below).
>
You can try this one (untested):
qemu.exe(not stripped) + SDL.dll(stripped) (1576kbytes)
http://daimon55.free.fr/qemu/qemu.zip
> Thanks,
> Joe
>
next prev parent reply other threads:[~2005-01-17 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 20:38 [Qemu-devel] W2K SP0 Status - mmx build Joe Bogner
2005-01-17 21:10 ` Ronald [this message]
2005-01-17 23:58 ` [Qemu-devel] " Joe Bogner
2005-01-18 4:30 ` [Qemu-devel] " Joe Bogner
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=pan.2005.01.17.21.10.50.899610@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--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).