On 8/8/2013 3:07 PM
> I am very new here and to Win7 (many years with XP).
> I have successfully installed Eudora 7.1.0.9 on my new Win7 laptop.
> It now takes a very long time to connect to my email server.
Do you mean that there is a long wait to connect to the first server
using SSL (or TLS), which may even cause a time-out at the server end,
but that subsequent repeated connection attempts,
so long as Eudora is not re-launched, then proceed without delay?
Those would be the very specific indications of a problem in Windows
(yes, folks, this is another Windows-caused problem)
which takes Windows an extremely long time
to simply return the memory address of a new "scratchpad" area
(a/k/a "heap"), which the "OpenSSL" library version within Eudora
uses to collect some "random data" (a/k/a "entropy")
for initializing SSL, which would not really securely encrypt anything
if it did not select a full 128 independent "random bits"
when creating an encryption key for each session.
The then current OpenSSL version called upon Windows 80 times
to simply provide the address of the next "heap," whereas
by the time Windows 7 appeared, Windows took nearly
an entire second of time to do that, even once,
so obviously it will then take way north of an entire minute
to get Windows to do it again, up to 80 times.
The value 80 is in a single byte of Eudora program file QCSSL.dll,
and by changing that single byte's value to 1 instead of 80,
that time is condensed into about one second instead.
There was naturally some concern about whether this would
adversely affect security at the same time, but the conclusion
of a lot of study by various people, including at
openssl.org,
is that so much other "entropy gathering" is performed
to initialize the OpenSSL library that all the scanning of
multiple "heaps" was unnecessary "overkill" -- even Bruce Schneier,
a Eudora user as well as a well known author in the field of Cryptography,
asked another Eudora forum about this same problem, and eventually
declared that it was probably all his fault, for so strongly emphasizing
the "original shuffling of the cards" before dealing hands
that OpenSSL went somewhat overboard there, which wouldn't
have been a problem if Windows itself hadn't made it so much worse
by taking so long just to find the next "memory heap" ;-)
Finding the single byte to change, within an entire program file,
was accomplished by a brilliant anonymous Eudora forum contributor
known only as "JCF," who matched the "open source" programs
from OpenSSL.org to the compiled program file which comes with Eudora,
and found the exact location of that one byte needing change.
> I KNOW this has been discussed before, but the solutions suggested
> either don't work (run in compatibility mode), or no longer seem to exist
> [downloading a copy of Eudora program file QCSSL.DLL
> which has a single byte changed from the original file]
>
> Is there a new location for that file?
Do NOT run Eudora in "compatibilty mode" -- it does not help,
and some reports indicate that this could cause other problems.
"Patched" program file QCSSL.dll remained downloadable
from Eudora forums via a direct URL for some while
after the Eudora forums lost all page formatting,
but even that direct URL to the original "attachment"
(to a forum post) seemed to stop working after a while.
You can, however, get yourself a "hex editor" for binary files,
then change the single byte yourself.
You can get a good, free hex editor from:
<
http://www.softcircuits.com/cygnus/fe/>
The size of program file QCSSL.dll for Eudora version 7.1.0.9
should be exactly 507904 bytes (7C000 in hexadecimal).
Make a COPY of that file, and perform the following on the copy:
Using your hex editor, verify that starting at hex location 283F3
you find these consecutive (hex) byte values: BB 50 00 00 00
Change the byte whose value was 50 to 01,
without changing the file length (i.e. you want to
overwrite that single byte value, rather than insert a byte),
so that location 283F3 ends up containing BB 01 00 00 00,
then you can save the changed new file.
As a final confirmation of correct patching,
you may open a command window (cmd.exe)
and use a built-in Windows file compare command:
fc/b QCSSL.dll.original QCSSL.dll.patched
The correct complete output of that command should be:
Comparing files QCSSL.dll.original and QCSSL.dll.patched
000283F4: 50 01
If this was successful, rename the files so that your patched file
ends up being the new QCSSL.dll, then enjoy faster Eudora launches.
And keep this in mind:
"There is more to life than simply increasing its speed" [M. K. Gandhi]
--