Search found 11 matches
- Fri Sep 29, 2017 2:02 pm
- Forum: wimlib discussion
- Topic: Can't read object ID
- Replies: 2
- Views: 12258
Re: Can't read object ID
Not sure what happened. Tried again with a clean install of Windows 10 1703 and it's working fine now.
- Thu Sep 21, 2017 8:28 pm
- Forum: wimlib discussion
- Topic: Can't read object ID
- Replies: 2
- Views: 12258
Can't read object ID
Hello, Sorry to bug you again. Everything has been working good from Linux since I got the versions squared away. Now I'm having an issue when trying to capture from WinPE using your Windows binaries. When trying to capture Windows 10 Build 1703 the following error is displayed. [ERROR] "C:\Win...
- Sat Sep 16, 2017 6:19 pm
- Forum: wimlib discussion
- Topic: Failed to convert UTF-16LE string to multibyte string!
- Replies: 3
- Views: 7686
Re: Failed to convert UTF-16LE string to multibyte string!
Somehow the symlink was still linked to an old version of the library. So the binary said version 1.12.0 but it wasn't really accurate. I updated the link and all is well now. Thanks for pointing me in the right direction.
- Fri Sep 15, 2017 3:11 pm
- Forum: wimlib discussion
- Topic: Failed to convert UTF-16LE string to multibyte string!
- Replies: 3
- Views: 7686
Failed to convert UTF-16LE string to multibyte string!
When attempting to capture Windows 10 build 1703 the following error occurs. [ERROR] Failed to convert UTF-16LE string to multibyte string! [ERROR] This may be because the UTF-16LE string could not be represented in your locale's character encoding. ERROR: Exiting with error code 66: A Unicode strin...
- Tue Apr 18, 2017 6:16 pm
- Forum: wimlib discussion
- Topic: cannot convert multicharacter to fit UTF-16LE into UTF-8
- Replies: 2
- Views: 6888
Re: cannot convert multicharacter to fit UTF-16LE into UTF-8
This is a direct capture of an NTFS volume on Linux. Both versions were linked to ntfs-3g 2016.2.22. I will try and get the exact error message. It was passed along to me by a 3rd party and that is the error they sent me.
- Tue Apr 18, 2017 3:47 pm
- Forum: wimlib discussion
- Topic: cannot convert multicharacter to fit UTF-16LE into UTF-8
- Replies: 2
- Views: 6888
cannot convert multicharacter to fit UTF-16LE into UTF-8
When trying to capture an image the error cannot convert multicharacter to fit UTF-16LE into UTF-8 is displayed when coming across file names such as Menú Inicio. This does not occur when using version 1.9.1, however using the latest 1.11.0 it does. Do I need to do something different with the newes...
- Sat Aug 13, 2016 12:58 am
- Forum: wimlib discussion
- Topic: Only apply metadata
- Replies: 2
- Views: 6006
Re: Only apply metadata
Yes the process is being killed before it finishes. I understand it is not the fault of wimapply, just for my situation having the ability to restore only the metadata without extracting all of the file data would be a valid work around for me. I just wasn't sure if there was flag I could use to do ...
- Thu Aug 11, 2016 5:34 pm
- Forum: wimlib discussion
- Topic: Only apply metadata
- Replies: 2
- Views: 6006
Only apply metadata
Is it possible to only apply the metadata from the wim image? If not would it be difficult to add? I am using a pipable wim and have an issue when restoring. I have a parent process that receives the wim via multicast and everything works fine up until applying metadata. At that point the actual tra...
- Fri Nov 20, 2015 4:34 pm
- Forum: wimlib discussion
- Topic: segmentation fault
- Replies: 3
- Views: 10021
Re: segmentation fault
This ended up being a corrupted gconv folder. It is working fine now. Thanks.
- Fri Nov 20, 2015 2:53 am
- Forum: wimlib discussion
- Topic: segmentation fault
- Replies: 3
- Views: 10021
Re: segmentation fault
The system has very limited capabilities. I will need to see if I can somehow get a debugger included in it. Right now it doesn't have that built in.