Mozilla™ for OpenVMS™ Alpha™

Installation Guide and Release Notes

April 19, 2002

Mozilla 1.0 Release Candidate 1 (A1.0)
CPQ-AXPVMS-MOZILLA-A0100--1.PCSI

Contents:

Before Installing Mozilla

• Hardware and Software Prerequisites
  
• Account Quotas and System Parameters
  
• Mozilla.org Release Notes
  
• Upgrading from a Previous Kit
  

Downloading and Installing Mozilla

• Downloading the Kit
  
• Expanding the Kit
  
• Installing Mozilla
  
• Stopping and Restarting the Installation
  
• Installing the Mozilla Images
  

Running Mozilla

• Invoking Mozilla-bin
  
• Setting Up a Helper Application
  (Example: Adobe™ Acrobat™ Viewer for Java™)

Release Notes

Frequently Asked Questions (FAQ)

Problem Reporting and Bugzilla

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.

The following software is required in order to successfully run Mozilla:

• OpenVMS Version 7.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
  • MultiNet

  Important: If you are running MultiNet V4.3A or lower, or TCPware V5.5-3 or lower, you must install a new LIBNSPR4.SO image in your Mozilla directory. See http://www.process.com/techsupport/mozilla.html for more information.

Important: If you are using Java via the Compaq Software Development Kit (SDK) for the OpenVMS Operating System, for the Java™ Platform with Compaq Secure Web Browser, you should add the PGFLQUOTA required for Compaq SDK to the Compaq Secure Web Browser requirement to obtain a total number. Do the same for the FILLM requirement. It is the total numbers that you must set in your SYSUAF entry.

The current Compaq SDK PGFLQUOTA requirement is 2,000,000. The current Compaq SDK FILLM requirement is 4,000. See the Compaq Software Development Kit (SDK) for the OpenVMS Operating System, for the Java™ Platform documentation page for more information.

• PGFLQUOTA

  PGFLQUOTA is the most important process quota to check. Following is an estimate of the PGFLQUOTA you need for Compaq Secure Web Browser:

  • 60,000 -- Starts Compaq Secure Web Browser and displays a simple page
  • 100,000 -- Displays several normal pages
  • 200,000 or more -- Runs Mail/News, Composer, and displays complex pages

• FILLM
  • Increase the account's FILLM to at least 200.

  If you use the supplied INSTALL.COM to install the Compaq Secure Web Browser images, the default FILLM of 100 is sufficient.

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 has provided release notes for 1.0 RC1.

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].

If the Mozilla M0.9.9 kit is currently installed, it will be removed automatically before the A1.0 kit is installed.

If the most recent Mozilla kit you installed is earlier than M0.6, the installation procedure displays a warning that A1.0 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 A1.0.) During the installation you are asked if you want to continue. Press Return to remove the previous kit and to continue installing A1.0.

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 55,295 blocks. The expanded kit will occupy 150,816 blocks.

To expand the Mozilla for OpenVMS self-extracting file, enter the following command:

$ RUN MOZILLA-OPENVMS-ALPHA-A100.SFX_AXPEXE

The system expands the file and names the decompressed file CPQ-AXPVMS-MOZILLA-A0100--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

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.

Use the following procedure to stop and restart the installation:

1. To stop the procedure at any time, press Ctrl/Y.

2. 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.

3. 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 46 global sections and 64,464 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

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.

This section contains notes on the current release of Mozilla.

• Current Release of Mozilla Supported Only on OpenVMS Version 7.2-1 and higher

  M0.9.5 is the last milestone release of Mozilla that is supported on OpenVMS Version 7.1-2 and earlier. The current release of Mozilla for OpenVMS is supported only on OpenVMS Alpha Version 7.2-1 or higher.

  Note: Although Mozilla can be installed and run on OpenVMS Version 7.1-2 systems, the official end of support date for Version 7.1-2 is December 31, 2001. Customers are encouraged to upgrade to a later version of OpenVMS, such as Version 7.2-2 or Version 7.3.
  
  

• Support for the Java™ platform in Mozilla for OpenVMS

  Mozilla for OpenVMS requires the Compaq Software Development Kit (SDK) v 1.3.1-1 for the OpenVMS Operating System, for the Java™ Platform, to run Java applets. Version 1.3.1-1 of the Compaq SDK contains the required OJI (Open JVM Integration) support.
  
  You can download the Compaq SDK from the Compaq Java for Alpha Systems software download page.
  
  For more information about OJI, see http://www.mozilla.org/oji/.
  

• UCX Version 4.2 No Longer Supported

  Beginning with Mozilla M0.9.1 for OpenVMS, UCX Version 4.2 is no longer supported, and Mozilla will not run on a UCX Version 4.2 stack.

  Mozilla for OpenVMS requires Compaq TCP/IP Services Version 5.0 for OpenVMS. See Hardware and Software Prerequisites for other (untested) TCP/IP networking products that you can use with Mozilla for OpenVMS.

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.2) 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.2) browser was built from the Mozilla M0.9.4 code base. OpenVMS has a more recent baselevel of Mozilla available, A1.0.

Netscape 6.2 and Mozilla M0.9.4 are essentially the same browser, except that Netscape includes AOL Instant Messenger and AOL branding with their offering.

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.2 is Mozilla M0.9.4. A newer release of Mozilla, A1.0, is currently available on OpenVMS. Compaq Secure Web Browser (CSWB) is the supported version of Mozilla on OpenVMS Alpha.

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: Yes. 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.

Report all problems to Bugzilla. Do not report problems into the OpenVMS PTR system, or in newsgroups, or contact the CSC about Mozilla.

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.