Well of course - this is how TC saves its language file location.The problem is how TotalSQX determines current language in TC. It seems it determines it by LanguageIni key from Wincmd.ini
Which file?file must be placed in %COMMANDER_PATH%
%COMMANDER_PATH% is always valid for all plug-ins. I could use GetCommandLine but I guess that won't make you happySo, you need to 1. run TC so %COMMANDER_PATH% will be valid

Not necessarily.2. use "wincmd.ini" for settings.
Indead reading a differing filename from registry is not supported at the moment.After I renamed wincmd.ini to "tc_my.ini" (using IniReloc), TotalSQX could not determine language and set English.
As I read in Clo's statement this is not the case here.
This is the only chance you have. This wouldn't be a workaround but the only solution. Your aim must be to emulate a real TC in your plug-in manager. If you fail to do so you really have a problem.I may make a workaround: set %COMMANDER_PATH% variable in TC_plugman.
There is no logical connection between this registry setting and a TC installation. For example the setting may point to another or a non existing installation. Another case is that the setting simply doesn't exist.Lefteous will determine path to TC settings file not using %COMMANDER_PATH% variable, but using registry keys.
I can only recommend you to ask the user for a TC location if %COMMANDER_PATH% is not present. You should skip reading this registry setting!
Well this is not quite true. The /I parameter is already supported by Total SQX.he assumes that settings file name is "wincmd.ini", that is not correct.
Beside that I really don't understand why this plug-in manager should be used to configure packer plug-in settings
