>Number:         25550
>Category:       port-i386
>Synopsis:       i386 boot selector broken
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 12 21:21:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     Gregory McGarry
>Release:        NetBSD 2.0_BETA from tgm on 2004-05-05
>Organization:
>Environment:
NetBSD/i386
>Description:
The i386 boot selector was working fine at and before NetBSD 1.6.  It doesn't now.

I have NetBSD 2.0 installed in the first MBR partition on wd0 and Windows installed in the first MBR partition on wd1.  The old boot selector would allow me to assign the names "NetBSD" and "Windows" to the F1 and F5 keys to boot from these partitions.

No it has the following problems:

1) It doesn't display any text on the display and sits there waiting until the timeout expires.
2) None of the F* keys work (it prints "Error?" to the display), except for _F2_, which boots from the NetBSD partition.  

As per PR25113, I think there has been a regression in functionality of the boot selector, since it won't allow names to be allocated to partitions and the F* keys.  But then, I would mind so much if they worked.

As an aside, and perhaps should be a separate PR, when I was originally trying to install NetBSD on wd1, the boot blocks were installed on wd1, rather than wd0.  I could never boot NetBSD.  Consequently, I had to swap the drives between master and slave.  But now I cannot boot Windows, because the boot selector is hosed.
>How-To-Repeat:
Try installing the boot selector.
>Fix:
I will try to use the 1.6 bootblocks, however, I'm not sure if the 2.0 fdisk will allow it.
>Release-Note:
>Audit-Trail:
>Unformatted: