Downloading and Installing Mozilla

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). Approximately 188 global sections and 69,280 global pages are required to install the Mozilla images.

For example:

$ SET DEFAULT SYS$COMMON:[MOZILLA] $ @INSTALL

You can also use the INSTALL.COM procedure to REPLACE (update) the Mozilla images if they have been previously installed.

If you want to re-install the Mozilla images, enter the following commands:

$ SET DEFAULT SYS$COMMON:[MOZILLA] $ @INSTALL REPLACE

If you want to UNINSTALL the Mozilla images, enter the following commands:

$ SET DEFAULT SYS$COMMON:[MOZILLA] $ @INSTALL REMOVE

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

This section contains notes on the current releases of Mozilla.

• Error in M1.4 Kit Released July 2, 2003

  The M1.4 kit was repackaged on July 9, 2003, because of a problem in the July 2, 2003 kit. The July 2 kit (build ID 2003062310) contains a ZIP error in one of the JAR files, which causes the Advanced Preferences panel to not load. (See Bugzilla bug 211757 for more details.)

  The July 9 kit (build ID 2003070807) corrects this problem. If you downloaded the M1.4 kit between July 2 and July 8, 2003, please download and reinstall the kit.

• IPv6 Support Disabled in M1.3b

  IPv6 support is disabled by default beginning with Mozilla for OpenVMS M1.3b. Earlier versions of Mozilla enabled IPv6 support by default.

  You can manually enable IPv6 support by defining the logical MOZILLA_IPV6 to any value before running Mozilla.

  Note: Enabling IPv6 support may cause you to experience excessive GENERIC_POLL messages and frequent hangs. HP OpenVMS Engineering is working on a permanent solution for this problem.

• Mozilla Kit Includes GTK+ for OpenVMS and OpenVMS Porting Library

  Beginning with Mozilla for OpenVMS M1.3a, GTK+ for OpenVMS and the OpenVMS Porting Library are included in the Mozilla for OpenVMS self-extracting file. When you expand the self-extracting file, three PCSI kits are placed in your target directory.

  Install only the Mozilla kit. During the Mozilla installation, the installation procedure checks to see if the latest versions of GTK+ for OpenVMS and the OpenVMS Porting Library reside on your system. If they do not, the installation procedure installs GTK+ and OPL along with Mozilla.

• Mozilla Supported Only on OpenVMS Version 7.2-2 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-2 or higher.
  
  

• Support for the Java™ platform in Mozilla for OpenVMS

  Mozilla for OpenVMS requires the 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 and later releases of the SDK contain the required OJI (Open JVM Integration) support.

  All versions of Mozilla for OpenVMS, including M1.4, work with the SDK v 1.3.1-1. Support for the SDK v 1.4-0 and higher is included only in Mozilla for OpenVMS M1.3 and higher.

  You can download the SDK from the Java for Alpha Systems software download page.
  

  Important: After you install the SDK, copy the OJI plugin from the Java area to the Mozilla area, then restart Mozilla. Refer to the documentation available from the SDK Documentation website for more information. Specifically, see the Using the Plug-In section of the SDK v1.3.1 release notes or the SDK v1.4.1 release notes.

• Support for the Interface to Plugins and Helper Apps in Mozilla for OpenVMS

  Mozilla for OpenVMS contains support for the plugin interface to several plugins and helper apps. The following plugins and helper apps are available separately: a Java/OJI plugin, a Flash plugin, and a PDF viewer helper app.

  • Java Plugin

    The SDK Java functionality is implemented in Mozilla for OpenVMS through the Java/OJI plugin. See Support for the Java™ Platform in Mozilla for OpenVMS for more information.

  • Flash Plugin

    The Flash plugin for OpenVMS is provided by Mark Berryman, who ported Olivier Debon's open source flash player. The Flash plugin for OpenVMS currently supports most of Flash 4 but does not support the actionscript features of Flash 5. Support for sound is underway.

    Download the Flash plugin from ftp://mvb.saic.com/extra/libflashplugin.so.

    Then, copy the LIBFLASHPLUGIN.SO file into SYS$COMMON:[MOZILLA.PLUGINS] (or into the [.PLUGINS] directory of the location where you installed Mozilla for OpenVMS) and restart your browser.

    Feedback is welcome; please send mail to Mark.Berryman@Mvb.Saic.com.

  • XPDF Helper App

    XPDF is a freeware PDF viewer. Version 0.9.2 is available on the OpenVMS Freeware CD. (More recent versions are available from http://decwarch.free.fr/pspdf#XPDF.)

    After you download and install XPDF, you must create a command file that Mozilla for OpenVMS uses to invoke XPDF. (Mozilla passes the PDF filespec in UNIX format, and XPDF requires it to be in OpenVMS format).

    Assuming XPDF.EXE resides in DKA0:[TOOLS], create the command file DKA0:[TOOLS]XPDF.COM and insert the following commands:

    $ f = "sys$scratch:" + p2 - "/tmp/" $ mcr dka0:[tools]xpdf 'f' $ exit

    Next, start Mozilla for OpenVMS and click on Edit -> Preferences, Navigator, Helper Applications. In the pane on the right, click "New Type..." and then fill in the following information:

    Description of type: PDF File extension: pdf MIME Type: application/pdf Application to use: /dka0/tools/xpdf.com

    Click on OK to add the new Helper App and then OK again to exit Preferences. The next time you try to view a PDF file, the XPDF viewer will be launched.

• 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 HP 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.

• Integrating Mozilla for OpenVMS on the CDE Desktop

  After you have installed Mozilla for OpenVMS, you can optionally integrate Mozilla onto the CDE (Common Desktop Environment) desktop.

  Integrating Mozilla allows you to invoke Mozilla using an icon instead of entering a command into a terminal window.

  These instructions describe two ways you can integrate Mozilla for OpenVMS onto the CDE desktop:

  • As a desktop icon. In this case, you start Mozilla for OpenVMS by double-clicking on the icon.

  • As an entry in the control panel. In this case, you simply select the Mozilla for OpenVMS icon.

  In addition, you can optionally download the Mozilla for OpenVMS icon set. If you choose not to download the Mozilla for OpenVMS icon set, CDE assigns a default icon for Mozilla for OpenVMS.

  Downloading the Mozilla for OpenVMS Icon Set

  To download the Mozilla for OpenVMS icon set and stage them for integration, follow these steps. If you do not want to use the Mozilla for OpenVMS icon set, proceed to the next section.

  1. Download the UNZIP utility for OpenVMS Alpha, if you have not previously done so.

  2. In your SYS$LOGIN directory, create the subdirectory [.DT.ICONS] if the subdirectory does not already exist.

  3. Download the file CDE_ICONS_V2.ZIP.

  4. Unzip the contents of CDE_ICONS_V2.ZIP into the [.DT.ICONS] subdirectory. Use the -V option to preserve OpenVMS file attributes.

  Making Mozilla for OpenVMS a "Known Application" to CDE

  To make CDE aware of the Mozilla for OpenVMS application, follow these steps:

  1. Start the Application Manager (click on the icon of a filing cabinet with a pencil).

  2. In the Application Manger window, double-click on the Desktop Apps icon.

  3. In the Desktop Apps window, double-click on the Create Action icon.

  4. Fill in the Create Action panel:

     • Enter Mozilla in the Action Name field.

     • If you chose not to use the Mozilla for OpenVMS icon set (and you did not download the zip file), ignore the following four steps and proceed to the Command When Action Is Opened step.

     • In the Action Icons area, Click on Find Set...

     • In the left pane, double-click on cde$home_defaults:[icons]

     • In the right pane, click on the Mozilla icon (a red head).

     • Click on OK.

     • In the Command When Action Is Opened field, enter the following:

       @sys$common:[mozilla]mozilla/output=sys$login:mozilla.log

       Note: If you installed Mozilla for OpenVMS to a non-default location, this command will be different on your system.

     • In the Help Text For Action Icon field, enter Mozilla is an open source browser (or other help text you want to appear when help is requested).

     • In the Window Type field, select Graphical (X-Window).

  5. Add Icons to Mozilla related file types (optional):

     If you want to see HTML files with a Mozilla icon in the File Manager, perform the following steps. This step is optional; you can skip this section and proceed to step 6.

     • Click on the Advanced button on the lower left side of the "Create Action" window.

     • Click on the Add button next to the "Datatypes That Use This Action" pane. A new "Add Datatype" window will open.

     • Click on the Edit button. A new window will open.

     • Click on the small button to the left of the "Name Pattern" box.

     • Fill in *.html in the "Name Pattern" box.

     • Click on OK. You are back in the Add Datatype window.

     • Click on the "Find Set" button.

     • Choose the Icon File you would like to use.

     • Click on OK

     • Click on OK in the Add Datatype window.

     • Repeat for all datatypes you would like to give the Mozilla icon. Suggested filetypes are: *.html, *.htm, *.shtml, *.xhtml, and *.css.

     If you want the selected file automatically opened in the newly created Mozilla window, download MOZILLA_DECW.COM or create MOZILLA_DECW.COM. (The file must reside in the same directory as MOZILLA.COM.) Modify the Command When Action Is Opened field to contain the following line:

     @sys$common:[cswb]mozilla_decw/output=sys$login:cswb.log $1

     Note: If you previously added the Mozilla icon to your desktop, and you now want to enable the Mozilla icon in the File Manager, execute these steps:

     • Perform the steps 1, 2 and 3 above.

     • In the "Create Action" window select File -> Open. You should see a Mozilla.dt file in the right pane.

     • Select this file and click on OK.

  6. When you have finished filling in the Create Action panel, select File -> Save.

  7. Select File -> Exit to exit the Create Action application.

  8. Log out and terminate the CDE session, and then log back in again starting a new CDE session. This is required so that CDE can see the changes you made.

  Making Mozilla for OpenVMS Appear as a Desktop Icon or Entry in the Control Panel

  Mozilla for OpenVMS is now a "known application" to CDE. To make Mozilla for OpenVMS appear as a desktop icon or appear as an entry in the Control Panel, perform the following steps.

  1. Start the File Manager (click on the icon of a filing cabinet with files).

  2. If necessary, scroll down the window until you see the Mozilla for OpenVMS icon.

  3. To create a desktop icon, drag the Mozilla for OpenVMS icon from the File Manager onto the desktop.

  4. To add Mozilla for OpenVMS to the control panel:

     • Expand the sub-panel to which you want to add Mozilla for OpenVMS (for example, Personal Applications) by clicking on the upwards facing triangle above the sub-panel.

     • Drag the Mozilla for OpenVMS icon from the File Manager onto the Install Icon icon.

  Mozilla for OpenVMS is now integrated onto your CDE desktop.

Known Problems and Restrictions

• Mail Sub-Folders Do Not Work

  Mozilla for OpenVMS (all versions) contains a bug where mail sub-folders do not work properly, and cannot be deleted. To avoid the problem, do not create sub-folders in mail. You can, however, create additional mail folders.

  See Bugzilla 185838 for more information.

• Mail Folders Do Not Display if FILLM Quota is Low

  If some of your mail folders do not display, it is possible that you do not have sufficient FILLM quota. See Account Quotas and System Parameters for more information.

• GENERIC_POLL Messages and Frequent Hangs with IPv6 Support Enabled (M1.3a and earlier only)

  If your Mozilla for OpenVMS M1.3a or earlier browser frequently fails to load a page, or hangs, and messages similar to the following appear on the screen, then you are being affected by a networking problem that only seems to manifest itself on fast processors:

  GENERIC_POLL: unknown condition, errno=16 vaxc$errno=708 GENERIC_POLL: unknown condition, errno=4 vaxc$errno=2096 GENERIC_POLL: unknown condition, errno=16 vaxc$errno=708 GENERIC_POLL: warning, unable to find the bad FDs GENERIC_POLL: warning, expected 1 events but found 2

  This problem occurs only when IPv6 is enabled. Beginning with M1.3b, IPv6 support is disabled by default. (See IPv6 Support is Disabled for more information.)

  On M1.3a and earlier, use the following workaround to prevent the problem. This workaround disables IPv6 support. You cannot use this workaround if you require IPv6 functionality. Edit MOZILLA.COM and find the line:

  $ define /user GETIPNODEBYNAME TCPIP$GETIPNODEBYNAME

  Change the definition to:

  $ define /user GETIPNODEBYNAME NO_SUCH_NAME

  Then restart Mozilla for OpenVMS.

• Switching to or from Full Screen Mode Causes Browser to Exit (M1.2.1 and earlier only)

  When switching to or from full screen mode, Mozilla for OpenVMS will sometimes issue one of the following error messages and exit:

  Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter) serial 12538 error_code 9 request_code 14 minor_code 0 Gdk-ERROR **: BadWindow (invalid Window parameter) serial 6453 error_code 3 request_code 15 minor_code 0

  This is a known problem in the Mozilla M1.2-1 code base. This problem will be fixed in the next release of Mozilla for OpenVMS.

• Error When Downloading File: "You have chosen to download a file of type: "#1" [#2] from" (M1.0 only)

  Mozilla for OpenVMS 1.0 contains a problem that occurs when you try download a file. This problem does not occur in releases of Mozilla for OpenVMS higher than 1.0.

  Problem: A dialog box appears that reads:

  "You have chosen to download a file of type: "#1" [#2] from"

  If you select the "Save" option, the file is not always saved.

  Workaround: Shift-click on the file, which displays the Save As dialog box.

  Correction: Perform the following steps to correct the problem.

  1. Download VMS_JACKETS.SFX_EXE.

  2. Enter the following command to expand the file into the VMS_JACKETS.SO image.

     $ RUN VMS_JACKETS.SFX_EXE

  3. Copy VMS_JACKETS.SO into SYS$COMMON:[MOZILLA].

  4. If you installed the CSWB images using the INSTALL command file, replace VMS_JACKETS.SO by entering:

     $ INSTALL REPLACE SYS$COMMON:[MOZILLA]VMS_JACKETS.SO

  The VMS_JACKETS.SO image can be used with both Mozilla 1.0 and Compaq Secure Web Browser V1.0. The problem is corrected in Mozilla 1.1 Alpha (and higher) releases.

This section contains frequently asked questions about Mozilla for OpenVMS Alpha.

Differences between Mozilla and HP Secure Web Browser

Q: What are the differences between Mozilla for OpenVMS and HP Secure Web Browser for OpenVMS?

A: HP Secure Web Browser is supported by HP, and Mozilla for OpenVMS Alpha is not supported by HP. The most current release of Mozilla is usually available in Mozilla for OpenVMS, because new baselevels of Mozilla for OpenVMS are released by HP shortly after new baselevels are released by Mozilla.org. New versions of the HP Secure Web Browser are released less frequently.

Differences between Mozilla and Netscape

Q: What are the differences between Mozilla and Netscape?

A: The Netscape 7 PR1 browser was built from the Mozilla M1.0 RC2 code base. The Netscape 6 (V6.2) browser was built from the Mozilla M0.9.4 code base. OpenVMS has a more recent baselevels of Mozilla available.

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.

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 the Release Notes section Support for Java in Mozilla for OpenVMS.

Changing Date Format

Q: A date field in Mozilla is always displayed in MM/DD/YY format. Can I change it?

A: Yes. The format that Mozilla uses to display the date is determined by the locale, which you can change. For example, to set the locale to French, which causes dates to be displayed in DD.MM.YY format, define LC_ALL before running Mozilla. For example:

$ DEFINE LC_ALL FR_FR_ISO8859-1

To list all the locales available on your system, enter the following:

$ LOCALE SHOW PUBLIC

GENERIC_POLL: unknown condition, errno=4 vaxc$errno=2096

Q: From time to time I see the GENERIC_POLL message above. What's the problem?

A: There is no problem. The message, which typically appears when a java applet starts up, is purely informational and can be ignored.

PAGE UP key doesn't work

Q: Why doesn't the PAGE UP key work as expected?

A: The key bindings for the six keys in the middle of the keyboard (which include PAGE UP or REMOVE) assume that you have an LK style keyboard. If you have a PC style keyboard, you should define the logical GTK_KEY_MAPPING_MODE to 2 before running Mozilla. For example:

$ DEFINE GTK_KEY_MAPPING_MODE 2

Valid values for GTK_KEY_MAPPING_MODE are:

0 - no mapping
1 - LK keyboard (default)
2 - PC keyboard

Mozilla terminates with Gdk-ERROR **: BadAlloc (insufficient resources for operation)

Q: Why am I getting an insufficient resources for operation error, which causes Mozilla to terminate?

A: If Mozilla terminates with an error similar to the following:

Gdk-ERROR **: BadAlloc (insufficient resources for operation) serial 3993912 error_code 11 request_code 53 minor_code 0 Gdk-ERROR **: BadDrawable (invalid Pixmap or Window parameter) serial 3993915 error_code 9 request_code 70 minor_code 0

It is likely that you need to increase the amount of virtual memory available to your DECwindows X server process. The default is 100,000 pages. HP recommends that you set the value of virtual memory to 200,000 pages.

To change this number, edit the file SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM and add a line such as:

$ decw$server_page_file == 200000

If the file SYS$STARTUP:DECW$PRIVATE_SERVER_SETUP.COM does not already exist, create it and add the preceding line.

The amount of virtual memory required depends on many factors. In general, the higher the resolution of your display and the higher the number of planes used for color (8, 16, or 24), the more virtual memory the X server needs.

After saving the file, restart your X server for the change to take effect. To restart your X server, enter the following command:

$ @sys$startup:decw$startup restart

Note: Restarting the X server will terminate all of your running DECwindows programs.

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

MOZILLA_DECW.COM

$! Command file to run Mozilla/CSWB and accept a VMS filespec as P1. $! This command file must exist in the root Mozilla/CSWB directory $! (where MOZILLA.COM resides). $! $ moz_self = f$envir("procedure") $ moz_dir = f$parse(moz_self,,,"device") + f$parse(moz_self,,,"directory") $! $ if p1 .eqs. "" $ then $ write sys$output "No argument passed in" $ @'moz_dir'mozilla $ else $ fs_vms = p1 $ fs_unix = "/" + f$parse(fs_vms,,,"device") - ":" $ fs_vms_dir = f$parse(fs_vms,,,"directory") - "[" - "]" - "<" - ">" $ i=0 $uloop: $ e=f$element(i,".",fs_vms_dir) $ if e .nes. "." $ then $ fs_unix = fs_unix + "/" + e $ i=i+1 $ goto uloop $ endif $ fs_unix = fs_unix + "/" +- f$parse(fs_vms,,,"name") + f$parse(fs_vms,,,"type") $ fs_unix = f$edit(fs_unix,"lowercase") $ write sys$output "VMS: ", fs_vms $ write sys$output "UNIX: ", fs_unix $ @'moz_dir'mozilla file://'fs_unix' $ endif $ exit

» back to Mozilla for OpenVMS home page