Heaventools Resource Tuner

Contact Sales | About Us | Site Map

    English   Deutsch

Home   Tutorials   Download   Pricing

home  resource tuner tutorials  how to...

What Are Resources And Why Would I Want to Edit Them?

In a nutshell, a Windows application's resources are separate from the program code, letting you make significant changes to the interface without recompiling your entire application.

A resource is any non-executable data that is logically deployed with an application. Examples of resources include:

• Error messages
• User interface elements: menus, dialogs, hot keys
• Icons and cursors
• Strings of text
• Multimedia files: sounds, images, and videos
• Product information and vendor details (copyrights, trademarks, origins)
• Data objects
  

When developers create an application, they embed these resources directly into the executable file (EXE). This results in a single file containing both the code and the resources. During runtime, the application uses these resources repeatedly without running out. The operating system also reads the file's resources to display the application icon on your desktop and show product information such as version number, file description, and copyright notice.

Storing data in a resource section allows for changing the data and enables updates and customizations without modifying the underlying code. This makes tasks like translating the interface into different languages easier and faster.

A resource editor is the tool that enables you to access and modify these hidden resources within an executable. With Resource Tuner, you can seamlessly add, edit, modify, rearrange, and delete controls and resources within the executable file.

The Resource Editor Isn't a Magic Solution

There are several limitations to using a resource editor. Firstly, it operates solely with the resource section of the compiled executable file (represented in green). This section is just a small part of the entire PE file structure. Any data outside this resource section is beyond the resource editor's reach.

The resource editor can't alter the program code, nor can it introduce new functions if they weren't initially programmed by the original developer.

You can't edit files that are protected from modification. We are not going to defeat the security attempts of other software authors.

Resource Tuner exclusively supports 32- and 64-bit PE files. It does not provide support for 16-bit applications designed for outdated Windows versions like 3 or older.

Having just Resource Tuner won't help you edit files produced with Visual Basic. Programs compiled using Visual Basic do not commonly have menu, dialog, or string resources, but store this information elsewhere within the program code, making them inaccessible. Only Microsoft holds this information and they aren't saying. Basically, an icon and the version information are all there is in the resources.

Resource Tuner doesn't support editing the contents of installation packages. In most instances, they all look identical regardless of size, with the compressed data positioned after PE EOF. Again, the setup file's resources mainly consist of an icon and version information.

Is this legal?

Resource Tuner is intended to be used in various scenarios, including software development, translaton and localization, and even reverse engineering, often being the primary method to access a file's resources. Editing resources is the most common way to localize applications and deliver them to the internatonal market.

However, it's important to note that modifying resources could potentially lead to legal complications. Depending on the license agreement of the program you're attempting to edit, such modifications may be strictly prohibited.

< previous | next >