Re: HACK Executable File Icons Changer 5 Portable
Sanora Ngueyn
Add an icon in the resource section of you C++ project. This icon will be shown as an Application icon for your executable. [Note: make sure you are in the Resource View window, not the Solution Explorer window. Then right-click on the rc folder to Add Resource...]
Also note that while adding the icon you need to add different size images for the Icon like 16*16, 32*32. These different icon images will be used by Windows Explorer to display Application Icon in different View Modes(Small Icons, Medium Icons, Larget Icons, Extra Large icons etc.)
In traditional windows executables, the icons are included in a part of the .exe file called a "resource" and you use a "resource editor" to edit the resource. (You could also modify the actual executable to point to a different resource, but that is much more difficult).
I have lot of executable that I have compiled (long time back) for many of which I don't have sourcecode now. But when I compiled them I didn't put any icons for them, so they all look like same dull, bald default icon. So my questions are,
The icon used for the executable is nothing but the first ICON resource encountered in the EXE file. You can use a tool like ResHack to extract icons from existing binaries, and (I think) you can also use it to change the icons attached to a particular resource.
Hence for your problem, I would suggest to dump the overlay, make required modifications on the PE, and finally re-append back the dumped overlay to the end of the executable.
For the last step you can use a Hex Editor or the MS-DOS COPY command.
When the tool is minimized or the main window is in the background, i would like to see immediately whether the tool is running or not. Since the running executable is shown in the task bar. I thought it would be nice if I could change that small icon displayed in the task bar into "red" or into "green" depending on whether time is being tracked or not, please see a photoshopped example:
Things can get a little repetitive and boring with the icons. Even the EXE files can start to look similar after a while. All you need to do is find the icons you like and then use one of the options listed above to make your program icons different.
Ive developed a software and exported it as a unix executable file. The thing is I want to change the icon of the file to my company logo. Does anyone know how to change the .ico of a unix executable?
In short, the current NetBeans IDE (6.7) only provides limited support for changing application icons. Alternate solutions are described below, but NetBeans itself does not include any way to change the icon of the Windows launcher executable called .exe, nor does it provide a way to specify an .icns file for Mac OS X. There is already an enhancement request for Windows icon support: issue #64612.
When changing icons, make certain that the replacement sources are the same size and have the same number of colors as the item to be replaced (e.g. a 16x16 4-bit icon cannot be replaced with a 32x32 8-bit icon). If you keep getting a mismatch error when trying to change out an icon that looks the same size and bits, it only means the source icon is not the same color depth (24-bit and 32-bit icons look very much alike).
Why is it so important? Because the icon size and color depth in the EXE file is not optional, and there are more than just one icon inside any Windows executable file. When Windows prepares to display a main application icon, a desktop shortcut for example, it chooses an icon based on specific criteria rather than the first one available. Carelessly swapping out the icon sizes may result in visual artifacts.
There is one thread with this question but it has not been answered. One person suggested the standard way to change windows icons, but that was not what the poster asked. The standard defualt Brave icon is huge and distracting. IN the program .exe file there are several other colors instead of the red, that would be FAR preferable to those of us with multiple shortcuts stored on our Windows desktop. How can we go about changing which icon Brave uses as its default icon?
In order to change the icon of the executable application file itself, as it is presented on the desktop (that is, prior to application launch), it is necessary to employ another, platform-dependent technique.
To configure your application's icon, a resource file containing information about the icon is required. A resource file is a text file that contains information about the application resources, such as icons, cursors, fonts, and so on. For more information about resource files and what it can contain, see About Resource Files.
Although many programs can create icon files (.icns), the recommended approach is to use the iconutil program supplied by Apple. iconutil is a command-line tool that converts iconset folders to deployment-ready, high-resolution icns files. Using this tool also compresses the resulting icns file, so there is no need for you to perform additional compression.
Notice that the first set command defines the MACOSX_BUNDLE_ICON_FILE variable, which is required to add the icon file to the Info.plist file. The second set command defines the app_icon_macos variable with the absolute path to the icon file. This variable is then used to configure MACOSX_PACKAGE_LOCATION, which defines the icon file's install location. Finally, the add_executable uses the app_icon_macOS variable to set the application's icon.
In this section we briefly describe the issues involved in providing icons for applications for two common Linux desktop environments: KDE and GNOME. The core technology used to describe application icons is the same for both desktops, and may also apply to others, but there are details which are specific to each. The main source of information on the standards used by these Linux desktops is freedesktop.org. For information on other Linux desktops please refer to the documentation for the desktops you are interested in.
Often, users do not use executable files directly, but instead launch applications by clicking icons on the desktop. These icons are representations of "desktop entry files" that contain a description of the application that includes information about its icon. Both desktop environments are able to retrieve the information in these files, and they use it to generate shortcuts to applications on the desktop, in the start menu, and on the panel.
Although desktop entry files can usefully encapsulate the application's details, we still need to store the icons in the conventional location for each desktop environment. A number of locations for icons are given in the Icon Theme Specification.
Although the path used to locate icons depends on the desktop in use, and on its configuration, the directory structure beneath each of these should follow the same pattern: subdirectories are arranged by theme, icon size, and application type. Generally, application icons are added to the hicolor theme, so a square application icon 32 pixels in size would be stored in the hicolor/32x32/apps directory beneath the icon path.
Application icons can be installed for use by all users, or on a per-user basis. A user currently logged into their KDE 4 desktop can discover these locations by using kde4-config, for example, by typing the following in a terminal window:
Typically, the list of colon-separated paths printed to stdout includes the user-specific icon path and the system-wide path. Beneath these directories, it should be possible to locate and install icons according to the conventions described in the Icon Theme Specification.
If you are developing exclusively for KDE, you may wish to take advantage of the KDE build system to configure your application. This ensures that your icons are installed in the appropriate locations for KDE.
Application icons are stored within a standard system-wide directory containing architecture-independent files. This location can be determined by using gnome-config, for example by typing the following in a terminal window:
If you are developing exclusively for GNOME, you may want to use the standard set of GNU Build Tools. For more information, see the Integration Guidelines section. This ensures that your icons are installed in the appropriate locations for GNOME.
Changing the icons used by programs on your computer is a great way to customize your business computer and reflect your corporate personality on the desktop. Icons used by the executable files are actually embedded resources inside the program file itself. It is not easy nor is it completely safe for your system to modify these resources. Doing so can risk the integrity of your system. However there is another way to use your custom icons by using Windows shortcuts. Windows shortcuts are typically what you already have on your desktop, which are pointers to the real executable. In Windows 7, you can modify the icon used by the shortcut easily without risky modifications to your machine's registry.
Resource Tuner is an ideal choice for modifying icons in Windows executable files, whether it's the exe file's icon or the default menu icons. However, it's essential to remember that Windows executable files contain multiple icons grouped together.
These icons are stored within EXE or DLL files in Icon Groups, and each Icon Group can consist of several icon images, each with distinct sizes and color depths. Common icon sizes include 16, 32, and 48 pixels square, while color depths vary between 32-bit (24-bit with 8-bit alpha channel), 8-bit (256 colors), and 4-bit (16 colors).
When replacing icons and cursors, make certain that the replacement sources match the size and color depth of the item being replaced. For instance, a 16x16 4-bit icon cannot be swapped with a 32x32 8-bit icon.
If you encounter a mismatch error while attempting to change an icon that appears to have the same size and bits, it indicates that the source icon's color depth is not the same (24-bit and 32-bit icons may look similar but have different color depths).
aa06259810