I noticed my Total Commander was not working correctly. I found out it was because wincmd.ini was in utf-8 and Total Commander did not interpret the first line correctly.
Try this:
In a folder of your choice create a file called wincmd.ini with the following contents:
Well, saving without BOM would result in the same file as when saving as ANSI now would it
Only if the file is 7-bit ansi. If there are 8-bit ansi characters they will be saved differently when saved as ansi than when saved as utf8 (with or without bom).
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
white, wincmd.ini (and all other TC's INI and BAR files) can't be in UTF-8. Windows doesn't support UTF-8 for INI files. If you want Unicode, save file in UCS-16 (called just Unicode in Notepad) - all will work.
I think BOM for UTF-8 may cause your errors because Windows doesn't expect to see it in INI file.
MVV wrote:white, wincmd.ini (and all other TC's INI and BAR files) can't be in UTF-8. Windows doesn't support UTF-8 for INI files. If you want Unicode, save file in UCS-16 (called just Unicode in Notepad) - all will work.
I think BOM for UTF-8 may cause your errors because Windows doesn't expect to see it in INI file.
It wasn't my choice to store it in UTF-8..
I noticed as soon as Total Commander wants to store some unicode characters in the ini, my ANSI ini is changed into UTF-8.
It's unfortunately a limitation of the Windows functions to read ini files. They see the BOM at the beginning of the first line instead of square brackets, and therefore ignore it.