From owner-freebsd-doc@FreeBSD.ORG Thu Feb 17 01:10:05 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B0D51065741 for ; Thu, 17 Feb 2011 01:10:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 177E58FC0C for ; Thu, 17 Feb 2011 01:10:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1H1A4wb078420 for ; Thu, 17 Feb 2011 01:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1H1A4OJ078419; Thu, 17 Feb 2011 01:10:04 GMT (envelope-from gnats) Resent-Date: Thu, 17 Feb 2011 01:10:04 GMT Resent-Message-Id: <201102170110.p1H1A4OJ078419@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Warren Block Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C09C106566B for ; Thu, 17 Feb 2011 01:01:19 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 7C5E88FC15 for ; Thu, 17 Feb 2011 01:01:19 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p1H11JhL072985 for ; Thu, 17 Feb 2011 01:01:19 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p1H11Jr4072984; Thu, 17 Feb 2011 01:01:19 GMT (envelope-from nobody) Message-Id: <201102170101.p1H11Jr4072984@red.freebsd.org> Date: Thu, 17 Feb 2011 01:01:19 GMT From: Warren Block To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/154837: [patch] update Handbook for writing memstick image with Windows X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2011 01:10:05 -0000 >Number: 154837 >Category: docs >Synopsis: [patch] update Handbook for writing memstick image with Windows >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 17 01:10:04 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Warren Block >Release: 8-stable >Organization: >Environment: FreeBSD lightning 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0: Tue Feb 15 18:21:28 MST 2011 root@lightning:/usr/obj/usr/src/sys/LIGHTNING i386 >Description: Add Windows instructions for writing a FreeBSD memstick. >How-To-Repeat: Look for memstick creation instructions for Windows users in the Handbook. >Fix: Apply patch. Patch attached with submission follows: --- en_US.ISO8859-1/books/handbook/install/chapter.sgml.orig 2011-01-16 23:41:02.000000000 -0700 +++ en_US.ISO8859-1/books/handbook/install/chapter.sgml 2011-01-17 00:51:56.000000000 -0700 @@ -631,35 +631,78 @@ - Prepare the Memory Stick - - - The example below lists - /dev/da0 as the target device from - which you will be booting. Be very careful that you - have the correct device as the output target, or you may - destroy your existing data. - - - Set the kern.geom.debugflags sysctl - to be able to write a master boot record to the target - device. + Write The Image File to the Memory Stick + + + Using FreeBSD To Write the Image - &prompt.root; sysctl kern.geom.debugflags=16 - + + The example below lists + /dev/da0 as + the target device where the image will be written. Be + very careful that you have the correct device as the + output target, or you may destroy your existing data. + + - - Write the Image File to the Memory Stick + + Writing the Image with &man.dd.1; + + Set the kern.geom.debugflags sysctl + to be able to write a master boot record to the target + device. - The .img file is - not a regular file you copy to the - memory stick. It is an image of the complete contents of - the disk. This means that you cannot - simply copy files from one disk to another. Instead, you - must use &man.dd.1; to write the image directly to the - disk: + &prompt.root; sysctl kern.geom.debugflags=16 + + The .img file is + not a regular file you copy to the + memory stick. It is an image of the complete contents of + the disk. This means that you cannot + simply copy files from one disk to another. Instead, you + must use &man.dd.1; to write the image directly to the + disk: + + &prompt.root; dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k + + + + + Using &windows To Write the Image - &prompt.root; dd if=&os;-&rel.current;-RELEASE-&arch.i386;-memstick.img of=/dev/da0 bs=64k + + The example below lists + H: as the + drive letter of the device where the image will be + written. Be very careful that you have the correct + device as the output target, or you may destroy + existing data. + + + + Obtaining <application>Image Writer for Windows</application> + + Image Writer for Windows + is a free application that can correctly write an + image file to a memory stick. Download it from + + and extract it into a folder. + + + + Writing The Image with Image Writer + + Double-click the Win32DiskImager + icon to start the program. Verify that the drive letter + shown under Device + is the drive with the memory stick. Click the folder + icon and select the image to be written to the memory + stick. Click Save to accept the + image file name. Verify that everything is correct, and + that no folders on the memory stick are open in other + windows. Finally, click Write to + write the image file to the drive. + + >Release-Note: >Audit-Trail: >Unformatted: