| Delay copy start | Specifies the number of minutes that DataArmour will wait before beginning any backup process. This gives your system time to boot up before more disk thrashing occurs! |
| Allow maximum of 'n' threads | Limits the number of backup items that can be running at once. If you set this to one (1), each backup item will execute sequentially. This can be usefull if you would like DataArmour to impact performance as little as possible. If you are performing many backups to FTP sites (at mediocre connection speeds) it might be usefull to bump this up to a higher value. |
| Application priority | Sets the priority of the DataArmour application relative to other running applications. |
| Start when windows starts | If ticked, DataArmour will load when you start windows. It achives this not by placing an icon in the 'Startup' folder, but by placing a key in the registry. The key location is: HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Run \ DataArmour. |
| Compact process heaps | This works for Windows NT only. If ticked, when all backups complete, the process heaps will be compacted - the aim being to reduce memory fragmentation and increase system performance. |
| Show on task bar when minimized | Applies only when DataArmour is minimized. If ticked, DataArmour will have its own 'button' in the task bar and an icon in the system tray. If un-ticked, only the icon in the system tray will be visible. |
| Show unhandled exceptions | Unfortunately, we humans are not perfect. If anything goes horribly wrong in DataArmour, you can choose to log the fault. A small, information email to the author would then be in order. |
| Centre windows over mouse | If enabled, all windows (item editor, FTP format editor, configuration and log) will centre over the mouse when they open. If the new position of the window would be out of screen bounds, the window will automatically be repositioned so that it is as visible as possible (taking into account the position and size of the task bar). |
| Encrypt registry settings | If enabled, the configuration data is encrypted before it is written to the registry. This will be required if you use the FTP features of DataArmour. When you have instructed DataArmour to backup to an FTP site, you have to supply a username and password. For these details to be stored without encrytion, it would be possible for someone to view the registry and obtain the username and password for the FTP server. By encryting these settings, you minimise this possibility. |
| Minimize when closed pressed | When enabled this will cause DataArmour to be minimized when the close application by clicking on the close button icon in the upper right corner of the DataArmour window. If this option is not selected then DataArmour will exit and will be unable to perform any backup items. |
| Autorefresh log | If ticked, forces DataArmour to update the log file window (it must be open) when the current running backup(s) complete. This saves you having to click the Refresh button in the log window. |
| Require write access during backup | With this option enabled, DataArmour will perform a check to ensure that it has full, exclusive write access to files before they are backed up. This will prevent DataArmour from backing up any files that have been opened for write access by other applications or the operating system. This option is used in conjunction with open file options in the options tab of a backup item properties. |
| Truncate log | Ensures that the log file does not exceed the specified size. The log file is checked (and possibly truncated) and the end of a backup (when all items have completed). |
| Log management of Handles | Used only for testing: Logs the management of handles used to track the on file change rules. |
| Log management of Threads | Used only for testing: Logs the management of threads. Threads are created/destroyed for each backup item. |
| Seperate config per user | If enabled, the configuration files for DataArmour are saved under the users registry key. If disabled, DataArmours settings are saved under the machines registry key; thus anyone who logs onto the machine will share the same DataArmour settings. |