From owner-freebsd-hackers Thu Aug 19 7:22:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id E46AA15151 for ; Thu, 19 Aug 1999 07:22:44 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id KAA91343 for ; Thu, 19 Aug 1999 10:21:42 -0400 (EDT) Message-Id: <199908191421.KAA91343@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: CDROM boot on a ThinkPad 600E... Date: Thu, 19 Aug 1999 10:21:40 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been attempting to track down why cdrom boots will not work with /boot/loader, but do just fine with the boot-block. I have come to the following wild speculation, and stab in the dark. /boot/loader uses some int13 stuff, which I found while reading in the boot0inst man page may cause trouble on certain machines. I believe this may be our smoking gun, but I lack the time and experience to actually track it down. I could use boot0cfg to set 'packet' mode, but I am affraid that by doing so I may loose all access to my machine and need to attack it with a boot floppy. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message