When you run datovka.exe from command line or from PowerShell then the application doesn't generate any text output into the terminal window. This is because for some reason Windows does not allow terminal output to be generated from application that provide a GUI.
You can mitigate this issue either by using the datovka-lob.bat or datovka-portable-log.bat scripts. These scripts redirect the log output into a file. The file is called datovka.log and it can be located in two places depending on the version of the application:
datovka-log.bat writes the file into your home directory,
datovka-portable-log.bat writes the file into the application directory.
You can also try running the application from a POSIX-compliant environment (e.g. Cygwin, MinGW) to obtain log information into a terminal window.
There is a special command-line client for Windows which does not provide any GUI interface. The executable is called datovka-cli.exe or datovka-cli-portable.exe. These applications are designed to provide the CLI functionality and they cany be run from the command line without any restrictions. This makes them suitable to be used in batch scripts.
Datovka for Windows exist in two modifications. (Ordinary) Datovka - which is installed using an installer; and a portable Datovka - distributed as a ZIP archive.
Datovka stores the user data by default into the user home directory. This is the default behaviour - the Linux/UNIX and macOS version behave the same way. Multiple different users can use the same application. The users cannot see potentially sensitive data of other users (provided that they don't have right to access other users' home directories). Other operating-system-specific measures can me applied to increase the security of the user data.
Portable Datovka stores all its data into the application directory. The entire application with all its data can the be easily put or copied onto a portable device. If you want to increase the security of the data stored on your portable device then you may want to consider storing the portable application on a partition which is encrypted (e.g. by BitLocker).
Since the version 4.10.0 Datovka can be installed either by using an EXE or a MSI installer. The usage of the MSI installer is the recommended way of installing the application as it provides more flexibility - especially for system administrators.
the MSI installer cannot update an previous installation that has been performed using an EXE installer (and vice versa). In such cases you will be asked to uninstall the application manually and to run the installer again. No user data are going to be uninstalled as these are normally stored in user home directories an are not removed during the deinstallation process.
We will continue shipping for a wile before discontinuing the usage of the EXE installer.
Disabling Version Notification
By default the application checks the new available version and notifies the user if a newer version is available. These checks can be enabled or disabled by the user.
If you are a system administrator and your users run Datovka in a managed environment then you may want to disable the version notification completely (i.e. prohibiting the users from enabling it manually) because the users don't have enough privileges to update the application.
Since Datovka 4.10.2 there is a mechanism to disable the version notification by setting a special Windows registry value.
The application reads the registry entry DisableVersionNotification sequentially in these locations with descending priority:
if you are running 64-bit Windows. For more detail see here.
The value DisableVersionNotification should preferably be an integer number with the value of 0 or 1 (or a boolean value), because it is converted to a boolean in the programme. Setting the value DisableVersionNotification overrides the values set in the user configuration.
Values of DisableVersionNotification:
0/False - New version notification is enabled and cannot be disabled in the programme by the user. This value should not be used.
1/True - New version notification is disabled and cannot be enabled in the programme by the user.
The application generates a log entry when it tries to read the registry values mentioned above.