Hi tml,
>> But when there were hundreds of different files in
both installation
>> sets, the result was not usable.
>
> Do you have any more detailled memory of what made it
unusable? Didn't
> Windows Installer cope with many patches in one .msp?
Did it just stop
> working, hang or something? Or did you get some clear
error messages
> saying that the .msp is too complex?
well, the msp file most times did nothing. After a few
seconds it ended
with a success message, but in reality the original
installation was not
changed. We did not investigate this extensively, because we
did not
like the complete process of making patches as a difference
of two or
more adminstrative installations and using a Patch Creation
Property file.
Unfortunately this seems to be the only way, to make Windows
Installer
patches using the Windows Installer SDK. Or do you have
another idea how
to create msp files?
> Yep, I agree. Once I have something that I think has a
chance of being
> accepted (and I am reasonable certain that producing
MSI patches will be
> feasible) I will submit it upstream.
Great 
Ingo
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe installation.openoffice.org
For additional commands, e-mail: dev-helpinstallation.openoffice.org
|