Plugins not working: "File plugin.wcx not found!"

lhalda · Post by *lhalda » 2015-03-20, 16:07 UTC

Hello, I just reinstalled my Windows 8.1 64bit machine, restored backup of TC 8.51 installation, and no packer plugins work.

When I go to Configuration - Options - Plugins - Packer Plugins - Configure, select any extension and hit OK, error message emerges saying "File plugin.wcx not found!". Same happens when installing plugins anew. See screenshot of the error (for illustration showing a folder with an .iso file that should have an archive icon and be unpackable if the plugin worked - but it still is associated with Windows iso mount tool and even Ctrl+PgDn doesn't work).

TC is installed in c:\Programy\totalcmd, plugins are in c:\Programy\totalcmd\Plugins\, and is run as an administrator (doesn't work in nor non-admin neither admin mode). Settings are stored in the program folder, everything has transferred successfully, including FTP accounts and plugins settings.

I re-installed TC 8.51a over the installed data from old Windows installation (also x64 8.1).

Strangely, SFTP plugin seems to work (%COMMANDER_PATH%\Plugins\WCX\ex2fs\sftpplug\sftpplug.wfx), other file system plugins aren't working either. See it in second screenshot.

I also can't connect to FTPS (FTP over SSL), TC requests OpenSSL DLL to be put in its folder, even though it's already there. So I guess it doesn't see its installation folder. How do I find its %COMMANDER_PATH% currently in use and check if it really is the c:\Programy\totalcmd path that I use? Strangely, settings (both WINCMD.INI and WCX_FTP.INI) also located in that folder are loaded properly.

Any suggestions how to repair it? I don't want to do a clean install as I don't really remember what have I customized in my options.

Dalai · Post by *Dalai » 2015-03-20, 16:24 UTC

Well, you should navigate to %COMMANDER_PATH%\Plugins\wcx\iso and check whether there is an iso.wcx file in there.

Regards
Dalai

lhalda · Post by *lhalda » 2015-03-20, 16:36 UTC

Dalai wrote:Well, you should navigate to %COMMANDER_PATH%\Plugins\wcx\iso and check whether there is an iso.wcx file in there.

Thanks for fast reply

Checked this, it is there. What surprised me is that %COMMANDER_PATH% is a global system variable that even Explorer finds

Anyways, this works as it should and still my TC doesn't see its plugins and DLLs.

Horst.Epp · Post by *Horst.Epp » 2015-03-20, 16:52 UTC

I guess you miss some of the required runtime libraries.
And new Windows installation misses a lot of the required old libraries.
Also the x64 TC of course needs x64 plugins and DLLs.
So ISO.WCX is not sufficient.

Dalai · Post by *Dalai » 2015-03-20, 17:03 UTC

2Horst.Epp
iso.wcx doesn't import any functions from external libraries, only kernel32.dll.

2lhalda
Please make sure you use 32 bit plugins for TC 32 bit and 64 bit plugins for TC 64 bit.

lhalda wrote:What surprised me is that %COMMANDER_PATH% is a global system variable that even Explorer finds

That can't be right. %COMMANDER_PATH% should only be available in TC itself and the processes it launches, but it should not be a global variable. Maybe that variable points to the wrong directory.

Regards
Dalai

lhalda · Post by *lhalda » 2015-03-20, 18:12 UTC

Horst.Epp, Dalai - thanks, the 32/64 bit mixup was the problem

Most of my setup is transferred from older 32bit Windows installation, including the plugins. Fortunately I installed 32bit + 64bit version, so I can choose which to run.

Is there any benefit to using 64bit TC?

Dalai wrote:
lhalda wrote:What surprised me is that %COMMANDER_PATH% is a global system variable that even Explorer finds
That can't be right. %COMMANDER_PATH% should only be available in TC itself and the processes it launches, but it should not be a global variable. Maybe that variable points to the wrong directory.

Nope, it points to a right directory. Works when TC is closed as well. I find it strange, as it is not present in my system's environment variables (neither system variables nor user variables) found in System Properties - Advanced - Environment Variables. It works nonetheless - when I go to path bar in Explorer, input %COMMANDER_PATH% and hit Enter, it shows the C:\Programy\totalcmd folder.

It doesn't matter though, I just find it interesting

Horst.Epp · Post by *Horst.Epp » 2015-03-20, 18:54 UTC

If you have the required plugins I prefer an x64 TC in a x64 OS.
This gives you full access to the real system32 dir for example.
Personaly I always install the combined version but use most of the time the x64 TC since all importand plugins I use are available as x64.
So I only use the x86 version for testing problems reported with TC x86.