If I remember correctly a simple "wincmd.ini" was not good enough and I needed a full path, making it challenging to make TC portable, but its okay, I wrote a simple program to run it with the local path.
The plugin base dir is still wrong, and a relative "plugins\" can't be used there either.
The same goes for the 7zip plugin. 7z=plugins\7zip\7zip.wcx does not work there either.
Wouldn't it be simpler if it checked in (appdir)\plugins? without a static path for plugins read from the INI file? or at least checking there instead of not working?
So I had to adapt my program to edit the ini file and correct it before running.
Using TC any other way would be a massive security risk.
Then I've got another version of TC outside of the encrypted volume, just in program files for quick file management stuff while the volume is not mounted.
On this one its a security risk that it saves so much history.
There should be an option to leave no history.left,right,SearchName,SearchIn,MkDirHistory,Command line history,SearchText,RenameTemplates,RenameSearchFind,RenameSearchReplace,RightHistory,LeftHistory
So I had to modify my program again to delete all that history from the ini file each time it is run.