windows plugin directory created and set in cfg.

The windows installer now creates also a directory
for plugins, ususally C:\Program Files\Bareos\Plugins

Also, this directory is set in the plugin directory comment
in the default bareos-fd.conf

Also, we now have a "compatible=no" comment in the fd.conf
that tells the user that for new bareos features this has to
be set to no to disable the Bacula compatible mode.

Signed-off-by: Marco van Wieringen <marco.van.wieringen@bareos.com>

platforms/win32/fillup.sed

@@ -8,3 +8,4 @@ s#@dir_password@#XXX_REPLACE_WITH_DIRECTOR_PASSWORD_XXX#g
 s#@dir_port@#9101#g
 s#@fd_port@#9102#g
 s#@sd_port@#9103#g
+s#@plugindir@#"C:/Program Files/Bareos/Plugins"#g

platforms/win32/winbareos.nsi

@@ -311,6 +311,7 @@ SectionIn 1 2 3
   SetOutPath "$INSTDIR"
   SetOverwrite ifnewer
   CreateDirectory "$SMPROGRAMS\${PRODUCT_NAME}"
+  CreateDirectory "$SMPROGRAMS\${PRODUCT_NAME}\Plugins"
   CreateDirectory "$APPDATA\${PRODUCT_NAME}"
   File "bareos-fd.exe"
   File "bpipe-fd.dll"
@@ -919,6 +920,7 @@ ConfDeleteSkip:
 
   Delete "$SMPROGRAMS\${PRODUCT_NAME}\Website.lnk"
   Delete "$SMPROGRAMS\${PRODUCT_NAME}\Uninstall.lnk"
+  RMDir "$SMPROGRAMS\${PRODUCT_NAME}\Plugins"
   RMDir "$SMPROGRAMS\${PRODUCT_NAME}"
   RMDir "$INSTDIR"
   DeleteRegKey ${PRODUCT_UNINST_ROOT_KEY} "${PRODUCT_UNINST_KEY}"

src/filed/bareos-fd.conf.in

@@ -34,6 +34,10 @@ FileDaemon {                          # this is me
 
   # remove comment in next line to load plugins from specified directory
   # Plugin Directory = @plugindir@
+
+  # if compatible is set to yes, we are compatible with bacula
+  # if you want to use new bareos features, please set
+  # compatible = no
 }
 
 # Send all messages except skipped files back to Director