Hello,
for testing of previously reported bugs I tried to install LibO 3.5
beta in parallel to OpenOffice 2.4.3 and LibO 3.3.4. Before this
installation attempt I had removed an existing (and working)
parallel installation of LibO 3.4.
But the new installation always fails with the message:
Runtime error! Program ...\unopkg.bin
This program has requested the Runtime to terminate in an
unusual way. Please contact ...
After pressing OK it shows
unopkg.bin has crashed
Also when running soffice.exe it always says
LOdev3.5 has crashed.
Does anyone have an idea how to get it installed?
I have already tried to run the installation without Java or
anti-virus software, but no change.
Here comes some data of my system:
Software to be installed:
LibO-Dev_3.5.0beta2_Win_x86_install_multi.msi from
http://www.libreoffice.org/download/pre-releases/
Installed:
LibreOffice 3.3.4 OOO330m19 (Build:401) tag libreoffice-3.3.4.1
OpenOffice 2.4.3
System:
32 Bit Windows Vista Home Premium SP2
AMD Turin 64x2 Mobile Technology TL-58
Thanks,
Karl
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Installation problem LO 3.5 beta · Karl-Heinz Bellgardt
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.