That was in fact the problem, thanks! On Sat, Mar 22, 2008 at 11:42 AM, Bob Arnson <[EMAIL PROTECTED]> wrote: > Geoff Finger wrote: > > In the ModuleInstallExecuteSequence table of the msm files we have rows > such as: > > > > Action: RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9 > > Sequence: > > BaseAction: CostInitialize > > After: 0 > > Condition: INSTALLCONDITION=1 > > > > Does the ModuleInstallExecuteSequence table in the .msm also have a row > for CostInitialize? Mergemod.dll requires merge modules to be > "self-contained" in how they schedule actions. See the > ModuleInstallExecuteSequence table doc in the MSI SDK for an explanation > -- even if it's a lame one.<g> Try using smoke.exe to run validation on > the merge module; it might provide details about problems that lead to a > fix. > > -- > sig://boB > http://joyofsetup.com/ > > >
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
