Earlier I posted a link to a site that has a free third part Windows program that can hide a set of install files into one EXE file. The documentation indicates it would serve the needs of the OP. However, the OP either did not red the linked page, or else he already has his heart set on some other way to solve his problem.
Dear OP,
Hope you are still with us. The forum is made of volunteers with different backgrounds and skills. The general consensus is the MD5 is only part of a number of methods used to improve security in computer systems.
It has been suggested that you try something that is more completed and self-contained to dove your problem.
Yes, it is possible to write a program in a text editor that will look like nonsense. But it will execute hidden commands when lo pended in DOS. - But later versions of Windows have blocked off that method for security reasons.
Noways the proper way to begin a sires of actions without the user knowing the details is by using an
Installer Program.Before you conclude that an installer is NOT for you, please look at the link below:
http://en.wikipedia.org/wiki/List_of_installation_software.
Also, the idea is discussed on the Microsoft site. But it may not be for you.
http://www.microsoft.com/en-us/download/details.aspx?id=25This white paper describes the patch sequencing functionality in Microsoft® Windows Installer version 3.0. Beginning with the theory of patch sequencing in Windows Installer version 3.0 and finishing with specific sequencing sample techniques for controlling the lifetime of patches through supersedence relationships, this document identifies the concepts of patch migration and compatibility, advanced sequencing scenarios, and integration of sequencing with other features of the Windows Installer.
This document is targeted at installation developers or Setup authors responsible for the design, creation, and management of Windows Installer patches (.msp files). Familiarity with the basic principles of the Windows Installer and Windows Installer patches is assumed. Sample patch metadata tables in this document may be authored by using the Orca tool in the software development kit for Windows Installer version 3.0. Other authoring tools may require different authoring steps or may provide access to a subset of the described functionality.
OK, that is not exactly what you want, but close. The installer does thinbgs with the user NOT knowing the details. Nor can the user change it.
Just trying to help