Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0 Reference page 20

ConflictManager Reference
2. From File Conflicts, select an option.
Normal file conflicts (warnings and errors only)
Find files with the same name but different file information that are installed to
the same directory or to different directories by multiple packages.
Normal conflicts plus informational
Find files with identical file information that are installed to the same directory
or to different directories by multiple packages. Finding information conflicts
slows conflict detection.
Do not detect file conflicts
Run conflict detection without looking for file conflicts. You might select this
option to check for a specific type of conflict other than file conflicts.
3. Use file hash values to determine conflicts
The Import Wizard in Software Manager scans every source file in a package and, if
it can find the file, it generates a hash value for that file. Mark this to use the hash
value to find conflicts. Using hash value comparisons results in faster conflict
detection and analysis because, once it compares the hash values, ConflictManager
does not have to compare anything else.
See Hash Value Comparisons in Conflict Detection
4. If file has version information, ignore date/time for conflict detection
Mark this to ignore date and time differences between files that have the same
version and size. Clear this to have the conflict detection find date and time
differences when all other file information is the same.
5. Ignore Component GUID mismatches if both files have the shared DLL
counter set
Normally, installing two files with the same name to the same location when their
component GUIDs do not match causes a conflict, even if the shared DLL counter is
set for both files. When the shared DLL counter is set, problems are not likely to
occur. Mark this check box to ignore such conflicts.
6. From Registry Conflicts, select an option.
Normal Registry conflicts (warnings and errors only)
Find registry keys that are set to different values by multiple packages.
Normal Registry plus informational conflicts
Find registry keys that are set to the same value by multiple packages. Finding
information conflicts slows conflict detection.
Do not run registry conflicts
Run conflict detection without looking for registry conflicts. You might select this
option to check for file conflicts only, or for a specific type of conflict other than
registry conflicts.
7. From Component Conflicts, select an option to determine whether to detect
Windows Installer component conflicts.
Component conflicts involving files only
Find component conflicts involving files (example: components that install the
same file but have different component GUIDs). Although these conflicts are
legitimate, some organizations choose to ignore them because they believe that
the Windows Installer self-healing functionality will resolve most of the
problems they might cause.
Setting Up ConflictManager
on page 14.
20