The Dependencies tab provides the ability for services to be started and stopped in sequence. All the services and load order groups listed on this tab must be running before this service can run.

For example, to make a FireDaemon Pro service named 'ServiceA' depend on a service named 'ServiceB', add 'ServiceB' to the service dependencies list. During system startup, Windows will first start ServiceB and then ServiceA.

If both ServiceA and ServiceB are stopped, then manually starting ServiceA will firstly cause ServiceB to start. Similarly, manually stopping ServiceB will force ServiceA to stop as well.

ServiceA can have multiple dependencies, in which case all dependencies must be running in order for ServiceA to run.

Note: Service dependencies have no effect during a system shutdown.

To create a new service dependency, click on the Add drop-down list below the Services panel and select the relevant service. The name of the service dependency will then appear in the panel. Multiple dependencies may be added. The dependencies are listed alphabetically.

Note: If you are running FireDaemon Pro on Windows Vista, Windows Server 2008 or later, ensure that your services (especially the interactive services) depend on the Interactive Services Detection service (UI0Detect).

To remove an existing service dependency, click on the relevant entry in the list and then click on the Remove button.

Load Order Groups

Load Order Groups are groups of one or more Windows drivers and services. These are pre-defined as part of every Windows installation.

To make a FireDaemon Pro service dependent upon a Load Order Group, add the name of the Load Order Group to the service's Load Order Group Dependencies list. The corresponding display panel, the Add drop-down list and the Remove button all operate in the same manner as described above for service dependencies.

Changes to a service's dependencies take effect when the changes are saved and the service is (re)started.