To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=116035
------- Additional comments from [email protected] Fri Jan 21 09:54:43 +0000 2011 ------- is -> fyva: But why do you, or the other person, install msvc libraries and manifest files by hand? I think, this is really a bad idea. In the OpenOffice.org installation set you find a sub folder "redist". There are redistributables for the runtime libraries for 64 bit and 32 bit systems. Looking into the msi database of the vcredist_x86.exe I can see that it contains 127 (!) files at 59 components and 43 CustomActions. You do not expect to get a valid installation if you only copy these files. In your example you do not mention the policy file. But this is essential. The soffice.bin was built with msvcr90.dll in version 21022. Therefore this version is written into its manifest file. And if you install the vcredist.exe correctly you get installed the msvcr90.dll in version 30729 together with a policy file that says the Windows system, that if an application requires the msvcr90.dll in version 21022, it can use the version 30729 because this is obviously downward compatible. So the correct installation of vcredist.exe is absolutely necessary that all this Windows internal processes can work successfully. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
