Version 0.8.10 release.

1 files changed, 29 insertions, 28 deletions

diff --git a/README.Windows b/README.Windows
index 3194838..3f49023 100644
--- a/README.Windows
+++ b/README.Windows
@@ -7,10 +7,13 @@ Most versions of Windows cannot boot from a GPT disk on BIOS-based
 computers, and most varieties prior to Vista cannot read GPT disks. GPT

 fdisk is a partition editor for GPT disks, and it will *AUTOMATICALLY

 CONVERT* MBR disks to GPT form. Therefore, you should **NOT** use GPT fdisk

-on a Windows system unless you fully understand what you're doing! If you

-accidentally use GPT fdisk on your boot disk, or perhaps even on a data

-disk, you may find recovery to be very difficult! This caveat does not

-apply to FixParts, though; that tool works only on MBR disks.

+on a Windows system unless you fully understand what you're doing or are

+certain that your computer boots in EFI/UEFI mode! If you accidentally use

+GPT fdisk on a BIOS-mode boot disk, or perhaps even on a data disk, you may

+find recovery to be very difficult! Pre-installed Windows 8 and later

+systems almost always use GPT disks and boot in EFI/UEFI mode, but

+self-installed Windows 8 systems sometimes use BIOS mode. This caveat does

+not apply to FixParts, though; that tool works only on MBR disks.

 ***************************************************************************

 

 Read the main README file for general information on the program, and read

@@ -32,16 +35,22 @@ attempted to do this myself, though. If you care to try, check
 http://gnuwin32.sourceforge.net/packages/popt.htm for information on popt

 for Windows.

 

-The FixParts program (fixparts.txt) is new with GPT fdisk 0.7.0. As

-described in the main README file, this program fixes certain partition

-table problems that can be created by buggy partitioning software. Windows

-seems to be unfazed by most such problems, but I've not done an extensive

-survey of Windows partitioning tools on this score.

+Beginning with version 0.8.10, I'm distributing both 32-bit and 64-bit

+binaries, which include the strings "32" or "64" in their names. The 32-bit

+binaries work fine on most versions of Windows, but some 64-bit

+installations of Windows 8 lack 32-bit support libraries and so may need

+the 64-bit binaries.

 

-To install the programs, copy the gdisk.exe and fixparts.exe program files

-to any directory on your path, such as C:\Windows. Alternatively, you can

-change to the program's directory or type its complete path whenever you

-use it.

+The FixParts program (fixparts32.exe and fixparts64.exe) is new with GPT

+fdisk 0.7.0. As described in the main README file, this program fixes

+certain partition table problems that can be created by buggy partitioning

+software. Windows seems to be unfazed by most such problems, but I've not

+done an extensive survey of Windows partitioning tools on this score.

+

+To install the programs, copy the gdisk32.exe and fixparts32.exe (or

+gdisk64.exe and fixparts64.exe) program files to any directory on your

+path, such as C:\Windows. Alternatively, you can change to the program's

+directory or type its complete path whenever you use it.

 

 To use the programs, first launch a Command Prompt as the Administrator. To

 do this, locate the Command Prompt program icon, right-click it, and select

@@ -59,7 +68,7 @@ Disks are numbered starting from 0, so the preceding command launches gdisk
 on the first disk. The second way to specify a disk device is via a

 harder-to-remember name:

 

-gdisk \\.\physicaldrive0

+gdisk32 \\.\physicaldrive0

 

 This command is equivalent to the earlier one -- it edits the partition

 table on the first physical disk. Change the number at the end of the

@@ -79,15 +88,6 @@ support of GPT, see Microsoft's Web page on the topic:
 

 http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx

 

-The GUIDs generated by gdisk to uniquely identify disks and partitions

-aren't "proper" GUIDs; they're purely random numbers. In practice, this has

-caused me no problems; however, it's conceivable that some disk utility

-will complain. The Unix versions of GPT fdisk generate proper GUIDs, as of

-version 0.6.3. Note that this limitation applies ONLY to the unique GUIDs

-for disks and partitions, not to the GUIDs used to identify partition type

-codes; those are standardized and are handled correctly by all versions of

-GPT fdisk.

-

 The Windows binaries I've compiled do not support Unicode UTF-16LE GPT

 partition names. This feature was added to version 0.7.1 of the software

 for Linux, FreeBSD, and OS X, and with changes to some #ifndef lines in the

@@ -104,11 +104,12 @@ I have successfully compiled GPT fdisk using three different Windows
 compilers:

 

 - MinGW (http://www.mingw.org), and in particular its Linux-hosted

-  cross-compiler -- Under Fedora Linux, the Makefile.mingw file enables

-  compilation of the software via MinGW. (Type "make -f Makefile.mingw" to

-  compile the software.) If you try to compile using another compiler or

-  even using MinGW under Windows or another Linux variety, you may need to

-  adjust the Makefile.mingw options.

+  cross-compiler -- Under Ubuntu Linux, the Makefile.mingw and

+  Makefile.mingw64 files enable compilation of the software via MinGW.

+  (Type "make -f Makefile.mingw" to compile 32-bit binaries, and "make -f

+  Makefile.mingw64" to compile 64-bit binaries.) If you try to compile

+  using another compiler or even using MinGW under Windows or another Linux

+  variety, you may need to adjust the Makefile.mingw options.

 

 - Microsoft Visual C++ 2008 Express

   (http://www.microsoft.com/express/Windows/) -- This compiler requires a