Search found 474 matches
- Fri Sep 22, 2017 4:34 am
- Forum: wimlib discussion
- Topic: Can't read object ID
- Replies: 2
- Views: 12188
Re: Can't read object ID
Well, Windows is returning a strange error code which I haven't seen used in that situation. But I'm not able to reproduce the problem. Given a fresh Windows 10 Build 1703 installation, I tried capturing from the Windows PE included in the installation media, from an older Windows PE (Windows 7), an...
- Wed Sep 20, 2017 2:56 am
- Forum: wimlib discussion
- Topic: Failed to convert UTF-16LE string to multibyte string!
- Replies: 3
- Views: 7570
Re: Failed to convert UTF-16LE string to multibyte string!
Ah, I should probably make wimlib-imagex print the version of wimlib it is using, in case it's not the same as the version of wimlib-imagex. (FYI: using a version of wimlib that is older than wimlib-imagex may work, but is not guaranteed to. Using a *newer* library with an older wimlib-imagex is def...
- Wed Sep 20, 2017 2:34 am
- Forum: wimlib discussion
- Topic: Some basic use for dummies?
- Replies: 3
- Views: 8946
Re: Some basic use for dummies?
A WIM file can contain multiple images, each of which is a logically independent directory tree. The 'wimappend' command adds a new image. For an incremental backup you can just append an image that is named with a timestamp or datecode, then refer to it by name later. The --update-of option is also...
- Fri Sep 15, 2017 10:02 pm
- Forum: wimlib discussion
- Topic: Failed to convert UTF-16LE string to multibyte string!
- Replies: 3
- Views: 7570
Re: Failed to convert UTF-16LE string to multibyte string!
The way strings are converted between different encodings was improved in wimlib v1.10.0, but you're using an older version. Can you please try the latest version? You are definitely *not* using v1.12.0, because the error message quoted does not exist anymore.
- Thu Aug 17, 2017 3:46 am
- Forum: wimlib discussion
- Topic: Files with the same modification date and size in delta backups
- Replies: 7
- Views: 19180
Re: Files with the same modification date and size in delta backups
There's no need for a "hash compare" option, since it's the default behavior. Just don't specify --update-of, and wimlib will hash every file rather than trying to optimize it by checking file timestamps and sizes.
- Sun Aug 13, 2017 6:28 pm
- Forum: wimlib discussion
- Topic: resuming failed extraction
- Replies: 1
- Views: 5310
Re: resuming failed extraction
Sorry, there's no way to do that currently. Just retry it from the start.
- Sun Aug 13, 2017 6:27 pm
- Forum: wimlib discussion
- Topic: depth option for wimdir
- Replies: 2
- Views: 6726
Re: depth option for wimdir
Do you mean that --depth=N would list the given path, plus N more levels underneath? What about an option to just list the immediate children, like the `ls` command?
- Sat Jul 29, 2017 9:24 pm
- Forum: wimlib discussion
- Topic: wimlib 1.12.0 released
- Replies: 1
- Views: 5786
wimlib 1.12.0 released
There haven't been too many changes, but there hasn't been a release in a while so I've gone ahead and released wimlib 1.12.0. List of changes: * Fixed a bug that was causing the LZMS decompressor to be miscompiled with GCC 7 (this broke extracting "solid" archives). * The Windows 10 Recyc...
- Sun Jul 16, 2017 5:04 pm
- Forum: wimlib discussion
- Topic: wimlib without archive
- Replies: 8
- Views: 12622
Re: wimlib without archive
wimlib-imagex v1.12.0-BETA2 has a --quiet option now.
- Thu Jul 13, 2017 1:24 am
- Forum: wimlib discussion
- Topic: How "wimcapture --pipable" option works
- Replies: 2
- Views: 7148
Re: How "wimcapture --pipable" option works
Also, if you're looking for more detail see write_pipable_wim() in src/write.c. There's a comment that explains the format changes that were made.