>>Are you telling me that your executable is on the Desktop?
It looks like it, in a folder "HttpsTestv1.2"
>>And you have set the SSL directory to where your executable is running from?
Correct.
>>And where is that then?
C:\Users\hjhu\Desktop\HttpsTestv1.2\
>>And where did you copy your SSL files?
The zip file pointed to in previous post only contains 3 files.
HttpsTestXE4.exe
ssleay32.dll
libeay32.dll
>>There are clearly NOT at "ExtractFilePath(Application.ExeName)" wherever that is.
They clearly are...
>>But: Stop using the 'executable' directory to put things in. This may be anywhere.
And what is wrong with that? Are you familiar with "ExtractFilePath(Application.ExeName)"?
I will give that a try
It looks like it, in a folder "HttpsTestv1.2"
>>And you have set the SSL directory to where your executable is running from?
Correct.
>>And where is that then?
C:\Users\hjhu\Desktop\HttpsTestv1.2\
>>And where did you copy your SSL files?
The zip file pointed to in previous post only contains 3 files.
HttpsTestXE4.exe
ssleay32.dll
libeay32.dll
>>There are clearly NOT at "ExtractFilePath(Application.ExeName)" wherever that is.
They clearly are...
>>But: Stop using the 'executable' directory to put things in. This may be anywhere.
And what is wrong with that? Are you familiar with "ExtractFilePath(Application.ExeName)"?
(05-09-2018, 06:19 PM)rlebeau Wrote: Usually, when the DLLs themselves fail to load into memory, it is because they likely have dependencies on additional DLLs that are missing on the user's system, such as Microsoft's VC++ runtime DLLs. Try using the OpenSSL DLLs at http://indy.fulgan.com/SSL/, they don't have any extra dependencies (only to each other).Thanks Remy.
I will give that a try