I guess I was under the mistaken impression that using UseLZMAPacker() or Importing ZLib would result in a file that could be opened on it's own by using 7zip.
This seems to be incorrect. Is it recommended that we use UseZipPacker() when we need external processes to be able to read and open the file?
What should open zlib or LZMA compressed files?
- RichAlgeni
- Addict

- Posts: 935
- Joined: Wed Sep 22, 2010 1:50 am
- Location: Bradenton, FL
Re: What should open zlib or LZMA compressed files?
There are unique complex structures defined for each compression utility such as Zip and 7-Zip.
But, several utilities may use similar compression algorithms internally.
If you compress memory using LZMA or zlib and store the results to file, only your unique pattern can unlock it.
But, several utilities may use similar compression algorithms internally.
If you compress memory using LZMA or zlib and store the results to file, only your unique pattern can unlock it.
The nice thing about standards is there are so many to choose from. ~ Andrew Tanenbaum
- RichAlgeni
- Addict

- Posts: 935
- Joined: Wed Sep 22, 2010 1:50 am
- Location: Bradenton, FL
Re: What should open zlib or LZMA compressed files?
So we should use AddPackFile when we want to save compressed data to a file? And LZMA isn't supported in AddPackFile?skywalk wrote: If you compress memory using LZMA or zlib and store the results to file, only your unique pattern can unlock it.
Thanks Steve!
Re: What should open zlib or LZMA compressed files?
Not always. I don't use the Packer lib but I do store custom compressed data(password protected and encrypted) to file and can read it back since I know the structure used. For now, zlib import seems fastest for me, but not the best compression.
The LZMA implemented in the Packer lib does not expose compression ratios or dictionary sizes, so it's not a fair comparison. If those get added later, I will consider using the internal CompressMemory() cmd with #PB_Packer_LZMA.
The LZMA implemented in the Packer lib does not expose compression ratios or dictionary sizes, so it's not a fair comparison. If those get added later, I will consider using the internal CompressMemory() cmd with #PB_Packer_LZMA.
The nice thing about standards is there are so many to choose from. ~ Andrew Tanenbaum