spending too much time on trying to get the traceback to work as it can be
very difficult.
-The changes that might needed are to add a correct path to the {\bf gdb}
+The changes that might be needed are to add a correct path to the {\bf gdb}
program, correct the path to the {\bf btraceback.gdb} file, change the {\bf
mail} program or its path, or change your email address. The key line in the
{\bf btraceback} file is:
to edit the bacula-fd.conf file, and if you respond with yes, it will be
opened in notepad.
\
-\item Then the installer will ask if wish to install Bacula as a service. You
+\item Then the installer will ask if you wish to install Bacula as a service. You
should always choose to do so:
\addcontentsline{lof}{figure}{Win32 Client Service Selection}
As a default, Bacula backs up Windows systems using the Windows API calls.
If you want to backup data on a WinNT/2K/XP system and restore it on a
Unix/Win95/98/Me system, we have provided a special {\bf portable} option
-that backups the data in a portable fashion by using portable API calls.
+that backs up the data in a portable fashion by using portable API calls.
See the \ilink{portable option}{portable} on the Include statement in a
FileSet resource in the Director's configuration chapter for the details on
setting this option. However, using the portable option means you may have
\index[general]{Windows Firewalls }
\addcontentsline{toc}{subsubsection}{Windows Firewalls}
-If you turn on the firewalling feature on Windows (default in WinXP SR2), you
+If you turn on the firewalling feature on Windows (default in WinXP SP2), you
are likely to find that the Bacula ports are blocked and you cannot
-communicated to the other daemons. This can be deactivated through the {\bf
+communicate to the other daemons. This can be deactivated through the {\bf
Security Notification} dialog, which is apparently somewhere in the {\bf
Security Center}. I don't have this on my computer, so I cannot give the exact
details.