Output Path #
The Output Path specifies the location where ExeOutput for PHP will create the executable file for distribution.
In the Output Path field, provide the full path for the final application file, including the directory and filename. This file must have a .exe extension.
Notes:
- It is recommended that you save your project before compiling.
- If the application file already exists, it will be overwritten without warning.
- If the output folder does not exist, it will be created automatically.
- Additional subfolders, such as
Data, may be created to store external files. - Ensure the output folder is not read-only, especially on Windows versions with User Account Control (UAC) enabled.
- All resources (e.g., splash screens) and source files must be present during compilation.
- Ensure you have sufficient free disk space, as ExeOutput for PHP does not check for available storage before compiling.
Application Title #
ExeOutput for PHP requires a title for display in message boxes and window title bars. The application title should be a short, descriptive phrase, such as “My Wonderful Site” or “Demonstration for E=mc²”. This title will appear in the Windows taskbar and Task Manager.
Application GUID #
Similar to how an ISBN identifies a book, the Application GUID uniquely identifies your application, allowing it to store and manage its settings on the user’s computer. To generate a new GUID, click the button to the right of the field.
Note: Do not change the GUID after starting a new project. If you want to share settings between different applications, assign them the same GUID.
Request Elevated Rights (User Account Control) #
Configure how elevated rights are requested on Windows versions with User Account Control (UAC). If your application needs to perform tasks that require administrative privileges, you can set the appropriate execution level.
You have three options for setting the requested execution level:
- As Invoker (Default): Turn off the Request Elevated Rights option. The application runs with the same access token as the parent process.
- Turn on the option and choose between two levels:
- Require Administrator: The application will only run for administrators and must be launched with a full administrator access token.
- Highest Available: The application runs with the highest privileges the current user can obtain.
Enable Third-Party Obsidium Software Protection API #
If you protect your application with Obsidium software protection, you can invoke its API directly from PHP or HEScript. Refer to our complete video tutorial on adding licensing features to your PHP apps with ExeOutput and Obsidium.
To enable support for the Obsidium API in your PHP application:
- Check the option Enable Third-Party Obsidium Software Protection API. This allows ExeOutput for PHP to use a special version of the EXE stub.
- Ensure this special version has been downloaded and installed with the Web Update utility.
Please also read the licensing topic dedicated to Obsidium.
Warning
This option is not compatible with UPX compression.
Use the Same EXE Filename for PHP Child Processes #
By default, PHP child processes created by ExeOutput for PHP have a standard name. This can sometimes cause issues with Windows security solutions. In such cases, you can enable the Use the Same EXE Filename for PHP Child Processes option.
Important: Enabling this option may lead to occasional, random crashes of PHP processes. If you experience such crashes, do not enable this option. It is disabled by default.
Disable Multithreading for Troubleshooting Purposes #
By default, ExeOutput for PHP enables multithreading support. Each PHP script called by the internal browser is executed in a separate thread or process, independent of the main UI thread. This ensures that the UI remains responsive.
If you encounter issues, you can disable multithreading to help diagnose the problem:
- Disable Multithreading: This executes all PHP scripts on the main thread, which can help identify if multithreading is the source of conflicts or other issues.
