From owner-freebsd-bugs Sun Jun 18 13:40:08 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA02547 for bugs-outgoing; Sun, 18 Jun 1995 13:40:08 -0700 Received: from vegemite.Stanford.EDU (2842@vegemite.Stanford.EDU [36.159.0.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA02531 for ; Sun, 18 Jun 1995 13:40:04 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA18716; Sun, 18 Jun 1995 13:40:02 -0700 Date: Sun, 18 Jun 1995 13:40:01 -0700 (PDT) From: Howard Lew To: Terry Lambert cc: Bruce Evans , bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <9506172320.AA16151@cs.weber.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk > If you *only* have BSD on the second drive, and are willing to blow it > away, you can get the same effect by making the BSD drive the primary > drive, installing OnTrack (assuming you have it), then installing BSD onto > what is now the first drive. Yep, I only have FreeBSD on the second drive, but unfortunately, Ontrack is smart in that it won't install on a drive that didn't have the software bundled with the hard drive in the first place. Now the question is if I did swap cables and redo the jumpers, will DOS boot from drive D if I used the FreeBSD bootmanager on drive C. (The bios says boot from A and then C.) I can see a potential problem in that I will not be able to access the DOS files from FreeBSD because no Ontrack DM boot overlay will ever be loaded. > The DOSBOOT.COM might be more easily hacked to work -- but it depends > on if negative offsets are allowed. Okay, I have not heard a lot about this DOSBOOT.COM, so will it let me boot up FreeBSD from wd1a from DOS (wd0)? If it does, then this will be a good temporary fix (of course I have to boot up DOS every time I want to use FreeBSD or a place a script in the autosec.bat).