Index: readme.build.txt
===================================================================
diff -u -N -rb50df1679bb9a1e885407c034fc37fb7064709a8 -re5f0a0e2d61c9d5f77b844944f8318b5d122a5b3
--- readme.build.txt	(.../readme.build.txt)	(revision b50df1679bb9a1e885407c034fc37fb7064709a8)
+++ readme.build.txt	(.../readme.build.txt)	(revision e5f0a0e2d61c9d5f77b844944f8318b5d122a5b3)
@@ -1,7 +1,12 @@
 To build Copy Handler from source code, you need to have:
-- Visual Studio 2008 (at least standard edition, because of dependencies on MFC) + SP1
-- Debugging tools for Windows (needed for crash dump generation)
-- Recommended: newest Windows SDK
+- Visual Studio 2008 (at least standard edition, because of dependencies on MFC) + SP1 + newest Visual Studio updates
+- Newest Windows SDK
+- Debugging tools for Windows (needed for crash dump generation) - seems to be integrated with newer Windows SDKs
 
 Copy Handler project depends on:
 - Boost libraries (http://www.boost.org)
+   - Needs building:
+     for x64
+        bjam --toolset=msvc-9.0 address-model=64 define=_BIND_TO_CURRENT_VCLIBS_VERSION --build-type=complete --stagedir=lib\x64 stage
+     for x32
+        bjam --toolset=msvc-9.0 address-model=32 define=_BIND_TO_CURRENT_VCLIBS_VERSION --build-type=complete --stagedir=lib\x32 stage
Index: readme.scripts.txt
===================================================================
diff -u -N
--- readme.scripts.txt	(revision 0)
+++ readme.scripts.txt	(revision e5f0a0e2d61c9d5f77b844944f8318b5d122a5b3)
@@ -0,0 +1,13 @@
+The scripts/ directory contains scripts aiding with releasing new Copy Handler versions.
+
+Scripts requirements:
+- ActivePerl (for tagging debug symbols with source server information)
+- Subversion client (command line) with svnversion script
+- Debugging tools for Windows (symstore)
+- 7zip (packaging)
+- InnoSetup + Preprocessor pack
+
+Notes:
+1. Those requirements does not include the dependencies required by the build process, which must also be met.
+2. All tools must be available in %PATH
+3. Scripts should be called/executed from the scripts/ directory.
Index: scripts/readme.txt
===================================================================
diff -u -N
--- scripts/readme.txt	(revision b50df1679bb9a1e885407c034fc37fb7064709a8)
+++ scripts/readme.txt	(revision 0)
@@ -1,13 +0,0 @@
-This directory contains scripts aiding with releasing new Copy Handler versions.
-
-Scripts requirements:
-- ActivePerl (for tagging debug symbols with source server information)
-- Subversion client (command line) with svnversion script
-- Debugging tools for Windows (symstore)
-- 7zip (packaging)
-- InnoSetup + Preprocessor pack
-
-Notes:
-1. Those requirements does not include the dependencies required by the build process, which must also be met.
-2. All tools must be available in %PATH
-3. Scripts should be called from the directory where they are placed.
\ No newline at end of file
Index: release_checklist.txt
===================================================================
diff -u -N
--- release_checklist.txt	(revision 0)
+++ release_checklist.txt	(revision e5f0a0e2d61c9d5f77b844944f8318b5d122a5b3)
@@ -0,0 +1,15 @@
+1. Commit new translations from forum to svn repository
+2. Tag the trunk (svntag.bat)
+2. Prepare packages with the release - installer, zip, sources, symbols (script: make_release.bat tag)
+3. Post-build checks (is everything ok? does it install?)
+4. Upload files to the sourceforge.net (scripted: upload_release.bat (might not work due to the sf.net changes to upload system made a while ago))
+5. Prepare human readable changelog
+6. Create new site story with changelog (en + pl).
+7. Add new sf.net release, set release notes and changelog links.
+8. Add files to the newly created release, set file types/processors.
+9. Send notifications to users monitoring the copyhandler package.
+10. Create sf.net news entry.
+11. Change entries in ch.com download pages (change version names).
+12. Create news on site about new version.
+13. Create new chver.ini for automatic notifications.
+14. Add new artifact group with new release name (sf.net).
\ No newline at end of file
Index: scripts/release_checklist.txt
===================================================================
diff -u -N
--- scripts/release_checklist.txt	(revision 03340b954ead8138d669ee4f8df7124dc84c5612)
+++ scripts/release_checklist.txt	(revision 0)
@@ -1,15 +0,0 @@
-1. Commit new translation from forum to svn repository
-2. Tag the trunk (svntag.bat)
-2. Build packages with release - installer, zip, sources, symbols (scripted: make_existing_release.bat)
-3. Post-build checks (is everything ok? does it install?)
-4. Upload files to the sourceforge.net (scripted: upload_release.bat (might not work due to the sf.net changes to upload system made a while ago))
-5. Prepare human readable changelog
-6. Create new site story with changelog (en + pl).
-7. Add new sf.net release, set release notes and changelog links.
-8. Add files to the newly created release, set file types/processors.
-9. Send notifications to users monitoring the copyhandler package.
-10. Create sf.net news entry.
-11. Change entries in ch.com download pages (change version names).
-12. Create news on site about new version.
-13. Create new chver.ini for automatic notifications.
-14. Add new artifact group with new release name (sf.net).
\ No newline at end of file