Total7zip

[Profane0360]

The doc says the following: "If Total Commander is started in portable mode, Total7zip.xml will be stored in the plugin folder, as it was in previous versions. Default path is %COMMANDER_PATH%\Plugins\WCX\Total7zip\Total7zip.xml In all other cases Total7zip.xml will be saved to the directory where Total Commander stores the wincmd.ini."

I have Total commander in a folder like D:\TCmd, placed there via unzipping the installer, i.e. not actually installing it. If the folders structure is

D:\TCmd
D:\TCmd\ini
D:\TCmd\plugins
D:\TCmd\tools

then Total7zip.xml is stored in the folder D:\TCmd\plugins\Total7zip. But if the folders structure is

D:\TCmd\bin
D:\TCmd\ini
D:\TCmd\plugins
D:\TCmd\tools

i.e. with all the TC files in the bin folder, then Total7zip.xml is stored in the folder D:\TCmd\ini.

Why this difference? What does "portable mode" actually mean? Thank you.

[Profane0360]

I believe that the actual answer is this one:

“Now it supports what you want - if TC stores wincmd.ini _anywhere_ _inside_ %COMMANDER_PATH% folder, the plugin creates Total7zip.xml in its own folder.”

[Horst.Epp]

Here, TC runs in portable mode.
The plugin is stored under
C:\Tools\Wincmd\PLUGINS\Total7zip\
The Total7zip.xml is stored as
C:\Tools\Wincmd\PLUGINS\Total7zip\Total7zip.xml

Your folders bin, ini and tools are not part of a standard portable TC installation.

[Profane0360]

So portable mode implies that %COMMANDER_INI%\.. is actually the same as %COMMANDER_PATH%, and plugins is a folder of %COMMANDER_PATH%. Thank you!

[Horst.Epp]

So portable mode implies that %COMMANDER_INI%\.. is actually the same as %COMMANDER_PATH%, and plugins is a folder of %COMMANDER_PATH%. Thank you!

%COMMANDER_INI% may point to some other path if TC was started with a /I= parameter.

[Profane0360]

Then I am confused. When Total7zip.xml stays in its own folder? According to the doc this happens in the case of a portable setup. Not a “standard” portable setup. What does that mean?

o I can start TC with my ini files elsewhere. Does this make the setup not portable? It shouldn’t.
o I can have other tools that I need, where these stay is irrelevant for the setup itself.

So my conclusion is that a portable setup has to have the plugins folder inside %COMMANDER_PATH%, and not elsewhere. This is the only major difference between my two scenarios.

[petermad]

2Profane0360

You can actually force the location of plugin ini-files:

[ReplaceIniLocation] Set a different ini file location for specific plugins, via function *SetDefaultParams, parameter DefaultIniName, via line pluginfile.ext=c:\path\newinifile.ini or pluginfile.ext=c:\path\ - the plugin may ignore the name and just use the path.
pluginname.ext= New location of ini file sent to the plugin. The plugin name must be specified without path, and with extension as configured in wincmd.ini, e.g. sftpplug.wfx
Special values:
* send default value, but redirect to user profile if location not writable (default for packer, file system, and lister plugins)
- send default value, but do not redirect to user profile on fail (default for content plugins)

So try:

Code: Select all

[ReplaceIniLocation]
Total7zip.wcx=%COMMANDER_DRIVE%\TCmd\Plugins\WCX\Total7zip\Total7zip.xml

You cannot use %COMMANDER_PATH% it points to D:\TCmd\bin

[Profane0360]

Thank you!