From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BcRY0-00038K-CW for qemu-devel@nongnu.org; Mon, 21 Jun 2004 12:21:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BcRXy-000388-KG for qemu-devel@nongnu.org; Mon, 21 Jun 2004 12:21:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BcRXy-000385-Hc for qemu-devel@nongnu.org; Mon, 21 Jun 2004 12:21:26 -0400 Received: from [62.253.162.46] (helo=mta06-svc.ntlworld.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BcRVy-0005Mw-EP for qemu-devel@nongnu.org; Mon, 21 Jun 2004 12:19:22 -0400 Received: from [10.10.10.100] ([81.107.87.144]) by mta09-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20040617104330.CUHK12232.mta09-svc.ntlworld.com@[10.10.10.100]> for ; Thu, 17 Jun 2004 11:43:30 +0100 Subject: Re: [Qemu-devel] Useful Q&A From: Antony T Curtis In-Reply-To: <40D0AF18.3070203@fabianowski.de> References: <1087396951.40d05c57252a0@www.raysa.org> <40D0AD00.7050207@silentsoftware.co.uk> <40D0AF18.3070203@fabianowski.de> Content-Type: text/plain Message-Id: <1087468971.16227.43.camel@pcgem.rdg.cyberkinetica.com> Mime-Version: 1.0 Date: Thu, 17 Jun 2004 11:42:51 +0100 Content-Transfer-Encoding: 7bit Reply-To: 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 On Wed, 2004-06-16 at 21:35, Bartosz Fabianowski wrote: > > Where can I find a *Full* listing of all of the command line parameters > > for QEMU (i.e. includes "-cirrus")? > > I posted this a few days ago. Go to QEMU's source directory and run: > > egrep "^ QEMU_OPTION_" vl.c > > > Why doesn't (guest) Windows 98 (FE) recognise the emulated sound card > > as new hardware on my host Mandrake 10.0 machine when I specifiy > > "-enable-audio" - it doesn't think there is one at all? > > If you're not using -pci, the sound card is not plug'n'play. Maybe the > Windows hardware detection just fails to find it and you need to add it > manually? Using my PnP patch, it shouldn't be hard to make it "Plug and Play" compatible... --