Re: libeay32.dll 3906

PSPad v4.5.7 (2450) running at Win7 Professional (Spanish).
Since I've updated my free avast! antivirus, PSPad can't find teh ordinal 3906 in LIBEAY32.dll.
I've download your sugested package (libeay32.dll, libssl32.dll and msvcr71.dll) and uncompressed in my PSPad folder and it has not solved the issue.
On the other hand, I think this only affects SSL connections. So, I can continue using PSPad in 'local mode'?

Thanks for reading.
Jesus

It has influence of FTPS only. Standard FTP connection isn't touched

I checked it. There were no changes in PSPad sources.
PSPad doesn't load the library during start, it loads it dynamically when FTP client require SSL/TLS connection.
I have tested PSPad witřh dependancy walker (http://www.dependencywalker.com/) and there is no Libeay32.dll what should be loaded during PSPad start.

I really don't understand why the error occurs.

Thanks, PSPad, for your interest shown.
Continue to report if find a solution.

Manfred has same problem and he uses Avast too:
forum.pspad.com

SOLVED?

I disabled the WSH option in the Programs Settings > System Integration and the error message no longer appears.

I hope not to need that option.

Jesus

There is problem with Avast, not with PSPad.
You can add PSPad to Avast exclusions and wait for the Avast update.
The problem was confirmed from the Avast support.

Edited 1 time(s). Last edit at 2013-10-21 17:23 by pspad.

PSPad v. 4.5.7 (2450) on Win XP SP3:

I have been getting this same error, so I uninstalled and re-installed PSPad, but the error persisted. The only way I was able to prevent it was to turn off Integrated scripting support (WSH) in Settings/Program Settings/System integration.

I don't understand the post indicating that this is an Avast problem rather than a PSPad problem. The Windows installer does put a libeay32.dll file (version 0.9.8.7) in the Program Files\PSPad editor directory, and the PSPad.exe file does seem to use that DLL. Avast does not detect any problems in the files in this directory, so the DLL is not being moved anywhere.

--
Scott Inrig
Ottawa, Canada

I got answer from Avast Support team.
They wrote me it should be fixed next week.

I suggest add PSPad into Avast exceptions.

inrig:

PSPad v. 4.5.7 (2450) on Win XP SP3:
I don't understand the post indicating that this is an Avast problem rather than a PSPad problem. The Windows installer does put a libeay32.dll file (version 0.9.8.7) in the Program Files\PSPad editor directory, and the PSPad.exe file does seem to use that DLL. Avast does not detect any problems in the files in this directory, so the DLL is not being moved anywhere.

PSPad uses this library for FTP transfer if you check SSL/TLS in FTP connection settings. This library is loaded dynamically in this case only. It's not used for any other usage.

This problem occurs even there is no Libeay32.DLL in PSPad folder
Problem is when WSH is initialized.
This problem occurs with Avast only, nno other antivirus causes it
This problem occurs with different PSPad versions
Avast support confirmed this is a problem of Avast