From owner-freebsd-current@FreeBSD.ORG  Mon Apr 19 07:28:16 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 11D4416A4CE
	for <current@freebsd.org>; Mon, 19 Apr 2004 07:28:16 -0700 (PDT)
Received: from chuggalug.clues.com (chuggalug.demon.co.uk [62.49.17.236])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5A42A43D2D
	for <current@freebsd.org>; Mon, 19 Apr 2004 07:28:15 -0700 (PDT)
	(envelope-from geoffb@chuggalug.clues.com)
Received: from chuggalug.clues.com (localhost [127.0.0.1])
	by chuggalug.clues.com (8.12.10/8.12.10) with ESMTP id i3JEMg3N066650
	for <current@freebsd.org>; Mon, 19 Apr 2004 14:22:43 GMT
	(envelope-from geoffb@chuggalug.clues.com)
Received: (from geoffb@localhost)
	by chuggalug.clues.com (8.12.10/8.12.10/Submit) id i3JEMg6a066649
	for current@freebsd.org; Mon, 19 Apr 2004 14:22:42 GMT
	(envelope-from geoffb)
Date: Mon, 19 Apr 2004 14:22:42 +0000
From: Geoff Buckingham <geoffb@chuggalug.clues.com>
To: current@freebsd.org
Message-ID: <20040419142242.GB65324@chuggalug.clues.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: newfs_msdos behaviour change between 4.x and 5?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2004 14:28:16 -0000


Under 4.x the following produces a bootable dos fat partition:

newfs_msdos -B /boot/win28.b -S 512 -r 32 -i l -c 32 -n 2 -k 6 -m 0xf8 /dev/da0s1
mount_msdos -l /dev/da0s1 /dest
cp IO.SY /dest/
cp MSDOS.SYS /dest/
cp COMMAND.COM /dest/

Where /boot/win28.b is a dd'd copy of the first 28 512 byte 
sectors of a bootable win95 sr2 partition and IO.SYS,
MSDOS.SYS and COMMAND.COM come from the same FS.

(Obviosley the da0s1 need to be created matching the BIOS's 
idea of the GEOMTREY)

However under 5.2.1 the above produces a non-bootable fs

Any ideas where I should be looking for the cause of this?