Technical notes and system requirements

System requirements and limitations for publications

Minimal configuration

Note that this list may change in the future.

  • Microsoft Windows® XP SP3, 2003 Server, Vista, 2008 Server, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows 10.1 or higher. Windows 95 /98 /Me/2000/NT are no more officially supported, although publications may still work on them.

  • 256 MB RAM or greater (recommended: 512 MB RAM, especially if virtualization is enabled).

Size limitation

HTML Executable can create publication .exe files up to 4 GB. This is a limitation inherited from the Windows executable format. If the .EXE file is larger than 4 GB, it won’t be recognized as an application file by Windows.

A workaround is available: please see the Output Format page.

This is always better to split very large publications into a group of smaller ones. If your publication contains thousands of files, it may be less responsive, depending on the end user’s computer configuration.

Notes about IE Browser and HTML Viewer publications

  • ASP, PHP, JSP and ASPX pages which are designed to run on a server cannot work properly in publications. They will be treated as normal web pages. If you want to run PHP files in compiled ebooks, please consider our other product: ExeOutput for PHP.

  • Some ActiveX plug-ins may not work properly, depending on how they were designed. Try to use the built-in HTTP server or the Special Content feature when you experiment with them.

  • Cookies should be replaced by global variables.

  • Java applets may not always work (it actually depends on the complexity of your Java applet). Normally they will work if you follow instructions from the Java applets topic.

  • HTML Viewer publications cannot connect directly to a remote server through an HTTP protocol. You need to use an IE browser publication instead if you want to actually put “online” pages in your publication (some kind of “what’s new” pages).

  • Direct http links in Flash movies displayed in HTML Viewer publications are not supported: the external browser will be started. To avoid this, use FSCommand commands and the OnFlashFSCom HEScript event.

  • If the publication is not portable, it stores its settings on the user’s computer in a unique “publication” folder located at: C:\Users\[User name]\AppData\Roaming\HTML Executable\UserPublication\[Publication GUID] on Windows Vista/Seven C:\Documents and Settings\[User name]\Application Data\HTML Executable\UserPublication\[Publication GUID] on Windows XP. This folder can be changed as explained here. If you do not want your publication to leave files, you’ll need to add a reference to this folder for the uninstaller, so the latter will remove the contents inside this folder.


Copyright G.D.G. Software 2018. All rights reserved