HP Secure Web Browser for OpenVMS Alpha
HP Secure Web Browser for OpenVMS Alpha (based on Mozilla)
Installation Guide and Release Notes
June 2006
Secure Web Browser Version 1.7-13 for OpenVMS Alpha
Based on Mozilla M1.7.13
CSWB-OPENVMS-ALPHA-V1713.SFX_AXPEXE
Contents:
Before Installing the Secure Web Browser
- Hardware and Software Prerequisites.
- Disk Space Requirements
- Memory Requirements
- Software Prerequisites
- Account Quotas and System Parameters
- mozilla.org Release Notes
Installing the Secure Web Browser
- Downloading the Kit
- Expanding the Kit
- Installation Procedure
- Stopping and Restarting the Installation
- Installing the Secure Web Browser Images
Running the Secure Web Browser
Release Notes
- Secure Web Browser kit includes GTK+ for OpenVMS and OpenVMS Porting Library
- IPv6 support disabled beginning in V1.2-1
- Using the Java plug-in with the Secure Web Browser
- Support for the interface to plug-ins and helper apps
- Integrating the Secure Web Browser on the CDE desktop
Known Problems and Restrictions
- Secure Web Browser fails to start up for non-privileged user
- Mail folders do not display if FILLM quota is low
- Mail sub-folders disappear after renaming parent folder (V1.2-1 and earlier only)
- Mail sub-folders do not work (V1.2-1 only)
- GENERIC_POLL messages and frequent hangs with
IPv6 support enabled (V1.2-1 and earlier only)
- Switching to or from full screen mode causes
browser to exit (V1.2-1 and earlier only)
Frequently Asked Questions (FAQ)
Support
Before Installing the Secure Web Browser
Hardware Prerequisites
The HP Secure Web Browser for OpenVMS Alpha is available
only on the Alpha platform. (The HP Secure Web Browser for OpenVMS I64
is also available for download from the
Secure Web Browser web site.)
If you encounter color problems when running the Secure
Web Browser 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 the Secure Web Browser
before you start the other application. These problems usually do not occur
on a 16 or 24-plane video mode system.
Disk Space Requirements
The HP Secure Web Browser for OpenVMS Alpha compressed self-extracting
archive contains 74,848 blocks. The expanded PCSI kit
requires an additional 150,000 blocks of working disk space to install.
Memory Requirements
For HP Secure Web Browser (SWB), based on Mozilla, the minimum memory requirement is 256
MB. However, 512 MB is highly recommended for more robust performance.
Software Prerequisites
The following software is required in order to
successfully run the Secure Web Browser:
- OpenVMS Alpha Version 7.3-2 or higher
- DECwindows MOTIF Version 1.3-1 or higher
- HP TCP/IP Services Version 5.4 or higher for OpenVMS
- Optional: Java™ Platform, Standard Edition, Development Kit (JDK)
v 1.3.1-1 or higher (needed to
use the Java plug-in with the Secure Web Browser)
The Secure Web Browser has been tested and verified
using HP TCP/IP Services for OpenVMS. HP 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.6
MultiNet Version 4.4
Important: The Secure Web Browser requires that local files be
in Stream_LF record format. Files of other record formats are not
supported and the results of attempting to use any such file is undefined.
Account Quotas
If you are using
Java™ Platform, Standard Edition, Development Kit (JDK) with the Secure Web
Browser, you
should add the PGFLQUOTA required for JDK to the 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 JDK PGFLQUOTA requirement is 2,000,000. The current
JDK FILLM requirement is 4,000. See the Java™ Platform, Standard Edition
documentation website
for more information.
- PGFLQUOTA
PGFLQUOTA
is the most important process quota to check. Following is an estimate of the
PGFLQUOTA you need for the Secure Web Browser:
- 60,000 -- Starts the 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 by 2N where N is
the total number of mail folders you have, or to 200, whichever is higher.
Note: The FILLM quota of a process should always be less than the
SYSGEN CHANNELCNT parameter. Care must be taken when
increasing FILLM, and if necessary, CHANNELCNT must also be increased.
If
you use the supplied INSTALL.COM to install the Secure Web Browser
images, the default FILLM of 100 is sufficient.
See The FAQ section -
insufficient resources for operation error
for information about setting the amount of virtual memory available
to your DECwindows X server process.
System Parameters
The Secure Web Browser
requires a relatively large number of process sections, so you may find that
you have an insufficient number. (Note: If you install the
Secure Web Browser images after you install the Secure Web Browser
kit, you can avoid this problem completely. See Installing the Secure Web Browser
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 Secure Web Browser
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
The Secure Web Browser is based on Mozilla M1.7.13. Mozilla.org has provided
release notes for M1.7.13.
The release notes contain
sections about Mozilla on Windows®, Mac®, and UNIX®. The Secure Web
Browser 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].
Installing the Secure Web Browser
Downloading the Kit
The Secure Web Browser kit is included with the OpenVMS I64
and OpenVMS Alpha layered product distributions. A compressed,
self-extracting file is also available for
download from the
Secure Web Browser website.
Beginning with the Secure Web Browser V1.4, GTK+ for OpenVMS and
the OpenVMS Porting Library are included in the Secure Web Browser
self-extracting file. See the Release Notes for more information.
The size of the compressed Secure Web Browser Version 1.7-13 kit is
52,385 blocks. The expanded Secure Web Browser kit will occupy
141,648 blocks. The expanded GTK+ for OpenVMS kit will occupy 6768 blocks.
The expanded OpenVMS Porting Library kit will occupy 352 blocks.
Expanding the Kit
Expand the Secure Web Browser self-extracting
file by entering the following command:
$ RUN CSWB-OPENVMS-ALPHA-V1713.SFX_AXPEXE
The system expands the file and names the decompressed
files as follows. Do not rename these files.
UnZipSFX 5.41 of 16 February 2006, by Info-ZIP (
http://www.info-zip.org).
This self-extracting archive file contains PCSI kits for:
- Secure Web Browser (CSWB)
- GTK+
- OpenVMS Porting Library (OPL)
Once the PCSI files are extracted, use the PRODUCT INSTALL command to
install CSWB. If you don't already have the required versions of
GTK+ and OPL installed, they will be automatically installed too.
inflating: CPQ-AXPVMS-CSWB-V0107-13-1.PCSI$COMPRESSED
inflating: CPQ-AXPVMS-CSWB-V0107-13-1.PCSI$COMPRESSED_ESW
inflating: CPQ-AXPVMS-GTK-V0102-10-1.PCSI$COMPRESSED
inflating: CPQ-AXPVMS-GTK-V0102-10-1.PCSI$COMPRESSED_ESW
inflating: CPQ-AXPVMS-OPL-V0100-0A9-1.PCSI$COMPRESSED
inflating: CPQ-AXPVMS-OPL-V0100-0A9-1.PCSI$COMPRESSED_ESW
$
After you expand the Secure Web Browser kit, you can delete
the .SFX_AXPEXE file. Alternatively, you can first install
the Secure Web Browser, then delete the .PCSI files, and
keep the smaller .SFX_AXPEXE file in case you need to
re-install the kit.
Installation Procedure
Use the following procedure to start the installation.
Note: Multiple users can run the Secure Web Browser on the same system.
You need to install the Secure Web Browser only once.
User specific information is maintained in a user profile, and these are
stored in each user's SYS$LOGIN tree.
You must install the Secure Web Browser into a
top-level directory. If you do not accept the PCSI default destination, make
sure that you do not attempt to install the Secure Web Browser into a
subdirectory.
To install the Secure Web Browser for OpenVMS Alpha
kit, enter the following command:
$ PRODUCT INSTALL CSWB
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.
Performing product kit validation ...
%PCSI-I-VALPASSED, validation of WATER$DKB100:[000000.CSWB]CPQ-AXPVMSCSWB-
V0107-13-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VALPASSED, validation of WATER$DKB100:[000000.CSWB]CPQ-AXPVMSGTK-
V0102-10-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VALPASSED, validation of WATER$DKB100:[000000.CSWB]CPQ-AXPVMSOPL-
V0100-0A9-1.PCSI$COMPRESSED;1 succeeded
The following product has been selected:
CPQ AXPVMS CSWB V1.7-13 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 CSWB V1.7-13
Do you want the defaults for all options? [YES]
Secure Web Browser (SWB) for OpenVMS Alpha
CPQ AXPVMS GTK V1.2-10
GTK+ for OpenVMS Alpha
CPQ AXPVMS OPL V1.0-0A9
OpenVMS Porting Library for OpenVMS Alpha
Do you want to review the options? [NO]
Execution phase starting ...
The following products will be installed to destinations:
CPQ AXPVMS CSWB V1.7-13 DISK$V0732:[VMS$COMMON.]
CPQ AXPVMS GTK V1.2-10 DISK$V0732:[VMS$COMMON.]
CPQ AXPVMS OPL V1.0-0A9 DISK$V0732:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
The following products have been installed:
CPQ AXPVMS CSWB V1.7-13 Layered Product
CPQ AXPVMS GTK V1.2-10 Layered Product
CPQ AXPVMS OPL V1.0-0A9 Layered Product
$
If the product is installed on OpenVMS Alpha V7.3-2 or V8.2, the output looks similar to the following:
$ prod install cswb
The following product has been selected:
CPQ AXPVMS CSWB V1.7-13 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 CSWB V1.7-13
Do you want the defaults for all options? [YES]
Secure Web Browser (SWB) for OpenVMS Alpha
CPQ AXPVMS GTK V1.2-10
GTK+ for OpenVMS Alpha
CPQ AXPVMS OPL V1.0-0A9
OpenVMS Porting Library for OpenVMS Alpha
Do you want to review the options? [NO]
Execution phase starting ...
The following products will be installed to destinations:
CPQ AXPVMS CSWB V1.7-13 DISK$ALPHA732P5:[VMS$COMMON.]
CPQ AXPVMS GTK V1.2-10 DISK$ALPHA732P5:[VMS$COMMON.]
CPQ AXPVMS OPL V1.0-0A9 DISK$ALPHA732P5:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...50%...60%...70%...80%...90%...100%
The following products have been installed:
CPQ AXPVMS CSWB V1.7-13 Layered Product
CPQ AXPVMS GTK V1.2-10 Layered Product
CPQ AXPVMS OPL V1.0-0A9 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 Secure Web Browser Images
After you install the Secure Web Browser using the PRODUCT INSTALL command, you can also optionally
install the Secure Web Browser images. There are two benefits to
installing the images:
- If several users on the same
system are using the Secure Web Browser, 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.
Approximately 190 global
sections and 64,576 global pages are required to install the Secure
Web Browser images.
To install the Secure Web Browser images, run the command file INSTALL.COM
(which resides in
the Secure Web Browser root directory). For example:
$ SET DEFAULT SYS$COMMON:[CSWB]
$ @INSTALL
You can also use the INSTALL.COM procedure to REPLACE (update) the Secure Web Browser
images if they have been previously installed. To re-install the Secure Web Browser images, enter the following commands:
$ SET DEFAULT SYS$COMMON:[CSWB]
$ @INSTALL REPLACE
If you want to uninstall the Secure Web Browser
images, enter the following:
$ SET DEFAULT SYS$COMMON:[CSWB]
$ @INSTALL REMOVE
Running the Secure Web Browser
The Secure Web Browser is a full browser with extensions, and closely resembles
Netscape 7. The Secure Web Browser contains:
- Navigator -- Web browser
- Composer -- HTML page editor
- Messenger -- Mail client
- Newsgroups -- News client
You invoke the Secure Web Browser application through the supplied MOZILLA.COM
command file. To invoke the Secure Web Browser, enter the following:
$ @SYS$COMMON:[CSWB]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 the Secure Web Browser will contain a different disk or
directory.
You can also pass arguments to the application. For
example:
$ @SYS$COMMON:[CSWB]MOZILLA
$ @SYS$COMMON:[CSWB]MOZILLA -edit
$ @SYS$COMMON:[CSWB]MOZILLA -ProfileManager
When you run the Secure Web Browser, the system must
have approximately 336 global pages and one global section available. A
check is made when you invoke the Secure Web Browser. If these
requirements are not met, a warning is issued and terminating the Secure
Web Browser is recommended.
The Secure Web Browser requires that local files be
in Stream_LF record format. Files of other record formats are not
supported and the results of attempting to use any such file are undefined.
When running the Secure Web Browser, you will see
messages similar to the following appear in the terminal output.
$ @SYS$COMMON:[CSWB]MOZILLA
Starting mozilla-bin...
Many other messages are displayed when using the
Navigator, Mail/News and Composer components of the Secure Web Browser.
This is normal behavior.
Release Notes
This section contains notes on the current release of the Secure Web Browser.
- Secure Web Browser Kit Includes GTK+ for OpenVMS
and OpenVMS Porting Library
Beginning with Version 1.4 of the Secure Web Browser,
GTK+
for OpenVMS and the
OpenVMS Porting Library are included in
the Secure Web Browser self-extracting file. When you expand the self-extracting file,
three PCSI kits are placed in your current directory.
Install only the Secure Web Browser kit. During the Secure Web Browser installation,
the installation procedure checks to see if the required versions of
GTK+ for OpenVMS and the OpenVMS Porting Library reside on your system.
If they do not, the installation procedure installs or updates GTK+ and OPL
along with the Secure Web Browser.
- IPv6 Support Disabled Beginning in Version 1.2-1
IPv6 support is disabled by default beginning with the Secure Web Browser Version 1.2-1.
Earlier versions of SWS 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.
OpenVMS Engineering is working on a permanent solution for this problem.
- Using the Java Plug-in with the Secure Web
Browser
To use the Java plug-in with the Secure Web Browser, perform the following steps:
- Download and install the JDK from the
Java Technology Software download page.
-
Copy the OJI plug-in from the
Java installation to [CSWB.PLUGINS], where x is the version of the JDK you installed:
$ copy /prot=W:RE SYS$COMMON:[JAVA$14x.JRE.PLUGIN.ALPHA.NS610]
LIBJAVAPLUGIN_OJI.SO - SYS$COMMON:[CSWB.PLUGINS]
-
Run the Java setup command for the version of Java you installed.
For example, if you installed the Java SDK v 1.4.2, enter the following command:
$ @SYS$STARTUP:JAVA$142_SETUP
-
Restart the Secure Web Browser.
Refer to the
Installing
and Running Mozilla and the Plug-In section of the SDK User Guide for more information.
Note: The Secure Web Browser for OpenVMS requires the Java™
Platform, Development Kit (JDK) v 1.3.1-1 and later to run Java applets.
Support for the JDK v 1.4-0 and
higher is included only in the Secure Web Browser Version 1.2-1 and higher.
The Secure Web
Browser Versions 1.2-1 and 1.0 work with the SDK v 1.3.1-1.
- Support for the Interface to
Plug-ins and Helper Apps in the Secure Web
Browser
The Secure Web Browser contains support for several plug-ins and helper apps,
including a Java/OJI plug-in, a Flash plug-in, a Mozplugger plug-in,
and a PDF viewer helper app. (Currently
only the Java/OJI plug-in is supported by HP.)
See the Secure
Web Browser Plug-ins page for more information.
- Integrating the Secure Web Browser on the CDE Desktop
After you have installed the Secure Web Browser, you can
optionally integrate the Secure Web Browser onto the CDE (Common Desktop Environment) desktop.
Integrating the Secure Web Browser allows you to
invoke the Secure Web Browser using an icon instead of entering a command into a terminal window.
These instructions describe two ways you can integrate the Secure Web Browser
onto the CDE desktop:
-
As a desktop icon. In this case, you start the Secure Web Browser
by double-clicking on the icon.
-
As an entry in the control panel. In this case, you simply select
the Secure Web Browser icon.
In addition, you can optionally download the Secure Web Browser icon set.
If you choose not to download the Secure Web Browser icon set,
CDE assigns a default icon for the Secure Web Browser.
Downloading the Secure Web Browser Icon Set
To download the Secure Web Browser icon set and stage them for integration,
follow these steps. If you do not want to use the Secure Web Browser icon set, proceed to
the next section.
-
Download the UNZIP utility for OpenVMS Alpha,
if you have not previously done so.
-
In your SYS$LOGIN directory, create the subdirectory [.DT.ICONS] if the subdirectory does not
already exist.
-
Download the file CDE_ICONS_V2.ZIP.
-
Unzip the contents of CDE_ICONS_V2.ZIP into the [.DT.ICONS] subdirectory. Use
the -V option to preserve OpenVMS file attributes.
Making the Secure Web Browser a "Known Application" to CDE
To make CDE aware of the Secure Web Browser application, follow these steps:
-
Start the Application Manager (click the icon of a filing cabinet with a pencil).
-
In the Application Manager window, double-click the Desktop Apps icon.
-
In the Desktop Apps window, double-click the Create Action icon.
-
Fill in the Create Action panel:
-
Enter Secure Web Browser in the Action Name field.
-
If you chose not to use the Secure Web Browser 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 Find Set...
-
In the left pane, double-click
cde$home_defaults:[icons]
-
In the right pane, click the Secure Web Browser icon.
-
Click OK.
-
In the Command When Action Is Opened field, enter the following:
@sys$common:[cswb]mozilla/output=sys$login:cswb.log
Note: If you installed the Secure Web Browser to a non-default location, this command
will be different on your system.
-
In the Help Text For Action Icon field, enter Secure Web Browser 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).
- Add Icons to the Secure Web Browser related file types (optional):
If you want to see HTML files with a Secure Web Browser icon in the File Manager,
perform the following steps. This step is optional; you can skip this section and proceed to step 6.
-
Click the Advanced button on the lower left side of the "Create Action" window.
-
Click the Add button next to the "Datatypes That Use This Action" pane.
A new "Add Datatype" window will open.
-
Click the Edit button. A new window will open.
-
Click the small button to the left of the "Name Pattern" box.
-
Fill in *.html in the "Name Pattern" box.
-
Click OK. You are back in the Add Datatype window.
-
Click the "Find Set" button.
-
Choose the Icon File you would like to use.
-
Click OK
-
Click OK in the Add Datatype window.
-
Repeat for all datatypes you would like
to give the Secure Web Browser icon. Suggested filetypes are:
*.html, *.htm, *.shtml, *.xhtml, and *.css.
If you want the selected file automatically opened in the
newly created Secure Web Browser 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 Secure Web Browser icon to your desktop, and you now
want to enable the Secure Web Browser 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 CSWB.dt file in the right pane.
-
Select this file and click OK.
-
When you have finished filling in the Create Action panel, select File -> Save.
-
Select File -> Exit to exit the Create Action application.
-
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 the Secure Web Browser Appear as a Desktop
Icon or Entry in the Control Panel
The Secure Web Browser is now a "known application" to CDE. To make the Secure Web Browser appear as a desktop
icon or appear as an entry in the Control Panel, perform the following steps.
-
Start the File Manager (click the icon of a filing cabinet with files).
-
If necessary, scroll down the window until you see the Secure Web Browser icon.
-
To create a desktop icon, drag the Secure Web Browser icon from the File Manager onto the desktop.
-
To add the Secure Web Browser to the control panel:
-
Expand the sub-panel to which you want to add the Secure Web Browser (for example, Personal Applications) by
clicking on the upwards facing triangle above the sub-panel.
-
Drag the Secure Web Browser icon from the File Manager onto the Install icon.
The Secure Web Browser is now integrated onto your CDE desktop.
Known Problems and Restrictions
- Secure Web Browser Fails to Start Up For Non-Privileged User
All versions of the Secure Web Browser contain a problem where
the browser will not start up for a
non-privileged user, but does start and run for a privileged user.
When this problem occurs, an error message may or may not be displayed.
For example:
$ @sys$common:[cswb]mozilla
Starting mozilla-bin...
LoadPlugin: failed to initialize shared library
/sys$common/mozilla/plugins/libnullplugin.so
[OpenVMS status is decimal 114690]
$
This problem occurs when the file protection of the COMPREG.DAT
file is incorrect. When the Secure Web Browser is first installed, the
file [.COMPONENTS]COMPREG.DAT
is correctly protected as W:RE.
This protection is required for a non-privileged user to
run the Secure Web Browser. However, after a privileged user has run
the Secure Web Browser,
the protection
on COMPREG.DAT is changed to W:. A non-privileged user is then unable to run
the Secure Web Browser.
To correct the problem, change the protection on COMPREG.DAT to W:RE as follows:
$ SET DEFAULT SYS$COMMON:[CSWB.COMPONENTS]
$ SET FILE /PROT=W:RE COMPREG.DAT
See Bugzilla 208909
for more information. A permanent correction to this problem will be available
in a future release of the Secure Web Browser.
- 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.
- Mail Sub-Folders Do Not Work (Version 1.2-1 only)
Version 1.2-1 of the Secure Web Browser contains a bug where mail sub-folders
do not work properly, and cannot be deleted. You should not create mail
sub-folders, but you can create additional mail folders.
This problem is corrected beginning in Version 1.4. See
Bugzilla 185838
for more information.
- Mail Sub-Folders Disappear After Renaming Parent Folder (Version 1.2-1 and earlier only)
If you rename a mail folder that contains sub-folders, the sub-folders
disappear. This is caused by a problem in the way the rename operation is performed on OpenVMS.
This problem is fixed beginning in Version 1.4.
If you rename the folder back to its original name, the lost sub-folders reappear.
If you want to keep the new folder name, you can re-attach the lost
sub-folders as follows.
In this example the old folder name is old,
the new folder name is new, and the profile being used is named profile.
(If you have not created additional profiles, your only profile is named default).
$! make sure Secure Web Browser is not running
$!
$ SET DEFAULT SYS$LOGIN
$ DIRECTORY [._MOZILLA.profile...MAIL...]old_SBD.DIR
$ SET DEFAULT <directory where old_SBD.DIR resides>
$ RENAME old_SBD.DIR new_SBD.DIR
$!
$! restart Secure Web Browser
- Switching to or from Full Screen Mode Causes Browser to Exit (Version 1.2-1 and earlier only)
When switching to or from full screen mode, the Secure Web Browser 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 the Secure Web Browser.
- GENERIC_POLL Messages and Frequent Hangs (Version 1.2-1 and earlier only)
If the Secure Web 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 Version 1.2-1, IPv6 support is disabled by default. (See
IPv6 Support is Disabled
Beginning in V1.2-1 for
more information.)
In Version 1.0 of the Secure Web Browser, 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 the Secure Web Browser.
Frequently Asked
Questions (FAQ)
This section contains frequently asked questions about the Secure Web Browser for OpenVMS Alpha.
Differences between Secure Web Browser and Netscape
Q:
What are the differences between
the Secure Web Browser and Netscape?
A:
There are very few differences. The Secure Web Browser and Netscape 7 are both based
on Mozilla code.
Differences between Secure Web Browser and Mozilla
Q:
What are the differences between
the Secure Web Browser and Mozilla for OpenVMS?
A:
The Secure Web Browser is supported by Hewlett-Packard, but
Mozilla for OpenVMS Alpha is not supported.
You can download
Mozilla for OpenVMS Alpha from the OpenVMS web site.
Java Support in the Secure Web Browser
Q:
Is there support for Java in the Secure Web Browser for OpenVMS?
A:
Yes. See Support for
the Java™ Platform in the Secure Web Browser for OpenVMS.
Secure Web Browser on OpenVMS VAX
Q:
Will a version of the Secure
Web Browser be available on VAX systems?
A:
There are currently no plans to
port the Secure Web Browser to the VAX platform.
Installing the Secure Web Browser and Mozilla on the same
system
Q:
Can I install Mozilla on the same
system as the Secure Web Browser?
A:
Yes. Both the Secure Web Browser and Mozilla can
coexist on the same system. User profiles are common to the Secure Web Browser and Mozilla so
your mail, bookmarks, and so on that you have on the Secure Web Browser will be available on
Mozilla. The reverse is also true: mail and bookmarks on Mozilla are
available on the Secure Web Browser.
Changing the date format
Q:
A date field in the Secure Web Browser is always displayed in MM/DD/YY format. Can I change it?
A:
Yes. The format that the Secure Web Browser 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 the Secure Web Browser. For example:
$ DEFINE LC_ALL FR_FR_ISO8859-1
To list all the locales available on your system, enter the following:
$ LOCALE SHOW PUBLIC
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
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.
Secure Web Browser terminates with Gdk-ERROR **:
BadAlloc (insufficient resources for operation)
Q: Why am I getting an insufficient resources
for operation error, which causes the Secure Web Browser to terminate?
A: If the Secure Web Browser 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. 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 similar to the following:
$ 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.
Secure Web Browser fails to load the Java plug-in at startup
Q:
Why can't the browser load the Java plug-in
after I installed Java and copied the OJI plug-in file? I get this error:
$ @mozilla
Starting MOZILLA-BIN...
LoadPlugin: failed to initialize shared library
/dkb300/vms$common/mozilla/plugins/libjavaplugin_oji.so
[OpenVMS status is decimal 98962]
A:
You need to set up Java before starting the Secure Web Browser.
For JDK v 1.3.1, enter the following command:
$ @sys$startup:java$131_setup
Secure Web Browser doesn't start up - decimal error
Q:
The Secure Web Browser 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.
Secure Web Browser doesn't start up - process or global
section error
Q: The Secure Web Browser 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 the Secure Web
Browser, 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.
Support
V1.7-13 Customer Release Version
Support for the HP Secure Web Browser Version 1.7-13 for OpenVMS Alpha is
provided under existing OpenVMS service agreements through standard support
channels.
See
HP support for
information about the Secure Web Browser support.
If you do not have a support contract and are not interested in acquiring one,
you can informally exchange information with other users in the OpenVMS
newsgroup comp.os.vms.
For technical feedback to the Secure Web Browser for OpenVMS engineering
team, please
send mail via the form on the SWB Support page at
http://www.hp.com/products/openvms/securewebbrowser/.
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
» Return to the Secure Web Browser for OpenVMS home page
