From owner-freebsd-questions Wed May 12 13:32:16 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 8F2C2153B5 for ; Wed, 12 May 1999 13:32:08 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id NAA07353; Wed, 12 May 1999 13:32:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 12 May 1999 13:32:04 -0700 (PDT) From: Doug White To: Laurence Berland Cc: questions@FreeBSD.ORG Subject: Re: Win 98/FreeBSD with System Commander In-Reply-To: <373501B0.D0F23DE6@confusion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 May 1999, Laurence Berland wrote: > System commander is designed to let me place complete partitions for any > OS anywhere on the disk. I've seen linux partitions placed well above > the 1024 cylinder with SysCom. While trying a 3.1-Release install off > the CD, i get as far as the disk labeler, where it complains that the > partition is above 1024 and so it can't create the partition, or if I > try to make swap partition it says could not create, Too big? What do > I do? Is there a way to force it to label anyway? If not I'm worried > this person won't use FreeBSD, but will turn to Linux instead, and I > don't want that to happen. The problem is that your BIOS can't address the disk that high. SysCommander can shim the bootloader enough to make it start, but it won't load the kernel since it can't read the disk. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message