From owner-freebsd-hackers  Mon Jun  5 12:30:41 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id MAA23274
          for hackers-outgoing; Mon, 5 Jun 1995 12:30:41 -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 MAA23267
          for <hackers@freebsd.org>; Mon, 5 Jun 1995 12:30:40 -0700
Received: (hlew@localhost) by vegemite.Stanford.EDU (8.6.10/8.6.4) id MAA03656; Mon, 5 Jun 1995 12:30:30 -0700
Date: Mon, 5 Jun 1995 12:30:29 -0700 (PDT)
From: Howard Lew <hlew@genome.Stanford.EDU>
To: Poul-Henning Kamp <phk@ref.tfs.com>
cc: hackers@freebsd.org
Subject: Re: latest boot.flp
In-Reply-To: <199506051910.MAA22511@ref.tfs.com>
Message-ID: <Pine.SUN.3.91.950605122457.3628B-100000@vegemite.Stanford.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@freebsd.org
Precedence: bulk

On Mon, 5 Jun 1995, Poul-Henning Kamp wrote:

> > > 1) I select NONE for bootcode, it still overwrites the OS/2 bootmanager
> > > boot code.
> > > 
> > 
> > I had a similar problem here when the 2.05A install did a clean wipe of the 
> > On Track Disk Manager DOS bootcode for a wd0 even though I was installing on 
> > wd1.
> 
> This is bad.
> 
> Did it see the On Track at all ?  (either boot -v, or look for offset -63
> in the partition screen).

Yes, at boot up it did see the On Track DM (a very quick message).

I think in the SNAPs, the boot code used to place itself first, and 
retain the rest of the boot sequence.  But this time it didn't.

Is there any chance we will have the option to copy an image of the original 
bootcode to a floppy and have the opportunity to undo the boot stuff if 
our DOS partition becomes unbootable after installing the boot manager?