OK.
But I was speaking about the code in MFCMAPI. We could do it manually using fixmapi.exe. In MFCMAPI, FixMAPI or fixmapi.exe isn't used. So I was saying about checking if FGetComponentPath is present in mapi32.dll which was replaced by other email client. If it fails then load mapistub.dll and then check for FGetComponentPath.
What is done in MFCMAPI is mapi32.dll is loaded. If it fails then load mapistub.dll and use FGetComponentPath.
In such cases mapi32.dll is loaded even if it is replaced by other email client, mapistub.dll isn't loaded and FGetComponentPath fails.
I got fixmapi.exe in C:\WINDOWS\system32 and C:\WINDOWS\system32\dllcache after searching it in the drive where windows is installed.
But I was speaking about the code in MFCMAPI. We could do it manually using fixmapi.exe. In MFCMAPI, FixMAPI or fixmapi.exe isn't used. So I was saying about checking if FGetComponentPath is present in mapi32.dll which was replaced by other email client. If it fails then load mapistub.dll and then check for FGetComponentPath.
What is done in MFCMAPI is mapi32.dll is loaded. If it fails then load mapistub.dll and use FGetComponentPath.
In such cases mapi32.dll is loaded even if it is replaced by other email client, mapistub.dll isn't loaded and FGetComponentPath fails.
I got fixmapi.exe in C:\WINDOWS\system32 and C:\WINDOWS\system32\dllcache after searching it in the drive where windows is installed.