From owner-freebsd-bugs Sun Jun 18 14:36:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA04766 for bugs-outgoing; Sun, 18 Jun 1995 14:36:13 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA04760 for ; Sun, 18 Jun 1995 14:36:12 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19499; Sun, 18 Jun 95 15:29:12 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9506182129.AA19499@cs.weber.edu> Subject: Re: 2.05R panics on boot To: hlew@genome.Stanford.EDU (Howard Lew) Date: Sun, 18 Jun 95 15:29:11 MDT Cc: bde@zeta.org.au, bugs@FreeBSD.org In-Reply-To: from "Howard Lew" at Jun 18, 95 01:40:01 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > 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). The DOSBOOT.COM loads the master boot record off the drive and gives control to it; in efect, it is a soft (targetable) reboot. The hacks you could do would choose the target. The source is either in the i386 directory or in the netboot directory (I forget). The file you will want to copy to your DOS disk as DOSBOOT.COM is dosboot.nohdr (again from memory -- check the docs and makefiles in the sources). This will be useless unless you can get booted and running to the point where the sources are installed and you can boot normally (if with a lot of effort). In otherwords, think about this *later*. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.