Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference page 207

Wise Package Studio Reference
Capture non-Microsoft ODBC information
In most cases, you can leave this check box cleared. If this check box is cleared,
ODBC information is added to the ODBC driver table (in Windows Installer
packages) or added as an Install ODBC Driver action (in WiseScript packages).
If you mark this check box, ODBC information is added as registry entries instead.
Mark this check box only if:
You know the installation you're capturing contains ODBC drivers, and
those drivers were not installed using Microsoft's recommended technique.
(Microsoft recommends that developers register their ODBC drivers using
ODBCInst.dll.)
Create installation sequence report
(Not available in Standard Edition.)
Mark this to generate a log file that shows the changes that the installation made in
the order in which they occurred. This check box is unavailable if you are using
snapshot comparisons only, because the snapshot method does not capture the
order of installation, only the changes.
This option is unrelated to the View Report button on the SetupCapture Inclusions/
Exclusions dialog boxes, which generates a temporary report regardless of what you
select here.
Enhanced File and Registry Key Association
Normally, SetupCapture associates a file and registry keys by reading the file's self-
registration information from the registry and from the file's type library. When a
file's self-registration information and type library do not include all of the registry
keys that the file updates during registration, SetupCapture may place those
registry keys into different components than the file. (This mis-association can
cause self-repair problems if one of the components is uninstalled.)
When you mark this check box, SetupCapture performs an additional step (using
the WiseComCapture.exe utility) to find all registry keys that are updated when a
file is actually registered. With this additional information, SetupCapture moves
registry keys updated by a file into the same component as the file, as necessary. If
the additional step finds registry keys that were not found by the primary capture,
those registry keys are not added to the repackaged installation. Using this feature
speeds the installation that is created with SetupCapture.
This feature registers every self-registering .DLL found in the capture. If you have a
self-registering .DLL that you know is not set to be registered during the installation,
then you might not want to use this feature because it could cause the repackaged
installation to not function properly.
Advertising Setting (Windows Installer)
(Windows Installer packages only.)
Windows Installer considers some kinds of registry entries, such as file extension
definitions, to be advertising information.
See Platform Support of Advertisement in the Windows Installer SDK Help.
Specify how to handle advertising information:
Retain registry information as-is
Try to create a package that does not support advertising. SetupCapture will not
convert registry entries to advertising information, but instead leaves them as
registry entries.
Capturing Applications
207