From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Diwzw-0002po-Ni for qemu-devel@nongnu.org; Thu, 16 Jun 2005 12:13:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Diwzs-0002nZ-9T for qemu-devel@nongnu.org; Thu, 16 Jun 2005 12:13:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Diwzr-0002mx-RU for qemu-devel@nongnu.org; Thu, 16 Jun 2005 12:13:39 -0400 Received: from [64.233.162.204] (helo=zproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Dix0n-0004Us-Bn for qemu-devel@nongnu.org; Thu, 16 Jun 2005 12:14:37 -0400 Received: by zproxy.gmail.com with SMTP id 34so331160nzf for ; Thu, 16 Jun 2005 09:12:47 -0700 (PDT) Message-ID: <2ad73a050616091264ddb033@mail.gmail.com> Date: Thu, 16 Jun 2005 13:12:47 -0300 From: =?ISO-8859-1?Q?Andr=E9_Braga?= Subject: Re: [Qemu-devel] Booting Linux in Windows XP In-Reply-To: <4e39348605061606123222d205@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4e39348605061606123222d205@mail.gmail.com> Reply-To: =?ISO-8859-1?Q?Andr=E9_Braga?= , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 2005/6/16, Aaron Feng : > Yesterday I tried QEMU for the first time, I downloaded the 0.70 > Windows installer package, and everything installed just fine. I also > downloaded Mandrake 10 image from freeoszoo.org, but I'm having > trouble to get Mandrake to boot. Here is the command I used: >=20 > qemu.exe -L "path_to_my_mandrake_image" >=20 > Nothing happened, I just get the prompt back without any errors. Is > there any way for me to get a more informative error messages when I'm > trying to boot? Well, I guess you misunderstood the documentation, as you gave QEMU the wrong option. -L is supposed to be fed with the path to the BIOS image, not the OS image. The OS image file should be specified with -hda or -cdrom, depending on the case. --=20 "I invented the term Object-Oriented, and I can tell you I did not have C++ in mind"-Alan Kay