Eudora DLL Swapping Restrictions Eudora User Manual
251
QUALCOMM Incorporated
7Exit Windows.
Once Eudora’s MAPI DLLs get into the wrong “state” with respect to Eudora, you cannot
correct the state mismatch until all MAPI client applications unlo ad the MAPI DLLs and
Windows is able to unlock the DLL file. Since the MAPI DLLs are shared by multiple MAPI
client applications, Windows does not unlock the MAPI DLL file until the last MAPI client
application is shut down. Therefore, to force all MAPI client applications t o unload the
DLLs, you must shutdown all MAPI client applications.
Important. When running 16-bit MAPI client applications under Windows NT, then Eudora
cannot detect the lock placed on the MAPI DLLs by Windows unless the SHARE program
is running. This means that Eudora can inadvertently perform the DLL s wap and/or
unswap procedures while the MAPI DLL is loaded into memory. This almost always
causes Windows to become unstable and can lead to crashes in MAPI cl ient applications
as well as in Windows itself.
Note. If you run 16-bit MAPI client applications under Windows NT, then you should
always run the SHARE program.
The good news is that Windows 95/98 implements the SHARE functionality wi thout
requiring you to explicitly run the SHARE program. By default, Windo ws NT only imple-
ments the SHARE functionality for 32-bit applications. If you are running a 16-bit applica-
tion under Windows NT, then you must run the SHARE program explicitly.