

- #Enigma virtual box extractor cracked#
- #Enigma virtual box extractor install#
- #Enigma virtual box extractor full#
- #Enigma virtual box extractor portable#
- #Enigma virtual box extractor software#
When the snapshot is ready, ThinApp will tell you to install the application.Following the instructions there, ThinApp will create a snapshot of your OS inside the VM.Start ThinApp Setup Capture inside the virtual machine (it's somewhere in the start menu).
#Enigma virtual box extractor portable#
Transfer the installer of the app you want to make portable to the virtual machine.Take a snapshot of the virtual machine.You can use the Shared Folders functionality to tranfer files into the VM and back. Transfer ThinApp's setup files in the virtual machine.Prefer the same version as the one you are running. Create a new virtual machine and install a copy of Windows on it.There is a trial version too which you can get from their site.
#Enigma virtual box extractor cracked#
It wasn't made just for making portable apps but I bet more than 80% of the people that use it, have torrented a cracked version and are using it to make portable apps.
#Enigma virtual box extractor software#
So if you find any, leave a comment! Oh and since many people asked, you can change PAL's icon either by recompiling it with a different icon (AutoIt3 source code is included in the zipfile) or you could use ResHacker to change the icon.įirst of all ThinApp is proprietary software and is really, I mean REAAAAAAAALY, expensive. Keep in mind that PAL is still in beta so there might be bugs. If this happens to you just rerun PAL on the same computer and it will probably fix everything. In cases like these it might not have time to cleanup the portable settings or bring back the local settings (if any) from the backup. The only thing that PAL might not be able to handle is a shutdown before closing the portable app. It will first backup the local version settings to appropriate files, copy the portable settings to the registry and/or the filesystem (replacing the local settings), run the program and when the program exits it will save the settings back to the portable files and then bring back the old local settings that it has backed up. In case you wondered what happens if you try to run the portable version of an app on a computer that already has that app installed, PAL can handle that just fine. Now take that portable version to another computer (again, it can be just a virtual machine) to test it by running PAL.exe. You may also rename PAL.exe to whatever you want but do not rename PAL.ini. When you are done editing it, save PAL.ini. If your app doesn't use a directory in the filesystem to store data, then just delete this line completelly. As you can see in the sample INI above, you may use enviroment variables like %appdata% etc. The FilesPath= should point to the place in the filesystem where your app stores files or settings. If your app doesn't use the registry just delete this line completelly. The RegistryPath= line should point to the registry path where you application stores its settings. Edit the Executable= line so that it points to the main executable of your application. If you app uses, for example, two folders in the filesystem to store settings, PAL will not be able to completely handle that app, meaning it will leave traces or not even work.Īfter finding where this app stores its settings, open and edit PAL.ini. This is adequate for most apps I've seen. Currently PAL can only handle one registry path and one filesystem path. Then run and exit it once and start searching as described in the first method for places in the registry or in the filesystem where the installed program might be storing settings. You may rename that directory to App if you want (just like in the sample INI file above). Then download PAL from here, unzip it somewhere and copy the program's directory from the place it was installed right next to PAL.exe. But if it doesn't work for you, please send me an error report with all the details you can and I'll try to fix it.So just like in the first method, install the program you want to make portable. It's a lot of fun (and source of the most obscure bugs), trust me! Conclusion Since Molebox internally uses ANSI, it required changing quite a few structure definitions and rewriting several string manipulation routines. Starting from Delphi 20072009, strings are Unicode. The solution was to get rid of my Zlib implementation and rewrite all methods that deal with decompression.

Unit Graphutil was compiled with a different version of zlib.TZDecompressionStream. But it won't compile with new versions of Delphi, giving error message Delphi 3 didn't have Zlib library, so you had to supply your own Zlib implementation.

Original unpacker was compiled with Delphi 3.
#Enigma virtual box extractor full#
sad I had to do a full and complete rewrite of all those methods. ImageBase ) ), endAddress - startAddress, decryptionKey )
