Changing the Location of Total Commander Configuration Files

Depending on how you installed Total Commander, the default settings location may resolve to the installation directory or the user profile. This article explains how to locate the configuration files and shows how to move them to any directory of your choice.

The Total Commander Config Files

Total Commander stores all settings in the files wincmd.ini and wcx_ftp.ini. The location of these config files depends on your setup.

Locating the Total Commander Config Files

If the installation directory contains a wincmd.ini file, and if that file has a setting UseIniInProgramDir=7, the INI files from the installation directory are used.

Otherwise, Total Commander stores its settings files in %AppData%\Ghisler (i.e., the user profile).

Changing the Location of the Total Commander Config Files

Registry

The default location of the configuration files can be overridden in the registry. Total Commander checks the following registry keys in the order listed below:

  1. HKCU\Software\Ghisler\Total Commander
  2. HKLM\Software\Ghisler\Total Commander

To specify the location of the configuration files, create or update the following REG_SZ values in one of the keys listed above:

  • IniFileName: path to wincmd.ini
  • FtpIniName: path to wcx_ftp.ini

Command-Line Parameters

As an alternative to the registry-based approach, you can also specify the location of the config files with command line parameters:

  • /i=: path to wincmd.ini
  • /f=: path to wcx_ftp.ini

In the following example, we’re starting the 64-bit version of Total Commander with the config files located in D:\Data\Total Commander:

"D:\Tools\Total Commander\TOTALCMD64.EXE" /i="D:\Data\Total Commander\wincmd.ini" /f="D:\Data\Total Commanderwcx_ftp.ini"
ConfigurationTotal Commander

Comments

Related Posts

Fixing VS Code UI Unresponsiveness Caused by GitHub Copilot Extension

Fixing VS Code UI Unresponsiveness Caused by GitHub Copilot Extension
This article shows a simple solution to a problem that doesn’t seem to be adequately documented: VS Code UI lags, freezes, and delays caused by the GitHub Copilot extension. Problem: VS Code UI Becoming Slow Having worked on a Python project for a while, I noticed that VS Code’s UI was frequently freezing for seconds at a time. This was happening in various places of the UI: the editor itself but also in the GitHub Copilot Chat window. Copilot also seemed to be taking more and more time getting ready to answer, and the extension-host process would fully saturate one CPU core for long periods of time.
Applications

Latest Posts

Filebrowser to Be Archived. Migrate to a Modern Alternative: Sambee

Filebrowser to Be Archived. Migrate to a Modern Alternative: Sambee
Filebrowser is being archived. As the author writes, the codebase dates back to when he was but 15 years old. Having created such a popular file management tool is a more than impressive achievement for anyone, let alone a teenager. However, when it comes to security and reliability, Filebrowser seems to be built on a less than ideal foundation, so much so that the author states:
Home Automation, Networking & Self-Hosting