wimlib

It looks like the problem is that LZMS implies the use of the new WIM format instead of the old one, and then wimlib sees that because both the source and destination WIMs are in the new format and the source WIM has solid resources, it should use solid compression in the destination WIM. And there'...

By the way, please note that the directions for building wimlib on Windows changed slightly in v1.14.0, and things should be a bit easier than they used to be. Refer to the "Building from source" section of README.WINDOWS.md.

Interesting. Do I understand correctly from your proof-of-concept that getting these EAs already works as-is with NtQueryEaFile(); it's just setting them that doesn't work as-is (with NtSetEaFile()), so your driver adds an ioctl for that purpose? In that case wimlib would be saving these EAs in WIM ...

I haven't tested wimlib_extract_image_from_pipe() on Windows. On Windows, _open_osfhandle() (https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/open-osfhandle?view=msvc-170) is the usual way to allocate a C runtime file descriptor from an operating system file handle. Have you tried c...

There's no way to do this using standard path globs, which is what wimlib supports. (DISM behaves the same way, IIRC.) `*` doesn't match path separators. It would be necessary to add support for extended globs or regexes.

The list of error codes is at https://wimlib.net/git/?p=wimlib;a=blob ... 403e#l2536.

What you have is fine. You could also increase the non-solid chunk size, but that won't make much difference since you're using --solid.

Please note, if you need compatibility with Microsoft software, you generally can't customize either chunk size.

Nothing. wiminfo shows the chunk size for non-solid data only. It maybe should work differently, but this originates from the way the WIM file format is designed; there is not a single solid chunk size like there is for non-solid data.

I think this is one of the cases that's still limited to LZX 32K as the best available compression method, but this is a limitation in Microsoft software that I don't have insight into. Try it and see if it works with the particular Windows version you're using.

For most purposes just using the WIM version number should be fine: 68864 = .wim, 3584 = .esd. But as you may have noticed, technically the v3584 just allows solid resources; there might not actually be any. If you want to know for sure whether there are any solid resources you indeed need to explic...