I've released wimlib 1.14.5:
Fixed excessive progress messages from `wimlib-imagex`. It now prints the progress updates at a more reasonable rate, improving performance.
Fixed build error with the latest version of Mingw-w64.
Fixed build error in `mount_image.c` on some old Linux distros ...
Search found 497 matches
- Fri Jan 30, 2026 4:28 am
- Forum: wimlib discussion
- Topic: wimlib 1.14.5 released
- Replies: 0
- Views: 1022
- Fri Jan 30, 2026 3:12 am
- Forum: wimlib discussion
- Topic: stat error?
- Replies: 5
- Views: 1421
Re: stat error?
I've fixed this in commit 3b9fa443e90d382e53133d165ae79e45d7c98178. Please pull down the latest "master" branch, and it should work now.
- Fri Jan 30, 2026 2:20 am
- Forum: wimlib discussion
- Topic: Licensing LZX compressor as LGPLv2 for integration to Wine?
- Replies: 4
- Views: 22775
Re: Licensing LZX compressor as LGPLv2 for integration to Wine?
Well, written permission from the copyright holder (me) still counts even if it's not pushed out to the repo. But sure, I understand it would be clearer if the repo itself was updated. I've pushed out a commit which updates the library license from LGPLv3+ to LGPLv2.1+.
- Fri Jan 23, 2026 4:35 am
- Forum: wimlib discussion
- Topic: stat error?
- Replies: 5
- Views: 1421
Re: stat error?
Is this wimlib v1.14.4? And are you following the instructions from "Building from source" in the README.WINDOWS.md file?
- Mon Jan 12, 2026 7:45 pm
- Forum: wimlib discussion
- Topic: [WARNING] '--update-of' is unreliable on Windows!
- Replies: 1
- Views: 1297
Re: [WARNING] '--update-of' is unreliable on Windows!
If no programs have the files open, it should be fine since the modification times should be up-to-date.
- Tue Dec 09, 2025 3:35 am
- Forum: wimlib discussion
- Topic: [Out-of-bounds read] when avl-tree nodes are allocated in specific addresses
- Replies: 4
- Views: 4425
Re: [Out-of-bounds read] when avl-tree nodes are allocated in specific addresses
Adding some assertions might be a good idea.
But again, the required alignment is no more than the natural alignment, i.e. __alignof__(struct avl_tree_node). That's either 4 or 8. So even if the code didn't use the bottom two bits of parent_balance for other information, it would still have ...
But again, the required alignment is no more than the natural alignment, i.e. __alignof__(struct avl_tree_node). That's either 4 or 8. So even if the code didn't use the bottom two bits of parent_balance for other information, it would still have ...
- Sat Dec 06, 2025 7:01 pm
- Forum: wimlib discussion
- Topic: [Out-of-bounds read] when avl-tree nodes are allocated in specific addresses
- Replies: 4
- Views: 4425
Re: [Out-of-bounds read] when avl-tree nodes are allocated in specific addresses
This is not a bug. The avl_tree_nodes are aligned to at least 4-byte boundaries in the actual code, so this issue does not occur. Note that their natural alignment suffices to achieve this.
- Fri Sep 26, 2025 9:56 pm
- Forum: wimlib discussion
- Topic: Licensing LZX compressor as LGPLv2 for integration to Wine?
- Replies: 4
- Views: 22775
Re: Licensing LZX compressor as LGPLv2 for integration to Wine?
Yes, that's fine with me. You can use the LZX code under LGPLv2. Thanks!
- Fri Apr 04, 2025 7:43 pm
- Forum: wimlib discussion
- Topic: LZMS solid multithreading issue (or bug)
- Replies: 4
- Views: 208115
Re: LZMS solid multithreading issue (or bug)
A lot of the memory used during compression is accessed randomly, not sequentially. So latency is super important, not just throughput. Having it be paged in and out of disk would be extremely slow. Probably multiple orders of magnitude slower which would easily defeat the point of using any more ...
- Thu Apr 03, 2025 5:43 am
- Forum: wimlib discussion
- Topic: LZMS solid multithreading issue (or bug)
- Replies: 4
- Views: 208115
Re: LZMS solid multithreading issue (or bug)
That's strange. Is it possible that your setup.wim has an uncompressed size between 128 MiB and 256 MiB? That's the only case that I can think of where this would happen. wimlib checks whether the total uncompressed size of the file data is less than or equal to the chunk size (the chunk size that ...