Search the Community
Showing results for tags 'Encoding'.
Found 2 results
-
Hello World, Just a tip for those whom might have ran into this. If you have ever had a corrupt DISM log. The Answer Change your log files text encoding to UTF-8Example of a corrupt log from an improper encoding. Powershell will by default create files in UCS-2 Little Endian Encoding so this may happen to you. [2764] ImageUnmarshallHandle: Reconstituting wim at Y:\ADK\SOURCES\WINDOWS-8.1.1-AMD64.WIM.[2764] ImageUnmarshallHandle: Reconstituting wim at Y:\ADK\SOURCES\WINDOWS-8.1.1-AMD64.WIM.믯㊿ⴴ㘰ㄭ‶ㄱ㌺㨶〰牅潲††††††††䥄䵓†䄠䥐›䥐㵄㜲㐶吠䑉㈽㔳′慐正条慰桴渠敥獤琠敢⸠慣牯⸠獭⁵楦敬ⴠ䐠獩䅭摤慐正条䥥瑮牥慮⡬牨〺㡸〰〷㔰⤷[2764] ImageUnmarshal
-
Hello, and thank you for this great website and this awesome tool. NT6.x True Integrator and Win Tool Kit are simply extraordinary tools that compliment my current arsenal. I am a total n00b when it comes to coding .ini and .inf files, so please excuse my ignorance. Just one question today,.. When coding .ini and .inf file for use with NT6.x True integrator, What is the proper encoding and line ending convention should I be using when using Netepad2. ie: Unicode, UTF-8, etc... ie: Windows (CR+F), UnIX (LF), etc... Any insight would be much appreciated. Thanks in advance.
