From owner-freebsd-stable Fri Oct 1 0:23:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 6222B14DE4 for ; Fri, 1 Oct 1999 00:23:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA02259; Fri, 1 Oct 1999 00:16:02 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910010716.AAA02259@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ed Watkeys Cc: stable@freebsd.org Subject: Re: Cdrecord problems to record 1 CD In-reply-to: Your message of "Tue, 28 Sep 1999 23:50:43 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Oct 1999 00:16:01 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 28 Sep 1999, Jeremy McMillan wrote: > > > You need to read the spec for El-Torito. > > > > Basically, you need a boot image written to block 0 of your raw CD-R. That > > boot image needs to know how to access your hardware (ie. load a kernel from > > somewhere?). Bootable CDROM supporting BIOS just looks at the first block of > > your CDROM and uses it *just* like the boot blocks from a floppy. > > This is not the most helpful response. At your urging, I read the El > Torito spec, and what you're saying above does not appear to be true > of the Walnut Creek 3.2 install CD I have or the ISO image for the 3.3 > install CD. What you're describing seems to be the "multiple boot > image configuration" that's discussed in the spec. The 3.2 and 3.3 CDs > appear to be of the "single boot image configuration" variety. We just use mkisofs to creat the bootable images, same as everyone else. The problem, which was resolved this evening, seems to be that mkisofs space-pads the copyright text in the boot catalog. If you have no copyright text (like eg. the 3.2 image), it's all-0 and boots properly on most systems. If you have copyright text, it's space-filled and terminated with a single 0 byte, and this fails. Interestingly, the Windows NT CDROM has copyright text in the boot catalog that is nul-filled, and this CDROM (probably the only benchmark for bootable CDROMs in the industry) boots just fine, leading to the conjecture that someone got sloppy in their BIOS code, which has been widely replicated. In effect, it's the fact that Jordan was _more_ careful cutting the 3.3 images that lead to this problem. Damn that quality control process. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message