What does 64-bit TC share if in the same directory

[commodore]

I'm considering migrating to the 64-bit version of TC; however, there are still a few plugins which I need the 32-bit version for. I read that both versions of TC can reside in the same directory. Do they share anything else apart from the location in such case (such as settings files)?

[petermad]

All your setting files (wincmd.ini, wcx-ftp.ini, usercmd.ini, pkplugin.ini, lsplugin.ini, fsplugin.ini and contplug.ini ), your button bar files, and .lng, .mnu and .inc files are shared. If you have made redirections of sections in your wincmd.ini to other files, then they will also be shared.

The 64 bit version makes four extra entries in wincmd.ini for the 64bit plugins:
[PackerPlugins64]
[ListerPlugins64]
[ContentPlugins64]
[FileSystemPlugins64]

These sections are not copies of the four old plugin sections, they are there for TC to keep track of which of your plugins that are 64bit. The actual plugins are still listed in the old sections.

All the .exe files and .dll's are not shared - the 64bit versions of these files will typically have "64" as part of the file name.

[commodore]

Great, this is just what I need. Well, I installed it side by side, everthing seems fine, but "old" plugins are shown in Configuration | Plugins in the 64-bit version. Are they just shown there but ignored otherwise?

[petermad]

Are they just shown there but ignored otherwise?

Yes - and I find that inconvenient - you cannot see what version the plugins are installed for. You cannot even see it from the file extension in the configuration list, because often the plugins are listed as for example .wlx even though there is only a .wlx64 file installed.

Here's obviously a subject for improvement. It would be nice if the lists in the configuration had a column that showed whether a listed plugin is available or not. At least for Lister, Content and File system plugins. (the list for Packer plugins are not suited for this).


EDIT: I have just put a suggestion for improvement here http://ghisler.ch/board/viewtopic.php?p=253663

[MaxX]

for example .wlx even though there is only a .wlx64 file installed

There's no such a plugin today, which does NOT have x32 version.
So no problem with it.

BTW, I solved lots of problems (incl. this one) with splitting config files and creating links with /I="****.ini" parameters.
That's easy to do.

[commodore]

So when I installed the first plugin in TC64 (namely bzip), it said it's already installed, and if I want to overwrite it. I chose yes. Does this mean the plugin won't work anymore under the 32-bit TC?

[petermad]

There's no such a plugin today, which does NOT have x32 version.
So no problem with it.

I have are several plugins that only has a .*64 file in their installers:
wcx64_DiskDirExtended_1.67.zip
wlx_SWFView_1.3.8.1_x64.zip
wlx_mmedia251.zip
wlx_fileinfo221.zip
wfx_registry_5.0_x64.zip

Most of my 64bit plugins has installed themselves as .w?x files in the respective [*Plugins] sections - only DiskDirExtended and SWFView has installed themselves as .w?x64 files - it depends on what the author of the plugin has written in pluginst.inf at: file=

Anyway - it you can still not see in the Configuratian dialog whether or not a listed plugin is active for the current TC version when the two versions are combined using the same ini-files.

[petermad]

2commodore

Does this mean the plugin won't work anymore under the 32-bit TC?

No - it will work for both TC 32bit and TC 64bit - If the new vession of bzip has both a .wcx and a .wcx64 file it will install both and overwrite your old .wcx file with a new one. If it only has a .wcx64 file it will install this and leave the old .wcx file for use with your 32 bit TC.

[aLieN_Enemy]

for example .wlx even though there is only a .wlx64 file installed

There's no such a plugin today, which does NOT have x32 version.
So no problem with it.

BTW, I solved lots of problems (incl. this one) with splitting config files and creating links with /I="****.ini" parameters.
That's easy to do.

what do you mean by "creating links with /I="****.ini" parameters."?

[Gral]

From TC help

Code: Select all

Command line parameters
 
Total Commander can be called with one or two directories as command line parameters. This will set these directories in one or both of the file windows. This allows you to create multiple icons for Total Commander in progman or the start menu, which start Total Commander in different directories or even with packed files. Furthermore a different ini file than the default wincmd.ini can be specified to allow multiple users on the same machine to have different settings in Total Commander.
 
Syntax:
 
totalcmd.exe [/o] [/n] [Drive1:\Directory1 [Drive2:\Directory2]] [/i=name.ini] [/f=ftpname.ini]
or:
totalcmd.exe [/o] [/n] [/L=Drive1:\Directory1] [/R=Drive2:\Directory2] [/i=name.ini] [/f=ftpname.ini]

[...]

/i=name.ini Use a different INI file name.ini instead of wincmd.ini to save settings