0. Mosaic 2.4 for VMS (release 2) This file describes a port of Mosaic 2.4 to VMS. This version has been generated and tested on VAXes running VMS 5.5-2 or OpenVMS 6.1 and on AXP machines using OpenVMS 1.5 or 6.1. The machines have used either UCX (2.0E or UCX 3.1) or MultiNet (3.2 or 3.3). Support for CMU/IP is in preparation. An earlier version had sup- port for PathWay provided by TWG. The files used there are still included but are not tested. The program has been compiled with VAX C and DEC C. The port is done for the basic Mosaic with WAIS support included from freeWAIS-0.3. This port has unfortunately been over half a year underway. It is based on my previous VMS port of Mosaic 2.0 and of course, on the Mosaic 2.4 fileset available from NCSA. Note that there is also a port done by Digital and available from gatekeeper.dec.com. This latter port will probably be included in VMS in some form in the future. I believe I have a few features not present in DEC's ver- sion, and I hope that my port also builds and runs equally well. But, you should make the choice! The file Mosaic-2_4-2.zip contains the sources from NCSA with my modifications. My changes are ifdef-ed with my signature (BSN) in a comment. Note that the file is a ZIP archive, so you need the UNZIP program to unpack it. If you have any problems with installing or running this program, feel welcome to write a note to me. 1. Before installation. - Make sure that you have DECWindows Motif and the Miscellaneous Utilities optional library. The latter is an optional part of the DECWindows Motif kit. You can check if it is present with SHOW LOGICAL XMU which should show something like "XMU" = "SYS$SYSROOT:[DECW$INCLUDE.XMU]" Check that the XMU directory contains a set of include files. If you do not have this software, stop here. - First unpack the archive. You need the UNZIP program for this. You can find ZIP/UNZIP sources at ftp.wku.edu and mirrors. - The sources have many defaults built in. Mosaic is using aux- illiary programs for viewing etc. The default definitions for these programs are in [.libwww2]HTInit.c There are many other resources defined in [.src]xresources.h Four of these can be defined in the scripts you will use when building, either MAKE_MOSAIC.COM or [.src]descrip.mms Make sure you do not remove any of the quotes, all of them are necessary:-( 1) You may want to define your own default home page for the homeDocument resource. Change HOME 2) Choose a print command appropriate to your site. Change PRINT_COMMAND 3) If you intend to read News with Mosaic you may define a DEFAULT_NEWS_HOST in MAKE_MOSAIC.COM or in [.libwww2]descrip.mms 4) Finally you should choose an appropriate Mail suffix. At CERN we use a mailer dxmint via DECnet and prefixVMSMail is set to "dxmint::". If you have PMDF or MX, this suffix should be "IN%" or "MX%" Mosaic puts in all the necessary quotes to satisfy VMS MAIL. Change MAIL_PREFIX Other defaults that you could consider changing are: 1) Instead of DECterm you may want to use xterm or what you have. See [.src]xresources.h 2) I have chosen gunzip for all uncompressing, you may want to change that. Also in [.src]xresources.h 3) If you have not installed ghostview and ghostscript you can use DECWindows VIEW as PostScript Previewer. You must then change [.libwww2]HTInit.c appr. line 180 where application/postscript is defined to gv. Change "gv %s" to "View/Interface=DECWindows/Format=PS %s" 4) You may want to put the file documents.menu somewhere else than in DECW$System_Defaults See [.src]xresources.h 5) You may like to start DECsound differently than I did See [.libwww2]HTInit.c - There could be some font problems. Most DEC X-servers still miss the Lucida fonts. Also, often the 17pt fonts used by Mosaic are missing. The fonts used are listed in xresources.h I have inserted ifdefs so that normally 17pt fonts are replaced by 18pt fonts, and Lucida by fixed. Check your server if this is really necessary. You can use xlsfonts for this. There is a version in SYS$COMMON:[SYSHLP.EXAMPLES.DECW.UTILS] if your system is correctly installed. 2. Installation Decide whether you want to build with MMS or just use the command file MAKE_MOSAIC.COM In the first case, check the various DESCRIP.MMS files. There is one in each directory, but the most important one is [.SRC]DESCRIP.MMS which has some defaults described above. Then build by $ @MAKE_MOSAIC_MMS or $ MMS/Ignore=Warning/Macro=... executed in the top directory. If you use MAKE_MOSAIC.COM, make any changes you might need (check the setting of HOME, PRINT_COMMAND, NEWSHOST and MAIL_PREFIX at the top) and then execute it: $ @Make_Mosaic In either case this should build everything. You should not get any errors or warnings. If you do I would like to know about it. However, if you are using UCX and get a list of unsatisfied externals, you can probably blame me. When linking to UCX on VAXes the UCX_VAX.OPT file is used. This includes UCX by referring to the object library SYS$LIBRARY:UCX$IPC.OLB/LIB On AXPs the corresponding option file UCX_AXP.OPT uses a shareable SYS$LIBRARY:UCX$IPC_SHR.EXE/SHARE If there are cases where this does not work I would very much like to hear about them. 3. Post-installation. Mosaic, like most programs using X, needs an application resource file. There is a colour and a mono version in Mosaic.Dat_Color and Mosaic.Dat_Mono. Check these, and move the appropriate one to your "applications defaults" directory with name SYS$COMMON:[DECW$DEFAULTS.USER]Mosaic.Dat However, you should make both files publicly available. Users, who want to customize more, should copy the appropriate file to DECW$USER_DEFAULTS (normally SYS$Login:) with name Mosaic.Dat and modify it further there. Mosaic is also using a file named documents.menu to configure one of the pull-down menus. Check this file, and then copy it to the location given in [.src]xresources.h 4. Post post-installation. You may find that you miss some auxilliary programs for uncompressing, viewing etc. You should be able to find most of what you need on Hunter Goatley's ftpserver at ftp.wku.edu in directory [.macro32.savesets], or at mirrors at many sites. Some other locations are: xv: ftp.cis.upenn.edu in the pub/xv directory. ghostscript: ftp.cs.wisc.edu in the /ghost/aladdin directory ghostview: pfc.mit.edu 5. Some more hints. You will also find much valuable information by reading the Mosaic Resources page (in the Documents menu). Some points that should be in a user's guide are: a) To read News: You must first define a News server. This can be done at compilation time (see above), or by defining a logical NNTPSERVER as the nodename of the server. You can then open newsreading using a URL like news:group, e.g. news:vmsnet.sources.d b) Mosaic can be controlled remotely. If you start the program with a -mbx switch it will act on commands sent to a mailbox named MOSAIC_username The logical name for the mailbox can also be set with an argument following a -mbx_name switch. Finally, the mailbox name can be entered in your group name table with a -mbx_grp switch, provided you have GRPNAM priv. The commands are defined and acted upon in the routine mo_process_external_directive in [.src]gui.c The possible commands are: goto|URL newwin pagedown pageup scrolldown scrollup flushimagecache backnode forwardnode reloaddocument reloadimages refresh iconify deiconify raise move resize The goto command must be followed by a vertical bar and then the URL of the page to display. The move and resize commands should be followed by a URL x|y, e.g. move:100|200 c) The HTFTP.c routine understands "long" listing from "normal" UNIX ftp servers, from Hunter Goatley's MadGoat ftp server and from MultiNet servers. If you find a server for which my HTFTP fails I would like to know. A URL starting with ftp://username:password@node can be used for ftp-ing from non-anonymous accounts. You must be extremely careful if you use this feature!! The password is displayed on your screen since it is part of the URL. It is also recorded in your MOSAIC.GLOBAL-HISTORY file! d) Mosaic may consume fairly much page file quota when expanding in-line images. Make sure that your AUTHORIZE pgflquo resourse is at least of the order of 40000 pages. If you have insufficient page file quota Mosaic will very likely crash sooner or later. And finally, do notify me if/when you find problems. If Mosaic crashes, please send me a mail describing how you used Mosaic just before the crash. What pages did you (try to) look at? Did you invoke Mosaic as a subprocess, as a detached process, or as a regular process? Did you have any problems compiling and linking? Give any other information you may find relevant too, and do remember do write your name:-) Enjoy! ==================================================================== I am grateful to several people who helped me test this port. In par- ticular I would like to mention Hunter Goatley, Jim Jennis and Martin Zinser who all pointed out bugs and flaws and gave me good advice. ==================================================================== Bjorn S. Nilsson, The Niels Bohr Institute, Copenhagen and ALEPH, CERN 7-Jan-1995. Email addresses: Niels Bohr Institute, Copenhagen: nilsson@nbi.dk (best choice) CERN: nilsson@alws.cern.ch http://alephinfo.cern.ch/@ALWHO?nilsson