It is possible to theme or brand FireDaemon Pro or FireDaemon Pro OEM. Theming (skinning) allows you to:
Note that you can't remove copyright notices and version numbers nor modify the registry keys or digital signatures of the executables. A commercial service is provided for customers who require FireDaemon Pro or Pro OEM skinned. For more information and pricing please contact sales support.
Main GUI (titlebar icon and description and toolbar icons):
New / Edit Service Definition dialog (titlebar icon and description and toolbar icons):
Help/About (titlebar description, primary icon and other text and links) plus Help/About/Details (titlebar description only) :
The minimum requirements for the replacement graphics are as follows:
Various caveats apply:
Changing The Product Name
The product name of both FireDaemon Pro and Pro OEM can be changed.
On x86 (32-bit systems) using the 32-bit version of FireDaemon or x64 (64-bit systems) using the 64-bit version of FireDaemon modify these registry key values:
On x64 (64-bit systems) using the 32-bit version of FireDaemon modify these registry key values:
ProductName is used on the splash screen, main FireDaemon Pro GUI and various other dialog boxes plus the command line. ProductShortName is typically used in message boxes.
Changing The Help File Name or Disabling Help
FireDaemon Pro and Pro OEM ship with a help file named FireDaemon-Users-Guide.chm. The help file must reside in the FireDaemon installation directory. You can rename the existing help file, supply your own help file or choose to have Help (F1) disabled.:
The help file can be any file that Windows Explorer can open. This can be a PDF, CHM, shortcut containing a URL or any other file system object that can be opened by Windows Explorer.
On x86 (32-bit systems) using the 32-bit version of FireDaemon or x64 (64-bit systems) using the 64-bit version of FireDaemon modify this registry key value:
On x64 (64-bit systems) using the 32-bit version of FireDaemon modify this registry key value:
The default key value is "FireDaemon-Users-Guide.chm". If the key is empty, help will be disabled. Alternately, set the value to the name of your help file (eg. "MyHelp.chm" or "MyHelp.pdf" or "MyHelp.lnk"). Note that any paths pre-pended to the file name will be stripped/ignored.
Renaming FireDaemon.exe and FireDaemonUI.exe
FireDaemon.exe can be renamed. To ensure FireDaemon recognises the EXE name change make sure you update the ServiceEXE registry key found under the the product registry key listed above to reflect the new name of the EXE. Note that ServiceEXE is appended to the installation directory. ServiceEXE should only contain the file name and extension delimited by a period (ie. "."). No path is permitted in ServiceEXE.
If you choose to change the name of FireDaemon.exe, the only services that will be displayed in the FireDaemon GUI will be those where the ServiceEXE matches the ImagePath registry key found in the service configuration itself typically located under HKLM\SYSTEM\CurrentControlSet\Services\<MyServiceName>. So if you decide to use the default name (ie. firedaemon.exe) then rename the EXE and update the ServiceEXE registry key - your pre-existing services will be hidden when filtering is turned on in the FireDaemon GUI.
FireDaemonUI.exe can be renamed with impunity. Core.dll and Core.manifest cannot be renamed.
Theme XML Example
FireDaemon Pro ships with a sample theme. The theme is defined in an XML file (see below). The theme XML file needs to be placed in a directory called "Skin" in the FireDaemon Pro installation directory (eg. C:\Program Files\FireDaemon\Skin). Underneath the Skin directory create a directory called "Graphics". Place all icons and bitmaps in this directory.
The default XML configuration file is as follows. Note that the ImageType tag needs to be either "icon" or "bmp" - the toolbar can only contain icons or bitmaps but not both.