SWF Maestro: versatile SWF-to-EXE, SWF-to-SCR compiler with a lot of features. Creates applications, games, screensavers from SWF files.

Project settings - Final application

Availability: SWF Maestro EXE (EXE PRO), SWF Maestro SCR (SCR PRO)

Output directory
Specify the "output" directory path where the resulting files will be saved. By default, if the directory is not specified, it creates a directory named "Output" under the directory containing the "source" SWF file.

Output base filename
Specify the name for the resulting application file(s).
Screensaver Note: Microsoft requires that the name of the screensaver file starts with ‘ss’, all letters are lowercase and its length is not larger than 8 characters. Otherwise the name of the screensaver may be incorrectly displayed in the ‘Display’ menu.
To install a screensaver in the system, just copy the compiled SCR file (including the DAT file if you choose to store data in a .dat file) to the System32 subdirectory of the directory where the Windows operating system is installed. To create an installer that will auto-install the screensaver use the Screensaver installer settings.

Store data in a .dat file
By default, all files are packed into one .exe (or .scr) file. However, sometimes (for example, when you need to include a large amount of data in the application) it is better to pack them into a separate file because the operating system may load large executable files quite long. Enable the ‘Store data in a .dat file’ to pack all files to the .dat file stored together with the .exe (.scr) file of the application. The application will load data from the .dat file in this case.

Integrity check
This option adds an integrity check to the application. If someone modifies the application, it won't start.
Note: do not enable this option if you are going to sign the application using Authenticode (for example, with the help of Makecert, Signtool.exe) or use other modifying tools because the application won't start in that case.

Run after compilation
Optionally, you can automate some tasks that are performed right after compilation. For example, signing the application using Authenticode (Makecert, Signtool.exe), applying additional EXE packers (such as UPX), creating the application installation package (Inno Setup, Nullsoft Scriptable Install System), executing batch files (.bat), etc. To pass the full path to the final EXE or SCR file in the parameters of the task, use %%OUTPUTFILE%%. For example, the string of parameters for reducing the size of the executable file with UPX will look like this: '--best %%OUTPUTFILE%%'.