# Start-up Configuration

Argus start-up parameters are configured in Start-up Configuration dialogue.

Configuring the automatic opening of Dial-up lines

By default, Argus is configured so that there are no lines opened at start-up. It is possible to determine which lines are to be opened at start-up - this just saves you having to open them manually. Note that all the lines to be opened must be pre-configured.

The lines to be opened at start-up are listed in Dial-up Lines / Auto-open list box. All other lines (which could be open manually using System / Open Dial-up Line command) are listed in Dial-up Lines / Manual-open list box.

To make lines open automatically at start-up, select the desired lines in the Manual-open list-box and press the '>' button - the lines will be moved into Auto-open list. To remove an auto-opening line from the Auto-open list, select it in the Auto-open list box and press the '<' button.

Configuring TCP/IP Daemon start-up

If you want TCP/IP Daemon to start automatically each time Argus starts, tick the Auto-run TCP/IP Daemon checkbox.

Fast logging

By default, Argus keeps log files closed and opens them only when it is necessary to append new data. It makes possible to move or erase these files without restarting of Argus. Option Fast logging tells Argus to keep log files always opened to avoid permanent opening and closing these files whenever it is needed to append a new log record. It saves system resources and execution time, but can prevent from moving / erasing / truncating log files during Argus execution.

Please note that improper use of Fast logging in OFF mode may be dangerous. If Argus fails to open a log file for writing, it will never try to open it again while running. So do not open log files in a mode that will prevent Argus from writing. Better way would be to rename the file to a temporary name, analyse it, and then, possibly, move somewhere to archive directory.

See also: Extended logging.

## Log WZ pending/incomplete

This options turns on/off logging number of files in temporary inbound. There may be two reasons when incoming files are stored in temporary inbound after a session terminates. First reason is when Argus was unable to move received files from temporary inbound (e.g. due to file with same name already exists in destination directory). Such files in temporary inbound are called pending files. Second reason is when a session was aborted during a file transfer was in progress, so the file wasn't completely received. Such files are called incomplete files.

## ODBC logging

This option turns on ODBC logging, as described in ODBC logging chapter.