Off topic, but worth a shot...

Short answer: I don't know of any programs that extract images and class files from jexepack.

Long answer: It depends on your (and jetexepack's) intepretation of .EXE file.

If it is a single binary executable that is treated as the begin-all and end-all of the application, then the best thing you can do is to use an hex editor (or similar program) and try to identify the sequence of bytes that corresponds to an image.

I mention this possibility because I don't know if this is what jexepack generates.

Some .EXE files are actually nothing more than self extracting programs that indicate somewhere the starting point of the program. A jar file is the perfect example - JREs look for a certain document (or marker) within that file and the marker tells them exactly where and what the main( ) is.In such a case, those .EXE files "temporarily unpack" the necessary files and you can grab the image files you need out of the temporary directory.

Probably the easiest "solution" is to get a third party program that monitors what files are added to your computer. Launch the application, exit the application, check the logs, and see if the application does indeed unpack its files into a temporary directory.If the application cleans up after itself like it should, then maybe you can crash the application or explicitly kill the process.

It's worth mentioning that in jar's case, it may be that the JVM is the "parent" application and the jar is treated like a zip file - it extracts the sequence of bytes it needs when it needs it, and you would be out of luck using the snoop technique. Unless you rewrote a class loader.

If no temporary files are extracted, then yes, you are going to have to kind of reverse engineer jexepack and determine if there's a pattern to the bytes such that you can determine where the image files are.

TheDavida at 2007-7-16 1:08:21 >