Search found 474 matches
- Sat Feb 03, 2024 6:05 am
- Forum: wimlib discussion
- Topic: VSS paths unable to be used with wimlib-imagex
- Replies: 6
- Views: 6315
Re: VSS paths unable to be used with wimlib-imagex
Hi, I tested this and paths to the root of the volume do work: wimcapture \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\ test.wim However paths to subdirectories do not work: wimcapture \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\Users test.wim [ERROR] Can't open "\\Users" (status=c0...
- Fri Jan 26, 2024 4:03 am
- Forum: wimlib discussion
- Topic: Is wimexport with LZMS always solid?
- Replies: 2
- Views: 3736
Re: Is wimexport with LZMS always solid?
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'...
- Thu Jan 25, 2024 2:12 am
- Forum: wimlib discussion
- Topic: Kernel Extended Attribute Support on NTFS
- Replies: 20
- Views: 14537
Re: Kernel Extended Attribute Support on NTFS
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.
- Thu Jan 25, 2024 1:43 am
- Forum: wimlib discussion
- Topic: Kernel Extended Attribute Support on NTFS
- Replies: 20
- Views: 14537
Re: Kernel Extended Attribute Support on NTFS
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 ...
- Wed Jan 24, 2024 9:47 pm
- Forum: wimlib discussion
- Topic: Wimlib_extract_from_pipe and Windows.
- Replies: 2
- Views: 3667
Re: Wimlib_extract_from_pipe and Windows.
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...
- Sat Jan 13, 2024 6:06 pm
- Forum: wimlib discussion
- Topic: wildcard excluding recursively under specific path
- Replies: 2
- Views: 4309
Re: wildcard excluding recursively under specific path
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.
- Fri Dec 01, 2023 6:13 am
- Forum: wimlib discussion
- Topic: errorlevel codes
- Replies: 1
- Views: 7712
Re: errorlevel codes
The list of error codes is at https://wimlib.net/git/?p=wimlib;a=blob ... 403e#l2536.
- Mon Nov 06, 2023 3:21 am
- Forum: wimlib discussion
- Topic: Solid Compress ?
- Replies: 4
- Views: 11352
Re: Solid Compress ?
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.
Please note, if you need compatibility with Microsoft software, you generally can't customize either chunk size.
- Sun Nov 05, 2023 8:02 pm
- Forum: wimlib discussion
- Topic: Solid Compress ?
- Replies: 4
- Views: 11352
Re: Solid Compress ?
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.
- Thu Nov 02, 2023 3:24 am
- Forum: wimlib discussion
- Topic: [Solved] Winre.wim, boot.wim and LZMS compression (solid, non-solid)
- Replies: 3
- Views: 10206
Re: Winre.wim, boot.wim and LZMS compression (solid, non-solid)
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.