os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update the NT loader directions.

Browse source 
PR:		19174
Submitted by:	Mark Ovens <mark@dogma.freebsd-uk.eu.org>
This commit is contained in:
Jeroen Ruigrok van der Werven 2000-06-12 11:37:05 +00:00
parent 5656880b00
commit 39e10b04ea
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7329
2 changed files with 48 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

29
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.57 2000/06/04 15:18:05 asmodai Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.58 2000/06/09 11:10:48 alex Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -4390,10 +4390,29 @@ native partitions.</para>
<para>For FreeBSD 3.x systems the procedure is somewhat simpler.</para>
<para>If FreeBSD is installed on the same disk as the NT boot partition
copy <filename>/boot/boot1</filename> to <filename>c:\bootsect.bsd</filename>
or if FreeBSD is installed on a different disk copy
<filename>/boot/boot0</filename> to <filename>c:\bootsect.bsd</filename>.
Then edit <filename>c:\bootsect.ini</filename> as described earlier.</para>
simply copy <filename>/boot/boot1</filename> to
<filename>C:\BOOTSECT.BSD</filename> However, if FreeBSD is installed
on a different disk <filename>/boot/boot1</filename> will not work,
<filename>/boot/boot0</filename> is needed.
<warning>
<para>DO NOT SIMPLY COPY <filename>/boot/boot0</filename> INSTEAD OF
<filename>/boot/boot1</filename>, YOU WILL OVERWRITE YOUR PARTITION
TABLE AND RENDER YOUR COMPUTER UN-BOOTABLE!</para></warning>
<filename>/boot/boot0</filename> needs to be installed using
sysinstall by selecting the FreeBSD boot manager on the screen which
asks if you wish to use a boot manager. This is because
<filename>/boot/boot0</filename> has the partition table area filled
with NULL characters but sysinstall copies the partition table before
copying <filename>/boot/boot0</filename> to the MBR.</para>
<para>When the FreeBSD boot manager runs it records the last OS booted
by setting the active flag on the partition table entry for that OS
and then writes the whole 512-bytes of itself back to the MBR so if
you just copy <filename>/boot/boot0</filename> to
<filename>C:\BOOTSECT.BSD</filename> then it writes an empty partition
table, with the active flag set on one entry, to the MBR.</para>
</answer></qandaentry>

29
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.57 2000/06/04 15:18:05 asmodai Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.58 2000/06/09 11:10:48 alex Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -4390,10 +4390,29 @@ native partitions.</para>
<para>For FreeBSD 3.x systems the procedure is somewhat simpler.</para>
<para>If FreeBSD is installed on the same disk as the NT boot partition
copy <filename>/boot/boot1</filename> to <filename>c:\bootsect.bsd</filename>
or if FreeBSD is installed on a different disk copy
<filename>/boot/boot0</filename> to <filename>c:\bootsect.bsd</filename>.
Then edit <filename>c:\bootsect.ini</filename> as described earlier.</para>
simply copy <filename>/boot/boot1</filename> to
<filename>C:\BOOTSECT.BSD</filename> However, if FreeBSD is installed
on a different disk <filename>/boot/boot1</filename> will not work,
<filename>/boot/boot0</filename> is needed.
<warning>
<para>DO NOT SIMPLY COPY <filename>/boot/boot0</filename> INSTEAD OF
<filename>/boot/boot1</filename>, YOU WILL OVERWRITE YOUR PARTITION
TABLE AND RENDER YOUR COMPUTER UN-BOOTABLE!</para></warning>
<filename>/boot/boot0</filename> needs to be installed using
sysinstall by selecting the FreeBSD boot manager on the screen which
asks if you wish to use a boot manager. This is because
<filename>/boot/boot0</filename> has the partition table area filled
with NULL characters but sysinstall copies the partition table before
copying <filename>/boot/boot0</filename> to the MBR.</para>
<para>When the FreeBSD boot manager runs it records the last OS booted
by setting the active flag on the partition table entry for that OS
and then writes the whole 512-bytes of itself back to the MBR so if
you just copy <filename>/boot/boot0</filename> to
<filename>C:\BOOTSECT.BSD</filename> then it writes an empty partition
table, with the active flag set on one entry, to the MBR.</para>
</answer></qandaentry>