From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuCTJ-0008FU-DV for qemu-devel@nongnu.org; Tue, 23 Mar 2010 18:21:13 -0400 Received: from [140.186.70.92] (port=57779 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuCTI-0008DA-0f for qemu-devel@nongnu.org; Tue, 23 Mar 2010 18:21:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuCTH-0000kp-3z for qemu-devel@nongnu.org; Tue, 23 Mar 2010 18:21:11 -0400 Received: from smtp2-g21.free.fr ([212.27.42.2]:36308) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuCTG-0000k1-DI for qemu-devel@nongnu.org; Tue, 23 Mar 2010 18:21:11 -0400 Received: from smtp2-g21.free.fr (localhost [127.0.0.1]) by smtp2-g21.free.fr (Postfix) with ESMTP id 37C5D4B00E2 for ; Tue, 23 Mar 2010 23:21:05 +0100 (CET) Received: from laptop (vaf26-2-82-244-111-82.fbx.proxad.net [82.244.111.82]) by smtp2-g21.free.fr (Postfix) with ESMTP id 3F5DE4B009F for ; Tue, 23 Mar 2010 23:21:03 +0100 (CET) In-Reply-To: <61B4111F-8753-4C74-AA11-1E5918F7AB4B@claunia.com> Subject: Re: [Qemu-devel] BeOS R5 boot failure From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Tue, 23 Mar 2010 23:16:18 +0100 CET Message-Id: <11039166618-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > http://bochs.cvs.sourceforge.net/bochs/bochs/CHANGES=3Fview=3Dmarkup&content-type=3Dtext/vnd.viewcvs-markup&revision=3DREL=5F2=5F4=5F2=5FFINAL > > > 2.2.5 December 2005 BeOS boot failure fix in the PCI IDE code > > 2.3.5 September 2007 [1500216] Bochs fails to boot BeOs CD Hmm actually, I begin to think it just doesn't like booting from a partition image directly. The fact the bootloader lists the volume misleads into thinking it can boot... Using the image as cdrom with a floppy image works fine. Also, the log says ...ata/0/master/0/0=5F0 and 0=5F0 is supposed to be the first partition, which of course doesn't exist (and thus has a size of 0...), the whole block device should have been .../raw instead. I suppose I've been way too used to Haiku being able to boot this way. Those images were meant to be used in a FAT or ext2 partition, not straight away as disk images, unlike in Haiku. I suppose it was just too obvious :^) Fran=C3=A7ois.