Thank you for the quick response! I confirm that wimoptimize works as I'd expect it to work now.
Just one smallest thing, there's probably a typo in the new manpage example — the first command should probably say `wimoptimize install.esd ...`.
Search found 3 matches
- Mon Apr 03, 2023 7:12 am
- Forum: wimlib discussion
- Topic: wimoptimize vs. wimexport solid compression behavior
- Replies: 4
- Views: 3826
- Mon Apr 03, 2023 4:45 am
- Forum: wimlib discussion
- Topic: wimoptimize vs. wimexport solid compression behavior
- Replies: 4
- Views: 3826
Re: wimoptimize vs. wimexport solid compression behavior
As I can see, this is caused by wimoptimize not resetting non-solid compression algorithm when --solid is passed, but --compress is not (unlike wimexport); wimoptimize not resetting non-solid compression chunk size when the algorithm is changed (again, unlike wimexport). I can pass both explicitly e...
- Mon Apr 03, 2023 4:39 am
- Forum: wimlib discussion
- Topic: wimoptimize vs. wimexport solid compression behavior
- Replies: 4
- Views: 3826
wimoptimize vs. wimexport solid compression behavior
I have noticed that applying `wimoptimize --solid` to non-solid images (with the intention of converting a *.wim to *.esd, using non-precise terminology) produces different results compared to `wimexport all --solid`: $ cp install.wim install.wimoptimize.wim && wimoptimize install.wimoptimiz...