Replies: 1 comment
-
It's been suggested before #190 and I've looked into it at the time. The problem I have is that there's a lot that can go wrong with the process, and I already have a hard enough time catching bugs to do with permissions, security and the million and one ways files can seemingly exist on a computer. There'd be a lot of work to ensure corruption doesn't occur and I don't think I'm willing to learn C/C++ just to write a dangerous filesystem driver to make it work. There's also no guarantee of resiliency between windows updates, and I cannot be responsible for that much risk. Plus, wimlib (if I recall correctly) doesn't avoid the issue of decompression when modifying files. Even with using Windows to handle the actual filesystem linking and transparent compression, there are still people that run into corruption issues from time to time, and I very much doubt I'd do a better job of it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Wimlib compress faster and better than compact.exe, according to https://wimlib.net/compression.html#Benchmarks
It will be better to use user provided compress ration for lzx, like --compress=LZX:100 or :50.
E.g. LZX:50 is 2 times faster that compact.exe and compress ratio is better.
Paid ZipMagic already does this. It compress file to WofCompressed stream using wimlib.
Beta Was this translation helpful? Give feedback.
All reactions