From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CVziz-0003yB-Pg for qemu-devel@nongnu.org; Sun, 21 Nov 2004 16:58:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CVziz-0003xz-Cm for qemu-devel@nongnu.org; Sun, 21 Nov 2004 16:58:25 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVzix-0003xu-40 for qemu-devel@nongnu.org; Sun, 21 Nov 2004 16:58:25 -0500 Received: from [12.18.159.130] (helo=b.smtp.elltel.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CVzZR-00039C-Ri for qemu-devel@nongnu.org; Sun, 21 Nov 2004 16:48:34 -0500 From: Ross Melin Date: Sun, 21 Nov 2004 13:48:31 -0800 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411211348.32141.rdmelin@yahoo.com> Subject: [Qemu-devel] windows98 can't see a cdrom 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 Hi all, I'm using v.0.6.1 installed from the mandrake rpm. When I boot from a vmdk image win98 install the vm boots but doesn't recognize a cdrom. It seems to make no difference if I declare a device or an iso image. Using the monitor to "change cdrom test.iso" or anything else also makes no difference. I thought maybe it was an issue with the vmdk image so I installed win98 from scratch on a raw disk image. The install went smoothly until time to run windows for the first time. Then again windows could not see a cdrom. Is this a known bug? Or perhaps a problem with my configuration? I will gladly provide any debug information that will help. Best regards, Ross Melin