General Limitations of Uninstalling Initialization (.ini) File Entries

InstallShield 2024

The following limitations apply to uninstalling .ini file entries and modifications automatically:

•

Logging must be enabled when the .ini file functions are called.

•

If an .ini file was created by any of the .ini file functions, it is not removed.

•

If a section name was created by any of the .ini file functions, it is not removed, even if no more keys are present.

•

If a key value is completely replaced by an InstallScript function (not appended to, or prepended to), the key values that existed before the installation are not restored. In this case InstallShield considers the replaced key a newly created key and will uninstall it as if it is a new key that was created by the installation.

•

The uninstallation does not restore keys or values that were deleted using WriteProfString.

•

To append a value to existing key (for example, network under [386Enh]), the new entry must either be appended at the end or prepended in the very beginning of the existing string, but never inserted in the middle.

•

Only the comma (,) and semicolon(;) are considered valid delimiters. If a string value to be uninstalled is found as a part of longer string, the value and the delimiter before or after it is also removed appropriately (based on the string’s position) only if the delimiter is a comma or a semicolon. For example, if the uninstallation removes pqr from the string Key=pqr,rst,uvw, it also removes the comma after pqr. A character other than a comma or a semicolon in its place will not be removed. As a rule, avoid adding spaces around delimiters.