Change Win32 to Windows in win32.tex

diff --git a/docs/manuals/en/main/win32.tex b/docs/manuals/en/main/win32.tex
index da400e2dadbfb84b6cbaef70156b12fe25e9bb79..f36dc8a24ed82df7a15d2b8a21cedefbfa53a4b8 100644 (file)
--- a/docs/manuals/en/main/win32.tex
+++ b/docs/manuals/en/main/win32.tex
@@ -13,7 +13,7 @@ the File daemon (client) only.
 
 The Windows version of the Bacula File daemon has been tested on WinXP,
 Win2000, Windows Server 2003, Windows Server 2008, Vista, and Windows 7
-systems.  The Windows version of Bacula is a native Win32 port, but there
+systems.  The Windows version of Bacula is a native Windows port, but there
 are very few source code changes to the Unix code, which means that the
 Windows version is for the most part running code that has long proved
 stable on Unix systems.  When running, it is perfectly integrated with
@@ -26,10 +26,10 @@ Once installed Bacula normally runs as a system service. This means that it is
 immediately started by the operating system when the system is booted, and
 runs in the background even if there is no user logged into the system. 
 
-\section{Win32 Installation}
+\section{Windows Installation}
 \label{installation}
 \index[general]{Installation}
-\index[general]{Win32!Installation}
+\index[general]{Windows!Installation}
 
 Normally, you will install the Windows version of Bacula from the binaries.
 This install is standard Windows .exe that runs an install wizard using the
@@ -75,12 +75,12 @@ Bacula, so we don't recommend that option.
 \item Once launched, the installer wizard will ask you if you want  to install
    Bacula.  
 
-\addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
+\addcontentsline{lof}{figure}{Windows Client Setup Wizard}
 \includegraphics{\idir win32-welcome.eps}  
 
 \item Next you will be asked to select the installation type. 
 
-\addcontentsline{lof}{figure}{Win32 Installation Type}
+\addcontentsline{lof}{figure}{Windows Installation Type}
 \includegraphics{\idir win32-installation-type.eps}
 
 
@@ -90,7 +90,7 @@ Bacula, so we don't recommend that option.
    location that you choose later. The components  dialog looks like the
    following:  
 
-\addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
+\addcontentsline{lof}{figure}{Windows Component Selection Dialog}
 \includegraphics{\idir win32-pkg.eps}  
 \index[general]{Upgrading}
 
@@ -105,19 +105,19 @@ Bacula, so we don't recommend that option.
    not be displayed.
 
 
-\addcontentsline{lof}{figure}{Win32 Configure}
+\addcontentsline{lof}{figure}{Windows Configure}
 \includegraphics{\idir win32-config.eps}  
  
 \item While the various files are being loaded, you will see the following
    dialog:
 
-   \addcontentsline{lof}{figure}{Win32 Install Progress}
+   \addcontentsline{lof}{figure}{Windows Install Progress}
    \includegraphics{\idir win32-installing.eps}  
 
 
 \item Finally, the finish dialog will appear:  
 
-   \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
+   \addcontentsline{lof}{figure}{Windows Client Setup Completed}
    \includegraphics{\idir win32-finish.eps}  
 
 \ 
@@ -140,9 +140,9 @@ If you are using remote desktop connections between your Windows boxes, be
 warned that that tray icon does not always appear. It will always be visible
 when you log into the console, but the remote desktop may not display it. 
 
-\section{Post Win32 Installation}
-\index[general]{Post Win32 Installation}
-\index[general]{Win32!Post Installation}
+\section{Post Windows Installation}
+\index[general]{Post Windows Installation}
+\index[general]{Windows!Post Installation}
 
 After installing Bacula and before running it, you should check the contents
 of the configuration files to ensure that they correspond to your
@@ -155,19 +155,19 @@ not the case, you probably have not installed Bacula while running as
 Administrator, and hence it will be unlikely that Bacula can access
 all the system files.
 
-\section{Uninstalling Bacula on Win32}
-\index[general]{Win32!Uninstalling Bacula}
-\index[general]{Uninstalling Bacula on Win32}
+\section{Uninstalling Bacula on Windows}
+\index[general]{Windows!Uninstalling Bacula}
+\index[general]{Uninstalling Bacula on Windows}
 
 Once Bacula has been installed, it can be uninstalled using the standard
 Windows Add/Remove Programs dialog found on the Control panel. 
 
-\section{Dealing with Win32 Problems}
+\section{Dealing with Windows Problems}
 \label{problems}
-\index[general]{Win32!Dealing with Problems}
-\index[general]{Dealing with Win32 Problems}
+\index[general]{Windows!Dealing with Problems}
+\index[general]{Dealing with Windows Problems}
 
-Sometimes Win32 machines the File daemon may have very slow
+Sometimes Windows machines the File daemon may have very slow
 backup transfer rates compared to other machines.  To you might
 try setting the Maximum Network Buffer Size to 32,768 in both the
 File daemon and in the Storage daemon. The default size is larger,
@@ -224,7 +224,7 @@ sides must match for proper authentication.
 One user had serious problems with the configuration file until he realized
 that the Unix end of line conventions were used and Bacula wanted them in
 Windows format. This has not been confirmed though, and Bacula version 2.0.0 
-and above should now accept all end of line conventions (Win32,
+and above should now accept all end of line conventions (Windows,
 Unix, Mac).
 
 Running Unix like programs on Windows machines is a bit frustrating because
@@ -399,16 +399,16 @@ Marc Brueckner for doing the tests:
  \hline {WinXP} & {WinXP} & {Works } \\
  \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
 message) } \\
- \hline {WinXP} & {WinMe} & {Error: Win32 data stream not supported. } \\
+ \hline {WinXP} & {WinMe} & {Error: Windows data stream not supported. } \\
  \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
- \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
+ \hline {WinXP} & {Linux} & {Error: Windows data stream not supported. } \\
  \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
  \hline {\ } & {\ } & {\ } \\
  \hline {WinNT} & {WinNT} & {Works } \\
  \hline {WinNT} & {WinXP} & {Works } \\
- \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
+ \hline {WinNT} & {WinMe} & {Error: Windows data stream not supported. } \\
  \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
- \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
+ \hline {WinNT} & {Linux} & {Error: Windows data stream not supported. } \\
  \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
  \hline {\ } & {\ } & {\ } \\
  \hline {Linux} & {Linux} & {Works } \\
@@ -426,9 +426,6 @@ be restore to any machine.
 \section{Volume Shadow Copy Service}
 \index[general]{Volume Shadow Copy Service}
 \index[general]{VSS}
-In version 1.37.30 and greater, you can turn on Microsoft's Volume
-Shadow Copy Service (VSS).      
-
 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
 a backup-solution for Windows, this is an extremely important step. VSS
 allows Bacula to backup open files and even to interact with applications like
@@ -447,7 +444,6 @@ Bacula produces a message from each of the registered writer programs
 when it is doing a VSS backup so you know which ones are correctly backed
 up.
 
-Bacula supports VSS on both Windows 2003 and Windows XP.
 Technically Bacula creates a shadow copy as soon as the backup process
 starts. It does then backup all files from the shadow copy and destroys the
 shadow copy after the backup process. Please have in mind, that VSS
@@ -565,7 +561,7 @@ listening, you can enter the following command in a shell window:
 \normalsize
 
 TopView is another program that has been recommend, but it is not a
-standard Win32 program, so you must find and download it from the Internet.
+standard Windows program, so you must find and download it from the Internet.
 
 \section{Windows Disaster Recovery}
 \index[general]{Recovery!Windows Disaster}
@@ -585,12 +581,12 @@ being restored on a Unix machine. Once you have an operational Windows OS
 loaded, you can run the File daemon and restore your user files. 
 
 Please see 
-\ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
+\ilink{ Disaster Recovery of Windows Systems}{Windows33} for the latest
 suggestion, which looks very promising. 
 
 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
 Environment) Boot-CD, may be just what is needed to build a complete disaster
-recovery system for Win32. This distribution can be found at 
+recovery system for Windows. This distribution can be found at 
 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
 
 \section{Windows Restore Problems}
@@ -650,7 +646,7 @@ version 1.32f-3, Bacula creates these files with full access permission.
 However, there may be cases where you have problems accessing those files even
 if you run as administrator. In principle, Microsoft supplies you with the way
 to cease the ownership of those files and thus change the permissions.
-However, a much better solution to working with and changing Win32 permissions
+However, a much better solution to working with and changing Windows permissions
 is the program {\bf SetACL}, which can be found at 
 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}. 
 
@@ -671,7 +667,7 @@ the problem.
 
 The following solution was provided by Dan Langille \lt{}dan at langille in
 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
-they should apply to most Win32 platforms. The procedure outlines how to deal
+they should apply to most Windows platforms. The procedure outlines how to deal
 with a problem which arises when a restore creates a top-level new directory.
 In this example, "top-level" means something like {\bf
 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
@@ -805,14 +801,14 @@ Unicode filenames. There may still be some problems with multiple byte
 characters (e.g. Chinese, ...) where it is a two byte character but the
 displayed character is not two characters wide.
 
-\index[general]{Win32 Path Length Restriction}
+\index[general]{Windows Path Length Restriction}
 Path/filenames longer than 260 characters (up to 32,000) are supported
 beginning with Bacula version 1.39.20. Older Bacula versions support
 only 260 character path/filenames.
 
-\section{Win32 Specific File daemon Command Line}
-\index[general]{Client!Win32 Specific File daemon Command Line Options}
-\index[general]{Win32 Specific File daemon Command Line Options}
+\section{Windows Specific File daemon Command Line}
+\index[general]{Client!Windows Specific File daemon Command Line Options}
+\index[general]{Windows Specific File daemon Command Line Options}
 
 These options are not normally seen or used by the user, and are documented
 here only for information purposes. At the current time, to change the default