From owner-freebsd-bugs Sat Jun 17 13:25:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA03718 for bugs-outgoing; Sat, 17 Jun 1995 13:25:28 -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 NAA03710 for ; Sat, 17 Jun 1995 13:25:27 -0700 Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id NAA17592; Sat, 17 Jun 1995 13:19:09 -0700 Date: Sat, 17 Jun 1995 13:19:08 -0700 (PDT) From: Howard Lew To: Bruce Evans cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot In-Reply-To: <199506170757.RAA18958@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk On Sat, 17 Jun 1995, Bruce Evans wrote: > >> Only one case can't possibly work: loading the bootstrap off a floppy > >> and then attempting to boot from a hard disk (e.g., by typing > >> sd(1,a)/kernel). The boot code doesn't know about DM, so it won't > >> work if DM needs to be loaded. > >> > > >Right now the only way I can boot up FreeBSD system on the Ontrack DM > >system is by using boot.flp and entering wd(1,a)/kernel. This is very > >annoying. I have not tried and I doubt if I can access the msdos stuff > >from FreeBSD for now. > > This seems to be the case that I said can't work. Apparently wd1 doesn't > have Ontrack on it, but Ontrack on the boot disk adjusts for all disks. Yep, that's correct. It's too bad that DOS can't handle more than 504 MB for a large EIDE drive. Because if it could I wouldn't need to install the Ontrack DM overlay, and then FreeBSD would work like a charm. So can DOS access more than 504 MB per partition on SCSI drives? Oh well.... I guess the only alternative is to swap the hard drive cables and redo the master/slave jumpers... :-( Thanks for your help.