This chapter describes how to perform a full installation of SoftWindows from the two installation CD-ROMs, or upgrade from SoftWindows 4.0 using the upgrade CD-ROM.
To upgrade from SoftWindows 4.0 you will need network access to an existing SoftWindows 5.0 installation or CD-ROM.
To install SoftWindows you need an activation license, which can be one of the following:
Allows any number of users to run SoftWindows for a limited time period.
Allows a specified number of users to run SoftWindows for an unlimited time period.
Allows any number of users to run SoftWindows on a specific host machine for an unlimited time period
To install a license you need to:
Find your license server FLEXlm HostID and server name; refer to “Hostids for FLEXlm-supported machines.”
Install your license.
This chapter describes each of these procedures in detail, and contains the following detailed sections:
Additional information on installing and upgrading can also be found in the following chapters of this Admin guide:
Chapter 2, “Installation requirements”—Lists the installation requirements for SoftWindows running on Silicon Graphics workstations.
Chapter 5, “Additional installation information”—Describes how to upgrade from a previous version or deinstall SoftWindows, and lists the files that are installed by the installation procedure.
Chapter 9, “Advanced installation options”—Gives additional information about installing and setting up SoftWindows for specific requirements and includes details of secure mode.
Before installing SoftWindows, you need to have a suitable CD–ROM drive connected to your workstation. If necessary, refer to your system's documentation for information on how to do this.
To install SoftWindows a window manager such as Motif must be running on your workstation.
The installation process also requires:
At least 23.5Mbytes of disk space to perform a full installation, (plus 180 Mbytes for each user's C: drive) or 70 Mbytes of disk space to perform an upgrade from SoftWindows 2.0. See Chapter 2, “Installation requirements,” for more details of disk space requirements.
For an Indy system, at least 48 Mbytes of physical memory. The performance of SoftWindows will be improved with more memory. 64 Mbytes are recommended.
For an O2 system, you need at least 96 Mbytes of memory, with 128 Mbytes recommended.
It is recommended that at least three times the physical memory be allocated to the swap space, or twice the physical memory size, for systems with more than 48 Mbytes.
The optimum installation configuration depends on a number of factors including whether SoftWindows will be used in a single- or multi-user environment. Advantages and disadvantages of different installation options are discussed in Chapter 8, “Tuning the performance of SoftWindows.”
Decide on the following before you install:
Installing the hard disk data file (WIN95.DAT) is optional, but the file is required whenever a user creates a new C: or D: drive.
A hard disk data file occupies approximately 150 Mbytes of disk space. In a multi-user environment, unless your network has no shortage of disk space you should consider providing access to the hard disk data file from a single central source. You can do this in a number of ways:
Place the SoftWindows CD in a CD-ROM drive accessible across the UNIX network. When prompted, users should specify the path to the WIN95.DAT file in the directory on which the CD is mounted.
Install the hard disk data file once on a network file server, accessible across the UNIX network. When prompted, users should specify the network path to the sys.diskdata file in the SoftWindows installation directory.
Copy the WIN95.DAT file onto a network file server and create a symbolic link called sys.diskdata in each install directory pointing to the WIN95.DAT file. SoftWindows will be able to find the hard disk data file without prompting the user. See also “Creating Symbolic links to the hard disk data file.”
Installing the Windows 95 setup files is optional, but the files are required whenever a user changes the Windows configuration. For example, when installing additional Windows drivers, a dialog box appears.
In a multi-user environment, unless your network has no shortage of disk space you should consider providing access to the Windows 95 setup files from a single central source. You can do this in a number of ways:
Place the SoftWindows CD in a CD-ROM drive accessible across the UNIX network. Users should then set up an VFSA drive that points to the win95 directory on the CD. When prompted to insert the disk labeled Windows 95 CD-ROM, users should choose the VFSA drive that points to the win95 directory on the CD.
Install the Windows 95 setup files once on a network file server accessible across the UNIX network. Users should then set up an VFSA drive that points to the $SWINHOME/win95 directory. When prompted to insert the disk labeled Windows 95 CD-to users should choose the VFSA drive that points to the $SWINHOME/win95 directory.
Copy the win95 directory from the SoftWindows CD onto a network file server. In each user's $SWINHOME directory, create a symbolic link called win95 pointing to the win95 directory. Users should then set up an VFSA drive that points to the $SWINHOME/win95 directory. When prompted to insert the disk labeled Windows 95 CD-ROM, users should choose the VFSA drive that points to the $SWINHOME/win95 directory.
Consider whether you will need to install the cross-platform customization files. These are required in the following circumstances:
If users will run SoftWindows from X terminals or workstations other than the default type associated with the platform you are installing on.
If you perform an upgrade installation based on an existing SoftWindows 2.0 installation (as opposed to a SoftWindows 2.0 CD), and you install on a different platform from the one on which you installed SoftWindows 2.0 but wish to continue using the same keyboard as before.
Read the instructions that came with the installation CDs to install SoftWindows.
You can upgrade your original SoftWindows 4.0 disk for use with SoftWindows 95. Note that once you have done this, you will be unable to use the disk with SoftWindows 4.0. For this reason you should copy the SoftWindows 4.0 hard disk file, upgrade it, and use it with SoftWindows 95. You will then be able to continue using the original hard disk file with SoftWindows 4.0.
Upgrading installs enhanced drivers for use with Windows, and does not install Windows 95. To do this you need to perform a full installation, or use a standard Windows 95 upgrade CD package available from most PC suppliers.
Use this procedure to perform a fresh upgrade, or to add components to an existing upgrade installation.
Copy the original hard disk to your home directory, and name it WIN95-username.hdf, where username is your UNIX login ID.
Check that the disk has at least 10 Mbytes of free space available. If necessary, increase its size first.
SoftWindows automatically upgrades the WIN95-username.hdf disk to include the latest Windows drivers.
If SoftWindows has not yet been licensed, the SoftWindows license manager dialog box will be displayed towards the end of a full or upgrade installation:
This allows you to enter the licensing details for your copy of SoftWindows.
To license SoftWindows:
Enter the data into the license manager dialog box as follows.
|Note: You must enter the data exactly as shown on the license sheet:|
Table 3-2. SoftWindows Licenses
What you enter/select
Type Of License
Demonstration, concurrent, or nodelock.
A serial number in the form:
1234 1234 1234 1234
Note that you must enter the spaces. Alternatively, enter a demo code of the form 30-day, specifying the number of days.
Number Of Users (Concurrent license only)
The number of licenses purchased.
The expiry date supplied in the form Day, Month, Year (for example 15, 12, 1996), or 1,1,0 for concurrent licenses.
The 20-character authorization code; made up from the characters 0-9 and A-F (in upper case) with no spaces between the characters.
Choose Install License to install the license.
You can now set up each SoftWindows user, as described in the next section.
Once SoftWindows has been installed on the system you need to set up the environment for each SoftWindows user. SoftWindows includes a script to do this automatically; alternatively, you may prefer to set up the environment manually.
If you allow the environment to be set up automatically, the following files are altered: .login, .profile, .Xdefaults, .4Dwmrc.
This section lists the environment variables you need to change if you want to set up SoftWindows manually.
To make the changes permanent, include the appropriate lines in the user's .login file if using the C shell or in the .profile file if using the Bourne or Korn shell.
Unless a license has been installed on the user's machine, this needs to be set up to specify the location of the FLEXlm license server. It should be set to:
where portnumber refers to the TCP/IP port number of the license server. The default should be 744, as this is the number assigned to FLEXlm.
For example, if the server is called myserve, and FLEXlm is attached to port 744, then LM_LICENSE_FILE should be set up as follows:
For a C shell:
setenv LM_LICENSE_FILE [email protected]
For a Bourne or Korn shell:
[email protected] export LM_LICENSE_FILE
Depending on which window manager you are using, complete the installation process using the appropriate one of the following sections.
Once the installation is complete, log out and log in again as a user to make the changes to the system files take effect.
The user can now run SoftWindows; refer to “Running SoftWindows” in the SoftWindows 95 for UNIX User's Guide.
When starting SoftWindows after the initial run you may have problems reading man pages or accessing SoftWindows files.
This may be because on some X servers running xdm the .profile or .login file is not executed when you login, and therefore $SWINHOME is not set. In this case you should:
Add the following lines to your .xinitrc file in your home directory, taking care to insert them before any code beginning Xclients:
if[ -f$HOME/.profile ] then cd $HOME . .profile fi
Note that .xinitrc is usually executed with a Korn shell rather than a C shell, and so the .profile file is used rather than the .login file.
If you do not have a .xinitrc file in your home directory, refer to the manual pages for the xinit command, and determine whether you can copy a default (or what should constitute a default) .xinitrc file to your home directory.
Note that you must insert the above lines of code into your .xinitrc file if you have had to create one.
Log out and log in again for the changes to take effect.
This error occurs whenever SoftWindows detects that none of the fonts required are available from the X server, or the fonts installed in the SoftWindows installation are not usable by the X server. To resolve this problem you need to configure the X server to use the relevant fonts in the SoftWindows installation. Use the command:
xset +fp $SWINHOME/fonts/SGI xset fp rehash
where $SWINHOME is the SoftWindows installation directory.
To make the change permanent, include these commands in the .xinitrc file in each user's home directory. If the .xinitrc files does not already exist, create it and insert these commands.
Alternatively, you can use a font not provided with SoftWindows using the following procedure. You might want to do this if you need extended ANSI characters, such as ß, µ, or accented characters, which are not included in the default font.
Select a suitable font name to use.
This can be done using a program such as xlsfonts or xfontsel.
Once a font is selected, the following line should be added to the SoftWindows 95
app-defaults file, found in $SWINHOME/sOftWindows:
where fontname is the string you selected above.
Then restart SoftWindows.