View Full Version : merge module problem
12-17-1999, 12:00 AM
12-18-1999, 12:00 AM
In article <385A52B2.55C658C5@cost.se>, Luciana Soligo <email@example.com> wrote:
> I tried that and it didn't work.
> I tried all sort off things , including installing ISWI again!!!
> I even tried adding only my merge module , without adding the dependent ones
> (some MS merge modules), since i rememeber I got an error the first time I
> my project and I forgot to include them. Well, now I could build successfully,
> because somehow is ignoring my merge module.
> All this problem started when I installed the beta 1.1 and then decided to
> uninstall it
> and used the 1.03 instead.
> I'm getting desperate here, I 've already spent 2 whole days with this
> Any hint????
First, try opening your merge module project and make certain that there is no
condition on the components within, and that those components have files.
Then, build the merge module and make sure it gets copied to the i386 folder.
Then, open your main project, right-click on the merge module and delete it.
Re-add your merge module and rebuild and re-run.
> Jim Kang wrote:
> > In article <385864F3.EEEA4747@cost.se>, Luciana Soligo <firstname.lastname@example.org>
> > wrote:
> > > Hi,
> > >
> > > Looks like my merge module is not getting installed!
> > > It used to work before, but I can't find out what has changed for it not
> > > to work now.
> > > I don't get any building error, and the merge module seemed to be there,
> > > when you looked at the associated feature in the IDE, however, I think I
> > > remember seeing some informatoion about the merge modules when building
> > > my application before, and now they are just ignored.
> > >
> > > I also tried creating a feature just for the MM (no other components),
> > > and when I
> > > run the installation the space required for the feature is 0!
> > >
> > > What could be going on??
> > Is the cab file for the merge module being built?
> > Try *deleting* the merge module by right-clicking on it and selecting
> > "delete." Go to the merge modules view under the setup design view and
> > any other instances of it. Then, add it to your feature again and try
> > building.
> > ----
> > Jim Kang - Developer Support Engineer
> > InstallShield Software Corporation
> Content-Type: text/x-vcard; charset=us-ascii;
> Content-Transfer-Encoding: 7bit
> Content-Description: Card for Luciana Soligo
> Content-Disposition: attachment;
> org:Entegrity Solutions
> title:Software Engineer
> fn:Luciana Soligo
Jim Kang - Developer Support Engineer
InstallShield Software Corporation
11-29-2000, 12:00 AM
We don't have a problem with Windows 2000 because the file is a new enough
version. The problem occurs on NT4, and it is only when the service pack at
a certain level.
"Robert M. Dickau"
installshield.com> wrote in message news:email@example.com...
> If this is happening on Windows 2000, it might be the case that MFC42U is
> "protected" file, in which case only Microsoft service packs (and the
> can update the file.
> "Jay Black" <firstname.lastname@example.org> wrote in message
> > Hello all,
> > I'm trying to install some merge modules with my product. The merge
> > I'm trying to include are the "MFCDLL Shared Library - Retail Version"
> > "Microsoft (R) C Runtime Library." On a machine that these files do not
> > exist there are not any problems. However, if a machine has an older
> > of mfc42u.dll (file associated with MFCDLL module) it does not get
> > Is there any around this? I am using ISWI 1.1 and installing on mostly
> > machines.
> > Thanks
12-01-2000, 12:00 AM
Do you see any reference to MFC42U.dll in the installation log file? For
example, I get:
File: C:\WINNT\System32\mfc42u.dll; Won't Overwrite; Existing file is of
an equal version
"Jay Black" <email@example.com> wrote in message
> We don't have a problem with Windows 2000 because the file is a new enough
> version. The problem occurs on NT4, and it is only when the service pack
> a certain level.
> "Robert M. Dickau"
> installshield.com> wrote in message news:firstname.lastname@example.org...
> > If this is happening on Windows 2000, it might be the case that MFC42U
> > "protected" file, in which case only Microsoft service packs (and the
> > can update the file.
> > "Jay Black" <email@example.com> wrote in message
> > > Hello all,
> > >
> > > I'm trying to install some merge modules with my product. The merge
> > modules
> > > I'm trying to include are the "MFCDLL Shared Library - Retail Version"
> > > "Microsoft (R) C Runtime Library." On a machine that these files do
> > > exist there are not any problems. However, if a machine has an older
> > version
> > > of mfc42u.dll (file associated with MFCDLL module) it does not get
> > replaced.
> > > Is there any around this? I am using ISWI 1.1 and installing on mostly
> > Win2K
> > > machines.
> > >
> > > Thanks
11-12-2001, 09:03 AM
How do I associate a merge module with a specific feature? I would like the
option to not install files belonging to the msm (SQL Server merge modules,
in my case) if the user chooses to do so. I created a feature called "MSDE"
and associated all the modules to it, but all the files install even when I
do not select that feature.
What am I missing? I'm using IS Express 3.0.
11-12-2001, 04:23 PM
This could be a problem with the way the Merge Modules are authored. If the msm is a simple file that has only the File Table populated and no Custom Actions specified, then the files will be installed only if that feature is selected. Unfortunately Custom Actions are not associated with features are streamed in to the Execute and UI sequences regardless. So at runtime, these Custom Actions are most probably getting triggered. Best way to find out would be to open the msm with a tool like ORCA (comes with the Windows Installer SDK - Free download) and see if this is the case.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.