Discussion:
Eudora troubles after in-place upgrade from Windows 7 to 10
(too old to reply)
John Foust
2019-10-10 17:58:42 UTC
Permalink
Eudora 7.1.0.9 had been working reasonably well for me under Windows 7 Pro x64 for many years. Last week I performed an in-place upgrade to Windows 10.

The first problem was that the "find" window was very, very wide. Even with the main window stretched across two monitors, I couldn't resize it as it wouldn't budge from any corner or side.

I found a way to reset it. If I closed Eudora, renamed the Eudora.INI and restarted, then closed it and moved the old INI back, the window was back to a normal size. Does that mean the window size and resizable-flag is in the registry somewhere?

But in the last two days, I'm seeing a new error. Most often it happens as I type or edit the body text inside a new email or reply. The first hint is that typing just makes whitespace. Sometimes it just seems to advance the cursor over existing text like overstrike mode.

At this point Eudora will crash. The exceptions log says:

Eudora.exe caused an EXCEPTION_ACCESS_VIOLATION in module
MFC71.DLL at 0023:7C158431, Ordinal2234()+0015 byte(s)

and the last bit of the call stack was:

0023:7C16E1B8 (0x00531134 0x00000000 0x00000203 0x00000000) MFC71.DLL, Ordinal1209()+0059 byte(s)
0023:7C16E1F6 (0x00531134 0x00000000 0x00000203 0x00000000) MFC71.DLL, Ordinal1209()+0121 byte(s)
0023:745848EB (0x7C16E1BD 0x00000000 0x00531134 0x00000000) USER32.dll, AddClipboardFormatListener()+0075 byte(s)
0023:7456613C (0x7C16E1BD 0x00000000 0x00000000 0x00000000) USER32.dll, CallWindowProcW()+2860 byte(s)
0023:7456528E (0x00000001 0x00000000 0x00756920 0x00000000) USER32.dll, DispatchMessageW()+0558 byte(s)
0023:74569291 (0x004007EA 0x00000000 0x00756918 0x00000000) USER32.dll, IsDialogMessageW()+0257 byte(s)
0023:7458102E (0x004007EA 0x00000000 0x00756918 0x00000000) USER32.dll, IsDialogMessage()+0078 byte(s)
0023:7C153E61 (0x00000000 0x00000000 0x00000000 0x00000000) MFC71.DLL, Ordinal3920()+0026 byte(s)

There's little guarantee that my text will be saved at this point. Very annoying.

My MFC71.DLL in C:\Windows\SysWOW64 is version 7.10.3077.0, dated 10/17/2003.

My Eudora is installed at E:\Eudora.

I saw one google result that suggested moving to C:\Users\(name)\AppData\Roaming\Qualcomm\Eudora and making a registry change. Any truth to that?
John Foust
2019-11-11 22:28:23 UTC
Permalink
Post by John Foust
The first problem was that the "find" window was very, very wide. Even with the main window stretched across two monitors, I couldn't resize it as it wouldn't budge from any corner or side.
I found a way to reset it. If I closed Eudora, renamed the Eudora.INI and restarted, then closed it and moved the old INI back, the window was back to a normal size.
This method did not work reliably.

I later discovered that if I did not set any "compatibility mode" on the launch icon for Eudora, then this Find Messages window problem went away.
Post by John Foust
But in the last two days, I'm seeing a new error. Most often it happens as I type or edit the body text inside a new email or reply.
I have not yet found a resolution for this.
John Foust
2020-07-08 16:24:33 UTC
Permalink
Post by John Foust
But in the last two days, I'm seeing a new error. Most often it happens as I type or edit the body text inside a new email or reply.
I have not yet found a resolution for this. But in the last two days, I'm seeing a new error. Most often it happens as I type or edit the body text inside a new email or reply. The first hint is that typing just makes whitespace. Sometimes it just seems to advance the cursor over existing text like overstrike mode. At this point Eudora will crash.
An update. I still have not found a resolution for this text editing crash. It's quite predictable. It's made Eudora 7.1.0.9 unusable on Windows 10 x64.

It can be reproduced by making any significant changes to the quoted text in a "reply all" or even in re-editing an email I started, closed, and then re-opened before queuing for sending.

Is no one else seeing this bug? Is it a DLL incompatibility? A font?
DaveH2
2020-07-09 11:44:55 UTC
Permalink
Post by John Foust
Eudora 7.1.0.9 had been working reasonably well for me under Windows 7 Pro x64 for many years. Last week I performed an in-place upgrade to Windows 10.
The first problem was that the "find" window was very, very wide. Even with the main window stretched across two monitors, I couldn't resize it as it wouldn't budge from any corner or side.
I found a way to reset it. If I closed Eudora, renamed the Eudora.INI and restarted, then closed it and moved the old INI back, the window was back to a normal size. Does that mean the window size and resizable-flag is in the registry somewhere?
But in the last two days, I'm seeing a new error. Most often it happens as I type or edit the body text inside a new email or reply. The first hint is that typing just makes whitespace. Sometimes it just seems to advance the cursor over existing text like overstrike mode.
Eudora.exe caused an EXCEPTION_ACCESS_VIOLATION in module
MFC71.DLL at 0023:7C158431, Ordinal2234()+0015 byte(s)
0023:7C16E1B8 (0x00531134 0x00000000 0x00000203 0x00000000) MFC71.DLL, Ordinal1209()+0059 byte(s)
0023:7C16E1F6 (0x00531134 0x00000000 0x00000203 0x00000000) MFC71.DLL, Ordinal1209()+0121 byte(s)
0023:745848EB (0x7C16E1BD 0x00000000 0x00531134 0x00000000) USER32.dll, AddClipboardFormatListener()+0075 byte(s)
0023:7456613C (0x7C16E1BD 0x00000000 0x00000000 0x00000000) USER32.dll, CallWindowProcW()+2860 byte(s)
0023:7456528E (0x00000001 0x00000000 0x00756920 0x00000000) USER32.dll, DispatchMessageW()+0558 byte(s)
0023:74569291 (0x004007EA 0x00000000 0x00756918 0x00000000) USER32.dll, IsDialogMessageW()+0257 byte(s)
0023:7458102E (0x004007EA 0x00000000 0x00756918 0x00000000) USER32.dll, IsDialogMessage()+0078 byte(s)
0023:7C153E61 (0x00000000 0x00000000 0x00000000 0x00000000) MFC71.DLL, Ordinal3920()+0026 byte(s)
There's little guarantee that my text will be saved at this point. Very annoying.
My MFC71.DLL in C:\Windows\SysWOW64 is version 7.10.3077.0, dated 10/17/2003.
My Eudora is installed at E:\Eudora.
I saw one google result that suggested moving to C:\Users\(name)\AppData\Roaming\Qualcomm\Eudora and making a registry change. Any truth to that?
Hi John.
FWIW I'm using Eudora 7.1 on 64 bit Windows 10 version 2004 with no problems at all, so it can work! My MFC71.DLL is the same version as yours (7.10.3077.0), although the date stamp is later (17/03/2015).
Do the crashes still happen with a "clean" eudora.ini? I assume you've tried that. If they do it can't be anything to do with any changes to Eudora's default settings. AFAIK Eudora doesn't really use the system registry at all, it's only in there to register it as an e-mail client and for the installed programs list, no Eudora settings are stored there.
Cheers, Dave.

Loading...