Search found 474 matches
- Tue Jun 21, 2016 9:24 pm
- Forum: wimlib discussion
- Topic: File concurrently modified code 88
- Replies: 1
- Views: 5513
Re: File concurrently modified code 88
Yes, you used the commands correctly, although --update-of is more effective when appending an image to an existing WIM archive, as opposed to creating a new one. The error message is a little misleading in this case. It was originally intended to appear if any files being archived were being modifi...
- Fri Jun 17, 2016 4:18 pm
- Forum: wimlib discussion
- Topic: Decrease fragmentation when using ntfs-3G
- Replies: 9
- Views: 14088
Re: Decrease fragmentation when using ntfs-3G
Yes, this has been reported before and I am planning to investigate it sometime. The current code is actually already intended to preallocate the space for each file, but perhaps it doesn't work as intended.
- Wed Jun 08, 2016 2:17 am
- Forum: wimlib discussion
- Topic: [ExclusionException] not working
- Replies: 10
- Views: 19859
Re: [ExclusionException] not working
I should add, however, that the default capture configuration file is documented [1], so you could manually create a new configuration file based on that file.
[1] https://wimlib.net/man1/wimlib-imagex-capture.html
[1] https://wimlib.net/man1/wimlib-imagex-capture.html
- Mon Jun 06, 2016 6:18 pm
- Forum: wimlib discussion
- Topic: [ExclusionException] not working
- Replies: 10
- Views: 19859
Re: [ExclusionException] not working
Neither of those features is currently implemented.
- Wed Jun 01, 2016 2:48 am
- Forum: wimlib discussion
- Topic: wimlib 1.9.2 released
- Replies: 1
- Views: 4926
wimlib 1.9.2 released
wimlib version 1.9.2 has been released. There are a few small changes: On UNIX, wimlib can now overwrite readonly files when extracting. On Windows, fixed a bug where wimlib could leave a null DACL (a.k.a. "no NTFS permissions") set on some existing directories after extraction. On Windows...
- Sat May 28, 2016 8:52 pm
- Forum: wimlib discussion
- Topic: [ExclusionException] not working
- Replies: 10
- Views: 19859
Re: [ExclusionException] not working
Yes, just use "source list" mode. For the example you gave, create sources.txt containing:
Then do:
See the documentation for details.
Code: Select all
c:\Users\test\AppData\Local\test \Users\test\AppData\Local\test
Code: Select all
wimcapture sources.txt out.wim --source-list
- Fri May 27, 2016 3:57 am
- Forum: wimlib discussion
- Topic: [ExclusionException] not working
- Replies: 10
- Views: 19859
Re: [ExclusionException] not working
Files underneath an excluded directory are not scanned. Therefore, in your example, the path \Users\test\AppData\Local\test is never seen by wimlib at all. Currently, the use case for [ExclusionException] is to name specific file(s) which should be included despite matching a wildcard pattern. This ...
- Sun May 22, 2016 2:54 pm
- Forum: wimlib discussion
- Topic: Failed to open iconv from UTF-8 to UTF-16LE: Invalid argument
- Replies: 3
- Views: 9421
Re: Failed to open iconv from UTF-8 to UTF-16LE: Invalid argument
Include the UTF-16 iconv module in your boot environment:
/usr/lib/gconv/gconv-modules
/usr/lib/gconv/UTF-16.so
/usr/lib/gconv/gconv-modules
/usr/lib/gconv/UTF-16.so
- Sun May 15, 2016 2:42 am
- Forum: wimlib discussion
- Topic: Applying a wim archive captured with --source-list and broken NTFS permissions
- Replies: 5
- Views: 10502
Re: Applying a wim archive captured with --source-list and broken NTFS permissions
Good news --- I found a workaround for the Windows bug that does not require changing directories' security descriptors. This entirely avoids the problem you've described, as wimlib now will never change the existing security descriptors (except when it actually needs to set a security descriptor gi...
- Sat May 14, 2016 12:34 am
- Forum: wimlib discussion
- Topic: Applying a wim archive captured with --source-list and broken NTFS permissions
- Replies: 5
- Views: 10502
Re: Applying a wim archive captured with --source-list and broken NTFS permissions
Hi, With regards to capturing the image: when a file or directory is added to a WIM image, wimlib creates any prerequisite ancestor directories with default metadata, including "no security descriptor". In your example, this applied to the root directory of the image. Since wimlib cannot, ...