Plugin auto-install HOWTO (TC 6.5 or newer)

[Umpal]

My wife's TC does not open zips anymore. When she presses Enter the Windows 10 opens its own window and handles it.
How to change it back?
The question is here because I wanted to install her a plugin (Cloud) and I can't do it manually (entering the archive with Ctrl+Page Dn does not prompt the installation).

[Hacker]

Umpal,
Configuration - Options - Packer - Treat archives like directories?

Roman

[Umpal]

I was looking for this option but I don't know how could I miss it
Thank you, it worked!

[me76]

Is it possible to have 32- and 64-bit versions of plugin in single archive, and have TC pick the right one?

[Horst.Epp]

Is it possible to have 32- and 64-bit versions of plugin in single archive, and have TC pick the right one?

That's the normal case for most plugins.

[petermad]

Well, during installation TC installs both versions if present in the archive, but when the plugin is used by TC, then TC picks the right one automatically.

[me76]

Well, during installation TC installs both versions if present in the archive, but when the plugin is used by TC, then TC picks the right one automatically.

Then how should I specify plugin file name (file parameter)?

[Dalai]

Then how should I specify plugin file name (file parameter)?

You can take a look at the pluginst.inf file of other plugins. Probably most (if not all) of them specify the 32-bit version, i.e. plugin.wcx, plugin.wfx, plugin.wdx or plugin.wlx.

Regards
Dalai

[Flint]

2me76
TC is designed in such a way, that you always specify the base 32-bit plugin name, like myplugin.wlx. When TC tries to load the plugin, it will automatically check if the more appropriate version is present in the plugin firectory (like myplugin.uwlx for 32-bit Unicode version, or myplugin.wlx64 for 64-bit version) and will load it instead.

[me76]

2me76
TC is designed in such a way, that you always specify the base 32-bit plugin name, like myplugin.wlx. When TC tries to load the plugin, it will automatically check if the more appropriate version is present in the plugin firectory (like myplugin.uwlx for 32-bit Unicode version, or myplugin.wlx64 for 64-bit version) and will load it instead.

Thank you Flint, that worked!