Added fix for bug #1275 where acl or xattr data is saved for virtual filenames genera...

[bacula/bacula] / bacula / src / win32 / win64_installer / Readme.txt

diff --git a/bacula/src/win32/win64_installer/Readme.txt b/bacula/src/win32/win64_installer/Readme.txt
index b8a52d8f07e2965862244ef0f284f0bdbc1e33fa..2e7397d939c26e4d33b2fab2aadd2909be84c771 100755 (executable)
--- a/bacula/src/win32/win64_installer/Readme.txt
+++ b/bacula/src/win32/win64_installer/Readme.txt
@@ -1,48 +1,48 @@
-Bacula - Windows Version Disclaimer
-===================================
-
-Please note, only the Win64 Client (File daemon) is supported, and
-contrary to the Win32 Client, the other components (Director, Storage daemon,
-their utilities) are not provided because they have not been ported.
-Note: the Win64 Client can only be installed on 64 bit Windows Operating
-systems.
-
-Bacula - Windows Version Notes
-==============================
-
-These notes highlight how the Windows version of Bacula differs from the 
-other versions.  It also provides any notes additional to the documentation.
-
-For detailed documentation on using, configuring and troubleshooting Bacula,
-please consult the installed documentation or the online documentation at
-http://www.bacula.org/?page=documentation.
-
-
-Start Menu Items
-----------------
-A number of menu items have been created in the Start menu under All Programs
-in the Bacula submenu.  They may be selected to edit the configuration files,
-view the documentation or run one of the console or utility programs.  The 
-choices available will vary depending on the options you chose to install.
-
-
-File Locations
---------------
-Everything is installed in the directory 
-"C:\Program Files\Bacula" unless a different directory was selected during
-installation. Note: due to a bug in the NSIS installer we are using, on 
-64 bit machines appears to install Bacula in "C:\Program Files (x86)\Bacula".
-
-Code Page Problems
--------------------
-Please note that Bacula expects the contents of the configuration files to be 
-written in UTF-8 format. Some translations of "Application Data" have accented
-characters, and apparently the installer writes this translated data in the
-standard Windows code page coding.  This occurs for the Working Directory, and 
-when it happens the daemon will not start since Bacula cannot find the directory.
-The workaround is to manually edit the appropriate conf file and ensure that it
-is written out in UTF-8 format.
-
-The conf files can be edited with any UTF-8 compatible editor, or on most 
-modern Windows machines, you can edit them with notepad, then choose UTF-8
-output encoding before saving them.
+Bacula - Windows Version Disclaimer\r
+===================================\r
+\r
+Please note, only the Win64 Client (File daemon) is supported, and\r
+contrary to the Win32 Client, the other components (Director, Storage daemon,\r
+their utilities) are not provided because they have not been ported.\r
+Note: the Win64 Client can only be installed on 64 bit Windows Operating\r
+systems.\r
+\r
+Bacula - Windows Version Notes\r
+==============================\r
+\r
+These notes highlight how the Windows version of Bacula differs from the \r
+other versions.  It also provides any notes additional to the documentation.\r
+\r
+For detailed documentation on using, configuring and troubleshooting Bacula,\r
+please consult the installed documentation or the online documentation at\r
+http://www.bacula.org/?page=documentation.\r
+\r
+\r
+Start Menu Items\r
+----------------\r
+A number of menu items have been created in the Start menu under All Programs\r
+in the Bacula submenu.  They may be selected to edit the configuration files,\r
+view the documentation or run one of the console or utility programs.  The \r
+choices available will vary depending on the options you chose to install.\r
+\r
+\r
+File Locations\r
+--------------\r
+Everything is installed in the directory \r
+"C:\Program Files\Bacula" unless a different directory was selected during\r
+installation. Note: due to a bug in the NSIS installer we are using, on \r
+64 bit machines appears to install Bacula in "C:\Program Files (x86)\Bacula".\r
+\r
+Code Page Problems\r
+-------------------\r
+Please note that Bacula expects the contents of the configuration files to be \r
+written in UTF-8 format. Some translations of "Application Data" have accented\r
+characters, and apparently the installer writes this translated data in the\r
+standard Windows code page coding.  This occurs for the Working Directory, and \r
+when it happens the daemon will not start since Bacula cannot find the directory.\r
+The workaround is to manually edit the appropriate conf file and ensure that it\r
+is written out in UTF-8 format.\r
+\r
+The conf files can be edited with any UTF-8 compatible editor, or on most \r
+modern Windows machines, you can edit them with notepad, then choose UTF-8\r
+output encoding before saving them.\r