Fully rebrand readme

Author: dasJ

README

@@ -21,7 +21,7 @@ Table of Contents
   8) Trouble-shooting Memory Errors
   9) Execution Time
  10) Memory Testing Philosophy
- 11) Memtest86 Test Algorithms
+ 11) Memetest86 Test Algorithms
  12) Individual Test Descriptions
  13) Problem Reporting - Contact Information
  14) Known Problems
@@ -32,56 +32,56 @@ Table of Contents
 
 1) Introduction
 ===============
-Memtest86 is thorough, stand alone memory test for Intel/AMD x86 architecture
+Memetest86 is thorough, stand alone memory test for Intel/AMD x86 architecture
 systems.  BIOS based memory tests are only a quick check and often miss
-failures that are detected by Memtest86.
+failures that are detected by Memetest86.
 
-For updates go to the Memtest86 web page:
+For updates go to the Memetest86 web page:
 
-	http://www.memtest86.com
+	http://www.memetest.org
 
 
 2) Licensing
 ============
-Memtest86 is released under the terms of the Gnu Public License (GPL). Other
+Memetest86 is released under the terms of the Gnu Public License (GPL). Other
 than the provisions of the GPL there are no restrictions for use, private or
 commercial.  See: http://www.gnu.org/licenses/gpl.html for details.
 
 
 3) Linux Installation
 ============================
-Memtest86 is a stand alone program and can be loaded from either a disk
+Memetest86 is a stand alone program and can be loaded from either a disk
 partition or from a floppy disk.
 
-To build Memtest86:
+To build Memetest86:
    1) Review the Makefile and adjust options as needed.
    2) Type "make"
 
-This creates a file named "memtest.bin" which is a bootable image.  This
+This creates a file named "memetest.bin" which is a bootable image.  This
 image file may be copied to a floppy disk or may be loaded from a disk
 partition via Lilo or Grub image from a hard disk partition.
 
-  To create a Memtest86 bootdisk
+  To create a Memetest86 bootdisk
    1) Insert a blank write enabled floppy disk.
    2) As root, Type "make install"
 
   To boot from a disk partition via Grub
-   1) Copy the image file to a permanent location (ie. /boot/memtest.bin).
+   1) Copy the image file to a permanent location (ie. /boot/memetest.bin).
    2) Add an entry in the Grub config file (/boot/grub/menu.lst) to boot
-      memtest86.  Only the title and kernel fields need to be specified. 
-      The following is a sample Grub entry for booting memtest86:
+      memetest86.  Only the title and kernel fields need to be specified. 
+      The following is a sample Grub entry for booting memetest86:
 
-	title Memtest86
-	    kernel (hd0,0)/memtest.bin
+	title Memetest86
+	    kernel (hd0,0)/memetest.bin
 
   To boot from a disk partition via Lilo
-   1) Copy the image file to a permanent location (ie. /boot/memtest.bin).
+   1) Copy the image file to a permanent location (ie. /boot/memetest.bin).
    2) Add an entry in the lilo config file (usually /etc/lilo.conf) to boot
-      memtest86.  Only the image and label fields need to be specified.
-      The following is a sample Lilo entry for booting memtest86:
+      memetest86.  Only the image and label fields need to be specified.
+      The following is a sample Lilo entry for booting memetest86:
 
-        image = /boot/memtest.bin
-        label = memtest86
+        image = /boot/memetest.bin
+        label = memetest86
 
    3) As root,  type "lilo"
 
@@ -93,19 +93,19 @@ To create a boot-disk with this pre-built image do the following:
 
 4) Serial Console
 =================
-Memtest86 can be used on PC's equipped with a serial port for the console.
+Memetest86 can be used on PC's equipped with a serial port for the console.
 By default serial port console support is not enabled since it slows
 down testing.  To enable change the SERIAL_CONSOLE_DEFAULT define in
 config.h from a zero to a one.  The serial console baud rate may also
 be set in config.h with the SERIAL_BAUD_RATE define.  The other serial
 port settings are no parity, 8 data bits, 1 stop bit.  All of the features
-used by memtest86 are accessible via the serial console.  However, the
+used by memetest86 are accessible via the serial console.  However, the
 screen sometimes is garbled when the online commands are used.
 
 
 5) Online Commands
 ==================
-Memtest86 has a limited number of online commands.  Online commands
+Memetest86 has a limited number of online commands.  Online commands
 provide control over caching, test selection, address range and error
 scrolling.  A help bar is displayed at the bottom of the screen listing
 the available on-line commands. 
@@ -131,7 +131,7 @@ the available on-line commands.
 
 6) Error Information
 ======================
-Memtest has three options for reporting errors.  The default is an an error
+Memetest has three options for reporting errors.  The default is an an error
 summary that displays the most relevant error information. The second option
 is reporting of individual errors.  In BadRAM Patterns mode patterns are
 created for use with the Linux BadRAM feature. This slick feature allows
@@ -204,7 +204,7 @@ results.
 
 7) Trouble-shooting Memory Errors
 ================================
-Please be aware that not all errors reported by Memtest86 are due to
+Please be aware that not all errors reported by Memetest86 are due to
 bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as
 the motherboard.  It is impossible for the test to determine what causes
 the failure to occur.  Most failures will be due to a problem with memory.
@@ -256,7 +256,7 @@ bad but certain combinations may need to be avoided.
 
 I am often asked about the reliability of errors reported by Mestest86.
 In the vast majority of cases errors reported by the test are valid.
-There are some systems that cause Memtest86 to be confused about the size of
+There are some systems that cause Memetest86 to be confused about the size of
 memory and it will try to test non-existent memory.  This will cause a large
 number of consecutive addresses to be reported as bad and generally there
 will be many bits in error.  If you have a relatively small number of
@@ -269,15 +269,15 @@ with marginal memory is risky and can result in data loss and even
 disk corruption.  You can be sure that Murphy will get you if you know
 about a memory error and ignore it.
 
-Memtest86 can not diagnose many types of PC failures.  For example a
+Memetest86 can not diagnose many types of PC failures.  For example a
 faulty CPU that causes Windows to crash will most likely just cause
-Memtest86 to crash in the same way.
+Memetest86 to crash in the same way.
 
 
 8) Execution Time
 ==================
-The time required for a complete pass of Memtest86 will vary greatly
-depending on CPU speed, memory speed and memory size. Memtest86 executes 
+The time required for a complete pass of Memetest86 will vary greatly
+depending on CPU speed, memory speed and memory size. Memetest86 executes 
 indefinitely.  The pass counter increments each time that all of the 
 selected tests have been run.  Generally a single pass is sufficient to 
 catch all but the most obscure errors. However, for complete confidence 
@@ -311,9 +311,9 @@ and manufacturers making this strategy impractical.  However, there
 are testing algorithms that can approximate this ideal strategy. 
 
 
-11) Memtest86 Test Algorithms
+11) Memetest86 Test Algorithms
 =============================
-Memtest86 uses two algorithms that provide a reasonable approximation
+Memetest86 uses two algorithms that provide a reasonable approximation
 of the ideal test strategy above.  The first of these strategies is called
 moving inversions.  The moving inversion test works as follows:
 
@@ -362,7 +362,7 @@ speed and thoroughness.
 
 11) Individual Test Descriptions
 ================================
-Memtest86 executes a series of numbered test sections to check for
+Memetest86 executes a series of numbered test sections to check for
 errors.  These test sections consist of a combination of test
 algorithm, data pattern and caching. The execution order for these tests
 were arranged so that errors will be detected as rapidly as possible.
@@ -446,9 +446,9 @@ Test 11 [Bit fade test, 2 patterns]
 
 12) Problem Reporting - Contact Information
 ===========================================
-Due to the growing popularity of Memtest86 (more than 200,000 downloads per
+Due to the growing popularity of Memetest86 (more than 200,000 downloads per
 month) I have been inundated by, questions, feedback, problem reports and
-requests for enhancements. I simply do not have time to respond to ANY Memtest86
+requests for enhancements. I simply do not have time to respond to ANY Memetest86
 emails. Bug reports and suggestions are welcome but will typically not be
 responded to.
 
@@ -461,9 +461,9 @@ Before submitting a problem report please check the Known Problems section
 to see if this problem has already been reported.  Be sure to include the
 version number and also any details that may be relevant.
 
-Chris Brady, Email: bugs@memtest86.com
+Chris Brady, Email: bugs@memetest86.com
 
-With some PC's Memtest86 will just die with no hints as to what went wrong.
+With some PC's Memetest86 will just die with no hints as to what went wrong.
 Without any details it is impossible to fix these failures.  Fixing these
 problems will require debugging on your part. There is no point in reporting
 these failures unless you have a Linux system and would be willing to debug
@@ -499,9 +499,9 @@ on the screen:
 This the BIOS reporting floppy disk read errors.  Either re-write or toss
 the floppy disk.
 
-Memtest86 can not diagnose many types of PC failures.  For example a
+Memetest86 can not diagnose many types of PC failures.  For example a
 faulty CPU that causes Windows to crash will most likely just cause
-Memtest86 to crash in the same way.
+Memetest86 to crash in the same way.
 
 There have been numerous reports of errors in only the block move test. Often
 the memory works in a different system or the vendor insists that it is good.
@@ -511,19 +511,19 @@ motherboard will correct these errors.  In other cases the only option is to
 replace the memory with better quality, higher speed memory.  Don't buy cheap
 memory and expect it to work at full speed.
 
-Memtest86 supports all types of memory.  If fact the test has absolutely
+Memetest86 supports all types of memory.  If fact the test has absolutely
 no knowledge of the memory type nor does it need to.  This not a problem
 or bug but is listed here due to the many questions I get about this issue.
 
 Changes in the compiler and loader have caused problems with
-Memtest86 resulting in both build failures and errors in execution.  A
+Memetest86 resulting in both build failures and errors in execution.  A
 binary image (precomp.bin) of the test is included and may be used if
 problems are encountered.
 
 
 15) Planned Features List
 =========================
-This is a list of enhancements planned for future releases of Memtest86.
+This is a list of enhancements planned for future releases of Memetest86.
 There is no timetable for when these will be implemented.
 
   - Testing in 64 bit mode with 64 data patterns
@@ -548,7 +548,7 @@ Enhancements in v4.0 (28/Mar/2011)
   are justifications for the decision:
 
     1. Controller identification has nothing to do with actual testing of
-       memory, the core purpose of Memtest86. 
+       memory, the core purpose of Memetest86. 
     2. This code needed to be updated with every new chipset. With the ever
        growing number of chipsets it is not possible to keep up with the
        changes. The result is that new chipsets were more often than not
@@ -579,7 +579,7 @@ Enhancements in v4.0 (28/Mar/2011)
   Memory speed reporting has been parallelized for more accurate reporting for
   multi channel memory controllers.
 
-  This is a major re-write of the Memtest86 with a large number of minor
+  This is a major re-write of the Memetest86 with a large number of minor
   bug-fixes and substantial cleanup and re-organization of the code. 
 
 
@@ -588,7 +588,7 @@ Enhancements in v3.5 (3/Jan/2008)
   Limited support for execution with multiple CPUs. CPUs are selected
   round-robin or sequential for each test.
 
-  Support for additional chipsets. (from Memtest86+ v2.11).
+  Support for additional chipsets. (from Memetest86+ v2.11).
 
   Additions and corrections for CPU detection including reporting of L3 cache.
 
@@ -604,7 +604,7 @@ Enhancements in v3.4 (2/Aug/2007)
 
   A new error summary display with error confidence analysis.
 
-  Support for additional chipsets. (from Memtest86+ v1.70).
+  Support for additional chipsets. (from Memetest86+ v1.70).
 
   Additions and corrections for CPU detection.
 
@@ -614,7 +614,7 @@ Enhancements in v3.4 (2/Aug/2007)
 
 Enhancements in v3.3 (12/Jan/2007)
 
-  Added support for additional chipsets. (from Memtest86+ v1.60)
+  Added support for additional chipsets. (from Memetest86+ v1.60)
 
   Changed Modulo 20 test (#8) to use a more effective random pattern rather
   than simple ones and zeros.
@@ -651,11 +651,11 @@ Enhancements in v3.2 (11/Nov/2004)
   Error reports are highlighted in red to provide a more vivid error 
   indication.
 
-  Added support for a large number of additional chipsets. (from Memtest86+
+  Added support for a large number of additional chipsets. (from Memetest86+
   v1.30)
 
   Added an advanced setup feature that with new chiset allows memory timings
-  to be altered from inside Memtest86. (from Memtest86+ v1.30)
+  to be altered from inside Memetest86. (from Memetest86+ v1.30)
 
 
 Enhancements in v3.1 (11/Mar/2004)
@@ -681,7 +681,7 @@ Enhancements in v3.0 (22/May/2002) Provided by Eric Biederman
    and the support has been done for some chipsets.
 
    Uses dynamic relocation information records to make itself PIC
-   instead of requiring 2 copies of memtest86 in the binary.
+   instead of requiring 2 copies of memetest86 in the binary.
 
    The serial console code does not do redundant writes to the serial port
    Very little slow down at 9600 baud.
@@ -698,7 +698,7 @@ Enhancements in v3.0 (22/May/2002) Provided by Eric Biederman
 Enhancements in v2.9 (29/Feb/2002)
 
    The memory sizing code has been completely rewritten.  By default
-   Memtest86 gets a memory map from the BIOS that is now used to find 
+   Memetest86 gets a memory map from the BIOS that is now used to find 
    available memory. A new online configuration option provides three
    choices for how memory will be sized, including the old "probe" method.
    The default mode generally will not test all of memory, but should be more
@@ -756,7 +756,7 @@ Enhancements in v2.6 (25/May/2001)
    Added screen buffer so that menus will work correctly from a serial
    console.
 
-   The Memtest86 image is now built in ELF format.
+   The Memetest86 image is now built in ELF format.
 
 Enhancements in v2.5 (14/Dec/00)
    Enhanced CPU and cache detection to correctly identify Duron CPU
@@ -876,15 +876,15 @@ Enhancements in v1.4
 
    Added support for a console serial port. (thanks to Doug Sisk)
 
-   On-line commands are now available for configuring Memtest86 on
+   On-line commands are now available for configuring Memetest86 on
    the fly (see On-line Commands).
 
 
 Enhancements in v1.3
    Scrolling of memory errors is now provided.  Previously, only one screen
    of error information was displayed.
 
-   Memtest86 can now be booted from any disk via lilo.
+   Memetest86 can now be booted from any disk via lilo.
 
    Testing of up to 4gb of memory has been fixed is now enabled by default.
    This capability was clearly broken in v1.2a and should work correctly
@@ -900,7 +900,7 @@ Enhancements in v1.3
    read from memory and not re-reading the bad data in the error reporting
    routine.
 
-   APM (advanced power management) is now disabled by Memtest86.  This
+   APM (advanced power management) is now disabled by Memetest86.  This
    keeps the screen from blanking while the test is running.
 
    Problems with enabling & disabling cache on some motherboards have been
@@ -909,7 +909,7 @@ Enhancements in v1.3
 
 17) Acknowledgments
 ===================
-Memtest86 was developed by Chris Brady with the resources and assistance
+Memetest86 was developed by Chris Brady with the resources and assistance
 listed below:
 
 - The initial versions of the source files bootsect.S, setup.S, head.S and
@@ -927,5 +927,5 @@ listed below:
   plus many bugfixes and significant code cleanup.
 
 - Major enhancements to hardware detection and reporting in version 3.2,
-  3.3 pnd 3.4 rovided by Samuel Demeulemeester (from Memtest86+ v1.11, v1.60
+  3.3 pnd 3.4 rovided by Samuel Demeulemeester (from Memetest86+ v1.11, v1.60
   and v1.70).