HP Secure Web Browser for
OpenVMS Integrity servers (based on SeaMonkey)
Installation
Guide and Release Notes
Secure Web Browser
V1.1-12 for OpenVMS Integrity servers
Based on SeaMonkey V1.1.12
HP-I64VMS-CSWB-V0101-12-1.PCSI_SFXEXE
December
2008
Contents
Before Installing
the Secure Web Browser
Hardware and
Software Prerequisites
Disk Space
Requirements
Memory
Requirements
Software
Prerequisites
Account Quotas
System Parameters
SeaMonkey-Project.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
Using the Java Plug-In with the Secure Web Browser
Integrating the Secure Web Browser on the CDE Desktop
Downloading the Secure Web Browser Icon Set
Making the Secure Web Browser a "Known Application" to CDE
Making the Secure Web Browser Appear as a Desktop Icon or
Entry in the Control Panel
Known Problems and
Restrictions
Secure Web Browser Must Be Installed on System Device
Secure Web Browser
Fails to Start Up for Non-privileged User
Mail Folders Do
Not Display if FILLM Quota Is Low
Installation warnings when
installing SWB V1.1-12 to replace SWB
V1.7-13
Frequently Asked
Questions (FAQs)
Support
Before Installing the Secure Web Browser
Hardware Prerequisites
The HP Secure Web Browser for OpenVMS
is available on the Integrity server platforms.
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
PCSI kit requires approximately 750,000 blocks of working disk space to
install. The size of the
compressed Secure Web Browser for OpenVMS Integrity
server kit
is 426972 blocks.
Memory Requirements
For
HP Secure Web Browser (SWB), based on SeaMonkey, 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 Version 8.2-1 or higher
- DECwindows MOTIF Version 1.5 ECO3 or higher
- HP TCP/IP Services Version 5.5 or higher for
OpenVMS
- Optional: Java Development Kit (JDK) for the OpenVMS
Operating System, for the Java Platform v 5.0-3 or higher
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 are
undefined.
Account Quotas
If you are
using Java via the Java Development Kit (JDK) for the OpenVMS Operating
System, for the Java Platform 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,097,152. The current JDK FILLM requirement is
4,096.
See the JDK for the
OpenVMS Operating System, for the Java Platform documentation
website for more information.
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 FAQs 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.
SeaMonkey-Project.org Release Notes
The Secure Web
Browser is based on Seamonkey V1.1.12. Seamonkey has provided release notes for
V1.1.12 at
http://www.seamonkey-project.org/releases/seamonkey1.1.12/
The release
notes contain sections about SeaMonkey 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.
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 software is
available for the Integrity servers platforms as compressed self-extracting
files.
The Secure Web
Browser is included with the OpenVMS Integrity servers and OpenVMS Alpha layered product
distributions. It is
also available for download from the Secure Web Browser
web site at
http://h71000.www7.hp.com/openvms/products/ips/cswbs/cswbs.html
Expanding the Kit
To expand the Secure Web Browser self-extracting
file, enter the following command:
$ RUN HP-I64VMS-CSWB-V0101-12-1.PCSI_SFXEXE
The system
expands the file and names the decompressed files as follows. Do not rename
these files.
UnZipSFX 5.42 of 14 January 2001, by
Info-ZIP (Zip-Bugs@lists.wku.edu).
inflating: HP-I64VMS-CSWB-V0101-12-1.PCSI$COMPRESSED
inflating: HP-I64VMS-CSWB-V0101-12-1.PCSI$COMPRESSED_ESW
$
On
OpenVMS Integrity servers, the Secure Web Browser kit includes all of the required images.
Unlike the Secure Web Browser
on OpenVMS Alpha, there is no separate GTK+ kit
or OpenVMS Porting Library kit.
After you
expand the Secure Web Browser
kit, you can delete the .PCSI_SFXEXE file. Alternatively, you can first install
the Secure Web Browser, then delete the .PCSI file and keep the
smaller .PCSI_SFXEXE file in case you need to re-install the kit.
Installation
Procedure
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 kit,
enter the following command:
$ PRODUCT INSTALL CSWB
Note: If you
install the Secure Web Browser on an ODS-2 disk volume, you will see PCSI
errors. See
the Known Problems and Restrictions section for more information.
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 AIR$DKA0:[000000.CSWB]
HP-I64VMS-CSWB-V0101-12-1.PCSI$COMPRESSED;1 succeeded
The following product has been selected:
HP I64VMS CSWB V1.1-12 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.
HP I64VMS CSWB V1.1-12
* This product does not have any configuration options.
CSWB for OpenVMS IA64
Execution phase starting ...
The following product will be installed to destination:
HP I64VMS CSWB V1.1-12 DISK$XBAZ_BL2:[VMS$COMMON.]
Portion done: 0%...10%...40%...50%...60%...70%...80%...90%...100%
The following product has been installed:
HP I64VMS CSWB V1.1-12 Layered Product
HP I64VMS CSWB V1.1-12
To start CSWB use the command "@SYS$COMMON:[CSWB]MOZILLA"
If the product is installed on OpenVMS Integrity servers V8.2-1, the output looks similar to the following:
$ PRODUCT INSTALL CSWB
The following product has been selected:
HP I64VMS CSWB V1.1-12 Layered Product
Do you want to continue? [YES]
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.
HP I64VMS CSWB V1.1-12
* This product does not have any configuration options.
CSWB for OpenVMS IA64
Execution phase starting ...
The following product will be installed to destination:
HP I64VMS CSWB V1.1-12 DISK$I64SYS:[VMS$COMMON.]
Portion done: 0%...10%...40%...50%...60%...70%...80%...90%...100%
The following product has been installed:
HP I64VMS CSWB V1.1-12 Layered Product
HP I64VMS CSWB V1.1-12
To start CSWB use the command "@SYS$COMMON:[CSWB]MOZILLA"
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 396
global sections and 446,000 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 reinstall 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 400 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 seamonkey-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.
GTK+ for OpenVMS
and the OpenVMS Porting
Library are included in the Secure
Web Browser self-extracting file.
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 is disabled by default. You can manually enable IPv6 support by
defining the logical MOZILLA_IPV6 to
any value before running the Secure Web
Browser.
Note: Enabling IPv6 support may cause you to experience excessive GENERIC_POLL
messages and frequent hangs.
To use the Java plug-in with Secure Web Browser, perform the following steps:
1.
Download and
install the Java (JDK) from the Java Technology Software download page.
(http://h18012.www1.hp.com/java/download/index.html)
2.
Copy the OJI
plug-in from the Java installation to [CSWB.PLUGINS]. For example,
$copy /protection=W:RE - SYS$COMMON:[JAVA$150.JRE.PLUGIN.IA64.NS610]
LIBJAVAPLUGIN_OJI.SO - SYS$COMMON:[CSWB.PLUGINS] 3.
Run the Java
setup command for the version of the JDK you installed. For example, if you
installed the Java JDK v 5.0-3, enter the following command:
$ @SYS$STARTUP:JAVA$150_SETUP
4.
Restart the
Secure Web Browser.
Refer to the JDK User Guide for more information.
The Secure Web Browser for OpenVMS requires the HP Java Development Kit (JDK)
v 5.0-3 for the OpenVMS Operating System, for the Java Platform, to run Java
applets. Version 5.0-3 and later releases of the JDK contain the required
OJI (Open JVM Integration) support.
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:
o
As a desktop icon. In this case, you start the Secure Web Browser by double-clicking
on the icon.
o
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.
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.
1.
In your SYS$LOGIN directory, create the subdirectory [.DT.ICONS]
if the subdirectory does not already exist.
2.
Download the file CDE_ICONS_V2.ZIP
from
http://h71000.www7.hp.com/openvms/products/ips/cswb/CDE_ICONS_V2.ZIP 3.
Unzip the contents of CDE_ICONS_V2.ZIP into the [.DT.ICONS]
subdirectory. Use the -V option
to preserve OpenVMS file attributes.
To make CDE aware of the Secure
Web Browser application, follow these steps:
1. Start the Application Manager (click the icon
of a filing cabinet with a pencil).
2. In the Application Manger window,
double-click the Desktop Apps icon.
3. In the Desktop Apps window,
double-click the Create Action icon.
4. 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).
5. 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 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.
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.
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.
1. Start the File Manager (click the icon of a
filing cabinet with files).
2. If necessary, scroll down the window
until you see the Secure Web Browser
icon.
3. To create a desktop icon, drag the Secure Web Browser icon from the File
Manager
onto the desktop.
4. 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 Must Be Installed on a System Device
The Secure Web Browser
for OpenVMS Integrity servers must be installed on a system device. If you attempt to install SWB
on a non-system device, the installation fails with the following error:
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
%SET-E-SEARCHFAIL, error searching for SYS$COMMON:[CSWB.COMPONENTS]*.DAT;
-RMS-E-FNF, file not found
%PCSI-E-EXEPSTFAIL, product supplied EXECUTE POSTINSTALL procedure failed
-SET-E-SEARCHFAIL, error searching for !AS
%PCSI-E-OPFAILED, operation failed
Terminating is strongly recommended. Do you want to terminate? [YES]
·
Secure Web Browser Fails to Start Up For Non-Privileged User
The Secure Web Browser contains 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 seamonkey-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.
SeamonkeyV1.0 was built based on the Mozilla
V1.8b1 code. The PCSI always considers V1.7-13 as the latest version instead of
V1.1-12 and the following warning message is displayed when you try to install SWB
V1.1-12 replacing SWB V1.7-13:
%PCSI-W-VERLOW, you have selected a lower version of an
installed product
-PCSI-W-VERINS, the installation of product HP I64VMS CSWB V1.1-12
-PCSI-W-VERREM, will remove current product HP I64VMS CSWB V1.7-13
Do you want to continue? [YES]
Frequently Asked Questions (FAQ) This section
contains frequently asked questions about the Secure Web Browser for OpenVMS.
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 HP, but Mozilla for OpenVMS Alpha is not supported. The
Secure Web Browser V1.1-12 is based on SeaMonkey V1.1.12. You can
download Mozilla for
OpenVMS Alpha from the OpenVMS web site at
http://h71000.www7.hp.com/openvms/products/ips/register_mozilla.html. Java Support
in the Secure Web Browser
Q: Is there support for
Java in the Secure Web Browser for
OpenVMS?
A: Yes.
See the Using the Java Plug-in with the Secure Web Browser section. 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.
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, 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
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 plugin at startup Q: Why can't the browser
load the Java plug-in after I installed Java and copied the OJI plugin file? I
get this error: $ @mozilla
Starting SEAMONKEY-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 Java v 1.5.0-3, enter the following command: $ @sys$startup:java$150_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.1-12
Customer Release Version
- Support for
the Secure Web Browser for OpenVMS is provided by HP under OpenVMS Integrity
servers Foundation
Operating Environment (FOE) service agreements through standard support
channels.
- Download is
a courtesy distribution mechanism for the Secure Web Browser for OpenVMS.
Kits or
updates other than security patch kits obtained via download are
unsupported.
- The OpenVMS
Integrity servers Operating Environments media kit is the official
distribution mechanism for the Secure
Web Browser for OpenVMS. Supported kits and updates must be obtained from
this mechanism or from
software product update services.
- 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 Secure Web Browser Support page at
http://h71000.www7.hp.com/openvms/products/ips/cswbs/cswbs.html.
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
| 
