Where are the latest Merge Modules for Mstudio VC++ Components?

[MRR]

Hi,

Does anybody know where I can find the latest merge modules for Measurement
Studio v. 6? I'm using the ComponentWorks++ tools. We recently switched our
Setup program from InstallShield for Visual C6 to InstallShield Express.
I've been trying to use the MSM merge modules that come with Measurement
Studio 6 without any luck. I keep getting build errors with National's
MSM's (MStudioUI.msm, MStudio3DGrph.msm), but not other MSM's. Are there
any newer updated MSM's available for downloading? I did look thru
National's web site, but haven't been able to find any downloads related to
the redistributable files.

Matt

[bilalD]

There are some dependency modules associated with these merge modules. I've attached a document that provides a list, this should also be in the help for Component works. Perhaps this is what was missing.

Hope this helps

[MRR]

> There are some dependency modules associated with these merge modules.
> I've attached a document that provides a list, this should also be in
> the help for Component works. Perhaps this is what was missing.

Thanks for the suggestion, but it doesn't help. The list is in the help &
I've doublechecked that several times. InstallShield Express is nice enough
to automatically select any required modules for me. Doesn't help though.
When I try to build with any National MSM included, I get, for example,

** Fatal Error: Error merging NI ComponentWorks 3D Graph 6.0 with module
ID C:\My
Documents\MySetups\MergeModules\MStudio3DGrph.msm

If I select them, one at a time. Express complains about each one with the
same error message except for th
e name of the offending National merge
module. Sounds like the National MSM's are invalid somehow. That's why I
want to try & download the latest modules from National's web site.

Has anyone used the merge modules that ship with MStudio 6.0 with success?
Or does anybody know where I can find newer ones to download?

[Elton Wells]

Are you using Measurement Studio 6.0 for Visual C++ 6.0 or Visual C++ .NET? Also, could you please provide a list of all of the Measurement Studio libraries that you're using in your project and all of the merge modules that you're using in your installer? Thanks.

- Elton

[MRR]

Hi Elton,

> Are you using Measurement Studio 6.0 for Visual C++ 6.0 or Visual C++
> NET?

MSVC++ 6.0 without a .NET

> Also, could you please provide a list of all of the Measurement
> Studio libraries that you're using in your project and all of the
> merge modules that you're using in your installer? Thanks.

We are primarily using CWUI.OCX & CW3DGRPH.OCX.

Here's the include list in my NiIncludes.h:

#include "NiGraph3DComponent.h"
#include "NiCommonComponent.h"
#include "NiMathComponent.h"
#include "NiUiComponent.h"
#include "NiUiCommonComponent.h"

Here the list of the National merge modules that I'm trying to use:

Glu32.msm
MStudioUi.msm
MStudio3dgrph.msm
NIPaths.msm
NIMesaDLLmsm
OpenGL32.msm

Here the Microsoft merge modules (included with Ins
tallShield Express):

COMCAT.msm
COMCTL32.msm
MFC42.msm
MSVCIRT.msm
MSVCRT.msm
MSVCP60.msm
OLEAUT32.msm

If I include any of the National MSM's I get the "Fatal Error: Error
merging..." message. It's a very poor error message from InstallShield as
there isn't an error number or any cause suggested.

Thanks for any help you can give me.

Matt Rhodes

[Elton Wells]

We've seen a similar to problem when building installers with the Visual Studio .NET installer projects, and it looks like it may be the same issue with InstallShield Express. Take a look at the Knowledge Base article Unable to Import Merge Module Error When Building Installer in Visual Studio .NET with Measurement S... and download the updated merge modules for OpenGL32.msm, MStudio3DGrph.msm, MStudioUi.msm, NiPaths.msm, NiReports.msm, and Glu32.msm that are at the bottom of the article. Please try these merge modules in your installer project and post a response about how they worked out. Thanks.

- Elton

[MRR]

Thanks Elton. That solved my build problems. If I put one of the old ones
back like Mstudio3dGrph.msm, then the error comes back too. I do have one
last question, though.

In trying them, I see that the newer MSM's generally have newer DLL's or
OCX's. I do notice that the cw3dgrph.ocx, though, is older than the one
Measurement Studio 6.0 installed on my system. The newer MSM includes a
version 6.0.588 cw3dgrph.ocx with a 7/27/01 datestamp, while Measurement
Studio put 6.0.589 on my system dated 8/1/01. Any idea why the newer
installer module doesn't include the newer OCX? After checking some more, I
see that my Measurement Studio 6 CD does the same thing with the 8/1/01 OCX
in the cab files for installation & a 7/27/01 OCX in th
e REDIST directory.
Is the difference in version numbers insignificant for some reason? Or
should I skip that MSM and manually include the 8/1/01 OCX ?

Thanks for the help.

Matt Rhodes,
Programmer,
Physical Acoustics Corp.

[Elton Wells]

I checked with a developer that worked on the installer at that time and this was his response:

"I checked our code base to see whether there were any changes made to the UI and 3d Graph controls between 7/27/01 and 8/1/01. No changes were made and the UI and 3d Graph controls with build number 6.0.588 and 6.0.599 are exactly the same in functionality. So you wouldn't lose any functionality by using the newer msm's."

- Elton

[MRR]

> I checked with a developer that worked on the installer at that time
> and this was his response:
>
> "I checked our code base to see whether there were any changes made to
> the UI and 3d Graph controls between 7/27/01 and 8/1/01. No changes
> were made and the UI and 3d Graph controls with build number 6.0.588
> and 6.0.599 are exactly the same in functionality. So you wouldn't
> lose any functionality by using the newer msm's."

Thanks Elton. I figured it was probably a insignificant difference, but
thought I'd better check before I used it.

In trying the new modules, I've run into another odd quirk with
NiMesaDLL.MSM which is not one of the updated MSM's. When I install on a
system without National previously
installed, InstallShield Express
complains that MESA.DLL is not found in D:\SHARED\MESA\ when D:\ is the
CD-ROM drive. It's a correct error message. After compiling my setup,
InstallShield Express puts MESA.DLL into D:\MESA not D:\SHARED\MESA. When I
put MESA.DLL into D:\SHARED\MESA, it works okay on a computer without
National installed on it. If I install on a computer with National already
installed, but no MESA.DLL, then InstallShield Express complains that it
cannot find MESA.DLL in D:\MESA\. I've looked for setting related to the
source directories on the CD in InstallShield Express, but can't find
anything. Seems like the info comes out of the MSM. For now I can make
sure it exists in both directories, but it seems like MESADLL.MSM is
confused about the source directory for MESA.DLL.

Matt Rhodes