diff --git a/INSTALL b/INSTALL
index 876fc5cd..bc76ddd2 100644
--- a/INSTALL
+++ b/INSTALL
@@ -11,13 +11,15 @@ When you have to check for correctness the application simply typing:
     make check
 
 If if terminates with "Success", you can install the application and
-the documentation running as root :
+the documentation running as root:
 
-    make install
+    sudo make install
 
 To start using SnapRAID you have to change the example configuration
 file snapraid.conf.example to fit your needs and copy it in /etc/snapraid.conf
 
-You can have more details in the manpage documentation available with:
+To get more help, see the "Getting Started" section in the snapraid manpage
+simply typing:
 
     man snapraid
+
diff --git a/Makefile.am b/Makefile.am
index fd167fa9..dfdc96fb 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -22,6 +22,7 @@ noinst_HEADERS = \
 	parity.h \
 	handle.h \
 	md5.h \
+	md5.c \
 	tommyarray.h \
 	tommychain.h \
 	tommyhash.h \
@@ -181,13 +182,14 @@ snapraid.html : snapraid.d
 
 DISTWIN = \
 	snapraid.txt \
-	snapraid.exe \
-	snapraid.conf.example
+	snapraid.exe
 
 distwindows: $(DISTWIN)
 	rm -f $(PACKAGE)-$(VERSION)-windows-x86.zip
 	mkdir tmp
 	cp $(DISTWIN) tmp
+	cp snapraid.conf.example.windows tmp/snapraid.conf.example
+	cp INSTALL.windows tmp/install.txt
 	cp README tmp/readme.txt
 	cp AUTHORS tmp/authors.txt
 	cp HISTORY tmp/history.txt
diff --git a/TODO b/TODO
index 4baa1b09..1f3440af 100644
--- a/TODO
+++ b/TODO
@@ -13,14 +13,6 @@ http://lxr.linux.no/#linux+v2.6.38/lib/raid6
 
 * Go multithread. We can do it when reading the new state (scan.c) and when syncing (sync.c)
 
-* Implement a faster XOR implementation using SSE2.
-
-* Evaluate to change from MD5 to FVN HASH.
-See:
-http://isthe.com/chongo/tech/comp/fnv/
-http://cessu.blogspot.com/2007/09/hashing-with-sse2.html (SSE implementation)
-http://isthe.com/chongo/src/fnv/hash_64a.c (C implementation)
-
 * Use the O_NOATIME flag if run as 'root'.
 Anyway a better solution is to mount the disk with the "noatime" and "nodiratime" options.
 
diff --git a/snapraid.1 b/snapraid.1
index 05f6c007..7d3c4219 100644
--- a/snapraid.1
+++ b/snapraid.1
@@ -101,6 +101,13 @@ With RAID you do not have to stop working when a disk fails.
 It\(cqs able to recover damages only from a single disk.
 With a Backup you are able to recover from a complete
 failure of the whole disk array.
+.IP \(bu
+It identifies changes checking file time and size. If you have
+a program that arbitrarily restore the file time, such changes
+are not detected if the size doesn\(cqt change.
+.IP \(bu
+Only the file data is saved. Permissions, time, extended attributes,
+hard\(hylinks, symbolic\(hylinks are not saved.
 .PD
 .SH GETTING STARTED 
 To use SnapRAID you need first select one disk of your disk array
diff --git a/snapraid.d b/snapraid.d
index 6de52a2d..b61bd61a 100644
--- a/snapraid.d
+++ b/snapraid.d
@@ -65,6 +65,11 @@ Limitations
 	* It's able to recover damages only from a single disk.
 		With a Backup you are able to recover from a complete
 		failure of the whole disk array.
+	* It identifies changes checking file time and size. If you have
+		a program that arbitrarily restore the file time, such changes
+		are not detected if the size doesn't change.
+	* Only the file data is saved. Permissions, time, extended attributes,
+		hard-links, symbolic-links are not saved.
 
 Getting Started
 	To use SnapRAID you need first select one disk of your disk array
diff --git a/snapraid.txt b/snapraid.txt
index be1777cf..a38c2e13 100644
--- a/snapraid.txt
+++ b/snapraid.txt
@@ -75,6 +75,11 @@ Other limitations are:
 * It's able to recover damages only from a single disk.
   With a Backup you are able to recover from a complete
   failure of the whole disk array.
+* It identifies changes checking file time and size. If you have
+  a program that arbitrarily restore the file time, such changes
+  are not detected if the size doesn't change.
+* Only the file data is saved. Permissions, time, extended attributes,
+  hard-links, symbolic-links are not saved.
 
 
 4 GETTING STARTED