Software Deployment

Hi TIA,

Did you use the "Convert registry entries into advertising info" option during capture?

The target file 'asycfilt.dll' is installed in '[SystemFolder]\' by two different components on an SFN system: 'asycfilt.dll' and 'Global_System_OLEAUT32.8C0C59A0_7DC8_11D2_B95D_006097C4DE24'. This breaks component reference counting. http://dartools/iceman/ice30.html File File asycfilt.dll

Evaluation: ICE30
[font="Courier New"]i went to the componets and found that only the asycfilt.dll componet was there and the Global_system componet seems to be a merge modual.
Just remove the asycfilt.dll component and you should be safe as they are installed into the same directory.

When you capture this application you got an question if you wanted to use the merge module for the asycfilt.dll instead of regular file.
It seems that you got this "duplicate", one in the asycfilt.dll component and in the Global_System_OLEAUT32.8C0C59A0_7DC8_11D2_B95D_006097C4DE24 merge module component.

This is weird as you shouldn't get the asycfilt.dll file into the asycfilt.dll component. Wise some times behave strange when it includes merge modules and just create empty components instead.

Reg key Global_Controls_MSMASK32OCX_r15.7EBEDD2D_AA66_11D2_B980_006097C4DE24 is used in an unsupported way. This key need not be written as it already exists in the system. http://dartools/iceman/ice33.html Registry Registry Global_Controls_MSMASK32OCX_r15.7EBEDD2D_AA66_11D2_B980_006097C4DE24

Evaluation: ICE33
I wouldn't fix errors/warnings in merge modules if they do not prevent the MSI from installing, self-healing or removal. So just leave this alone.


Reg key registry459 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. http://dartools/iceman/ice33.html Registry Registry registry459

Evaluation: ICE33
This may depends if you used the options I posted on top.
Guessing this registry entry is a copy of a com component used by a merge module instead.
Verify that the ProgId isn't added by the merge module into the ProgId table and if so remove this registry entry.
If this registry is part of a com component registration registry then depending on the registry entry/value may not be supported by the ProgId table and is therefore added to the Registry table. Please post the whole registry row.

Reg key registry460 is used in an unsupported way. ProgId - CLSID associations should be registered via the ProgId and Class tables. This entry may overwrite a value created through those tables. http://dartools/iceman/ice33.html Registry Registry registry460

Evaluation: ICE33
This may depends if you used the options I posted on top. Please post the whole registry row.

Reg key registry10 is used in an unsupported way. CLSID contexts should be registered via the Class table. This entry may overwrite a value created through that table. http://dartools/iceman/ice33.html Registry Registry registry10

Evaluation: ICE33
This may depends if you used the options I posted on top.
Guessing this registry entry is a copy of a com component used by a merge module instead.
Verify that the Class isn't added by the merge module into the Class table and if so remove this registry entry.
If this registry is part of a com component registration registry then depending on the registry entry/value may not be supported by the Class table and is therefore added to the Registry table. Please post the whole registry row.

Reg key Global_System_STDOLE_r3.8C0C59A0_7DC8_11D2_B95D_006097C4DE24 is used in an unsupported way. Typelib HELPDIR should be registered via the Typelib table. This entry may overwrite a value created through that table. http://dartools/iceman/ice33.html Registry Registry Global_System_STDOLE_r3.8C0C59A0_7DC8_11D2_B95D_006097C4DE24

Evaluation: ICE33
I wouldn't fix errors/warnings in merge modules if they do not prevent the MSI from installing, self-healing or removal. So just leave this alone.