Then everything will work, but it will be fine mess by my standards. Furtunately 32-bit version does not have zlibwapi.dll, so we can move it to %commander_path%.
We can put another copy of 64-bit dlls into plugin directory, but it also won't help, because it won't find zlibwapi.dll there. So it's clear where to put which set of dlls.īut then 64-bit SFTP won't work, because plugin uses standard library directory search order and it does not include %commander_path%\64. 64-bit TC will look there too, but in addition also in 64 subdirectory. So what to do about it? If we skip Windows and System directories, because we don't want to put anything there (or can't in case of portable TC), it only leaves us %commander_path% where 32-bit TC will look for OpenSSL dlls. Of course, because the only copy is in SFTP plugin directory and TC won't look there for internal FTP use. Expected result: 64-bit TC will work, while 32-bit will complain about missing OpenSSL dlls. Pooh.Īs this is one of the plugins which are used every day, time will tell pretty quickly whether both plugin flavours will do their job equally well. I assume I had not copied all 4 DLLs to %COMMANDER_PATH%, because the original 32-bit curl DLLs are only libea圓2.dll and libssh2.dll, but the 64-bit DLL list seems to be all 4 files, libea圓2.dll, libssh2.dll, sslea圓2.dll and zlibwapi.dll.Īnyway, after moving all 4 files to %COMMANDER_PATH% and launching "Secure FTP" and selecting a connection, this connection worked.
And it is the only location which works for this system. Though I had tried before putting the 64-bit DLLs provided by Christian here, it had not worked.
Trying to establish a connection just gives me the well-known error message which tells me to install libea圓2 and libssh2.dll to the plugin folder, %commander_path% or another folder listed in the %PATH% variable. This definitely does not work on this system for whichever reason. Thank you for your helpful input and advice.
0 kommentar(er)
