dnm221 information 1 glöps
- general:
- level: user
- personal:
- first name: Daniel
- last name: Marshall
- demotool Windows Crinkler by Loonies [web] & TBC
- Quote:
It is possible in principle. The 128k limitation comes from the fact that the address where the (decompressed) code and data are located is hardcoded to 0x420000, which is 128k after the ImageBase (executable load address) of 0x400000. Lifting the limitation is thus not just a matter of changing a constant somewhere, but will involve adding an option to move the code base address. This is something we have considered doing.
Have you tried kkrunchy on your executable? I would expect it to beat the compression ratio of Crinkler at those sizes. Or is there a reason that you want to use Crinkler specifically?
Crinkler is superior to any exe packer because it does not produce nearly as many A/V false flags, which is quite important in my case. - isokadded on the 2019-01-25 12:50:23
- demotool Windows Crinkler by Loonies [web] & TBC
- Is it possible to increase maximum allowed out.exe size from 128K to 256K or 512K? My use-case for Crinkler these days is slightly atypical and it would be very helpful for me if this feature could be added.
- isokadded on the 2019-01-24 12:58:35
- demotool Windows Crinkler by Loonies [web] & TBC
- Hi,
I would like to request a feature be added to Crinkler. I want to use Crinkler for small, data compression programs.
Here is an example - Please see the cpp, obj, and exe (created with crinkler 2.0a) files in this archive: https://www.dropbox.com/s/qw0drwzqqck26f7/lzss1.7z?dl=0
As you can see, the exe runs ok. But, when we try to send an argument via argv (i.e. to compress a file or decompress a file), the exe ignores the arguments are returns the main printf statement and exits.
If a feature could be added to support this, it would be greatly appreciated.
Thanks! - isokadded on the 2018-10-01 14:17:12
account created on the 2018-10-01 13:56:14