Martin Hollmichel
Wed, 30 Apr 2008 06:32:49 -0700
Stephan Bergmann wrote:
In case you have not yet noticed, <http://www.openoffice.org/issues/show_bug.cgi?id=88671> and <http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=22279> describe a potentially big problem of OOo 3 (incl. OOo 3.0 beta) on Windows machines where the Microsoft C/C++ runtime used by OOo 3.0 (msvcr90.dll et al) does not happen to be already installed system-wide: Any time OOo code calls the OOo function cppu::getCaughtException (and there are in the hundreds of such calls across our code base) OOo might crash. One such scenario is described in issue 88671, others are most probably waiting to happen.The simple solution would be to install the runtime, if required, system wide. A problem seems to be the so called "administrative network installation", right ? In this case OOo will get installed on a network drive and the Office application should be able to start from any Windows client using that installation. This works fine in OOo 2.x but would break for 3.0 if the runtimes don't get installed on the client systems. I'm not that familiar with those deployment, but I would expect that there is either the possibility for the admin to get the runtimes installed on all the clients machines and/or we make it a requirement, that an installation of the needed files need to get run on the client machines ? Any experts around for thoughts about this scenarios ?However, any kind of fix for this appears to be far from trivial (see <http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=22279> again and the follow-up <http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=22295>), each requiring rather weeks than days, with unclear outcome.In short, it is unclear for me whether and how this could or should be addressed for OOo 3.0 beta. (But a fix will of course have to be in place for OOo 3.0 final.)
For the beta I think we can add a paragraph in the release notes that the installation of the runtimes (link ?) is recommended.
-Stephan
Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]