Steps to Reproduce:
•Use RTS to generate initial *.ffs_real file by "Save as..."
•Modify *.ffs_real to include log file generation code from user manual:
echo %change_action% "%change_path%" >> ...
%TimeStamp%.log
[YYYY-MM-DD hhmmss].log
Contents of Config File:
1 <?xml version="1.0" encoding="utf-8"?>
2 <FreeFileSync XmlType="REAL" XmlFormat="2">
3 <Directories>
4 <Item>
5 %UserProfile%\Downloads\unsy
6 </Item>
7 <Item>
8 [USB_DEVICE_NAME]\unsy
9 </Item>
10 </Directories>
11 <Delay>
12 10
13 </Delay>
14 <Commandline>
15 "C:\Programs\FreeFileSync\RealTimeSync.exe" ^
16 "C:\Programs\FreeFileSync\configurations\work_bkup.ffs_real" ^
17 echo %change_action% "%change_path%" >> [USB_DEVICE_NAME]\ffs.logs\%TimeStamp%.log.txt
18 </Commandline>
19 </FreeFileSync>
20
21 <!--
22 Error Received:
23
24 Error parsing
25 "C:\Programs\FreeFileSync\configurations\work_bkup.ffs_real", row 17, column 47
26
27 Followed by:
28
29 Command: "C:\Programs\FreeFileSync\RealTimeSync.exe" "C:\Programs\FreeFileSync\configurations\work_bkup.ffs_real" failed.
30
31 Exit code 3
32 -->
How do I properly format the Command so that the parsing error does not occur? I'm at a bit of a loss as the ">>" is specified in the manual, but there is limited information about the format of the configuration files.
Thanks,
-robiv