I'm using a program that can pack/compile a folder with files into a single *.xyz file that only that program can decompile and read. In order for the program to create a compiled file the flag:
must be in the file Meta.ini. If not, the file cannot be unpacked/decompiled and there is no way to get back the source files.
I have created a compiled file and have lost the source files. I forgot to add the decompile flag, so I currently have no way to unpack the file and continue my work. I can still compile and decompile files using the program as long as I include the flag. The file produced is in the FoxPro FPT format. The program is written in Visual Basic.
- I have a compiled/packed file that I need to decompile/unpack.
- I have access to the program that can compile and decompile the file.
- I don't have the required decompile flag in the file.
- The file produced is in the FoxPro FPT format.
- The program is written in Visual Basic.
I know where the flag needs to go but I have no way of inserting it without first decompiling/unpacking the file (that I know of). When I open the file with Notepad++ it's mostly gibberish (makes sense as the file contains alot of images and geometry data) but the contents of Meta.ini are in plaintext. However, trying to add the flag or replace one of the other flags with it gives Incorrect String errors when the program tries to load the file.
My options are:
- Insert the flag into the file so the "Compile" option becomes available within the program
- Isolate the compiler (maybe it's all in one dll hidden within the program) and skip the program's check for the flag entirely.
- Find the flag check that returns false using a memory editor and changing it to true (suggested by @DarthGizka here).
How should I go about this?