From owner-freebsd-questions Tue May 14 19:02:52 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA02979 for questions-outgoing; Tue, 14 May 1996 19:02:52 -0700 (PDT) Received: from riley-net170-164.uoregon.edu (riley-net170-164.uoregon.edu [128.223.170.164]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA02974 for ; Tue, 14 May 1996 19:02:46 -0700 (PDT) Received: (from dwhite@localhost) by riley-net170-164.uoregon.edu (8.6.12/8.6.12) id TAA08094; Tue, 14 May 1996 19:05:33 -0700 Date: Tue, 14 May 1996 19:05:33 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Annelise Anderson cc: freebsd-questions@freebsd.org Subject: Re: Boot Manager Problem In-Reply-To: <01I4P4Q6K2KI005SCF@HOOVER.STANFORD.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 14 May 1996, Annelise Anderson wrote: > I have gotten into a little trouble with my OS/2 boot manager and I > hope someone here can tell me what to do. Let's take a look. I have a similar system as yours, less scsi. > Originally DOS/Win3.1 and FreeBSD 2.0.5R were running on a 515 MB SCSI > drive with BootEasy installed. OK... > I added a second SCSI hard drive and put a 300 MB dos partition on it > and gave 2.1R (now 2.1-STABLE) the balance, 1.7 Gb or something like > that. During this process I left BootEasy alone and installed OS/2's > boot manager; BootEasy added the OS/2 boot manager to its list of > options and also added an F5 for the second hard drive. But I didn't > put BootEasy on the second hard drive. That's OK, booteasy finds all sorts of stuff. It probably wouldn't have worked anyway. > Then I deleted the DOS/Win3.1 partition on the first hard drive, > created two primary partitions there, and put that awful monster > Win95 on the first one, with the second hard drive disconnected. Whoops. Win95 will wipe the boot sector when it installs. > Now BootEasy is apparently gone and I've reactivated OS/2's boot > manager, which sees everything on the first drive and the DOS > partition on the second drive, but not the FreeBSD 2.1S partition. > So to boot the 2.1S I have to select the 2.0.5 installation on the > first drive and type sd(1,a)/kernel. OK... > OS/2's fdisk shows the DOS partition on the second drive as bootable > (which it's not, but that's okay) and lists the FreeBSD partition > but won't let me give it a name or add it to the boot manager list. > So somewhere the information on where it is got lost, and I don't know > what to do to reestablish it. What is the error OS/2 Fdisk gives you? My FreeBSD partition added without a hitch, but it's on a second IDE disk. My guess is that you either didn't install the FreeBSD partition in other systems compatibility mode, the geometry is wrong, or the system can't see to boot onto sd1 (which may be if the SCSI doesn't have boot ROMs). Being somewhat ignorant of SCSI I'm not sure of the last one. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major