From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 16 20:55:24 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6B3216A4B3 for ; Thu, 16 Oct 2003 20:55:24 -0700 (PDT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A47C643FBD for ; Thu, 16 Oct 2003 20:55:18 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.9/8.12.8) with ESMTP id h9H3t5hk031920; Fri, 17 Oct 2003 13:25:09 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: John Reynolds , hackers@freebsd.org Date: Fri, 17 Oct 2003 13:25:04 +0930 User-Agent: KMail/1.5.3 References: <16270.42776.767653.86364@whale.home-net> In-Reply-To: <16270.42776.767653.86364@whale.home-net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_Yg2j/fqT1isfJoC" Message-Id: <200310171325.05020.doconnor@gsoft.com.au> X-Spam-Score: -5 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: Re: boot0 screen output with dual-boot of FreeBSD / WinXP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 03:55:25 -0000 --Boundary-00=_Yg2j/fqT1isfJoC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thursday 16 October 2003 23:41, John Reynolds wrote: > After rebooting from there I see: > > F1 ?? > F2 FreeBSD > > at the prompt once the machine boots. My fuzzy memory seems to recall from > years back that seeing ??'s was "bad" as it meant the boot mgr couldn't > find out something it wanted. I chose both F1 and F2 in multiple boots and > each OS boots fine and acts normal. ... > So, it appears that partition type "7" just isn't a "known" type. Other > partition types seem to just "map" to print "DOS" (or whatever else). I > couldn't see where the "os_misc" string would be printed in the case of an > error of any sort, so can I assume that all is well with this partition and > dual boot combo and just ignore the '??'? Is it possible to add in another > table entry for type 0x7? Is it advisable? Basically, no. There is no room left in boot0 :( I think you could do it by squeezing down some text strings, and removing other [less common] entries though. The attached diff is a quick and dirty change which should do it.. I booted my laptop with it so it shouldn't be _that_ broken, but please keep a backup :) to apply.. cd /usr/src/sys/ patch <~/winxp.diff cd boot/i386/boot0 make sudo make install sudo boot0cfg -Bv /dev/xxxx -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 --Boundary-00=_Yg2j/fqT1isfJoC Content-Type: text/x-diff; charset="iso-8859-1"; name="winxp.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="winxp.diff" Index: boot/i386/boot0/boot0.s =================================================================== RCS file: /usr/CVS-Repository/src/sys/boot/i386/boot0/boot0.s,v retrieving revision 1.14.2.6 diff -u -r1.14.2.6 boot0.s --- boot/i386/boot0/boot0.s 19 Dec 2000 00:32:19 -0000 1.14.2.6 +++ boot/i386/boot0/boot0.s 17 Oct 2003 03:46:19 -0000 @@ -364,7 +364,7 @@ # # These values indicate bootable types we know the names of # - .byte 0x1, 0x4, 0x6, 0xb, 0xc, 0xe, 0x63, 0x83 + .byte 0x1, 0x6, 0x7, 0xb, 0xc, 0xe, 0x63, 0x83 .byte 0x9f, 0xa5, 0xa6, 0xa9 # # These are offsets that match the known names above and point to the strings --Boundary-00=_Yg2j/fqT1isfJoC--