-All configuration options for running BNC on Unix/Linux/Mac systems are saved in file ${HOME}/.config/BKG/BKG_NTRIP_Client.conf, see annexed 'Configuration Example'. On Windows systems, configuration options are saved in register HKEY_CURRENT_USER/Software/BKG/BKG_NTRIP_Client. The default configuration file/register name 'BKG_NTRIP_Client' can be changed. The file/register contents can easily be edited. Some options can be changed on-the-fly. +All configuration files for running BNC on Unix/Linux/Mac systems are saved in directory ${HOME}/.config/BKG. The default configuration file name there is 'BKG_NTRIP_Client' with suffix '.conf'. +
++On Windows systems all configurations for running BNC are saved in register HKEY_CURRENT_USER/Software/BKG. The default configuration register name there is 'BKG_NTRIP_Client. +
++The default 'BKG_NTRIP_Client' can be changed. The contents of configuration files/registers can easily be edited. Some options can be changed on-the-fly. See annexed 'Configuration Example' for a complete set of saved configuration options.
@@ -847,10 +853,10 @@
-Command line options are available to run BNC in 'no window' mode or let it read data from a file in offline mode. BNC will then use processing options from the configuration file (Unix/Linux/Mac) or from the Windows register. Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. It is possible to introduce your own configuration file/register names instead of the default name 'BKG_NTRIP_Client'. +Command line options are available to run BNC in 'no window' mode or let it read data from a file in offline mode. BNC will then use processing options from the configuration file (Unix/Linux/Mac) or from the Windows register. Note that the self-explaining contents of the configuration file or the Windows register can easily be edited. It is possible to introduce a specific configuration file/register name instead of using the default name 'BKG_NTRIP_Client'.
3.15.1 No Window Mode - optional
-Apart from its regular windows mode, BNC can be started on all systems as a background/batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. +Apart from its regular windows mode, BNC can be started on all systems as a background/batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file/register on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems.
@@ -875,9 +881,9 @@
-Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed for RINEX. Note further that when running BNC in offline mode, it will use options for file saving, interval, sampling etc. from its configuration file. +Note that it is necessary to define a date and time for the first epoch because RTCM streams do not contain complete time stamps as needed for RINEX. Note further that when running BNC in offline mode, it will use options for file saving, interval, sampling etc. from its configuration file/register.
3.15.3 Configuration File - optional
@@ -886,5 +892,5 @@
-This leads to a configuration file 'MyConfig.conf' and a Windows register 'MyConfig'. +This leads to a BNC job using configuration file 'MyConfig.conf' or the Windows configuration register 'MyConfig'.
@@ -1227,5 +1233,5 @@-Note further that configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data. +Note further that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data: