wimlib

Does anyone know what could typically cause this?

Does anything appear in the error log, if you enable error logging?

On Windows, does wimlib_global_init() automatically enable privileges like SeBackupPrivilege / SeRestorePrivilege?

Yes, it enables those by default.

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 ...

I've fixed this in commit 3b9fa443e90d382e53133d165ae79e45d7c98178. Please pull down the latest "master" branch, and it should work now.

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+.

Is this wimlib v1.14.4? And are you following the instructions from "Building from source" in the README.WINDOWS.md file?

If no programs have the files open, it should be fine since the modification times should be up-to-date.

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 ...

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.

Yes, that's fine with me. You can use the LZX code under LGPLv2. Thanks!

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 ...