View | Details | Raw Unified | Return to bug 154837
Collapse All | Expand All

(-)en_US.ISO8859-1/books/handbook/install/chapter.sgml (-25 / +68 lines)
Lines 631-665 Link Here
631
	</step>
631
	</step>
632
632
633
	<step>
633
	<step>
634
	  <title>Prepare the Memory Stick</title>
634
	  <title>Write The Image File to the Memory Stick</title>
635
635
	  
636
	  <warning>
636
	  <procedure>
637
	    <para>The example below lists
637
	    <title>Using FreeBSD To Write the Image</title>
638
	      <filename class="devicefile">/dev/da0</filename> as the target device from
639
	      which you will be booting.  Be very careful that you
640
	      have the correct device as the output target, or you may
641
	      destroy your existing data.</para>
642
	  </warning>
643
644
	  <para>Set the <varname>kern.geom.debugflags</varname> sysctl
645
	    to be able to write a master boot record to the target
646
	    device.</para>
647
638
648
	  <screen><userinput>&prompt.root; sysctl kern.geom.debugflags=16</userinput></screen>
639
	    <warning>
649
	</step>
640
	      <para>The example below lists
641
	        <filename class="devicefile">/dev/da0</filename> as
642
	      the target device where the image will be written. Be
643
	      very careful that you have the correct device as the
644
	      output target, or you may destroy your existing data.
645
	      </para>
646
	    </warning>
650
647
651
	<step>
648
	    <step>
652
	  <title>Write the Image File to the Memory Stick</title>
649
	      <title>Writing the Image with &man.dd.1;</title>
650
	      
651
	      <para>Set the <varname>kern.geom.debugflags</varname> sysctl
652
	        to be able to write a master boot record to the target
653
	        device.</para>
653
654
654
	  <para>The <filename>.img</filename> file is
655
	      <screen><userinput>&prompt.root; sysctl kern.geom.debugflags=16</userinput></screen>
655
	    <emphasis>not</emphasis> a regular file you copy to the
656
	  
656
	    memory stick.  It is an image of the complete contents of
657
	      <para>The <filename>.img</filename> file is
657
	    the disk.  This means that you <emphasis>cannot</emphasis>
658
	        <emphasis>not</emphasis> a regular file you copy to the
658
	    simply copy files from one disk to another.  Instead, you
659
	        memory stick.  It is an image of the complete contents of
659
	    must use &man.dd.1; to write the image directly to the
660
	        the disk.  This means that you <emphasis>cannot</emphasis>
660
	    disk:</para>
661
	        simply copy files from one disk to another.  Instead, you
662
	        must use &man.dd.1; to write the image directly to the
663
	        disk:</para>
664
665
	      <screen>&prompt.root; <userinput>dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen>
666
	    </step>
667
	  </procedure>
668
	  
669
	  <procedure>
670
	    <title>Using &windows To Write the Image</title>
661
671
662
	  <screen>&prompt.root; <userinput>dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen>
672
	    <warning>
673
	      <para>The example below lists
674
	        <filename class="devicefile">H:</filename> as the
675
	        drive letter of the device where the image will be
676
	        written.  Be very careful that you have the correct
677
	        device as the output target, or you may destroy
678
	        existing data.</para>
679
	    </warning>
680
	    
681
	    <step>
682
	      <title>Obtaining <application>Image Writer for Windows</application></title>
683
	      
684
	      <para><application>Image Writer for Windows</application>
685
	        is a free application that can correctly write an
686
	        image file to a memory stick.  Download it from 
687
		<ulink url="http://launchpad.net/win32-image-writer/0.2/0.2/+download/win32diskimager-RELEASE-0.2-r23-win32.zip"></ulink>
688
		and extract it into a folder.</para>
689
	    </step>
690
	    
691
	    <step>
692
	      <title>Writing The Image with Image Writer</title>
693
	      
694
	      <para>Double-click the <application>Win32DiskImager</application>
695
	        icon to start the program.  Verify that the drive letter
696
	        shown under <computeroutput>Device</computeroutput>
697
	        is the drive with the memory stick.  Click the folder
698
	        icon and select the image to be written to the memory
699
	        stick.  Click <guibutton>Save</guibutton> to accept the
700
	        image file name.  Verify that everything is correct, and
701
	        that no folders on the memory stick are open in other
702
	        windows.  Finally, click <guibutton>Write</guibutton> to
703
	        write the image file to the drive.</para>
704
	    </step>
705
	  </procedure>
663
	</step>
706
	</step>
664
      </procedure>
707
      </procedure>

Return to bug 154837