Wininstall Conversion Guidelines - Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference

WinINSTALL Conversion Guidelines

Wise Package Studio Reference
When the process is finished, the Conversion Complete page appears. It shows the
results of the conversion and lists any errors or problems that might have occurred.
(Example: If files referenced by the source installation could not be found, an error
is displayed.)
6. To obtain a record of the conversion errors, click Save Errors or Print Errors.
7. Click Finish.
More errors might appear at this point, which have to do with saving in Windows
Installer format.
If a file that is part of a merge module is added, the Files in Merge Modules dialog
box appears. It prompts you to add the merge module and, if necessary, download
it.
See Adding Merge Modules Instead of Files
If a file that is used by a package in the Wise Software Repository is added, the Files
in Repository dialog box appears and prompts you to add a version of the file that is
in the repository.
See Adding Files From the Wise Software Repository
8. Open the resulting package in Windows Installer Editor to view the converted file
and to resolve reported problems.
Pages in Installation Expert, such as the Files page, are populated based on the
contents of the source installation.
Following are guidelines for using Legacy Setup Conversion to convert an existing
OnDemand Software WinINSTALL™ installation to a Windows Installer package (.WSI or
.MSI). In the Professional Edition, you also can convert a WinINSTALL package to a
WiseScript (.WSE).
Legacy Setup Conversion cannot convert a WinINSTALL installation (.NAI) or
compiled executable directly; you must first convert your WinINSTALL installation to
a text file (.TXT). Legacy Setup Conversion then converts the text file to a Windows
Installer package or WiseScript package (Professional Edition only).
All the files available to the original WinINSTALL installation project must be
available to the converted installation at the exact same locations.
Because WinINSTALL installations are based on a different technology than
Windows Installer or WiseScript, not all elements of a WinINSTALL installation are
converted:
Only the installation of files, registry changes, and other system changes are
converted.
Custom logic written in the WinINSTALL custom scripting language is not
converted.
WinINSTALL environment variable assignments are not converted. To re-add
environment variable assignments in a Windows Installer installation, open it in
Windows Installer Editor and use the Environment Variable icon, located on the
Features and Components tabs in Setup Editor. To re-add environment variable
assignments in a WiseScript, open it in WiseScript Package Editor (Professional
Edition only) and use the Autoexec.bat page.
Wise Package Studio Tools
on page 232.
on page 144.
114