Mozilla™ Technology Demonstration
Release for OpenVMS™ Alpha™
Installation Guide and Release Notes
October 15, 2001
Mozilla M0.9.5
CPQ-AXPVMS-MOZILLA-M0009-5-1.PCSI
On this page you'll find information about:
Before Installing Mozilla
Downloading and
Installing Mozilla
Running Mozilla
Release Notes
Performance Notes
Frequently Asked Questions (FAQ)
Problem Reporting and Bugzilla
Before Installing Mozilla
Hardware Prerequisites
Mozilla for OpenVMS is available only on the Alpha platform.
If you encounter color problems when running
Mozilla on an 8-plane video
mode system, it is likely that you are running
another
application that uses a large number of colors
(Navigator V3 is such an application).
In this situation, start Mozilla before you start
the other application.
These problems usually do not occur on
a 16 or 24-plane
video mode system.
Software Prerequisites
The following software is required in order to successfully run Mozilla:
- OpenVMS Version 7.1 or higher.
Future releases of Mozilla
will be supported only on OpenVMS V7.2-1 or higher.
- DECwindows MOTIF V1.2-4 or higher
- Compaq TCP/IP Services Version 5.0 for OpenVMS
Mozilla for OpenVMS has been tested and
verified using Compaq TCP/IP Services for OpenVMS.
Compaq has not formally tested and verified other TCP/IP network products,
including the following TCP/IP network products
from Process Software Corporation:
- TCPware Version 5.5
- MultiNet Version 4.3
Important: If you are running MultiNet V4.3A or higher, or TCPware V5.4-3 or higher,
you must install a new LIBNSPR4.SO image in your Mozilla directory. See http://www.support.process.com/mozilla.html
for more information.
Account Quotas
- PGFLQUOTA
PGFLQUOTA is the most important process quota to check.
Following is an estimate of the PGFLQUOTA you need:
- 50,000 -- starts mozilla-bin (formerly called apprunner) and displays a simple page
- 80,000 -- displays a couple of normal pages
- 150,000 or more -- runs mail, can view complex pages
- FILLM
The default value of FILLM is 100, which is not normally enough to run Mozilla.
To successfully run Mozilla, do one of the
following:
- Increase the account's FILLM to at least 200.
- Use the supplied INSTALL.COM to install Mozilla. If you use INSTALL.COM,
the default FILLM of 100 is then sufficient to run
Mozilla.
System Parameters
Mozilla requires a relatively large number of
process sections, so you may find that you have an insufficient number.
(Note: If you install the Mozilla images after you install the Mozilla kit, you can avoid
this problem completely. See
Installing the Mozilla Images
for more information.)
If you see
an error similar to either of the following, then you have exhausted the available
process sections:
nsNativeComponentLoader: GetFactory(/dka0/mozilla/components/libnsgif.so)
Load FAILED with error: OpenVMS status is decimal 540
%SYSTEM-F-SECTBLFUL, process or global section
table is full
|
There are three ways to solve this problem, as follows:
- Install the Mozilla images.
This is the preferred solution.
- Increase the difference between WSEXTENT and WSMAX.
For example, if your WSEXTENT and WSMAX values are both set to 65536,
increase WSMAX to 131072 or decrease WSEXTENT to 32768.
Because WSEXTENT is a per-user value, this is the preferred solution
if you cannot install the images.
- Increase the SYSGEN parameter PROCSECTCNT. However,
PROCSECTCNT affects every process on the system so this may not
be a very desirable solution.
Mozilla.org Release Notes
Mozilla.org has provided
release notes for M0.9.5.
The release notes contain sections about Mozilla on Windows®, Mac®, and UNIX®.
Mozilla for OpenVMS is ported from the UNIX code, so the notes in the
UNIX section are applicable to OpenVMS.
When reading UNIX documentation, note the following differences
between UNIX and OpenVMS:
-
File specification format
The mozilla.org release notes show example file specifications in UNIX format.
For example, the UNIX file specification
/dka100/foo/bar/file.dat is equivalent to DKA100:[FOO.BAR]FILE.DAT on OpenVMS.
-
Directory format
Directories that begin with a period on UNIX begin with an underscore on
OpenVMS. In addition, on UNIX, the tilde (~) is shorthand
for SYS$LOGIN. Therefore, on UNIX ~/.mozilla/mozprofile/prefs.js
is equivalent to [._MOZILLA.MOZPROFILE].
Upgrading from a Previous Mozilla Kit
If the Mozilla M0.9.4 kit is currently installed, it will be removed automatically before
the M0.9.5 kit is installed.
If the most recent Mozilla kit you installed is earlier than M0.6, the installation procedure
displays a warning that M0.9.5 is a lower version of an installed product.
(M0.6 started a new numbering scheme.
For example, M18, using the previous numbering scheme, is an earlier kit than M0.9.5.)
During the installation you are asked if you want to continue.
Press Return to remove the previous kit and
to continue installing M0.9.5.
Downloading and Installing Mozilla
Downloading the Kit
The Mozilla for OpenVMS software is available for the Alpha platform
as a compressed self-extracting file.
Please fill out and submit the Mozilla for OpenVMS
registration form. You will receive an email message with the
URL of the location of the kit to download.
The size of the compressed kit is 49,282 blocks.
The expanded kit will occupy 134,176 blocks.
Expanding the Kit
To expand the Mozilla for OpenVMS self-extracting file,
enter the following command:
$ RUN MOZILLA-OPENVMS-ALPHA-M095.SFX_AXPEXE
|
The system expands the file and names the decompressed file
CPQ-AXPVMS-MOZILLA-M0009-5-1.PCSI.
Do not rename this file.
Note: If you expand the kit on an ODS-5 disk, the filename defaults to
lowercase. PCSI requires all uppercase characters. Rename the file to the same
name, but containing all uppercase characters, before you begin the installation.
After you expand the Mozilla kit, you can delete the .SFX_AXPEXE file.
Alternatively, you can first install
Mozilla, then delete the .PCSI file, and keep the small .SFX_AXPEXE file
in case you need to re-install the Mozilla kit.
Installing Mozilla
Use the following procedure to start the installation.
Note: If many users want to run Mozilla on the same
system, they can all run from the same installation. User specific information
is maintained in a user profile, and these are stored in each user's
SYS$LOGIN tree.
You must install Mozilla into a top-level directory. If you do not accept
the PCSI default destination, make sure that you do not attempt to install
Mozilla into a sub-directory.
To install the Mozilla for OpenVMS Alpha kit, enter the following command:
$ PRODUCT INSTALL MOZILLA /SOURCE=KITS
|
For a description of the features you can request with the PRODUCT
INSTALL command when starting an installation such as running the IVP,
purging files, and configuring the installation, see the POLYCENTER
Software Installation Utility User's Guide.
As the installation procedure progresses, the system displays
the following information.
The following product has been selected:
CPQ AXPVMS MOZILLA M0.9.5 Layered Product
Do you want to continue? [YES]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
CPQ AXPVMS MOZILLA M0.9.5
* This product does not have any configuration options.
Mozilla for OpenVMS Alpha
You MUST confirm that the required ECOs are installed!
Please review the list of ECOs documented in the Release Notes.
Do you want to continue? [YES]
Execution phase starting ...
%PCSI-W-VERINS, the installation of product CPQ AXPVMS MOZILLA M0.9.5
-PCSI-W-VERREM, will remove current product CPQ AXPVMS MOZILLA M0.9.4
Do you want to continue? [YES]
The following product will be installed to destination:
CPQ AXPVMS MOZILLA M0.9.5 DISK$ALPHASYS:[VMS$COMMON.]
The following product will be removed from destination:
CPQ AXPVMS MOZILLA M0.9.4 DISK$ALPHASYS:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
The following product has been installed:
CPQ AXPVMS MOZILLA M0.9.5 Layered Product
The following product has been removed:
CPQ AXPVMS MOZILLA M0.9.4 Layered Product
$
|
Stopping and Restarting the Installation
Use the following procedure to stop and restart the installation:
- To stop the procedure at any time, press Ctrl/Y.
- Enter the DCL command PRODUCT REMOVE to reverse any changes to the
system that occurred during the partial installation. This deletes all
files created up to that point and causes the installation procedure to
exit.
- Go back to the beginning of the installation procedure to restart
the installation.
Installing the Mozilla Images
After you install Mozilla using the PRODUCT INSTALL command,
you can also optionally install the Mozilla images. There are two benefits to installing the images:
- If several users on the same system are using Mozilla, you make
better use of system resources and improve performance.
- Installing the images avoids the problem of running out of Process
Sections (described in
Account Quotas and System
Parameters.)
If you install the images, the problem is eliminated.
To install the Mozilla images, run the command file INSTALL.COM
(which resides in the Mozilla root directory). For example:
$ SET DEFAULT SYS$COMMON:[MOZILLA]
$ @INSTALL
|
Approximately 218 global sections and 67,488 global pages are
required to install the Mozilla images.
If you want to uninstall the Mozilla images, enter the following:
$ SET DEFAULT SYS$COMMON:[MOZILLA]
$ @INSTALL REMOVE
|
Running Mozilla
Invoking Mozilla-bin
The main Mozilla application in the kit
is Mozilla-bin (formerly named apprunner).
Mozilla-bin is the full browser with
extensions, and closely resembles Netscape Communicator.™
Mozilla-bin contains:
- Navigator -- Web Browser
- Composer -- HTML page editor
- Messenger -- Mail client
- Newsgroups -- News client
You invoke the Mozilla-bin application through the supplied
MOZILLA.COM command
file. To invoke Mozilla-bin, enter the following:
$ @SYS$COMMON:[MOZILLA]MOZILLA
|
This assumes that you installed the kit to the default location. If you directed
PCSI to install to a different location, then your command to start MOZILLA
will contain a different disk or directory.
You can also pass arguments to the application. For example:
$ @SYS$COMMON:[MOZILLA]MOZILLA "http://www.openvms.compaq.com"
$ @SYS$COMMON:[MOZILLA]MOZILLA "-edit"
$ @SYS$COMMON:[MOZILLA]MOZILLA """-ProfileManager"""
|
Note that any argument that is case-sensitive (such as ProfileManager
in the previous example) must be enclosed in three sets of
quotation marks.
When you run Mozilla, the system must have approximately 336
global pages and one global section available. A check is made
when you invoke Mozilla. If these requirements are not met, a warning
is issued and terminating Mozilla is recommended.
When running Mozilla, you will see messages similar
to the following appear in the terminal output. These are normal for this release.
$ @sys$common:[mozilla]mozilla
Starting mozilla-bin...
Purging Mozilla user files...
$
|
Many other messages are displayed when using the Navigator, Mail/News and
Composer components of Mozilla. This is normal for this milestone release.
Setting Up a Helper Application (Example: Adobe™ Acrobat™
Viewer for Java™)
Mozilla for OpenVMS includes support for helper applications.
The following example shows how to set up the the Adobe Acrobat Viewer (for Java) on
OpenVMS Alpha as a helper application.
After completing these steps, when Mozilla encounters a PDF file it will
automatically invoke the Acrobat Viewer to display the
contents of the PDF file.
- Install the the Adobe
Acrobat Viewer
(for Java) on OpenVMS Alpha and check that the
viewer is functioning correctly.
-
Create the following file, PDF.COM, in the directory where you
have installed the viewer. (The file acrobat.jar should already be
in this directory.)
$ sv = f$verify(0)
$ adobe_jar_file = "/dka0/adobeacrobatviewer/acrobat.jar"
$ @sys$manager:java$setup
$ cp = f$trnlnm("classpath") + ":" + adobe_jar_file
$ define /user classpath "''cp'"
$ sv = f$verify(sv)
$ if "''p2'" .nes. "" then p1 = p2
$ java -mx32m "com.adobe.acrobat.Viewer" 'p1'
$ exit
|
-
Modify the second line of PDF.COM for your system. The value of adobe_jar_file
must be the UNIX-style full file specification of
the ACROBAT.JAR file. This example uses /dka0/adobeacrobatviewer/acrobat.jar,
which is the UNIX-style format of
DKA0:[ADOBEACROBATVIEWER].
-
Make sure that the file protection of PDF.COM allows users access to it.
For example:
$ SET FILE /PROTECTION=WORLD:READ DKA0:[ADOBEACROBATVIEWER]PDF.COM
|
-
The command file PDF.COM can now be used to view any PDF file.
Test that you have PDF.COM set up correctly before you configure
Mozilla.
$ SET DEFAULT DKA0:[ADOBEACROBATVIEWER]
$ @PDF HELP.PDF
|
-
Configure Mozilla for the helper application by following these steps:
-
Start Mozilla
-
From the menu bar, select "Edit" and then "Preferences..."
-
From the Navigator section, select "Helper Applications"
-
In the "Helper Applications" area, select "New Type" and enter:
Description of type: PDF
File extension: PDF
MIME type: application/pdf
Application to use: DKA0:[ADOBEACROBATVIEWER]PDF
Note that if your viewer directory is not DKA0:[ADOBEACROBATVIEWER],
change this value to the correct directory specification.
Also note that you can enter the file specification in either OpenVMS or
UNIX syntax, or you can use the Choose button to locate
your application.
-
Click on OK to close the New Type window
-
Click on OK to close the Preferences window
Release Notes
This section contains notes on the current release of Mozilla.
Performance Notes
This section contains notes on how to improve the performance of Mozilla.
- Enable Caching
In previous milestone releases of Mozilla for OpenVMS,
Compaq recommended disabling the disk cache to improve performance.
This is no longer necessary. If you previously disabled the
disk cache, you should now enable it.
To enable the disk cache:
-
Select Edit | Preferences
-
In the pop-up preferences panel, click on the arrowhead next to Advanced
-
In the Advanced list, select Cache
-
Set the disk cache size to 5000 KBytes
-
Select OK
Frequently Asked Questions (FAQ)
This section contains frequently asked questions about Mozilla
for OpenVMS Alpha.
Netscape 6 and
Communicator 5
Q: What is Netscape 6 and what happened to
Communicator Version 5.0?
A:
Netscape 6 (Version 6.1) is the name of the current release of the
Netscape browser. (The names Navigator and Communicator are no longer used.)
Netscape has moved from Communicator Version 4.7 to Netscape 6.
There is no Communicator V5.0.
Differences between
Mozilla and Netscape 6
Q: What are the differences between
Mozilla and Netscape 6?
A:
The Netscape 6 (V6.1) browser was built from the Mozilla M0.9.3 code base.
OpenVMS has a more recent baselevel of Mozilla available, M0.9.5.
Netscape 6.1 and Mozilla M0.9.3 are essentially the same browser,
except that Netscape
packaged some additional components with their offering.
Netscape 6 contains the following additional components:
- AOL Instant Messenger
- AOL branding
Netscape 6 on
OpenVMS
Q: Will Netscape 6 be available on OpenVMS?
A:
While the actual Netscape 6 product will not be available on OpenVMS,
the code base for Netscape 6.1 is Mozilla M0.9.3.
A newer release of Mozilla, M0.9.5, is currently available on OpenVMS.
Compaq also plans to release a supported version of Mozilla
Version 1.0 on OpenVMS.
Security for
Mozilla on OpenVMS
Q: When will security be available for Mozilla on OpenVMS?
A:
Security support is included in Mozilla M0.8 for OpenVMS,
released February 16, 2001, and in subsequent milestone releases.
See the Release Notes
section for more information.
Mozilla on
OpenVMS VAX
Q:
When will a version of Mozilla be available for VAX?
A:
There are currently no plans to port Mozilla to the VAX platform.
Java Support in
Mozilla
Q:
Is there support for Java in Mozilla for OpenVMS?
A:
See Support for Java in Mozilla for OpenVMS.
Mozilla doesn't start up -
decimal error
Q: Mozilla fails to start up. I see errors similar to this displayed:
nsNativeComponentLoader: SelfRegisterDll(/dka0/mozilla/components/libvcard.so)
Load FAILED with error: OpenVMS status is decimal 114690
|
A: One of the account quotas may be too low. See
Account Quotas and System Parameters, in
particular the discussion about the FILLM quota.
Mozilla doesn't start up -
process or global section error
Q: Mozilla fails to start up. I see errors similar to this displayed:
nsNativeComponentLoader: GetFactory(/dka0/mozilla/components/libnsgif.so)
Load FAILED with error: OpenVMS status is decimal 540
%SYSTEM-F-SECTBLFUL, process or global section table is full
|
A: You have a shortage of process sections.
See Account Quotas and System
Parameters for information about how to solve this problem.
Can't open new DECterms
Q: After running Mozilla, I can't open any new DECterms.
Normal terminal sessions (for example, telnet) still work properly. Only a
reboot seems to fix the problem -- removing the installed components from
memory (INSTALL.COM REMOVE), or restarting X-Windows does not help. Other
X-Windows applications do not seem to be affected. What's going on?
A:
You are probably out of buffer object space. Try increasing the SYSGEN
parameter MAXBOBMEM.
Unable to open the
temporary file
Q: I can't send mail or create a page using
Composer. I see a message similar
to "Unable to open the temporary file." What's wrong?
A: Make sure that you do not have any logical
name or symbol definitions for tmp or tmpdir.
If you do, remove them.
Problem Reporting
Report all problems to Bugzilla.
Do not report
problems into the PTR system, or in newsgroups, or contact the
CSC about Mozilla (Mozilla is not a released
product).
Bugzilla
Mozilla has a bug reporting and tracking system named Bugzilla. This
system is used to track all Mozilla problems across all platforms, including
OpenVMS. For further information on Bugzilla, visit http://www.mozilla.org/bugs/.
Before entering any new problem report, please search the database
to make sure that the problem has not already been reported.
Mark OpenVMS specific
problems by setting the Platform to DEC and OS field to OpenVMS.
Back to Mozilla for OpenVMS Home Page
| 
![[Powered by - OpenVMS Alpha and Compaq Secure Web Server]](/images/csws_image.gif)