FreeBSD and Windows coexist channel Installation of the first 2,003, then loaded the BSD, BSD wanted to be added to the start menu for 2003, achieving multiple start, but found bottles BSD unable to start after 2003, the document seems to be activated damage and re-tested many times is the case, can you work methods ah? If this is the case I would not be able to heavy-BSD, a heavy equipment will not be able to use the BSD,2003 FreeBSD and Windows coexist channel Choose not to install BSD guide for the installation. Find a guide for dos proceedings to put the grub grub (purchase online) This is good. Grub is the best guide for the better than linux. . FreeBSD and Windows coexist channel Sbm guide with the most convenient. Http://btmgr.sourceforge.net/index.php3?body=docs/user-guide-zh-4.html FreeBSD and Windows coexist channel Continue FreeBSD and Windows coexist channel Here is the installation of grub, grub really good use, highly recommended. . Cd /usr/ports/sysutils/grub Make install clean FreeBSD and Windows coexist channel Determine your district when these two systems are the main area (some so-called basic District), 2003 can be put into an area of activity, and through the failure to restore control over the operations fixmbr and fixboot This can be activated by 2003, then the district into an FreeBSD activities. Bootmgr installation will add primes into 2003 with the launch of the guide can be recorded. Welcoming Exchange MSN:msen@hotmail.com ICQ:169356568 FreeBSD and Windows coexist channel If not the main area of activity can become established, in which the main branch is inside Windows -- it is the C : hard disk and the physical location of the district does not matter. FreeBSD and Windows coexist channel Disk access district manager, which is installed in the space that divided BSD interface? W, from the restart. I certainly do not see the stickers FreeBSD and Windows coexist channel FB installed into your system after installation using dd if=/dev/ FB district of=fb.boot bs=512 count=1 and then duplicating it to diskette. Before installing Windows, in addition c:\fb.boot= under BOOT "FreeBSD." Easy, of course, put a plate fb.boot Kaodao C -_- FreeBSD and Windows coexist channel [quote][i] Note from the original "goat"] to determine your district when these two systems are the main area (some so-called basic District), 2003 can be put into an area of activity, and through the failure to restore control over the operations fixmbr and fixboot so we can start 2003. then FreeBSD district into an activity that will be installed at their Bootmgr plus. . . . . . . . . . [/quote [/i] released : My method is complex and can be done after 2003 can not lead to the installation of FreeBSD, if it is a new system can refer to other older methods. FreeBSD and Windows coexist channel Ntloader started to realize more fully the use of the menu. In a project that will add boot.ini. I like that. [boot Loader] Timeout=1 Default=c:\freebsd.lnx [operating Systems] C:\freebsd.lnx= "FreeBSD 5.2" The multi (0) disk (0) rdisk (0) partiton (1) \WINDOWS= "Server 2003" /fastdetect Fb freebsd.lnx in order that generated using dd, only 512 bytes freebsd Sector front of the contents. FreeBSD and Windows coexist channel That further complicated repair about 2003 [ Closed window ]