Date: Sun, 18 Jun 1995 13:40:01 -0700 (PDT) From: Howard Lew <hlew@genome.Stanford.EDU> To: Terry Lambert <terry@cs.weber.edu> Cc: Bruce Evans <bde@zeta.org.au>, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot Message-ID: <Pine.SUN.3.91.950618133028.18684C-100000@vegemite.Stanford.EDU> In-Reply-To: <9506172320.AA16151@cs.weber.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.950618133028.18684C-100000>