9 days ago
Topic:
Total Commander
gcelsi
|
To overcome the portability issue of Total Commander, the best method is to use the startup parameters /i and /f. For example, if the executable is at c:\PortableApps\TotalCommander1156\TOTALCMD64.EXE you just need to run
c:\PortableApps\TotalCommander1156\TOTALCMD64.EXE /i=c:\PortableApps\TotalCommander1156\Wincmd.ini /f=c:\PortableApps\TotalCommander1156\wcx_ftp.ini
and then adjust all the settings inside Wincmd.ini such as
pluginbasedir=%COMMANDER_PATH%\Plugins However, since I use multiple computers and sometimes different versions of Total Commander, I created a dedicated folder,
c:\PortableApps\TotalCommanderMV\
which stays constant regardless of the TC versions and can also be placed on a USB drive or a Cloud-synced folder (provided it is writable). Inside it, there are several folders for organization:
- TotalCommanderMV\Bar
- TotalCommanderMV\GHISLER
- TotalCommanderMV\Icone
- TotalCommanderMV\Language
- TotalCommanderMV\Plugins
- TotalCommanderMV\Plugins\WFX
- TotalCommanderMV\Plugins\WLX
- TotalCommanderMV\Utility
In some situations, TC stubbornly tries to use the folder c:\Users\<username>\AppData\Roaming\GHISLER\
To solve this, I avoid using the startup parameters /i and /f and instead create a hard link inside the Windows user folders by deleting
c:\Users\<username>\AppData\Roaming\GHISLER
and replacing it with a hard link to the constant folder above, using the DOS command:
mklink /J "c:\Users\<username>\AppData\Roaming\GHISLER" "c:\PortableApps\TotalCommanderMV\GHISLER"
following the syntax:
MKLINK /J Link Target
edited by gcelsi on 22/09/2025 |