StarOffice 4 and 5 under lxrun
Contributed by: Krzysztof Hrebeniuk
[opole@pios.gov.pl or kkhrebeniuk@qnx.com]
I) StarOffice - versions 4.x and 5.x
Why did I write these installation scripts? Because I was not able to
run the original StarOffice setup program on SCO OpenServer 5.0.5
under control of lxrun 0.9. Even after installing SO4/5, when
everything seemed to work, it was still impossible. I have no idea
why - in the case of SO5, I had access to a running Red Hat 5.1 system
and I copied almost the whole contents of /lib, /usr/lib,
/usr/X11R6/lib to appropriate $LINUX_ROOT subdirectories (I omitted
libs concerning gnome, tk etc.).
The setup program crashes at one point with sh: $so_pid_number killed
info. I wrote the installation script for StarOffice 4.0 before I
gained access to a running linux system and was able to compare the
original installation with that created by install4 script.
Unfortuantely, the Help system didn't work on either of them.
Fortunately, it works in SO5 - both on linux and SCO! Directory trees
and all files will be identical to those created by SO4/5 setup on
linux. I gave up examining the problem of the SO4 Help because I use
SO5 now and after several days of tests everything looks OK. Maybe
some other volunteer will resolve it.
What do these scripts do? Almost all installation instructions are
contained in the setup.ins files of the SO4/5 distribution.
install4/5 simply reads all these concerning directory structure and
filenames, and extracts the f_number files to the appropriate location
(at the begining, the user is asked for a destination directory).
Permissions are also set. That is all for SO4. In the case of
StarOffice 5.0, some extra files are created in the program root
subdirectory (hereafter, $program_root). All but one of these files
are generated by install501. All these files are embedded into the
script body and in some cases variables inside them are replaced with
values supplied by the user. This script should be downloaded as a
binary because SO5 configuration files are in DOS format!
What do you need besides SO4/5? I have SCO OpenServer 5.0.5 and Lxrun 0.9.
No additional libraries are required.
I freshly installed Lxrun for test purposes and everything looks OK.
The first program execution lasts very long. I have rather fast machine
(Dell PowerEdge 2300 with 256 MB RAM), but I have to wait about 15 - 20
seconds before the SO logo apears.
If you don't use /etc/resolv.conf file, you should create it. SO4/5
will not start without it (you will see a "Can't connect to X-server
..." error). All StarOffice f_number files are zipped, so you will
have to have unzip in your PATH. If you want to run SO4/5 in KDE
environment, you should remember to set the DISPLAY variable properly
(the system name should be added). None of the scripts allows for
choosing components to install - everything will be installed. So you
will need plenty of free disk space - about 250 MB (60 - 70 MB in the
installation directory and about 180 MB in destination directory).
Before installation remove $HOME/.sofficerc or $HOME/.sversionrc files
- if you have any.
The LINUX_ROOT environment variable should be set, and your PATH
should contain /usr/local/bin.
Steps you should perform to install SO4/5:
II) StarOffice 4.0
1. Create installation directory $inst_dir
2. Copy all distribution files to $inst_dir (all f_number files,
*.res files and also libc.so.5.4.44 and libm.so.5.0.9 files)
3. copy install4 file to $inst_dir
4. cd to $inst_dir and run ./install4. Answer a question about
destination directory
5. after installation go to the $program_root/bin subdirectory and
edit soffice file.
Change the last line of this script from:
exec $sd_inst/bin/$sd_binary "$@"
to:
exec lxrun $sd_inst/bin/$sd_binary "$@"
6. go to the graphical environment, run scoterm,
cd to $program_root/bin
7. run ./soffice
Choose Tools/Options/General and Paths bookmark. Edit all settings
and remove the "/bin" part from the path. Standard templates should
point to $program_root/config/new and AutoPilots to
$program_root/config/wizard etc. That's all.
III) StarOffice 5.0
I have one-file distribution: so501.tar.gz. I assume that you have the same.
This is very important - it's an english version. Settings files generated
for SO5 by install501 are from this distribution and I don't know if it
will work with another language. (Try it!)
Among others, install501 generates $program_root/sofficerc and
$program_root/config/servicesrc files which have language sections.
Edit these carefully after installation!
It's impossible to run SO5 before you register on
http://www.stardivision.com (or http://www.stardivision.de). If you
omit this step you'll still be able to install program, but you won't
be able to run it. If you decide to do so, you will have to edit 2
files after installation: $program_root/config/authrc and
$program_root/sofficerc. In place of valid registration data you will
find some information about what appropriate fields should contain
(for example, change Company to your company name, First Name to your
name etc.) All the missing data should be supplied exactly in the
same form as on the stardivision site. I recommend to register first
-- you cannot skip this step anyhow and you will already have running
program after installation. It is the best to print your registration
sheet.
1. extract so501.tar.gz. Directory so501 will be created with
3 subdirectories: glibc2_inst, so501_doc and so501_inst
2. copy install501 to so501_inst
3. cd to so501_inst and run ./install501
4. answer the questions concerning registration data and program
destination directory. Remember that registration data are case
sensitive, and when you change one comma or space, it may result
in a non-functioning program!
5. After installation unpack glibc2.tar.gz, cd to the glibc2 directory
and move all its contents to $program_root/lib.
Files in glibc2 are often symlinks to other files in this
directory, so you can't simply run cp * in this directory because
links will vanish.
6. edit $program_root/bin/soffice and change last line from:
exec $sd_inst/bin/$sd_binary (...)
to:
exec lxrun $sd_inst/bin/$sd_binary (...)
7. edit $program_root/bin/setup and change last line from:
exec $sd_archive_path/$sd_setup_binary $*
to:
exec lxrun $sd_archive_path/$sd_setup_binary $*
8. download instdb.ins.gz and copy it to the $program_root directory
and ungzip it there. You'll need this if you want to use help in
SO5.
9. edit the instdb.ins file using scoedit or other editor which can
manage with DOS file (Midnight Commander internal editor for
example) and edit the third line of this file.
Change SourcePath = "/root/so501/so501_inst". Replace word "root"
with valid directory name of your SO5 source directory.
10. Run scoterm, cd to the $program_root/bin and run ./soffice.
You should be informed that program is preparing for
the first time execution.
11. exit program. From another terminal session run
ps -ef|grep soffice.bin and kill -9 $so_pid
12. in $program_root/bin directory run ./setup (this is not the same
setup as in so501/so501_inst directory).
You will be informed that all program components are installed.
Choose Repair option and exit. In this way Staroffice 5.0 help
files will be created and you will have fully functioning help
system!
As far as I know, impossibility of exiting the program in normal way is
the only restriction. The user will not be returned to the prompt in scoterm
window; you must manually terminate the program using kill -9 $so_pid from
another terminal session. Maybe somebody will find a solution to this
problem?
Enjoy!