Read this section carefully if you formerly ran a version of the OpenWindows environment that predates Version 3.3 and now want to migrate to Version 3.3, or later versions. In particular, much of this information applies to those who have been using the OpenWindows Version 2 Environment.
If you are currently running a version of the OpenWindows software earlier
than Version 3.3, you may have set up your system to use the
OPENWINHOME environment variable. It is no longer recommended
that users set the
environment variable, either by-hand or from a start-up file.
If you have set the
environment variable in either the .profile or .cshrc file in your home directory, comment out the line or delete
it altogether before running OpenWindows Version 3.3, or later versions.
To remove, or comment out, the
OPENWINHOME environment variable in the .profile or .cshrc file:
Open the .profile or .cshrc file using a text editor such as vi.
If you are working in the .profile file, use example a; if you are working in the .cshrc file, use example b
In the OpenWindows Version 2 environment, the openwin script automatically created a copy of /usr/openwin/lib/Xinitrc to a file called .xinitrc in your home directory. This is no longer the case in the OpenWindows Version 3.3 environment. This is significant because:
The openwin start-up script uses the default start-up file, /usr/openwin/lib/Xinitrc, unless there is an .xinitrc file in your home directory, which overrides the default.
It is important that you use the default /usr/openwin/lib/Xinitrc file that come with OpenWindows Version 3.3 software, or later versions. (However, if you want to retain any special changes you made to the .xinitrc file in the Version 2 software, you can do so by following the instructions in this section.)
If you are currently running a version of the OpenWindows software earlier than Version 3.3, it is important to determine the status of your .xinitrc file. The .xinitrc file is an OpenWindows start-up file your home directory that may contain user-defined options.
To determine the status of your .xinitrc file, type the following commands:
$ cd $ ls -a .xinitrc
Depending on the output of this command, do one of the following things:
If you do not have a .xinitrc file (that is, the results of the previous ls -a command does not return a listing for the file) do nothing. If there is no .xinitrc file in your home directory, OpenWindows uses the system default start-up file.
If you have a .xinitrc file (that is, the result of the previous ls -a command returns a listing for the file), but you have never made any changes to the file or do not want to keep the changes you have made, do Step 1 "A.2.3.1 Start-Up File Procedures".
If you have a .xinitrc file (that is, the result of the previous ls -a command returns a listing for the file), and you have made changes to the file that you want to keep, do Step 2 in "A.2.3.1 Start-Up File Procedures".
$ rm .xinitrc
Move .xinitrc to .xinitrc.save:
$ mv .xinitrc .xinitrc.save
Copy /usr/openwin/lib/Xinitrc to .xinitrc in your home directory:
$ cp /usr/openwin/lib/Xinitrc $HOME/.xinitrc
Add the lines that you want to keep from the .xinitrc.save to .xinitrc.
In prior versions of OpenWindows (before version 3.3), a change made in the Workspace Properties menu would be stored in the file .Xdefaults in your home directory. In OpenWindows version 3.3, and later versions, changes made in the Workspace Properties menu are now stored in the file .OWdefaults, also in your home directory. The .Xdefaults file can still exist, but precedence is given to the customizations made in .OWdefaults.
The .Xdefaults file should be used only to make additional customization changes that cannot be made through Workspace Properties. For example, you can edit the .Xdefaults file using a text editor such as vi to make customizations to non-OpenWindows applications or to add C pre-processor macros. Using Workspace Properties does not disturb these customizations.
If you already have a .Xdefaults file in your home directory and you do not want to make any customization changes to it, you do not need to remove it. Since the .OWdefaults file takes precedence over it, it does not interfere.
In OpenWindows 3.3, or later versions, you customize the Programs submenu on the workspace menu using Workspace Properties. Prior to OpenWindows 3.3, you did this customization by editing the .openwin-menu file in your home directory.
If you do not have a .openwin-menu file in your home directory, it is not necessary to do the following procedure. You can customize the workspace menu by using Workspace Properties.
If you do have a .openwin-menu file, you must perform the following steps in order to use Workspace Properties to customize your workspace menu.
If you see the following line in your .openwin-menu file:
"Programs" MENU /usr/openwin/lib/openwin-menu-programs
delete it and replace it with this line:
"Programs" INCLUDE openwin-menu-programs
If your .openwin-menu file does not contain the line that needs to be removed and replaced, simply add the substitute line to the .openwin-menu file, as shown above.
Adding or substituting this line adds the default Programs menu to your workspace menu. This enables you to customize it using Workspace Properties.
If, by chance, you end up with redundant items in your workspace menu, simply edit them out by removing the redundant lines from .openwin-menu.