Bug 17752

Summary: Cannot install BTX boot manager
Product: Base System Reporter: andrew <andrew>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.4-RELEASE   
Hardware: Any   
OS: Any   

Description andrew 2000-04-02 17:00:02 UTC 
/stand/sysinstall is supposed to automatically install BTX boot manager.
Unfortunately it silently uses the option 'Nopacket'. I have a system on
which nopacket is not viable, and boots to a bleep and sudden death.
There is no indication to the user that there is a choice over this 
matter in the install script, nor any hint in the man page for boot
that you need to do man boot0cfg! this must surely be the least guessable 
acronym in the knwon univers for a new user!

Fix: 

This is primarily a documentation deficiency: you cannot install the system
without knowing things which you cannot find out until it is installed!
sysinstall needs to be enhanced to probe as to whether packet option
is required, and there needs to be a way of selecting the option preferably
in the screen where you select where to install BootEasy. 
There also needs to be an obvious way of re-installing bootEasy/BTX 
after MS products trash your boot sector!
How-To-Repeat: Try installing on my PC! Haicom mobo with on board IDE set to AUTO
and a Seagate HD.
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-04-03 13:52:57 UTC 
Responsible Changed
From-To: freebsd-bugs->dcs

I think this is Daniel's arena.  Daniel, please let me know if 
I've madea mistake.
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2000-04-25 16:51:35 UTC 
State Changed
From-To: open->closed

Packet mode is not supported.  Installation on partitions above 8GB 
is not supported.  boot0cfg probably doesn't need to be cross-ref'd 
from boot(8), because instructions on re-installing the boot        
manager are provided in the FAQ: 

http://www.freebsd.org/FAQ/install.html#AEN480 

This FAQ addresses your concern regarding the perceived lack 
of documentation on recovering from Microsoft damage.
Comment 3 Sheldon Hearn freebsd_committer freebsd_triage 2000-04-25 16:51:35 UTC 
Responsible Changed
From-To: dcs->freebsd-bugs

This would have been better addressed by rnordier or jhb, 
although that's a moot point now. :-)