Troubleshooting Guidelines for WinINSTALL Conversion
AdminStudio 2023 | 25.0 | Repackager
Use the following troubleshooting guidelines to identify and fix WinINSTALL conversion problems.
| • | Repackager tool supports 6.0, 6.5, and 7.x project formats only. For all other formats, please use the WinINSTALL LE tool available as a free download in Windows 2000 to convert to 7.x files. |
| • | Repackager tool cannot convert WinINSTALL .NAI files—It can only convert WinINSTALL projects that have been converted to text (.txt). |
| • | All files must be available—All the files that were available to the original WinINSTALL installation project must be available to the converted installation at the exact same locations. |
| • | Not all elements of a WinINSTALL installation are converted—Because WinINSTALL installations are based on a different technology than Windows Installer, not all elements of a WinINSTALL installation are converted. Only the installation of files, registry changes, and other system changes are converted. |
| • | Custom logic is not converted—Custom logic written in WinINSTALL’s 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 the converted project in InstallShield Editor and use the Environment Variable view. |
| • | WinINSTALL variables are converted to a Windows Installer variable—If the target path of a file contains a WinINSTALL variable, then the WinINSTALL variable is converted to a Windows Installer variable. |
| • | Specify @ variables at conversion time—If the source path of a file in WinINSTALL contains either the @Server or @Wininstall variable, you can specify the values of these two variables at conversion time in the Repackager. |
| • | The WinINSTALL Preinstall and Postinstall scripts are not converted. |