From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J45z4-0007ux-QX for qemu-devel@nongnu.org; Sun, 16 Dec 2007 21:45:34 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J45yz-0007tF-Py for qemu-devel@nongnu.org; Sun, 16 Dec 2007 21:45:34 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J45yz-0007t8-M4 for qemu-devel@nongnu.org; Sun, 16 Dec 2007 21:45:29 -0500 Received: from mx10.roch.ny.frontiernet.net ([66.133.183.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J45yy-0003AC-1t for qemu-devel@nongnu.org; Sun, 16 Dec 2007 21:45:28 -0500 Received: from localhost (filter01.roch.ny.frontiernet.net [66.133.183.68]) by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id AA1C5A1450 for ; Mon, 17 Dec 2007 02:45:15 +0000 (UTC) Received: from relay04.roc.ny.frontiernet.net ([66.133.182.167]) by localhost (filter01.roch.ny.frontiernet.net [66.133.183.68]) (amavisd-new, port 10024) with LMTP id zKRexX0bP+j6 for ; Sun, 16 Dec 2007 21:45:15 -0500 (EST) Received: from fys (170-215-38-107.dsl2.kgm.az.frontiernet.net [170.215.38.107]) by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 41761A13DA for ; Mon, 17 Dec 2007 02:45:15 +0000 (UTC) Message-ID: <001301c84056$e0289420$01fea8c0@fys> From: "Benjamin David Lunt" Date: Sun, 16 Dec 2007 19:45:18 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] floppy disk 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 everyone, I only recently have started to use QEmu due to a request on the alt.os.development usenet group. My OS was not working on QEmu due to it would not recognize the (emulated) floppy. After a lot of testing, QEmu does not return the correct values for a Sense Interrupt command and the Status 0 byte. After looking over fdc.cc, someone has placed a hack write where it should return these values. I am just wondering if this hack is temporary or if it will be committed as code. For a more detailed description, QEmu returns the value 0x20 while Bochs, VMware, and real hardware return the values 0xC0, 0xC1, 0xC2, and 0xC3, for each drive 1 - 4 respectively. I am asking for more information on this subject. For more information, please see the thread Re: FYSOS under QEMU in alt.os.development dated 14 Dec 2007, 7:24pm Thank you. Ben Lunt