HP says that the secure web browser "based on mozilla" is no longer supported and we should move to the secure web browser "based on seamonkey" (CSWB 1.1-12.) OK, I don't mind doing that, but I have to say their update instructions are pretty poor.
It appears that the new PCSI will install into the same directory, SYS$COMMON:[CSWB], that was used by the old product. This strikes me as a rather bad idea, yet they don't tell you to remove the old version before installing the new.
Anyone have specific thoughts or experience to report on this? As I understand it, SeaMonkey is in fact still Mozilla under a new name, since the Mozilla folks stopped enhancing it in favor of Firefox and Thunderbird, but another group took over the source tree and continued development. That should mean that upgrading one right over the other should be OK, but undoing it could be a mess if it fails.
The explanation is at the Mozilla.org and related sites and is close to what you have.
The old version installed in [VMS$COMMON.MOZILLA] and the new version installs into [VMS$COMMON.CSWB], so you can run them both.
I have not been using either recently because I had to relocate my VMS system to a different room than I am usually at, and the Vista system does not have the up time needed for stable X11 displays, and the X11VNC port is not working well enough either.
Both browser products seem to use the same profile, and I seem to recall having some problems with using the CSWB one.
It also apparently is not smart enough to check to see if a VMS binary is available, and is nagging for an upgrade to versions that have not been built for VMS.
That would make sense, but seems not to be so. The old Mozilla-based browser was installed in SYS$COMMON:[CSWB] already. I did find a tiny reference in the release notes for the Seamonkey version saying that the new version number is lower than the old version number, so PCSI will complain about overlaying a newer program with an older one, but you should just let it go ahead.
Indeed that's what happens. The new version installs right into the same directory, replacing the old.
The Seamonkey browser requires significantly more resources. It runs slower. The killing blow, though, is the fact that no matter what I do, I can't get it to load the Java plugin. I've increased quotas as instructed, run AUTOGEN to raise WSMAX, etc. And yes, I am running the JAVA$150_SETUP script before starting the browser. It worked with Mozilla, but fails with Seamonkey.
I finally got disgusted and reinstalled the old Mozilla version, which nicely overlaid the "new but unimproved" version of Seamonkey. And, I'm happy to report, Java works again without changing anything else.
This is on a PWS433au so it's normal for it to run slower than the newer Alphas, but the memory slots are maxed out so it isn't really short of RAM. There's plenty of disk space (36Gb SCSI drive, 90% empty.)
The error message Seamonkey puts out is "Failed to load LIBJAVAPLUGIN_OJI.SO - VMS status code is decimal 540." Supposedly that means you ran out of global sections but the expected matching error about that condition does not appear.
malmberg December 12 2017 HPE only makes the most current version of OpenVMS Alpha / IA64 /VAX available to hobbyists. When I had access to the Alliance 1 program it was the same. No public downloads are allowed by HPE.
nmbonao December 08 2017 Is anybody knows OpenVMS 8.2 version downloadable version? or CD copy? Thank you very much
aarommes December 02 2017 Bitcoin and Blockchain enthusiasts ( plus distributed computing ) please connec / reply: http://www.openvmshobbyis t.com/forum/viewthread.ph p?forum_id=130&thread_id= 2991
malmberg September 10 2017 https://sourceforge.net/p /vms-ports/wiki/VMSInstal lation/ For the most part just use VMS 6.1 media instead of 7.3. But why run the older release?
DoeveR August 07 2017 Where can I find the write up on running VMS 6.1 using the simh emulator?
Bart March 20 2017 Happy to have found my password again!