Patching or Modifying an .exe File

[Michael Mattias]

Store the changeable info in program resources... then just change the resource as required with the UpdateResource function.

This is what I do. I never modify the actual executable code EXCEPT when there is an actual change to it. (at which time there is a version change).

Here's a demo to get you started: User-Defined Resource Demo January 26 2003

I suppose "in theory" you could come up with a way to replace functions in a compiled executable, but I never liked software which does this. If you have one or two functions which are subject to frequent change, put those functions in a DLL and when you update all you have to change out is that one DLL file.

MCM

[mark pruitt]

There are programs available that will allow you to create a "patch" to fix or update an .exe file.

I have an application that currently requires a user to create and then use a login name and password to use it. Some want to use the application without having to login. Since it's their nickel, I don't really care, I just want to do it as easily for me as possible.

One approach is to make a new .exe file and distribute it to those that don't want to login. I could also use available software and create a "Patch"; six of one and a half dozen of the other on this one.

I know there are some freeware and commercial products that will do this.

Has anyone done anything like this in PB? Or if not, is there an easier/better way to do this?

As always, any and all suggestions appreciated.