On Friday, September 29, 2000, 9:34:00 AM, bill wrote:
> One other MAPI occurrence. I installed the tbmapi.dll through the
> /installmapi switch earlier this month. It installed itself as
> mapi32.dll. Fine. When the revised tbmapi.dll was released a
> couple of days ago I installed it using the same routine.
> However, MAPI still did not work with Agent. Upon checking the
> mapi32.dll it had *not* been overwritten by the new version of
> tbmapi.dll. It was still the old original version. Opened a DOS
> window and tried to copy tbmapi over mapi32. I got a 'sharing
> violation'. Rebooting to DOS achieved the required result.
This happens when, among other possibilities, a program tries to
call the dll and fails (hangs). The dll files remains open and thus
couldn't be overwritten.
> I wonder if any other users are having a problem with MAPI because
> the old tbmapi is not being overwritten, or perhaps it is just a
> quirk of this machine.
This may happen to anybody, and it should be added to the list of
many quirks in TB's MAPI installation that RIT needs to work out
before its official release. Generally speaking, I think it is in
itself a bad idea trying to overwrite a dll file in the directories,
and RIT would be wise to avoid this if it's at all possible. But
sometimes MS just leaves you no choice.
--
Best regards,
Ming-Li
The Bat! 1.47 Beta/5 | Win2k SP1
--
--------------------------------------------------------------
View the TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBBETA, double-click HERE:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : archive@jab.org
