The packager writes your application into the image file named epappl by default. This file is created in the default directory. You can rename it as required.

You will need to have other files than an ini file and the output from the packager to successfully run your packaged image. See Files to distribute with your application for the files you need.

More complicated reduced runtime images may need more resources. For instance, some applications require third party resources. Any such requirements in the examples will be noted in the example itself.

Given a packaged image, the steps to run it are

To run a packaged image with a user interface in the default directory using the .ini file of the development image: nodialog –iepappl –ini:abt.ini.

However, if you pause to setup an intentional context for your runtime image, you will reap benefits.

It is possible that your application can successfully package, yet fail to run. If this happens, first review the packaging guidelines. Violations of these guidelines could result in runtime errors manifesting themselves as walkback log or a dialog box then look at the “Troubleshooting” section. See also how to choose how to launch your image.