From owner-freebsd-advocacy Wed Nov 29 9:47:39 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F75C37B400; Wed, 29 Nov 2000 09:47:35 -0800 (PST) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.org [12.23.109.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id KAA28591; Wed, 29 Nov 2000 10:47:29 -0700 (MST) Message-Id: <4.3.2.7.2.20001129104503.049744e0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 29 Nov 2000 10:47:23 -0700 To: Terry Lambert , /dev/null@FreeBSD.ORG From: Brett Glass Subject: Re: Here is what IBM thinks about using FreeBSD on their newer Thinkpads Cc: tlambert@primenet.com (Terry Lambert), freebsd-chat@FreeBSD.ORG, freebsd-advocacy@FreeBSD.ORG In-Reply-To: <200011281826.LAA10263@usr08.primenet.com> References: <200011281817.eASIHSF25817@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:26 AM 11/28/2000, Terry Lambert wrote: >I think this presumes that the HD is examined at boot time, >instead of stopping once the system sees a bootable CDROM, >which is the normal case when doing a recovery. If the problem is a BIOS that can't handle a FreeBSD boot sector, perhaps a special boot sector with replacement hard disk BIOS code -- such as the one included in OnTrack Disk Manager -- would serve as a workaround. The problem could also be that the laptop has a suspend/resume feature that's looking for a special partition or DOS file and not finding it. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message