How the F-Secure Antivirus Plug-In Works

Reference Guide › Utilities › eACoexist Utility—Detect and Register Coexisting Trusted Programs › How the Coexistence Utility Works › How the F-Secure Antivirus Plug-In Works

How the F-Secure Antivirus Plug-In Works

The coexistence utility runs the F-Secure Antivirus plug-in to scan the computer for F-Secure Anti-Virus registry keys and files, as follows:

Before the CA ControlMinder installation begins the plug-in stops the F-Secure Anti-Virus services.
When the CA ControlMinder installation completes, the plug-in queries the following registry key for existence:
```
HKLM\SOFTWARE\Data Fellows\F-Secure\Anti-Virus
```
If successful it extracts the "Path" value designated %PathFromRegistry%.

If the registry key exists, the plug-in:
- Reads the value of the Path entry
- Creates the following SPECIALPGM resources of type DCM:
```
FilePathFromRegistry\fssm32.exe
FilePathFromRegistry\fsgk32st.exe
```
  This is the default action as defined in the response file. The eTrust Audit plug-in does not add a trusted program (SPECIALPGM) rule by default.
Whenever the coexistence utility runs, the plug-in:
1. Stops the F-Secure Anti-Virus services
2. Creates the same SPECIALPGM resources it creates when the CA ControlMinder installation completes (as described earlier in this topic)
3. Restarts the F-Secure Anti-Virus services

Note: The response file determines the default action that the coexistence utility performs at prescribed stages (what to do before CA ControlMinder installation, after CA ControlMinder installation, and so on).