OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Neil Waldhauer on July 14, 2013, 03:53:11 pm
-
First, thanks to Yuri Dario for his work!!!
When I prepare to run OpenOffice, I use RPM to update as in the readme.
yum install libc gcc-4.4.4 gcc-4.4.6 openssl curl libjpeg libxslt libicu zlib libxml2 stdcpp mmap pthread urpo gcc-stdc++-shared-library
Transaction Check Error:
file /@unixroot/usr/lib/gcc335.dll from install of libc-devel-0.6.5-17.oc00.i3
86 conflicts with file from package libgcc335-3.3.5-6.oc00.i386
I tried to start OpenOffice by going to the openoffice program directory and executing swriter.exe, and I get
Unable to start Apache OpenOffice!
return code: 2
Failing module: ICUUC42
-
Hi Neils
Try the RPM
yum install openssl curl libjpeg libxslt libicu zlib libxml2 stdcpp mmap pthread urpo gcc-stdc++-shared-library
then try
yum install libc
I got some problems installing GCC with YUM, I thought it was only my specific problem, so I skipped that install. But once I installed the rest of components OpenOffice worked fine here.
-
Awesome, it works here! I had to try things, though.
When using the database wizard, I get a JRE Required dialog box. (OpenOffice requires a Java runtime environment (JRE) to perform this task. Please install a JRE and restart OpenOffice.)
Did I forget to configure something?
-
You've configured Tools - Options - OpenOffice - Java - path to your Java installation?
First OO4.0 I used has problems with Jave when OO was installed in a directory which contains blanks. So had to change 'Open Office 4.0' to 'OpenOffice4.0'. But most probably this is fixed in current versions.
-
I made the mistake of opening 'Tools'->'Media Player' and now the media player will not close. This means that I can not close OpenOffice as long as the media player is open so I have to kill it every time. Next time I start it, the media player is also opened (in any module). Anyone know of a way to start without the media player? Maybe I'll just delete and re-install...
-
You've configured Tools - Options - OpenOffice - Java - path to your Java installation?
First OO4.0 I used has problems with Jave when OO was installed in a directory which contains blanks. So had to change 'Open Office 4.0' to 'OpenOffice4.0'. But most probably this is fixed in current versions.
What would you fill in for Tools - Options - OpenOffice - Java? I tried java600, java600\jre, java600\jre\bin, java600\jre\bin\client, but none are recognized.
Neil
-
@David, I ended up deleting the OpenOffice directory that is at the level of program (I am surprised it is not under Home).
@Neil, not sure why you are not seeing it work, if I put Java160 in the path it finds it on its own... otherwise I was able to use the Add and find it. I did rename my Java11 directory as it was sometimes being found and would then crash.
-
Andy....
After much screwing around I found that deleting the file: \OpenOffice4\OpenOffice\4\user\registrymodifications.xcu cures the problem. You have to enter personal info again next time it is started though...
-
Hi All
Nice to see other people have got OO4 running. Shame it does not happen here, all I get is the splash screen followed by this message:-
OpenOffice 4.0.0 - Fatal Error
The application cannot be started.
exception occured raising singleton
"/singletons/co.su.star.deployment.ExtensionManager":
loading component library failed:
file:///J:/PROGRAMS/OPENOFFICE4/PROGRAM/../program/
deploy.dll
If anyone has any ideas to resolve the above problem I'm interested :-)
Regards
Pete
-
Pete,
In your situation, the first thing I would do is look for duplicate files on my system that may interfere with AOO. In case you don't already know, go to 'Local System'->'System Setup'->'OS/2 Kernel', then choose the 'System Paths' tab. Choose the path to check, then hit the 'Duplicates' button and you will get a list of duplicate files in the path chosen. Scrutinize those and see if maybe the 'wrong' one is earlier in the path. Temporarily rename any suspicious ones and see if it helps.
Another thing to look for... do you have any other versions of OpenOffice on your system (including Star Office)? Maybe there is a signal getting crossed from one of them (registry entry, path entry, ini file entry, or start folder program)?
Your error message is odd... it implies there is a 'program' directory under /OpenOffice4/Program somewhere. I don't see that here... maybe you set that up yourself? How did you install AOO?
-
Pete,
Your error message is odd... it implies there is a 'program' directory under /OpenOffice4/Program somewhere. I don't see that here... maybe you set that up yourself? How did you install AOO?
Actually... it is the same program. Notice, it is \program\..\program the .. takes it up a level from program and then back into program. It looks odd but should work fine.
Andy
-
Hi David
I unzipped OO4 - and then downloaded, unzipped and installed (hopefully) all required DLL files not already installed.
The unzipped DLL files went into \ecs\dll.
All duplicate files are eCS (OS/2) files.
I have several other OO installations: OO3 and OO2 both of which are not very reliable and OO115 for Windows running via ar5os2.exe which is the most stable, reliable and useable of all the OO packages to date. None of these packages have entries in config.sys and nothing in the Startup folder.
There are some INI file entries for the OO Desktop Objects plus Registry entries for font j:\programs\openoffice3\fonts\opens_.ttf and focpoo3.dll - OpenOfficeOrg document types - not sure which OO build.
Yes, the error message looks odd but the path should work. If I use the following on a command line:-
[J:\PROGRAMS]cd \PROGRAMS\OPENOFFICE4\PROGRAM\..\program
[J:\PROGRAMS\OPENOFFICE4\program]
It results in a directory change to /PROGRAMS/OPENOFFICE4/PROGRAM
Basically the "/../program" is redundant so deploy.dll should be found as it exists in J:/PROGRAMS/OPENOFFICE4/PROGRAM/../program.
My best guess is that either a(some) required DLL file(s) are not at the required build level or maybe I've managed to miss extracting 1 (or more) required DLL file(s) from the "packaged for unix" zip files.
Guess I'll have to wait for a later build that contains all required files or at least a comprehensive list of required files/build levels.
Regards
Pete
-
Pete, you might try what I did... rename your OO3 directory and then recreate it and put the 004 files in it in the same locations that OO3 was in. I did that just in case there were any ini entries that came into play. Also, I put the oowps DLL in there so that it works like it did with OO3.
-
Hi Andy
I thought it would be easier to uninstall OO2 and OO3 as neither package is worth having installed.
However, this seems to have left some OO3 entries that checkini reveals and cleanini does not get rid of - nor does DMT.
I would use IniEditor to manually remove those entries but IniEditor cannot find them...
What other tools are available to remove these ini file entries?
*DRIV: J:\ (397 handles)
*3920E:OPENOFFICE3 =>J:\PROGRAMS\OPENOFFICE3<-UNABLE TO ACCESS
*358A4:BASIS =>J:\PROGRAMS\OPENOFFICE3\BASIS<-UNABLE TO ACCESS
*30877:SHARE =>J:\PROGRAMS\OPENOFFICE3\BASIS\SHARE<-UNABLE TO ACCESS
*3AC55:TEMPLATE =>J:\PROGRAMS\OPENOFFICE3\BASIS\SHARE\TEMPLATE<-UNABLE TO ACCESS
*3D9B2:WIZARD =>J:\PROGRAMS\OPENOFFICE3\BASIS\SHARE\TEMPLATE\WIZARD<-UNABLE TO ACCESS
*390BB:LETTER =>J:\PROGRAMS\OPENOFFICE3\BASIS\SHARE\TEMPLATE\WIZARD\LETTER<-UNABLE TO ACCESS
*33B37:EN-GB =>J:\PROGRAMS\OPENOFFICE3\BASIS\SHARE\TEMPLATE\WIZARD\LETTER\EN-GB<-UNABLE TO ACCESS
*3C32F:BUS-MODERN_L.OTT=>J:\PROGRAMS\OPENOFFICE3\BASIS\SHARE\TEMPLATE\WIZARD\LETTER\EN-GB\BUS-MODERN_L.OTT<-UNABLE TO ACCESS
Regards
Pete
-
As there is not an OO4 installer, I decided to just swap it out so that if something needed to be there it would be.
-
Pete,
I have OO3 installed and working fine (as good as it can). I am able to run AOO4 on this system, so I don't think having OO3 installed is an issue. Have you tried starting swriter.exe in a command window? Maybe you will get a message that gives a clue.
I used YUM to install the requirements, maybe there is a discrepancy there? What zip package did you use for the required DLLs? I could look at that and compare to what is on my system...
-
Hi David
Yes, I tried starting several OO4 apps from the command line. No, there is no output.
I do not use yum/rpm so had a go at installing the required DLL files from the url given in the readme - I would not be surprised if I've missed something/installed a wrong DLL package/have older DLL files already installed.
I would refer to the above mentioned readme file more accurately but I've just discovered that (a)e.exe no longer wants to work properly - possibly a result of INI file checking/cleaning. The (a)e.exe starts when I click on a text file but does not appear on screen; it is on the Window List but selecting it does not make it appear on screen. The only thing I can do is "kill" the invisible application.
Getting (a)e.exe working properly again takes precedence over a package that probably will not work even if all support files are in place - based on my experience of OO3 releases.
Regards
Pete
-
Hi
Having resolved the (a)e.exe problem by deleting \os2\ae.ini I've had another look at OO4.
I'm not sure whether the error message indicates if deploy.dll failed to run or ran but could not do whatever was needed to avoid the error - exception raising singleton "/singletons/co.su.star.deployment.ExtensionManager":
Possibly the only person who could answer the question is Yuri. However, as there is no way of reporting the problem I guess Yuri is not interested in whether this build has problems.
I did discover that the gcc446.dll file I had installed is slightly older than the build in http://rpm.netlabs.org/release/00/zip/gcc-4_4_6-15_oc00.zip
I did try to check gcc444.dll but I have no idea which package that is hiding in...
I'm not going to bother trying to get OO4 working. I'll wait until GA - and then probably discover that it does not work anyway ;-)
Regards
Pete
-
However, this seems to have left some OO3 entries that checkini reveals and cleanini does not get rid of - nor does DMT.
I would use IniEditor to manually remove those entries but IniEditor cannot find them...
What other tools are available to remove these ini file entries?
*DRIV: J:\ (397 handles)
*3920E:OPENOFFICE3 =>J:\PROGRAMS\OPENOFFICE3<-UNABLE TO ACCESS
...
Checkini /h /c will remove them.
-
Pete,
If you want, I could e-mail you a zip file containing all the extra DLLs needed to run AOO that I am using (it's 11MB)...
-
Hi David
Thanks for the offer but my ISP - Virgin Media - does not allow email attachments larger than 10Mb. Any chance of uploading them somewhere? - or maybe splitting into 2 email attachments?
I've had a look at swriter.exe using pmdll and there are no problems reported. This suggests that DLL files may not be the problem but it would be worth checking that the DLL files I have are not incorrect build levels.
I've posted the problem in the comp.os.os2.apps newsgroup to try and get Yuris attention. That has not worked so far but Steven Levine has responded that the error message looks like a genuine application exception rather than a DLL problem.
Regards
Pete
-
Hi Dave
Yes, checkini /h /c seems to have done the job.
Thanks
Pete
-
Hi All
After a bit of faffing around with pmdll - must remember to run pmdll from the directory containing the application file(s) that need checking - I finally discovered that I had not installed xslt.dll from libxslt-1_1_26-1_oc00.zip
Having rectified that error i now have a working OO4 - and it has already proven far superior to all OO3 builds as I can select File, New, Label and OO4 does not disappear like OO3 always did.
Thanks to all for help/suggestions.
Regards
Pete
-
Hi Pete,
I've had a bit more luck than you.
I unzipped it and moved openoffice 4 to the root of my test drive. Going on past experience renamed it to openoffice-4 then created a program object for soffice.exe, double clicked on it and it started with no apparent problem, even if it was rather slow.
It opened an .odt document that I have been working on - using libreoffice 4 for windows in virtualbox - it even allowed me to edit and save it.
When I closed it, it threw a fault in doscall1 for some reason which I will try and track down when I have more time to play with it.
-
There are so many problems in previous versions of OpenOffice.org
http://forum.ecomstation.ru/viewforum.php?f=4
Is it possible fix old problems?
-
Hi Eugene
So far it seems that OO4 fixes the main problems that I had with OO3 builds - I see you have a copy of 1 of my posts about problems in your forum http://forum.ecomstation.ru/viewtopic.php?f=4&t=8741&sid=9d17ff36b32e28ed6083181bba5e294b
Maybe a few other old problems have been fixed in OO4.
Regards
Pete
-
Label printing has always worked for me in OpenOffice. It helps to have the templates.
http://www.worldlabel.com/Pages/openoffice-template.htm (http://www.worldlabel.com/Pages/openoffice-template.htm)
-
Hi Neil
Yes, I know OO3 worked fine for other people - works OK on the Mrs system right next to mine which used to cause me to gnash my teeth in frustration - but I also know that I was not the only person having problems with OO3.
I suspect that OO3 relied on something not installed on my system but I have no idea what. I'm fairly sure it was not hardware as when I changed mainboard, cpu and ram it made no difference to the behaviour of OO3.
What ever the causes of the problems in OO3 they are absent in OO4 - and I hope OO4 works as well for everyone else. I also hope OO4 GA is a little quicker than this developer snapshot :-)
Regards
Pete
-
As many other I also have problem starting OO 4.0. When trying to start the program by clicking one of the icons soffice.exe, quickstart.exe, swriter.exe, or anyone else I get this error message:
soffice - Fatal Error
The application cannot be started.
The user interface language cannot be determined.
I installed all the required dll using the proposed yum statement. Anyone having any ideas?
Regards
Einar
-
An observation after I put OO4 on several of the machines here.
All the single core processor machines here throw a fault on closing similar to the following:
07-22-2013 19:35:55 SYS3170 PID 06b9 TID 0001 Slot 00d1
N:\OPENOFFICE-4\PROGRAM\SOFFICE.BIN
c0010001
1c03c541
EAX=00000000 EBX=168faf84 ECX=230b1000 EDX=00000000
ESI=168f662c EDI=00000000
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:15480899 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:0012fc88 SSACC=f0f3 SSLIM=ffffffff
EBP=0012fca0 FLG=00092213
DOSCALL1.DLL 0003:0000c541
While all the 2, 4 and 6 core processor machines have no problems so far. I can open odt documents and even windows docx documents as well as windows excel and power point files.
I wonder if this may have something to do with the problems others have. Unfortunately, there doesn't appear to be anywhere to report problems.
-
I see a similar SYS3170 exception in DOSCALL1.DLL on closing OO 4. My system is dual-core.
I also got the following on highlighting a paragraph of text and hitting the Del key:
07-19-2013 17:58:04 SYS3175 PID 0048 TID 0001 Slot 0097
E:\PROGRAMS\APACHE\OPENOFFICE 4\PROGRAM\SOFFICE.BIN
c0000005
0faa35be
P1=00000001 P2=00000008 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=1668af84 ECX=21051000 EDX=00000000
ESI=1668662c EDI=00000000
DS=0053 DSACC=d0f3 DSLIM=5fffffff
ES=0053 ESACC=d0f3 ESLIM=5fffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:13ad0899 CSACC=d0df CSLIM=5fffffff
SS:ESP=0053:0012fc70 SSACC=d0f3 SSLIM=5fffffff
EBP=0012fc88 FLG=00010213
SWOO.DLL 0001:000835be
Otherwise, I have to say this dev build is a lot more stable (if slower to load) than the v3.4 ones were. I was quite pleased with how much more so, at least up until I got this crash. :P
-
Just checked this and I too get:
07-23-2013 15:19:27 SYS3175 PID 0048 TID 0001 Slot 0082
D:\OPENOFFICE-4\PROGRAM\SOFFICE.BIN
c0000005
110635be
P1=00000001 P2=00000008 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=18cfaf84 ECX=230b1000 EDX=00000000
ESI=18cf662c EDI=00000000
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:14e30899 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:0012fc70 SSACC=f0f3 SSLIM=ffffffff
EBP=0012fc88 FLG=00010213
SWOO.DLL 0001:000835be
when trying to delete a highlighted block of text although it does allow deleting a single line that is highlighted.
-
Something else I've just found. Extension manager does not work!
I have been able to get it to 'apparently' add an extension but having done so it locks up - I can't close it and have to kill soffice.bin to get anywhere. Needles to say, even though the extension is listed it does not appear where it should and is unusable.
Does anyone know where these problems can be reported?
-
Looks quite great 8)