Novell ADMINSTUDIO 9.5 User Manual page 626

Hide thumbs Also See for ADMINSTUDIO 9.5:

Table of Contents

Chapter 8: Converting Legacy Installations Using the Repackager Interface

Repackager Interface Reference

Table 8-28 • Options.ini File/General Section Properties (cont.)

OtherComponentFileExtensions

OtherFilesNewComponents

If selected, ODBC-related registry data is mapped to ODBC tables

instead of the Registry table. This data will only function correctly if

Windows Installer supports the ODBC resource being mapped; it is

recommended that you do not enable this option if you are unsure

whether the ODBC resources are supported correctly by Windows

This option is set to N by default.

For SmartScanned or ProLogged Projects:

If this is set to

Y, component conditions will store specific

operating system information. For example, if the filter is NT4, the

condition will be (VersionNT=4).

If this is set to

N, component conditions will store a grouping

of the operating system. For example, if the filter is NT4, the

condition will be (VersionNT).

This is set to N by default.

Specify additional extensions to use when defining components. MSI

has rules governing component creation for file types. For example,

portable executable (PE) files must have separate components.

Therefore, certain extensions have been defined (EXE, DLL, etc.).

Additional extensions can be defined in the options.ini file in the

Type1:Extension1|Type2:Extension2

where Type is one of the following numbers:

This option is set to 1:QTX|1:AX by default.

When this option is set to Y, one component will be created for every

file in your setup. Otherwise, new components will only be created for

each portable executable file.

This option is set to N by default.

ADS-0950-UG00

AdminStudio 9.5 User Guide

Troubleshooting