32 and 64-bit TC in same directory and OpenSSL dlls

Sob · Post by *Sob » 2011-09-25, 22:15 UTC

It does. Tested with both your dlls and my self-compiled dlls.

Only "what about plugins?" question remains unanswered.

Samuel · Post by *Samuel » 2011-09-25, 22:19 UTC

Sob wrote:Only "what about plugins?" question remains unanswered.

If the plugins need same named external dlls for 32 and 64 bit, they could also create a 64 bit folder inside the plugin directory.

Sob · Post by *Sob » 2011-09-25, 22:33 UTC

If the plugin loads all dlls itself, then yes. But if plugin loads only some dlls and they load others, then I don't think it will work very well.

You can see the behaviour with Ghisler's own sftplug. If you use his dlls an put them into plugin folder, then it will fail, because libssh2.dll loads zlibwapi.dll and does not look for it in the same directory. And if you view libssh2.dll as general third-party dll that you can't modify (not really true in this case), then it may be a problem. I don't know if there's any API to modify PATH for current process, that would be possible solution.

Flint · Post by *Flint » 2011-09-26, 19:53 UTC

ghisler(Author) wrote:Could someone try whether OpenSSL works with the 64-bit files in subdir "64" under the Totalcmd directory, please? This should work now with beta 2.

Seems to work fine. Tested with the libraries from
https://plugins.ghisler.com/addons/openssl+ssh64.zip

Post by *ghisler(Author) » 2011-09-27, 23:35 UTC

Thanks for testing!

karlchen · Post by *karlchen » 2011-10-01, 21:34 UTC

Hello, Christian.

Sorry to say so, but I cannot confirm that SFTP v1.1 64-bit works fine if I put the 64-bit DLLs
+ libeay32.dll
+ libssh2.dll
+ ssleay32.dll
+ zlibwapi.dll
in the folder %COMMANDER_PATH%\64.
It works correctly only provided they are stored in the folder %COMMANDER_PATH%.

For more details, please, cf. => here <=

Total Commander 8.0ß3 64-bit
SFTP v1.1 plus the DLLs provided by you
Server 2008 R2

Cheers,
Karl

Post by *ghisler(Author) » 2011-10-02, 15:07 UTC

Sorry, the sftp plugin has NOT been changed to look for the dlls in '64'. It expects them in the TC directory. The fix was only for the internal FTPS client.

MVV · Post by *MVV » 2011-10-02, 15:09 UTC

Christian, maybe it is possible to add 64 folder to PATH envvar? So plugins will search DLLs in it.

Post by *ghisler(Author) » 2011-10-02, 16:18 UTC

The plugin still seems to do that. Try putting them in the 64-bit system32 directory.

MVV · Post by *MVV » 2011-10-02, 18:05 UTC

I think users of portable TC won't do that.

Hm-m, it is interesting to try use batch or script that will add that folder to PATH envvar and then start TC - will plugins work this way? If so, it will solve a problem. I can't test it since I have no plugins that require OpenSSL.

Post by *ghisler(Author) » 2011-10-03, 21:15 UTC

For portable TC, you will have to put them in separate subdirs for the moment.

petergus · Post by *petergus » 2011-11-04, 02:00 UTC

ghisler(Author) wrote:Could someone try whether OpenSSL works with the 64-bit files in subdir "64" under the Totalcmd directory, please? This should work now with beta 2.

What is the solution for tcmatch if I don't want separate configuration files?
What about just adding a new name in wincmd.ini: tcmatch64

wlnx · Post by *wlnx » 2012-09-08, 15:27 UTC

Hello. Maybe, %COMMANDER_PATH%\x86 and %COMMANDER_PATH%\x64 folders for generally available resources (such as %COMMANDER_PATH%\*.exe and %COMMANDER_PATH%\*.dll) will help us? =)
Just let totalcmd search resources in x86 and totalcmd64 in x64... Plugins - yeah, they can create there own x86 and x64 folders inside their location. =))
Pleeease... I use portable installation and have already had problems with OpenSSL.