others) launching before the user even selects the feature to which the MM
I see MDAC running during the UI phase of the installation prior to getting
to the setup dialogs. I have some features that do not require the MDAC MM,
nor do I want MDAC installed on a customer machine if they don't need it
especially since it's irreversible.
Since MMs are components that are tied to features, then this behavior
should not occur. When I opened the MDAC26.MSM file as an ISWI project, I
found that there are custom actions in the ModuleInstallUISequence and the
ModuleInstallExecuteSequence tables which are then merged with the
InstallUISequence and InstallExecuteSequence tables, respectively, of the
I think the problem lies with the CAs in the UI-related tables, so I'm
modifying this MM (and the DCOM95 MM since it's built the same way) by
taking the CAs out of the ModuleInstallUISequence table. I haven't had any
success yet; MDAC won't launch now in the Execute sequence.
Has anyone come across this same thing?