hpxjeff
Posts: 2
Joined: Wed Jan 11, 2006 2:21 pm
Location: Melb. Australia

MS Merge module going to root dir in Win98

I have a requirement to install MFC71.dll & MSVCR71.dll merge modules, but find that in Win98SE the DLL files end up in the root directory instead of the APPDIR (as defined). All is OK with Win2k & Win2003.

MFC71 ends up installing to C:\ on a 98 PC whilst MSVCR71 ends up installed in both C:\ & D:\ (there are two drives on the PC, if there were more I guess it would install to all??)

Googling for info reveals quite a few threads in other forums. Many of which claim a bug in the msm because you "cannot" change the destination directory from APPDIR to something else. From my readings of comments in these forums by apparently knowledgable people in positions that you'd expect to know, I tend to believe their comments that MSoft have dictated APPDIR because they want you to put dependancies in APPDIR not in Sys32 where other people can break each others applications. (also an MS logo requirement)

Using AI & having the msm installing the files to APPDIR is fine for me but having them end up in C:\ (in the case of MFC71) or C:\ & D:\ (in the case of MSVCR71) when on a 98 machine wont leave the app working on the 98 system

Do you know of the problem & work arounds. (It would be kind-a-nice to use the merge module instead of dumping the DLL files straight in the directory, which is of course one solution (non MS approved)

I did see one other comment in the other forum regarding 98 putting files in the root directory so I guess it isn't an AI problem

JJ

MSM files involved are
VC_User_CRT71_RTL_X86_---.msm
VC_User_MFC71_RTL_X86_---.msm
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Hi,

You are right, this issue is related to the way Microsoft has build these merge modules.

I also found the following information:
The merge modules for Visual C++ .NET 2003 (VC 7.1) runtime libraries are not
retargetable like they were in Visual C++ .NET 2002 (VC 7.0). As a result they
install to the wrong directory (on some machines), e.g. the root of drive C:. The
modules are also using the wrong schema (schema 100).
One workaround would be the one you have already mentioned: do not use the merge
modules - just include the DLLs in question in your package. The merge modules do not
perform additional operations, they just install those DLL files (you can tell this by examining the MSMs with Orca).

Another workaround would be to create a Property Set with Formatted Custom Action scheduled on the "Begin" stage (in the "InstallExecuteSequence"). Set the following properties for this Custom Action:
- Property Name : TARGETDIR
- Formatted Text : [APPDIR] (or the directory where you want to install the DLLs)

Note that I have tested this only for "VC_User_MFC71_RTL_X86_---.msm".

Regards,
Denis
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/
dmh_nrltd
Posts: 20
Joined: Mon Dec 12, 2005 5:35 pm

Hi

We've experienced the same issue. Microsoft have confirmed this as a bug, detailed in the following article:
There is also a patch fix described in the article - a set of replacement MSM modules, which can be obtained from Microsoft Support. We've obtained the fix and used it successfully in product installs.

Hope this helps!

David.

Return to “Common Problems”