Installing the Software

Installing the Software

Most people should just use the single- user installation process, next .

If you're installing the program for an organization and you want some files, like templates you decide to include, on the network, use Installation: Multi-User on page 31. The information in this section is organized as follows :

  • Installation: Single-User on page 24

  • Installation: Multi-User on page 31 This applies if you are installing on one computer for several different users, as well as on one server and multiple client computers.

  • Installing Additional Components on page 34

  • Installing the Same Version Multiple Times on the Same Computer on page 35

  • Viewing Where Data Is Stored on page 36

Installation: Single-User


If you want to install the program, single-user, on several computers, you can do a variation on the multi-user install and save yourself some time. Run the server install (Installing on the Server on page 32). Then run the client install on each computer (Installing on Each Client on page 33), but select the Local installation option, not the smaller client installation.

The installation is pretty straightforwardjust stick the CD in the drive and go, with a few questions here and there.

  1. Be sure you've read the operating system-specific notes on page 20 and that you have at least 250 MB of free space where you'll be installing.

  2. In a Linux or Solaris environment, be sure you're logged in as the user who will be running the program.

  3. If you're installing from CD, insert the CD in your CD-ROM drive. The installation program will start automatically. If it doesn't, use the index.html file on the CD included with this book or navigate to the setup or setup.exe or setup file for your platform.

  4. The window in Figure 2-2 will appear. Click Next.

    Figure 2-2. Introductory window of installation


  5. The window in Figure 2-3 will appear. It contains operating system-specific information about the installation (your window might look different). Read the displayed information carefully , then click Next.

    Figure 2-3. Installation information


  6. The window in Figure 2-4 will appear, displaying the license agreement. Review it and, if you agree to the terms, click Accept.

    Figure 2-4. License agreement


  7. If you currently have the program installed, a window as shown in Figure 2-5 will appear, prompting you to import personal data from another location.

    Figure 2-5. Specifying existing user data location



    If you've been using StarOffice 5.2 Mail as your mail program, you must select Import personal data to get any of that data into 6.0 or 1.0. See Migrating Your StarOffice 5.2 Mail to Another Mail Program on page 47.

    Select the Import personal data option and enter the path to your old directory; it's a good idea to do it to avoid a lot of repeated setup. For more information see page 45.

  8. If you don't choose to import, or if you didn't have the software installed before, the personal data window in Figure 2-6 will appear. You can enter it now, or do it later (choose Tools > Options > program ).

    Figure 2-6. Personal information window


  9. The installation type window shown in Figure 2-7 will appear, then take step A or B.

    1. In Figure 2-7, pick Standard, or Custom if you want a little more control. (Minimal isn't a good idea since you don't know what it's leaving out.)

    2. If you chose Custom Installation, the window in Figure 2-8 will appear. Expand the options and double-click any item that you don't want to install. Click Next.

    Figure 2-7. Selecting installation type


  10. The window in Figure 2-9 will appear. Enter the directory and click Next.

    Figure 2-9. Selecting installation location


  11. The window in Figure 2-10 will appear. Click Install to begin copying files.

    Figure 2-10. End of installation options


  12. The window in Figure 2-11 will appear. This is an important window. If you mark any of these file types, when you double-click them or right-click on them in Explorer and choose Open , they will be opened in automatically.

    Figure 2-11. Choosing whether will open other file types automatically



    If you're wondering whether to leave them marked or not, unmark them; you can use your operating system tools later to associate them if you want. Check these carefully; if you're already used to opening and editing HTML files in Netscape or Dreamweaver, for instance, be sure to deselect HTML before continuing.

    Click Next.

  13. The window in Figure 2-12 will appear. The program needs Java software in order to run some of its features.

    Figure 2-12. Java setup


    If you don't have one currently installed, get one now, or get one later if you encounter problems. You can get the JRE 1.3.1 or 1.4 from; follow the links to the JRE.

    If you have a JRE, select one from the list in the window and click OK.

  14. The installation process will continue for quite a while; a progress bar will show how much of the process is complete and approximately how much time is left.

    The installation program sits for quite a while on the last item, Registration of the components. Even though it looks like it's done, it's not until you get the window in Figure 2-13.

    Figure 2-13. Installation complete


  15. Click Complete as instructed.

Installation: Multi-User


For scripts enabling multi-user installation, see the Administration Guide included with

You'll be installing the program on the server, then running a setup file that gets installed on the server, to install the program on clients .

  • The files installed on the server include program and help files, including the setup file used to run the client install, and a share directory containing shared resources such as templates you decide to include, and configuration settings for items like printers.

  • The files installed on the client include program and help files, including the soffice file used to start the program on the client, and a user directory containing files created by the user on that client (includes modified templates, client-specific configurations, etc.).


You must install as the user who will run the software. If clients do not have software installation rights, you might need to grant those rights, install, then take away those rights when installation is complete.

Installing on the Server

Complete the server installation in a directory with sufficient disk space (see System Requirements on page 22) and to which all users have read/write access.

  1. Be sure you've read the operating system-specific notes on page 20.

  2. If you've got a previous version of the program installed, first check for the following files on your system:

    • .sversionrc in the Solaris or Linux home directory

    • .sversion.ini in the Windows directory

    Open the files; they contain the path and version number of the program if it is currently installed. If the version number is 6.0, you need to uninstall the program first (see Removing the Program on page 40). For more information about these files, see Installing the Same Version Multiple Times on the Same Computer on page 35.

  3. Insert the CD in the server's CD-ROM drive. In Solaris and Linux, you'll probably need to mount the CD-ROM, typically with a command like mount /mnt/ cdrom

  4. In a Linux or Solaris environment, be sure you're logged in as the user who will be running the program.

  5. In a terminal window, navigate to the directory on the CD for your operating system. Type the appropriate command and press Enter: ./setup -net (Linux or Solaris) or ./setup.exe -net (Windows)

  6. Continue through the installation, which from this point on is the same as the single-user installation starting on page 24. When you get the option for Standard, Custom, or Minimal Installation, select Custom and select all items for installation. Click to open the Writer module and double-click it to make all items, including the import filters, turn blue.

Making the Installed Files Available to Clients and General Troubleshooting

You need to make sure the location where you installed the program on the server is accessible to client machines via the network.

You'll probably have to fuss with the directory permissions. All client machines will need read and execute permissions so that you can run the setup file on the server to do the client installation, and so that users can get at the files they need (including templates, icons, etc.).

Check the access permissions on all the directories where you installed the program. The program directory and all subdirectories need to have read and execute permission for any users accessing the program ( group and other , for example, in Solaris). If they don't, use the appropriate procedures for your operating system to set the permissions.

Depending on how your system is set up, users might not automatically have read, write, and execute permissions on their temporary directory, and that they can copy files into that directory. Check those permissions, as well, before beginning the client install.

Finally, take a look at the files in the share directory on the server. Any modifications or new files users make are generally saved in their own user folder, and aren't available to other users. If you want users to be able to create new or modified versions of those files, such as templates, and share them on the server, set the permissions appropriately and let users know where to save their new templates or other files. However, note that with this approach, users can permanently change shared resources if they modify the original instead of making a copy.

You might encounter problems in Windows if you install the program in the root directory and the number of files in the root directory exceeds 256. Solaris and Linux installations might fail if the home directory on the server isn't available.

Installing on Each Client


If you run the client installation of the multiuser installation with ./setup , the installation can freeze. This can happen with a normal user or root. To solve this, get the latest XFree86 at Be sure to follow the installation instructions and system prerequisites stated on the site.

Complete this procedure on each client computer, or have each user complete it. Be sure that if you complete it, you log in as the correct user for the client computer.

  1. In a Linux or Solaris environment, log into the client computer as the user who will be running the program there.

  2. On the client computer, navigate to the newly installed office/program directory on the server where you installed the program . (You don't need the CD.)

  3. Double-click the setup file or setup.exe file (not the soffice file, which just runs the program), or run either of the following commands:

      ./setup  or  ./setup.exe  


    If you have problems accessing the file, be sure that the correct access rights are set on the server computer for the client user and that you installed as the right user on the client and on the server.

  4. A welcome window will appear. Click Next. Continue through the installation. The only difference from the installation you've already seen is that, instead of Standard Custom or Minimal installations, you will be offered the options of Standard Workstation Installation.

    Select Standard Workstation Installation , unless you want all the files to be local. (That is, you're just trying to get the program onto a bunch of single-user machines fast, without using the CD.)

  5. Continue until the installation completes.

If You Installed as a Different User Than Who Will Run the Program

If you installed, for instance, as user X, but want to run the software as user Y, you'll need to fuss with the software a bit first. Do the following as the user you didn't install as. Locate the setup file in the directory where you installed, double-click it, and choose to run the repair program. Once it's complete, the user should be able to run,.

Installing Additional Components

If you didn't install everything you needed to, run the install again and pick Custom.

  1. Start the installation the same way you did before, with the setup or setup.exe file.

  2. In the Installation Program window, select the Modify installation option. Click Next.

  3. In the Select Modules window, make the icon dark blue next to everything you want installed. It's a good idea to just install everything. Double-click on the Program Modules and Optional Components items until the icons for both are colored.

  4. Click Complete. Continue the installation.

Installing Templates

Templates are not included with itself. However, templates are available on the CD included with this book and at locations listed at Copy the templates you want to use to the office\user\template directory (single-user) or the office\share\template\ language directory on the server (multi-user) and they'll show up in the organizer and when you use AutoPilots such as the Impress autopilot that rely on templates.

Update the paths where looks for templates, if necessary. Choose Tools > Options > > Paths. You'll also need to restart before it will recognize new templates.

Specifying the JRE

To get the JRE, go to and follow the links. Get the latest; 1.3.1 or 1.4 work. To specify the installed or another JRE, in the same directory, run jvmsetup or jvmsetup.exe . In the window that opens, select the right JRE and click OK.

Installing the Same Version Multiple Times on the Same Computer

If you install the program, then attempt to do another installation, you'll get a whiny error message saying no, sorry, it's already installed, as shown in Figure 2-14.

Figure 2-14. What you see if you start the install with the program already installed


The message states that you must remove it first (for instructions see page 40) if you want to reinstall.

The install program knows that you've already got an installed version of 6.0 because of the following registry-type file that tracks where and how the program is installed:

  • .sversionrc in the UNIX home directory

  • .sversion.ini in the Windows\Application Data directory

The contents look something like Table 2-1:

Table 2-1. sversionrc and sversion.ini files for a system that's used StarOffice and

[View full width]

;StarOffice 5.1a=C:\Office51a
StarOffice 5.2=C:\Office52 641=file:///C:/openoffice 101=file:///C:/Program%20Files/ graphics/ccc.gif office101 


;StarOffice 5.1a=/home/solveigh/Office51a
StarOffice 5.1=/home/solveigh/Office
StarOffice 5.2=/home/solveigh/office52 101=/home/solveigh/office101 

You can run do another install of what you've got installed now, without uninstalling if you comment out the current installation location. For example, if you had the file shown previously on your system, and you wanted to also install 101, you'd add a semicolon in front of the line for the current installation:

;StarOffice 5.1a=C:\Office51a
StarOffice 5.2=C:\Office52 641=file:///C:/openoffice  ; 101=file:///C:/Program%20Files/office101  

Keep in mind that this will almost certainly mess up the program icons that the installation adds to your task bar or Start menu. When you start the program, be sure to do so by typing ./soffice in a terminal window, in the appropriate office directory.


Make a backup of any files you edit.

Viewing Where Data Is Stored

You can use a couple different sources to see where your data ended up, and where the program is looking for it.

In addition, the Paths window within the program's general options is very useful, in order to see where each client installation looks for files. Choose Tools > Options > > Paths; the window in the following illustration will appear. Scroll through the list to see where each type of file is stored.

Figure 2-15. File paths window


If both the server and client are listed, it means that files of that type such as templates are stored on the server, but new or modified files of that type are stored locally.


Refer to Specifying the Default Directory You Save to and Open Files In on page 132 if you want to change where the client looks for files. Be sure that, if you change from the client to the server, the files on the server have permissions that allow the client to access them. In addition, all files might not be installed on the client, so exercise caution when switching from server to client.