 
All OpenVMS Freeware V7.0 FREEWARE_README.TXT Files
 
This file contains the contents of all FREEWARE_README.TXT files
from all of the volumes of Freeware V7.0.  Also please see
[000000]AAAREADME.TXT for a full listing of the packages present.
 
The contents of this file are generated by CREATE_FREEWARE_PACKAGE.COM
 

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[000TOOLS]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
000TOOLS, FREEWARE, Various Useful Tools

This directory contains a DEFINE_TOOLS.COM procedure used to
establish DCL foreign commands for a collection of useful DCL 
command procedures and executable images, and this particularly
contains the Unzip tools necessary to unpack the Zip archives.

This directory tree is duplicated on all OpenVMS Freeware disks.


+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[A2PS]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
A2PS, UTILITIES, Easily convert ASCII text files to Postscript for printing

Description: 	ASCII text to PostScript converter
Version: 	V4.0, 8-NOV-2004
Author: 	Various
Architecture: 	VAX,AXP,IA64
Size: 	266 blocks
Language: 	C
Released: 	8-NOV-2004

++++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[ANTIWORD-0_36]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
ANTIWORD,Miscellaneous, a MS Word document file reader/converter

Antiword 0.36 for VMS
Antiword is a MS Word document file reader, it extracts the plain text,
or converts it into a Postscript file.
Original Author: Adri van Os. Homepage: http://www.winfield.demon.nl/
Ported to VMS by Joseph Huber,Homepage: http://wwwvms.mppmu.mpg.de/~huber/pds/

Build instructions for VMS:
 Set default [.SRC]
 With GNU make (gmake) under DCL: Execute "(g)make -f makefile.vms" .
 With GNV bash shell: make -f makefile.vms_bash .
 With MMS or MMK , simply type "MMS" or "MMK" using the 
  DESCRIP.MMS  descriptor file provided .
 Without make or MMS, compile everything, except main_r, 
  then link main_u  and all other object files.
  (all commands are in vms_make.com).

Installation:
   define a foreign command pointing to antiword.exe
 or
   copy antiword.exe into dcl$path:
 Setup/font files:
 System-wide: copy the [.resources] files into the directory defined by 
  /usr/share/antiword
 or leave the [.resources] subdirectory in place, and let the user
 (or sys$sylogin) execute this procedure: antiword_setup.com
 Private: create directory [.ANTIWORD] in sys$login:
          copy the [.resources] files into the newly created directory.
 Usage:
 Produce a postscript file from a word-document:
   pipe antiword -p a4 file.doc >file.ps
A DCL commandfile in DCL$PATH directory does the postscript conversion 
and X11 display with Ghostscript in one go: wordviewer.com .
Use it in a commandline like this: wordviewer testdoc

Further info see antiword_vms.html.

Joseph.Huber at mppmu.mpg.de

+++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[ANTIWORD_Z]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++
 
Antiword_Z, Utilities, Convert MS Word documents to Text/PostScript

Installation

To build antiword just execute VMS_MAKE.COM which will simply build and link 
antiword from the sources.
In case you have GNU make installed, also make -f makefile.vms will do nicely.

Setup

Define the logical Antiwordhome to whereever you keep the files originally 
located in the [.Resources] subdirectory of the antiword source distribution. 
This contains files for fontname conversion between Windows and Postscript as 
well as character translation tables for various character encodings.

Mozilla

To use Antiword as a helper in Mozilla a small DCL is needed which first 
converts the file to text and then uses an editor to display it. The DCL as 
well as further intruction can be found in the Mozilla notes at 
http://zinser.no-ip.info/vms/sw/notes/mozilla.htmlx. 

The latest version of the OpenVMS port of Antiword should always be
accessible via

http://zinser.no-ip.info/vms/sw/antiword.htmlx

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[ASK_THE_WIZARD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
ASK_THE_WIZARD, MISCELLANEOUS, Ask The Wizard Answers

The zip archive contains almost 10,000 questions and answers from
the OpenVMS Ask The Wizard area, on a wide variety of OpenVMS topics.

For the Most current Wizard.Zip and related information, please visit:

    http://www.hp.com/go/openvms/wizard/


++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[BAT]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
BAT V1.10, UTILITIES, Easily submit multiple commands to batch queues

BAT V1.10 -- Submit multiple commands to a batch queue from DCL

This kit contains all the files necessary for installing the BAT
utility.  Requires VMS V5.0 or later.

BAT is designed to be invoked via a foreign command:

    $ BAT :== $disk:[directory]BAT.EXE

BAT lets you submit multiple commands to a batch queue easily and
quickly. For example, you can use:

    $ bat cc := cc/vaxc|mmk

or

    $ bat
    _Command: cc := cc/vax
    _Command: mmk
    _Command: ^Z
    $

to define CC for that batch job and then run MMK in the current
directory. BAT will automatically create the a temporary .COM file
that sets the default to the current directory and includes the
commands to be executed. The .COM file is then submitted to a batch
queue for processing.

BAT is written in BLISS. Complete sources are provided.
--------------------------------------------------------------------------------
Files in this directory:

AAAREADME.DOC			This file
AAAREADME.TOO			Change history
BAT.ALPHA_OLB			BAT object library (Alpha AXP)
BAT.HLP				On-line help file for BAT
BAT.OLB				BAT object library (VAX)
LINK.COM			Command procedure to link the executables

Files in [.SOURCE]:

BAT.B32				Source module for BAT
BAT.RNH				Source for BAT on-line help
BAT_CLD.CLD			CLI$ definition file for BAT
BAT_MSG.MSG			Messages used by BAT
BUILD_BAT.COM			Command procedure to build BAT
DESCRIP.MMS			Description file for building BAT
HG$GET_INPUT.B32		Smart LIB$GET_INPUT replacement

--------------------------------------------------------------------------------
CONTACTING THE AUTHOR

Comments, suggestions, and questions about this software can be directed to
the current maintainer at one of the following addresses:

Mail:	Hunter Goatley
	Process Software

E-mail:	goathunter@PROCESS.COM

--------------------------------------------------------------------------------
COPYRIGHT NOTICE

This software is COPYRIGHT  1991,2004, HUNTER GOATLEY. ALL RIGHTS RESERVED.
Permission is granted for not-for-profit redistribution, provided all source
and object code remain unchanged from the original distribution, and that
all copyright notices remain intact.

DISCLAIMER

This software is provided "AS IS".  The author makes no representations or
warranties with repsect to the software and specifically disclaim any implied
warranties of merchantability or fitness for any particular purpose.

+++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[BATCH_INFO]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++
 
BATCH_INFO, UTILITIES, SHOW PROCESS output and other info for a batch job 

This DCL command procedure allows you to obtain information about a
batch job without having to look up its PID. You only need to specify
the batch job's entry number. Optional qualifiers for the SHOW PROCESS
command can also be specified. 

The following information is provided:

SHOW ENTRY/FULL output
Process creation time
Current image
SHOW PROCESS output with or without qualifiers
SHOW SYSTEM/BATCH output

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[BIOSPORT]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
BIOSport, Utilities, BIOS Port Routines

BIOS Interrupt & Port I/O Routines      Created with PowerBASIC for DOS 3.50
Copyright (C) 2002 by B?la Valek        E-mail: bvalek2@freemail.hu
Version date: 10-20-2002

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

Miscellaneous from BIOS, Port, and Memory. BIOS-Port, not Bio-Sport... :)

 Routines are for: (see them listed at the end of this document)
==========
- SVGA graphics (see speed tests below)
- Bios data
- Direct Disk I/O
- Keyboard
- Paralel printer
- Rebooting
- Timer
The SUBs XYStr and XYStrBack use .FNT files. They are inefficient, but if you
look at the speed tests, it does not matters here. However, they can handle
DOS fonts of any vertical size, and 8 pixels wide.

This unit was originally created for personal purposes, it has no version
numbering. If you want the latest edition, get one with the latest version
date.
For more information on this unit or interrupts, refer to a BIOS manual.

 Files:
==========
- BIOSPORT.PBU   the unit
- BIOSPORT.BAS   the source
- BIOSPORT.INC   DECLAREs
- MEMORY  .INC   memory data
- EXAMPLE1.BAS   memory data example
- EXAMPLE2.BAS   font example
- EXAMPLE3.BAS   drawing example. Displayed a (possibly) working sample
                 source in a programming language that does not exists...
- TEST    .BAS   screen mode speed test
- COPYING        GNU/GPL document
- README  .TXT   this document
- sample font files (.FNT) for XYStr and XYStrBack

 Screen modes speed test:
==========
(* Mode number may be different in other videocards)
(Mode 13h uses direct memory writing, much faster than BIOS)

                       Fill screen with PutPixel     Fill 320x200 box

Mode   Resolution      Time (seconds)                Time (seconds)
                       Absolute        Relative      Absolute   Relative

*5Fh   640x480x256     15.05078        304.6038      3.130859   63.3636
*5Eh  1024x768x256     38.11719        771.4312      3.076172   62.25682
*5Ch   800x600x256     22.73828        460.1865      3.021484   61.15002
 13h   320x200x256      0.049411         1           0.049411    1
 12h   640x480x 16     12.08398        244.5605      2.525391   51.10989
 11h   640x480x  2     11.91992        241.2402      2.525391   51.10989
 10h   640x350x 16      8.623047       174.5167      2.470703   50.00309
 0Eh   640x200x 16      4.777344        96.68583     2.416016   48.89631
 0Dh   320x200x 16      2.361328        47.78952     2.361328   47.78952
 06h   640x200x  2      3.021484        61.15002     1.539063   31.14818
 05h   320x200x 16      1.482422        30.00186     1.482422   30.00186
 04h   320x200x 16      1.427734        28.89506     1.427734   28.89506

 Routines:
==========
-----------------------------------------------------------------------------
 SetVideo          -  Set video mode
 SetCursor         -  Set cursor type
 PutCursor         -  Set cursor position
 GetCursor         -  Read cursor position
 GetPen            -  Read light pen
 ActivePage        -  Select active display page
 ScrollUp          -  Scroll active page up
 ScrollDown        -  Scroll active page down
 GetAtCursor       -  Read character and attribute at cursor
 PutAtCursorC      -  Write character and attribute at cursor
 PutAtCursor       -  Write character at current cursor
 SetColorPal       -  Set Color Palette
 PutPixel          -  Write graphics pixel at coordinate
 GetPixel          -  Read graphics pixel at coordinate
 PutChar           -  Write text in teletype mode
 GetVideo          -  Get current video state
 SetDAC            -  Set DAC color register
 PutStr            -  Write String
-----------------------------------------------------------------------------
 PutLine           -  Draw line
 Box               -  Draw box
 FillBox           -  Draw filled box
 Ellipse           -  Draw ellipse
 FillEllipse       -  Draw filled ellipse
 Teletype          -  Write string
 XYStr             -  Write string at coordinate using fonts
 XYStrBack         -  Write string with background color
-----------------------------------------------------------------------------
 SetPalette        -  Set 256 color palette
 Reboot            -  Reboot PC in DOS or close command line in Windows
 WaitFrame         -  Wait for video enabled signal
-----------------------------------------------------------------------------
 Equipment         -  Equipment determination
 Memory            -  Memory size determination
-----------------------------------------------------------------------------
 ResetDisk         -  Reset Disk System
 GetDisk           -  Get Disk Status
 ReadSector        -  Read Disk Sectors
 WriteSector       -  Write Disk Sectors
 VerifySector      -  Verify Disk Sectors
-----------------------------------------------------------------------------
 WaitKey           -  Wait for keystroke and read
 GetKey            -  Get keystroke status
 GetShift          -  Get shift status
-----------------------------------------------------------------------------
 LPrintChar        -  Print character
 InitPrinter       -  Initialize printer port
 PrinterStatus     -  Read printer port status
-----------------------------------------------------------------------------
 Bootstrap         -  Bootstrap loader
-----------------------------------------------------------------------------
 ReadClock         -  Read system clock counter
 SetClock          -  Set system clock counter
-----------------------------------------------------------------------------

+++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[BITTORRENT]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++
 
BitTorrent, Utilities, File Distribution Software

This is a copy of the BitTorrent source tree (mostly written in
Python and WxPython), and  the code here may or may not operate
on OpenVMS; this is not (yet) a port.


++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[BLISS]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
BLISS, LANGUAGES, BLISS Implementation Language

Contains the HP-AXPVMS-BLISSA64-V0111-4-1.PCSI BLISS32 and BLISS64 
compilers V1.11-004 (GEM BL48) installation kit for the OpenVMS Alpha,
and the HP-I64VMS-BLISSI64-V0112-67-1.PCSI BLISS32 and BLISS64 compilers 
V1.12-067 (GEM BL50) for OpenVMS I64.  These are PCSI install kits.

The release notes in the kits are a required supplement to the original
1987-vintage BLISS Language Reference Manual and BLISS-32 User Manual.

Please particularly read these release notes carefully for information
on support that was dropped and features that were added specifically
for the OpenVMS I64 environment.

The OpenVMS VAX Bliss compiler has not changed from the V4.7-based version 
found on various previous Freeware distributions including Freeware V6.0, 
though the BLS32047 VMSINSTAL installation kit is replicated here.  (If 
you have already installed the OpenVMS VAX Bliss compiler from Freeware
V6.0, you do not need to reinstall it.)


+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[BOSS]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
BOSS, UTILITIES, Log in multiple times on a single serial-line terminal

BOSS V5.2

Ported to AXP by Malcolm MacArthur <M.McArthur@zippy.dct.ac.uk>.
Ported to IA64 by Hunter Goatley <goathunter@goatley.com>

This distribution was created by Hunter Goatley <goathunter@goatley.com>
and includes .OBJ files for Alpha and VAX (both using the PTD$ routines and
the old TW devices used prior to VMS V5.5).

This is BOSS V5.2.  A couple of minor changes were made to BOSS.C
to allow the code to build and run on OpenVMS IA64 (Itanium).
Hunter Goatley, August 22, 2004.

This is BOSS V5.1.  A bug in the routine to handle /STUFF_STRINGs was
fixed and the code was cleaned up to allow clean compiles using both
VAX C and DEC C (without /STANDARD=VAXC) by Hunter Goatley, September 25,
1996.
----------------------------------------
[readme file amended by M.McArthur@dct.ac.uk 02-May-94]
This is BOSS version 5.0 (May 2nd, 1994).  It consists of 6 files
    BOSS.README	      This file
    BOSS.HLP	      The user help file
    BOSS.C	      The source code
    BOSS_CLD.CLD      The command language definitions
    BOSS_BUILD.COM    The procedure for compiling and linking BOSS
    BOSS_INSTALL.COM  The procedure for installing BOSS

BOSS requires that pseudo TTY (PTY) drivers be installed on your system.
This should be the latest version posted to INFO-VAX by Kevin Carosso in
August 1988.  This is recommended version for both VMS 4.x and VMS 5.0.
Contact me if you need a copy of the PTY drivers. Alternatively, BOSS
will run with the FTdriver. It is currently set up to do so, but can
use the PY/TW driver combo instead; just edit the compile time conditional.
Alpha users please note that the only pseudo terminal drivers available are
the FTdriver ones. BOSS is set to automatically use these if you are compiling
on an AXP system.

If you plan to use BOSS/UW (to get multi-window operation on a Macintosh),
you will need the UW terminal emulator.  I can send you that too.

You should edit BOSS_INSTALL.COM to refer to the directory where BOSS.EXE
resides.  BOSS should be installed with both PHY_IO and OPER privileges.
You can get by without these privileges--see the comments in BOSS.C.

Please note that you must edit BOSS_INSTALL.COM to reflect the location of the 
BOSS executable on your system.

BOSS needs to be defined as a foreign command, i.e.,
    $ BOSS == "$<dev>:[<dir>]BOSS"
BOSS.HLP tells the user to do
    $ SETUP BOSS
before running BOSS.  SETUP on our system runs a .COM file which does the
necessary initialization for various utilities.  You will probably need to
edit BOSS.HLP to insert the incantation appropriate for your site.
BOSS.HLP should of course be installed in some easily accessible help
library.  Something like
    $ LIBRARY/HELP/REPLACE HLP$LIBRARY_1 BOSS
should do the trick.

   Charles Karney             
   Plasma Physics Laboratory      E-mail:  Karney@Princeton.EDU
   Princeton University           Phone:   +1 609 243 2607
   Princeton, NJ 08543-0451       FAX:     +1 609 243 2160
------------------------------------------------------------------------------
For Alpha users:

	I've ported BOSS to the Alpha, and it seems to work fine, but there
might be some unexpected bugs with it. If you find any bugs, please tell me.

	I haven't been able to test it with the Unix Windows software, and
I can't (we don't have Macs or Amigas here...) so if it falls down with 
either of those two, you're on your own. Sorry :-(

	I'm not a system administartor or anything; just a first year computing
student. So I haven't been able to test whether it'll work properly with PHY_IO
and OPER privileges. Don't blame me if it trashes your system disk :-)

         On the whole it seems to work. This version will compile on both
VAX and AXP systems.

	Enjoy!

	-Malcolm.
--
Malcolm MacArthur       M.McArthur@zippy.dct.ac.uk

My views are not my own. I got them out of a book.

------------------------------------------------------------------------------

The remainder of this file is specific to people running BOSS/UW.

The user documentation is in HELP BOSS Windows and its subtopics.

You will get a separate mailing containing the three files
    UNIX-UW-42.HQX	The UW terminal emulator and documentation
    UWPROTO.TXT		Internal documentation on UW protocols
    MACMOUSE.EL		Mouse support for Gnu Emacs

UNIX-UW-42.HQX should be downloaded to a Mac as a text file and run through
the BinHeX and Packit programs to give uw (the terminal emulator) and
uw.doc (the documentation in MacWrite format).

UWPROTO.TXT describes the protocol used by UW and BOSS/UW.  Can be ignored
if you like.

If you have Gnu Emacs:

MACMOUSE.EL should be moved to EMACS_LIBRARY:[LISP].
Add a uw entry in EMACS_LIBRARY:[ETC] with:

# Macintosh/UW termcap  (same as Mac without the cs, and has km = meta)
d0|uw|uw-am|unix-windows:\
	:cr=^M:do=^J:nl=^J:bl=^G:co#80:li#24:cl=50^O\E[;H\E[2J:\
	:le=^H:bs:am:cm=5\E[%i%d;%dH:nd=2\E[C:up=2\E[A:\
	:ce=3\E[K:cd=50\E[J:so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:\
	:md=\E[1m:mr=\E[7m:mb=\E[5m:me=\E[m:is=\E[1;24r\E[4l\E[24;1H:\
	:rs=\E>\E[?3l\E[?4l\E[?5l\E[?7h\E[?8h:\
	:ks=\E=\E[?1h:ke=\E>\E[?1l:\
	:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=^H:\
	:ho=\E[H:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:ta=^I:pt:sr=5\EM:vt#3:xn:\
	:ic=7\E[1@:dc=7\E[1P:al=9\E[1L:dl=9\E[1M:\
	:sc=\E7:rc=\E8:\
	:IC=7\E[%d@:DC=7\E[%dP:AL=3*\E[%dL:DL=3*\E[%dM:km:

Postscript:

I still prefer VersaTerm PRO to UW, even though it doesn't have multi-
window support.  There are too many VersaTerm features that I need which
are absent in UW.

I've only implemented the most basic level of UW service under BOSS
(protocol 1 in UWPROTO.TXT).  The next level allows windows to be retitled
from the VAX, as well as setting many of the other attributes of windows.
This will most likely not get implemented, unless multi-window support
appears in VersaTerm.

The main reason for implementing the UW features in BOSS was to show that
the Macintosh can provide a multi-window enviroment for the VAXes.  Now we
have to get Lonnie Abelbeck to modify VersaTerm to support the UW
protocol...

Note that Meshugena-term on Amiga, as well as UW on Amiga, support the UW
protocol.

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[CDRECORD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
CDRECORD, MultiMedia, CD-R Recording Software

This is the source code for the version of CDRECORD that
is included within OpenVMS Alpha V8.2.

Versions of CDRECORD are present in V7.3-1 and later,
please see SYS$MANAGER:CDRECORD.COM for related details.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[CGI_SCRIPTS_WASD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
SCRIPTS_WASD, WEB_TOOLS, WASD CGI scripts ported to other server environments

A small collection of VMS-useful "WASD Hypertext Services" CGI scripts package
(also on this freeware CD) ported to the CSWS V1.3 (OpenVMS Apache 1.3.26),
OSU (DECthreads, 3.10), Purveyor and other VMS CGI server environments.

  *  CONAN is used to access VMS Help and text libraries.

  *  HYPERSHELF is used to navigate BNU or Bookreader shelves.

  *  HYPERREADER is the book reader.

  *  HYPERSPI is a system performance monitor (of sorts!)

  *  HYPERSPI++ is hyperSPI plus more items plus better graphics

  *  QDLogStats provides elementary Web server access log statistics

  *  QUERY/EXTRACT is an ad hoc plain/HTML text search facility

  *  VMSeti is an interface for monitoring VMS SETI@home processing

  *  WWWCount is Muhammad A.Muquit's graphical Web page hit counter

  *  yahMAIL allows Web access to user's VMS mail

See FREEWARE_DEMO.TXT for installation instructions.

Access the HTML documentation using a browser on the local system.  First
ensure the freeware CD is mounted /SYSTEM, then enter

  file:///cd-device/cgi_scripts_wasd/

into the "Location:" field of the browser.

Mark.Daniel@wasd.vsm.com.au
(Mark.Daniel@dsto.defence.gov.au)
November 2004

http://wasd.vsm.com.au/
http://wasd.vsm.com.au/wasd/
ftp://ftp.vsm.com.au/wasd/index.html

++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DCL04]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
DCL04, SYSTEM_MGMT, DCL Utility Procedures

$ dir

Directory USER$ROOT:[HPW04]

BSTART.COM
	SUBMITs a software startup procedure to batch as user SYSTEM
	(requires CMKRNL privilege). Uses "SYS$STARTUP:*$STARTUP.COM" 
	as a "pattern" to match against, and if not found, looks for 
	SYS$MANAGER:*_STARTUP.COM

	Examples:
	$ @BSTART SLS
	Finds SYS$STARTUP:SLS$STARTUP.COM and submits it to the default 
	batch queue.

	$ BSTART MGA
	Finds SYS$MANAGER:MGA_STARTUP.COM and submits it to the default 
	batch queue.

CD.COM
	Yet another "Change Directory" command in DCL. Accepts VMS 
	syntax (DEV:[DIR]), UN*X syntax ("/dir") and DOS syntax 
	("\dir").

DELTREE.COM
	Yet another "DELete directory TREE" utility in DCL. Works best
	with BYPASS privilege.

DMP2BIN.COM
	Converts the contents of a DUMP output file to a Fixed-512 
	file. Good for .ZIPs, .EXEs, other binary files. Will also 
	work with /BLOCK dumps of any file type; RMS file and record 
	attributes must be restored manually.

DVOL.COM
	Estimates the amount of data to backup on a volume considering 
	the total disk space used minus the size of the .SYS files in 
	the MFD.

ENTDEL.COM
	Delete ranges of entries. Entries can be specified 
	individually, as a range (Example: 10-15) or as a comma-
	separated list of entries or ranges. 

FILCNT.COM
	Counts the number of files in a directory by reading the .DIR 
	file.

FIX_VERSION.COM
	"Fixes" the version numbers of selected files by RENAME-ing 
	them twice: once by reversing the sequence of characters in 
	the filetype extension, and again putting them back in the 
	right order. File version numbers begin at 1 afterwards.

FREEDISK.COM
	Displays the total, used and free disk space on all the 
	volumes MOUNTed to the system including freespace percentages 
	and totals in GB and TB (rounded).

GGFIND.COM
	Determines which $1$GGA device is associated with a $1$DGA 
	by matching against the WWIDs.

NA.COM
	Converts an integer into either a DECnet address (if less 
	the 65535) or an IP address in dotted-decimal notation.

PRCQUOTA.COM
	Displays the various process quotas and quota usage of 
	processes selected by command line parameters. Uses 
	F$CONTEXT() and F$PID() to find processes.

	P1 = Process name to match
	P2 = Node name to match ("*" for the entire cluster)
	P3 = Additional process selection criteria.

RESUBMIT.COM
	Submits a new version of a batch job procedure based on 
	information from an existing queue entry.

RM_RET_ENT.COM
	Removes retained entries from queues using criteria 
	stated in the command line parameters.

SHAFT.COM
	Displays the /AFTER time of queue entries, the date/time 
	submitted and the process start time if the job is 
	running. Entries can be specified individually, as a range 
	(Example: 10-15) or as a comma-	separated list of entries 
	or ranges. 

SHCLU.COM
	Displays the cluster members including hardware names, 
	and operating system version, cluster votes information, 
	and quorum disk information if a quorum disk is present.

SPLIT.COM
	Breaks up binary (Fixed-512) files into smaller pieces.

	P1 = Filespec
	P2 = Chunk size in blocks or MB

SYSTAT.COM
	RSTS/E-like SYSTAT display.

TEE.COM
	Excerpted from the on-line HELP for the PIPE command. Will 
	work better on V7.3-2 and later than on V7.2 thru V7.3-1.

TIME_COMMAND.COM
	Displays the elapsed time of a command.

VMSMEM.COM
	Displays the memory utilization for the local node.

WHICH.COM
	Displays what is executed for a given command. Locates 
	"foreign"commands (symbols) or uses the freeware VERB 
	utility	to analyze the DCL command table.

Total of 22 files.

++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DCL_CHECK]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++
 
DCL_CHECK, UTILITIES, Charlie Hammond's unsupported DCL checker

    Note: Information about DCL_CHECK 3.1 is at the end of this file.

The following information is extracted from DCL_CHECK's help file.
There is much more information in the help file.
The HELP utility can access the DCL_CHECK help file using the command

    $ HELP /LIBRARY=<device>:[<directory>]DCL_CHECK

or through DCL_CHECK with this command

    $ @<device>:[<directory>]dcl_check help


DCL_CHECK

        The DCL_CHECK procedure detects a variety of DCL coding errors and
        displays  diagnostic  messages  that  allow  you  to  correct  the
        problems. See "Diagnostics" for a list of the types of errors that
        DCL_CHECK can detect. See "Problems" for information on the limits
        of DCL_CHECK.

        When  you  execute  DCL_CHECK  with "HELP" as the first parameter,
        DCL_CHECK invokes the DCL Help utility.  If you provide additional
        parameters, they are passed to the Help utility.

        To exit the Help utility, press Return one or more times until the
        prompt "enter name of file:"  is displayed.


    Additional information available:

    DCL_CHECK     DCL_DIET        Diagnostics   Examples
    Format        Installation    Line_counts   Modifications
    Output        Problems        Version     

Topic? installation

INSTALLATION

        To install DCL_CHECK you must put the files

            DCL_CHECK.COM and
            DCL_CHECK.HLB

        into the same directory. You then execute DCL_CHECK as an indirect
        command procedure.  See "Format" for additional information.

        DCL_CHECK.COM  is provided in "dieted" form.  You may also wish to
        have the file DCL_CHECK.COM_SOURCE available; this  is  the  fully
        commented version of the procedure.

Topic? format

FORMAT

        DCL_CHECK  is  a  DCL  command  procedure.   It is executed by the
        following DCL command:

            $ @[<disk>:][<directory>]DCL_CHECK.COM [<input> [<list>]]
            $ @[<disk>:][<directory>]DCL_CHECK.COM HELP [<topic>...]

        <disk>  and/or  <directory>  may  be omitted; the current defaults
        will be used.

        The   file   DCL_CHECK.HLB  must  be  in  the  same  directory  as
        DCL_CHECK.COM if you use the HELP function in DCL_CHECK. The files
        may be in any directory to which you have read access.

        If  you  use DCL_CHECK frequently, you may wish to assign a symbol
        in your LOGIN.COM file to execute DCL_CHECK.  For example, if  the
        DCL_CHECK.COM  and  .HLB files are in you login default directory,
        you might put the following in your LOGIN.COM:

            $ DCL_CHECK :== "@SYS$LOGIN:DCL_CHECK"

        Alternatively,  if  you  put  DCL_CHECK.COM  and  DCL_CHECK.HLB in
        SYS$SYSTEM, you might put the following in your SYS$SYLOGIN (which
        is normally SYS$MANAGER:SYLOGIN.COM):

            $ DCL_CHECK :== "@SYS$SYSTEM:DCL_CHECK"


  Additional information available:

  Parameters

FORMAT Subtopic?  
Topic? modifications

MODIFICATIONS

        You  can  modify  or  "customize" DCL_CHECK by editing the command
        procedure, DCL_CHECK.COM. However, DCL_CHECK.COM is a "compressed"
        version  of  the  procedure.   To  save  disk  space  and  improve
        performance,  all  comments  and  unnecessary  spacing  have  been
        removed  from  DCL_CHECK.COM.  This makes it difficult to read and
        understand the procedure.

        It  should  be  much easier to edit the file DCL_CHECK.COM_SOURCE,
        which contains commands  and  is  formatted  to  facilitate  human
        reading.   You  can recreate a "compressed" version of the command
        procedure by using DCL_DIET.COM.


  Additional information available:
                
  Help

MODIFICATIONS Subtopic?
Topic? dcl_diet

DCL_DIET

        DCL_DIET  is  a  command  procedure  that  accepts  as input a DCL
        command procedure file.  It compresses, or "diets",  the  file  by
        removing  comments and unnecessary spaces.  The compressed version
        is created as output.

        The smaller size of the compressed file has two advantages:

            o It takes up less space on disk or tape.

            o It executes faster
                -- especially for larger command procedures.

        DCL_DIET is not part of DCL_CHECK.  It is provided separately.


---------------------------------------------------------

DCL_CHECK 3.1

The following comments from DCL_CHECK.COM_SOURCE outline the changes.

$!  D3.1    2003-AUG-21             Charlie Hammond
$!      Fixed some false instances of UMP and PSQ/PSR errors.
$!
$!  C3.1    2003-AUG-20             Charlie Hammond
$!      Avoid flagging possessives ("'s " in quoted string) as
$!      PSQ-W  possible error using single-quote (') in quoted string
$!
$!  B3.1    2003-AUG-20             Charlie Hammond
$!      Re-write code that finds the file-name logical-name on I/P verbs
$!      so that it can handle quoted strings and symbol substitution
$!      within quoted strings.
$!
$!  A3.1    2003-JUN-05             Charlie Hammond
$!      Improved checking for paired brackets
$!      by not checking in quoted strings


Version 3.0 of DCL_CHECK includes several new diagnostics related
to file checkin (OPEN, READ, WRITE and CLOSE commands).
It also contains a collection of incremental fixes and
improvements, and the new IFC diagnostic.

The following comments from DCL_CHECK.COM_SOURCE outline the changes.

$!  V3.0    2003-JUN-03             Charlie Hammond
$!      Add checking for paired brackets
$!
$!  H3.0    2003-APR-03             Charlie Hammond
$!      Added the contraction "They've".
$!      Added all contractions in all upper case.
$!      Added possessives for common accounting periods.
$!          "Day's", "Week's", "Month's", "Period's", "Quarter's",
$!          "Half's" and "Year's" (also in all lower and all upper case).
$!          Also names of weekdays and months
$!
$!  G3.0    2003-APR-01             Charlie Hammond
$!      Fixed various spelling errors/typos
$!      Fixed aproblme with ICO (Help from Norm Raphael @metso.com)
$!
$!  F3.0    30-Sep-2002             Charlie Hammond
$!      Don't do file checking on SYS$COMMAND, SYS$ERROR or SYS$PIPE
$!      (In addition to SYS$INPUT and SYS$OUTPUT)
$!      Fix a problem with double quotes in symbol used w/ READ/KEY
$!
$!  E3.0    16-Sep-2002             Charlie Hammond
$!      Avoid false diagnostics ICO-S for ">" and "<" in PIPEs
$!      Only check /END and /ERR labels on /END_OF_FILE and /ERROR
$!
$!  D3.0    04-Sep-2002             Charlie Hammond
$!      added " .ea ", " ea. " and " .ea. " to list of invalied
$!      comparison operators.
$!
$!  C3.0    18-Mar-2002             Charlie Hammond
$!      Fix problem getting file logical names when there is an
$!      /END or /ERR qualifier with spaces preceedign of following the "="
$!
$!  B3.0    13-Mar-2002             Charlie Hammond
$!      Fix problem with /ERROR on RUN statement
$!
$!  A3.0    18-Feb-2002             Charlie Hammond
$!      Add file verb checking
$!    NLN-S  An OPEN, READ, WRITE or CLOSE statement has no logical name
$!    ONC-E  A file that is opened has no close statement
$!    INR-A  file that is opened for read is not read
$!    ANR-E  A file that is opened for append is not written
$!    ONW-E  A file that is opened for write is not written
$!    RNR-S  A file that is not opened for read is being read
$!    WNW-S  A file that is not opened for write or append is being written
$!    UNU-S  A file that is not opened for read and write is being updated
$!    CNO-S  A file that is closed has no open statement
$!
$!  NOTE: There is no V2.2 --  A3.0 added sufficient functionality
$!        that the major version was bumped.
$!
$!  G2.2    20-Nov-2001             Charlie Hammond
$!          Make an "&" in a PIPE statement a warning.
$!          Re-word several ICF diagnostics.
$!          Include this in help.
$!
$!  F2.2    02-Aug-2001             Charlie Hammond
$!          Spelling corrections, mostly in comments, suggested
$!          by Norm.Raphael@jamesbury.com
$!
$!  E2.2    28-Jun-2001             Charlie Hammond
$!          Improve line number display in pass 2
$!          Display 1000, 2000, etc. instead of 500, 1500, etc.
$!          Also display line numbers in round 100's instead
$!          of actual numbers that could be off a bit.
$!
$!  D2.2    08-Jun-2001             Charlie Hammond
$!          Fix problem mistaking "CALL", "GOTO" and "GOSUB"
$!          at the end of a symbol name as a DCL command.
$!
$!  C2.2    31-May-2001             Charlie Hammond
$!          Fix problem with /END and /ERR on same line.
$!
$!  B2.2    22-Feb-2001             Charlie Hammond
$!          Fix problems with detecting various forms of $DECK and $EOD
$!
$!  A2.2    15-Aug-2000             Charlie Hammond
$!          Fix problem when first blank delimited token on line
$!          ends with ":" but is not a label.
$!
$!  V2.1    15-Aug-2000             Charlie Hammond
$!          Updated freeware release
$!
$!  H2.1    07-Aug-2000             Charlie Hammond
$!          Make ICF as warning for & and %
$!          Add information to ICF help.
$!
$!  G2.1    03-Aug-2000             Charlie Hammond
$!          Allow for a $ in a continued, "one-line" if statement.
$!          Avoid incorrect INT err that could happen if a PSQ error
$!              is found in a nested "one-line" if statement.
$!
$!  F2.1    02-May-2000             Charlie Hammond
$!          Add ICF invalid character found (#, %, ^ or &)
$!
$!  E2.1    24-Mar-2000             Charlie Hammond
$!          Improved EFB detection ("=" found between IF and THEN)
$!
$!  D2.1    13-Dec-1999             Charlie Hammond
$!          Improve detection of single quote errors
$!          Allow /OUT= on output file (P2)
$!
$!  B2.1    04-Dec-1999             Charlie Hammond
$!          Add LDS error -- Label defined by symbol substitution (warning)
$!          Fix single quote (') in definition of valid_lexicals
$!              It should be and now is a comma (,).
$!  A2.1    23-Oct-1999             Charlie Hammond
$!          Correct calculation of code_lines.
$!          We had been subtracting deck_lines twice.
$!
$!  V2.0    17-Sep-1999             Charlie Hammond
$!          For FREEWARE release
$!
$!  B2.0    31-Jul-1999             Charlie Hammond
$!          Correct handling of continuation comment that starts
$!              with only a "!" rather than "$!"
$!          Correct handling of SRT and INT errors.
$!              (SUBROUTINE/IF not terminated)
$!          "Beef up" a few help entries.
$!
$!  A2.0    28 July 1999            Charlie Hammond
$!          Improve handling for TNA/ENA/DNA
$!              (THEN/ELSE/ENDIF statement not allowed here)
$!          Make ENDSUBROUTINE cancel goto and exit shadows
$!          Handle SUBROUTINE and ENDSUBROUTINE
$!              IF/ENDIF and SUBR/ENDS may be disjoint or
$!              strictly nested -- they may not overlap
$!
$!  A1.0 - R1.0
$!          through October 1996    Charlie Hammond
$!          Many changes/additions
$!
$!  X-1     dd-mmm-1996             Charlie Hammond
$!          Original procedure created.

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DCL_DIET]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
DCL_DIET, UTILITIES, Charlie Hammond's unsupported DCL dieter

    [The following also appears near the beginning of
     DCL_DIET.COM and DCL_DIET.COM_SOURCE.]

    **************************************************************

    This procedure "DIETs" a command procedure file -- compressing
    it by removing comments and unnecessary space. This saves file
    space and improves execution time.  It may also remove comments
    that you don't want users to see.

    To run this procedure, enter command

        $@DCL_DIET <input> <output>

        where   <input> is the input command procedure
               <output> is the "DIETed" output file

    (<output> may also be in the form "/OUTPUT=<filename>"

    If you use DCL_DIET frequently, you may wish to assign a symbol in
    your LOGIN.COM file to execute DCL_DIET.  For example, if the
    DCL_DIET.COM is in you LOGIN default directory, you might put the
    following in your LOGIN.COM:

        $ DCL_DIET :== "@SYS$LOGIN:DCL_DIET"

    Alternatively, if you put DCL_DIET.COM in SYS$SYSTEM, you might put
    the following in your SYS$SYLOGIN (which is normally
    SYS$MANAGER:SYLOGIN.COM):

        $ DCL_DIET :== "@SYS$SYSTEM:DCL_DIET"

    If the translation of the logical name DCL$DIET_DOTDOT is true, then
    this version adds a space a the beginning of a line that starts with ".".
    This is to overcome a problem with SMTP mail in Compaq TCP/IP services
    so that TCP/IP V5.3-18's SMTP won't double the "."

    **************************************************************

Version 1.1 implements the following:

$!  We want to TRIM, COMPRESS and UNCOMMENT the dcl record,
$!  But first we must deal with problem that F$EDIT has:
$!
$!      - Exclaimation marks used for formating directives in F$FAO
$!        control strings may be taken as comments and removed.
$!        This only occurs when the F$FAO is preceded by two single quotes
$!        indicating symbol substitution within a quoted string.   e.g.
$!
$!          $ write sys$output "Value is: ''f$fao("!4UL",value)'"
$!
$!      - Multiple spaces in strings within a lexical function may be
$!        incorrectly compressed.  Again, This only occurs when the F$FAO
$!        is preceded by two single quotes indicating symbol substitution
$!        within a quoted string.   e.g. 
$!
$!          $ write sys$output "''f$locate("  a","        a")'"
$!
$!      (These may not be good coding practice, but tye ARE used.)
$!
$!  We could write a lot of clumsy code to handle this, but since it is
$!  an unusual occurance, we just skip dieting any lines that contain
$!  the string "''F$" or the string "''f$'"(although we do strip extra
$!  spaces after the "$" and we also strip any trailing spaces.

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DECXTERM]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
DECxterm, UTILITIES, DECxterm key remapping (for use on UNIX Systems)

DECxterm V1.9

The procedure remaps the Sun Keyboard, IBM AIX PC type Keyboard, Linux PC 
type Keyboard and Tru64 Compaq Unix keyboards to mappings suitable for VMS
This program is designed to run on a Unix machine, create a terminal 
emulator with VMS keyboard mappings and then telnet to a VMS machine.

USAGE: DECxterm [-option ...]
          which are identical to xterm. "#man xterm" for further details
   eg: DECxterm -e telnet yakka.ali.dec.com

Note 1: All keys in the same position are mapped to the standard
  VMS LKxxx ikeyboard except for the keys between the main keyboard
  keys and the Numeric/Application keys which remain as labelled.
  The keys on an DEC LKxxx Keyboard are marked on other keyboards as:-
  Find marked Home, Insert marked the same, Remove marked Delete,
  Select marked End, Previous marked Page-Up and Next marked Page-Down.

Note 2: Shift/F1 to Shift/F10 are mapped to F11 to F20

Note 3: Other Terminal Emulators such as dtterm or dxterm can be used
  by setting the variable DECXTERM_EMULATOR. The default is xterm.

Note 4: The default xterm qualiers are defined by the variable
  DECXTERM_OPTIONS and are set to:-
   -fn 9X15   Default font
   -sb        Enable scroll bars
   -sl 500    Number of lines saved that are scrolled off the top of window
   -cr red    Set the cursor color to red
   -tn vt100  Set the terminal type to vt100
   -132       Allow switching between 80 and 132 columns
  The default settings can be changed by defining this environment
  variable before running DECxterm.

xterm_options="${DECXTERM_OPTIONS:=-fn 9X15 -sb -sl 500 -cr red -tn vt100 -132}"

Note 5: To modify this program or to add further keyboard mappings edit out
  the C code from within DECxterm and follow the procedures documented in 
  DECxterm.

++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DFU]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
DFU, Storage_Mgmt, V3.1-1 High-Performance Disk/File Utility.

DFU V3.1-1 Disk and File Utilities is a high-performance utility 
developed to perform both routine maintenance and special-purpose
operations on disks, files and directories.  The functionality
offered by DFU is not available or is only partially available
through other DCL commands; through standard OpenVMS utilities.
 
Available functions :
 - DEFRAGMENT one or more files
 - DELETE files by file-id; delete directory(trees) fast
 - DIRECTORY functions : COMPRESS or DUMP directories
                       : search directories for files with 
                          multiple versions , alias files 
                          or empty directories
                       : create directories with 
                          preallocated size
 - REPORT disk for file, freespace and disk usage 
    statistics 
 - SEARCH very fast for specific files
 - SET : change many file attributes
 - UNDELETE files
 - VERIFY and REBUILD of the disk structure

PCSI installation kits for OpenVMS Alpha and OpenVMS I64
are provided.  No DFU kit is available for OpenVMS VAX,
nor is a VAX kit currently expected.


++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DISKBLOCK]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++
 
DISKBLOCK, UTILITIES, Editor amd performance tester for ODS and Foreign disks

  DISKBLOCK is a low level disk block editing tool.

  V6.1 of Diskblock has been updated to support OpenVMS on IA64 as well as
  Alpha and VAX. There is a single VMSINSTAL kit that will install on all
  three architectures

  Diskblock can be used to read, modify and write LBNs on a disk or VBN's 
  in a file.  It can also carry out read, write and seek performance 
  measurements.

  Diskblock ingores all locking activity on the selected Disk or File, it
  can access and modify ODS2 and ODS5 data structures such as file headers 
  and it can read, write and test individual shadow set members independently!

  There is a buffer which holds a copy of the block which you read, 
  you can modify the contents of this buffer using EXAMINE and DEPOSIT
  commands and then REWRITE it to the same block, WRITE it to a different
  block or SELECT a new disk or file and WRITE the buffer to any block.

  When you SELECT a disk, diskblock will attempt to map the Index File
  If it is successful then any command which requires an LBN (READ, WRITE,
  COPY etc...) will also accept a FID and operate on the appropriate file
  header.  This will work even if the disk is mounted /FOREIGN.

  There are commands to SAVE and RESTORE the buffer so that you can keep 
  a copy of the original block and undo changes if they do not work as you
  expect.

  There is a CHECKSUM command to enable you to recalculate the checksums
  for ODS2 and ODS5 file headers and home blocks.

  There is a DIRECTORY command which will find the header for a 
  file (even if the disk is mounted /foreign)

  There is a COPY command which will enable you to treat any block on a 
  disk as a file header and copy the LBNs described by its mapping pointers 
  to a new file (even if the disk is mounted /foreign).
  
  There is a SEARCH command which will search the entire disk/file 
  (or any range of blocks) for a particular string or integer or file
  header.

  There is a TEST command which will carry out performance testing.  You
  may specify queue lengths, I/O sizes, read/write ratios and seek types 
  and Diskblock will report throughput and bandwidth to the disk.

  Because of its potential to corrupt disks you should only
  use Diskblock in extreme desperation or on a disk which you have
  backed up.  
  
  You need LOG_IO privilege to run DISKBLOCK.

  Diskblock has an extensive help file with further information.




++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DIX]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
DIX,Utility,A program to read/modify records in any RMS (seq/relative/idx) file

This program lets you view/modify records in any RMS file.

Dix can work in three modes

a. Full screen mode. DIX uses SMG to display the data on the screen and 
   allows you to modify it (if you specify /MODIFY (not the default))
   This mode is the default on a terminal.
   You enter this mode by specifying the /SCREEN qualifier.

b. Interactive mode. DIX will prompt you for commands. This mode can also
   be used in batch with command files. If you specified /MODIFY
   the file can also be modified (not the default). 
   You also have scripting possibilities.
   You enter this mode by specifying the /INTER qualifier.
   See the help with DIX/HELP INTER for possible commands.

c. File mode. DIX will display one or more records and returns to DCL. No
   interaction is possible.
   You enter this mode by specifying the /FILE qualifier.

In all three modes the data can be displayed in two ways.

a. Interpreted. You need a record description to do this.
   The description file syntax looks like fortran record definitions(structures)
   and the descriptions can be in a file or in the DIX_DES.TLB text library.
   The layout of the description files is described in the DIX
   help library under the topic 
   DISPLAY_MODES INTERPRETED /DESCRIPTION

   See DIX/HELP DISPL INTERP /DESCR

   DIX delivers (in DIX_DES.TLB) descriptions for the following files
    SYSUAF.DAT
    RIGHTSLIST.DAT
    INDEXF.SYS 
    VMS$PASSWORD_HISTORY
    VMSMAIL_PROFILE
    DIRECTORY files
    Some ALL-IN-1 files.

   And you can add any file you like, if you know the record layout.
  
b. Raw dump. The program displays the data like VMS DUMP and
   you can modify any byte.


  See the help via the HELP command.

usage:
Define DIX as a foreign command

DIX:=$'directory'dix_alpha or DIX_VAX or DIX_IA64

DIX filename /qualifiers

For the qualifiers see the help via DIX/HELP, but one very 
one important one is the /MODIFY. If you do not specify /MODIFY the
file is opened readonly and cannot be modified.

Note:
The files DIX.HLB and DIX_DES.TLB must be in the same directory as DIX, or
you must define the logical DIX_HELP and/or DIX_DES to another file.

Building:
The executables and objects for Vax,Alpha and IA64 are skipped with the kit,
as well as the sources. If you want to rebuild DIX, goto the dix directory and
use the command procedure @create_dix. This will compile (fortran) and
link DIX.

Examples:

$DIX SYSUAF[/SCREEN]/EQ=smith [/MODIFY]
  Will display the SYSUAF record of user "SMITH" using SMG, and lets
  you scroll though this data. If you specified /MODIFY, you can also
  modify entries (When you type any character on that field, you enter 
  modify mode for that field (this is signalled by an underline under
  the text)). You leave modify mode for that field when you type ENTER.
  The (modified) data is not written to the file until you type DO or PF4.
  F10 or ^Z returns you to DCL.

$DIX SYSUAF/INTER/EQ=smith [/MODIFY]
  Will enter interactive mode (non-smg), and allows you to inspect/modify
  fields of the current record. It also contains a scripting
  language. Type help in this mode to see the possible commands.

$DIX SYSUAF/FILE/EQ=smith
  Will display the data on the terminal, but will not allow you to modify
  the record (DUMP command).

$DIX datafile/FILE/REC=10
  Will display the data on the terminal, but will not allow you to modify
  the record (DUMP command). Only record 10 will be displayed

$DIX datafile/FILE/RECORD=10/COUNT=5
  Will display the data on the terminal, but will not allow you to modify
  the record (DUMP command). The records 10 upto 14 (5) wil be displayed.


Example of a (complicated) description record of the INDEXF.SYS file
   the (n) are explained below

	ubyte		id_offset	! Offset to Ident area
	ubyte		map_offset	! Offset mapping area
	ubyte		acl_offset	! Offset to ACL area
	ubyte		res_offset	! Offset to reserved area
	integer*2	seg_num		! Extension seqment number
	byte struct_lev_min		! On disk structure level
	byte struct_lev_maj		! On disk structure level
	fileid          file_id		! File id
	fileid          ext_fid		! File id extension header
        structure       rec_attr	! RMS record attributes
         byte rectyp
         byte recattr
         integer*2 recsiz
         rinteger*4 hblk
         rinteger*4 eofblk
         integer*2 eofbyte
         byte bucketsize
         byte vfcsize
         integer*2 maxrec
         integer*2 defext
         integer*2 globbuf
         integer*2 %fil3(4)
         integer*2 verslim
	end structure
	bits*4		file_char -		(1)
		[Wascontig,Nobackup,Writeback,Readcheck,Writecheck,-
                 Contigb,Locked,Contig,,,,Badacl,-
		 Spool,Directory,Badblock,Markdel,Nocharge,Erase,alm_aip,-
                 shelved,scratch,nomove,noshelvable,shelv_res]
	character*2	%res_1		! reserved 1
	ubyte		map_in_use	! # map words in use
	byte		acc_mode	! File accessor priv mode needed
	uic		owner		! Owning UIC
	protection	protection	! File protection
	fileid		backl_fid	! Backlink file id
	bits*2		journal		! Journalling flags
	integer*2	ru_active	! Recover facility unit number
	integer		highwater	! Highest blocknr written + 1
	union
	 map struct_lev_maj=5                     (2)
	  byte FI5$B_CONTROL    [0=ODS-2,1=ODS-5] (3)
	  byte FI5$B_NAMELEN   
	  integer*2 FI5$W_REVISION   
	  date FI5$Q_CREDATE
	  date FI5$Q_REVDATE 
	  date FI5$Q_EXPDATE   
	  date FI5$Q_BAKDATE    
	  date FI5$Q_ACCDATE    
	  date FI5$Q_ATTDATE  
	  integer*8 FI5$Q_EX_RECATTR
	  integer*8 FI5$Q_LENGTH_HINT_LOW
	  integer*8 FI5$Q_LENGTH_HINT_HIGH
	  character*(fi5$b_namelen) FI5$S_FILENAME  (7)
	 end map
	 map struct_lev_maj=2
	  character*20	fnam		! Variable mapped entries
	  integer*2         revnr
	  date*8            cdat
	  date*8            rdat
	  date*8            edat
	  date*8            bdat
	  character*66	rest_fnam
	 end map
	 map *			(4)
	  integer*4 data(20)
	 end map
	end union
	range (map_offset*2:map_offset*2+map_in_use-1) (5)
           diskmap maps(256)	 
	end range
	range (acl_offset*2:res_offset*2-1)
	   acl acls(50)	
	end range
	position (min(510,max(0,recordsize)))    (6)
	integer*2/hex checksum

(1) is an example for a bits type. The part between the []
    gives an more friendly view of the bits.
    For example bit3 will be displayed as "readonly"
    Any bit not described will be displayed as BITnn (for example bit8)
(2) is an example of a union/map structure. A union contains one
    or more maps. This part is selected if the field STRUCT_LEV_MAJ 
    contains 5. See also (4)
(3) This is an example for an integer (byte). The part between
    the [] gives a list of possible values of the integer.
    For example : if the value of FI5$B_CONTROL is 1, the
    text displayed is ODS-5. Anly other value than 0 or 1 will
    be displayed as the normal numeric text.
(4) The rest of the union/map. If none of the map statements has
    matched, this one will. If you do not specify a map with an *,
    the first map will be taken (in this case the map struct_lev_maj=5 
(5) This is an example for the RANGE statement. A RANGE defines a
    part of the record. 
    In this case the field diskmap map(256) in contained in a part
    of the record between bytes map_offset*2:map_offset*2 and map_in_use-1
    The length 256 is choosen to be big enough.
(6) A example of a Position statement. This set the offset for the 
    next field to an absolute value (in this case 510).
    The next field (checksum) will be at offset 510.
(7) The length of the character string depends on a previous field
    (fi5$b_namelen). 

All fieldsizes are in bytes, except within a bitfield/endbitfield range.
In this bitfield_mode only (u)integer, bits and logical fields are allowed.


Another example of files that are linked 

  The example is about 3 RMS indexed files that form a simple sourcemodule
  cross_reference system

  The first file (CROSS_REF.CRF_CROSS) has the following description
  (.CRF_CROSS in the system or user textlibrary)
          integer*2    caller_nr /file=.crf_mod_names   !link to modulename
          integer*2    called_nr /file=.crf_mod_names   !link to modulename

  The second file (CROSS_REF.CRF_MOD_NAMES) has the following description
  (.CRF_MOD_NAMES in the system or user textlibrary)
          integer*2    mod_nr                           !primary key
          character*32 mod_name
          integer*2    file_nr/file=.crf_file_names     !link to the filename

  The third file (CROSS_REF.CRF_FILE_NAMES) has the following description
  (.CRF_FILE_NAMES in the system or user textlibrary)
          integer*2    file_nr                          !primary key
          character*60 file_name
          integer*2    %filler

  When you now (dix-)edit the CROSS_REF.CRF_CROSS file
    $DIX CROSS_REF.CRF_CROSS
    %DIX-I-USINGFIL, Using file DSA40:[DIR]CROSS_REC.CRF_CROSS
    %DIX-I-USINGDES, Using description SYSLIB(.CRF_CROSS)
    DIX> EXA *
     0|CALLER_NR>|738             !the > tells us there is a link present
     2|CALLED_NR>|-262

 You can follow the link to the next file

    DIX> Follow CALLER_NR         !try to follow this link
    File .CRF_MOD_NAMES not (yes) opened, open it (y/[n]):Y     !do you want to o
    %DIX-I-USINGFIL, Using file DSA40:[DIR]CROSS_REF.CRF_MOD_NAMES
    %DIX-I-USINGDES, Using description SYSLIB(.CRF_MOD_NAMES)
    DIX> Exa *
    0|MOD_NR  |738
    2|MOD_NAME|CHECK_ALLOWED_USER
   34|FILE_NR>|66                 !and this field also has a link defined

 Now follow the link to the third file (open automatic)

    DIX> Follow/automatic file_nr
    %DIX-I-USINGFIL, Using file DSA40:[DIR]CROSS_REF.CRF_FILE_NAMES
    %DIX-I-USINGDES, Using description SYSLIB(.CRF_FILE_NAMES)
    DIX> Exa *
    0|FILE_NR  |66
    2|FILE_NAME|REM_SERVER_CHECK_ACCESS

 Now backtrace to the CROSS_REF.CRF_MOD_NAMES file

    DIX> BACK
    %DIX-I-USINGFIL, Using file DSA40:[DIR]CROSS_REF.CRF_MOD_NAMES
    %DIX-I-USINGDES, Using description SYSLIB(.CRF_MOD_NAMES)
    DIX> Exa *
    0|MOD_NR  |738
    2|MOD_NAME|CHECK_ALLOWED_USER
   34|FILE_NR>|66
  

For a complete list of directives see the help in the DIX.HLB under the
topic "DISPLAY_MODES INTERPRETED_DUMP/DESCRIPTION RECORD_FORMAT". Use
DIX/HELP to display this help.

Note:

Be careful when modifying datafiles. DIX is very powerful and has no UNDO
function after you update the record. If you modify the record, there is 
no way back except the backup (if you have one). /BLOCK mode is even more
powerful, since it bypasses RMS. 

This package contains the following files

In the main directory

 DIX_VAX.EXE			The Vax executable
 DIX_ALPHA.EXE			The Alpha Executable 
 DIX_IA64.EXE			The IA64 Executable 
 DIX.HLB			The help library
 DIX_DES.TLB			The file containing the description records
 CREATE_DIX.COM			The command procedure to compile/link
 FREEWARE_README.FIRST		This file

In the [.SRC] directory

 The FORTRAN sources

  DIX_MAIN.FOR			The main program
  DIX_CON_LIBRARY.FOR           The conversion routines ascii<>binary
  DIX_DES_LIBRARY.FOR		The description file routines
  DIX_DUMP_LIBRARY.FOR 		The dump routines
  DIX_DUMP_FILE_LIBRARY.FOR	The dump to file (noscreen) routines
  DIX_DUMP_INTERACTIVE_LIBRARY.FOR	The dump to file (noscreen) routines
  DIX_DUMP_SCREEN_LIBRARY.FOR	The dump to screen (SMG) routines
  DIX_EDIT_LIBRARY.FOR		The editor functions
  DIX_EVAL_LIBRARY.FOR		The expression evaluation routines
  DIX_GET_VERSION.FOR		The interface to the help (FSHELP) program 
  DIX_HELP_LIBRARY.FOR		The interface to the help (FSHELP) program 
  DIX_KEYDEFS.FOR               The key-definition library
  DIX_LBR_LIBRARY.FOR		The LBR interface routines
  DIX_MEMTAB.FOR		The memory-file routines
  DIX_RMS_LIBRARY.FOR		The interface to RMS routines
  DIX_RMS_LIBRARY_VAX.FOR	The Extra interface to RMS routines for VAX
  DIX_RMS_LIBRARY_NOT_VAX.FOR	The Extra interface to RMS routines for Alpha/ia64
  DIX_STARTUP_LIBRARY.FOR       The Startup routines
  DIX_SYMBOL_LIBRARY.FOR        The routines for symbol manipulation.
  DIX_SMG_LIBRARY.FOR		The interface to SMG routines
  DIX_UTIL_LIBRARY.FOR		The utility library

 The include files

  DIX_SIZE_DEF.INC		The general size definitions
  DIX_DEF.INC			The general include definitions
  DIX_MEMTAB.INC		The MEMTAB definitions
  DIX_KEYDEFS.INC		THe keydefs definitions
  
 The Help file

  DIX.HLP

 The CLD files

  DIX_CLD.CLD			The command line definitions
  DIX_INT_CLD.CLD	   	The commands for interactive mode

In the [.VAX] directory
 The vax objects
In the [.ALPHA]
 The Alpha objects
In the [.IA64]
 The IA64 objects

Instructions:

 Unpack the save set
 If you want to rebuild the program

 If you have a fortran compiler 
   @create_dix 
 otherwise, just link
   @create_dix link
    I included all objects so you can relink.

The most recent version can be downloaded from oooovms.dyndns.org.

Author: Fekko Stubbe

If you have questions or suggestions, please mail to the mail address below:
Email : dixdev (at) oooovms.dyndns.org 

++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DRAIN]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
Drain-Printer, SYSTEM_MGMT, Capture a print stream into a file

When OpenVMS is used as a print server, text printouts flow right through
on their way to an actual printer. There are times an electronic copy of
the printout would be useful. This program acts as a virtual printer and
captures the print stream into a text file instead of sending it to a
physical printer.

Drain-Printer is an expansion on an older program by Aaron Leonard; the first
copy I found was called  DRAIN_TO_FILE and was posted to comp.os.vms on
November 11, 1997 under "SUBJ: Re: Multinet LPD Queue to File?" (and also to
vmsnet.sysmgt on October 10, 1997).

Drain-Printer is written in C and was developed for the Multinet TCP/IP
package; it may require modifications to work with another stack; see
AAA_README.TXT, SETUP_DETAILS.TXT and the included source code for more
information and setup details.


Verne
-----------------------------------------------------------------------
Verne Britton, Lead Systems Programmer     voice: (304) 293-5192 x230
Systems Support Group                      (in WV, call 1-800-253-1558)
West Virginia Network for                  FAX:   (304) 293-5540
     Educational Telecomputing             verne@wvnet.edu
837 Chestnut Ridge Road                    http://vaxa.wvnet.edu/~verne
Morgantown, WV  26505

++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[DSRPLUS]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
DSRplus, Languages, DIGITAL Standard Runoff Plus

This is a text-processing package for OpenVMS VAX that
builds on the DSR package.  DIGITAL Standard Runoff (DSR)
itself has been left latent within OpenVMS for some time,
and is unsupported.  This is the enhanced kit.

Also included here is TEMPLATE.RNH, an example template
for building OpenVMS help files using RUNOFF and DSRplus.


++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[EMACS]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
Emacs, Utilities, The Emacs 21.2 Text Editor

This is an OpenVMS port of the Emacs text editor.

The current status is that it is under development and not yet finished
and ready for ordinary use.

The last mature and fully usable Emacs was a patched 19.28.

You can either use a patched 19.28 or participate in 21 development.
(Email roart@nvg.ntnu.no if you want to participate).


+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FIND]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
FIND, Utilities, Enhanced Search Tool for OpenVMS

This tool provides searching capabilities beyond those of the 
standard DCL command SEARCH.


++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FLIST]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
FLIST, UTILITIES, File and Directory manager for OpenVMS

FLIST V2.6-2  [17-AUG-2004]
Copyright  1990, 2004, Hunter Goatley.  All rights reserved.

----------------------------------------
This code may be freely distributed and modified for non-commercial
purposes as long as this copyright notice is retained.  Modified
copies may not be redistributed.
----------------------------------------

FLIST is a file and directory manager written in VAX TPU and VAX C (DEC
C).  The program was originally written in 1987 by Hunter Goatley. 
FLIST v2.0 includes many new features, added by Hunter Goatley and Peter
Galbraith.  (Generic EVE and DCL code by Peter Galbraith is provided to
support a "kept" EVE subprocess.  This code is compatible with the code
used by EVEplus.)  More recent versions include significant contributions
by John Powers.

Please forgive me for the bad code---I wrote it quickly and have never
had the time to go back and really do much with it.  It isn't as
pretty as I'd like, but it works.

There also isn't much documentation, but pressing "H" while in FLIST
will show you help on the commands available.

To build, simply execute LINK.COM.  FLIST runs on OpenVMS VAX,
OpenVMS Alpha, and OpenVMS IA64.

To use, you must define a logical and a symbol:

	$ define FLIST_TPU_SECTION device:[dir]FLIST.TPU$SECTION
	$ FLIST :== $device:[dir]FLIST.EXE

You can then type

	$ FLIST [file-spec]

The optional file-spec can contain wildcards.  Once inside of FLIST, you
can type H for a one-line description of some of the commands.  Pressing
PF2 will show you a list of all key definitions.

All of the FLIST commands consist of either single-key presses or
GOLD-key combinations; be careful which characters you type once inside
FLIST.  (If you use a DECwindows mouse for cut and paste between
DECterms, be careful that you don't paste into a DECterm running FLIST,
because each pasted character will be treated as an FLIST command.)

Known limitations:

  o  Long  file  names  get  truncated and can't be viewed; it's one of
     those little bugs I just haven't gotten to yet.

See AAAREADME.TOO for additional information on FLIST and KEPT EVE.


--------------------------------------------------------------------------------
CONTACTING THE AUTHOR

FLIST was written by Hunter Goatley.  Comments, suggestions, and questions
about this software can be directed to this e-mail address:

	goathunter@goatley.com

--------------------------------------------------------------------------------
COPYRIGHT NOTICE

This software is COPYRIGHT  1990, 2004 HUNTER GOATLEY. ALL RIGHTS
RESERVED. Permission is granted for not-for-profit redistribution, provided
all source and object code remain unchanged from the original distribution,
and that all copyright notices remain intact.

DISCLAIMER

This software is provided "AS IS".   The author makes no representations or
warranties with repsect to the software and specifically disclaim any implied
warranties of merchantability or fitness for any particular purpose.

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FREETYPE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
FREETYPE, Utilities, FREETYPE for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.



++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FREETYPE2_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Freetype2 library, Graphics, Library to render truetype fonts

Building

  It is actually very straightforward to install the Freetype2 library. Just
  execute vms_make.com from the toplevel directory to build the library. This
  procedure currently accepts the following options: 

  DEBUG 
    Build the library with debug information and without optimization. 

  lopts=<value> 
    Options to pass to the link command e.g. lopts=/traceback 

  ccopt=<value> 
    Options to pass to the C compiler e.g. ccopt=/float=ieee 

  In case you did download the demos, place them in a separate directory
  directly below the the toplevel directory of Freetype2 and follow the same
  instructions as above for the demos from there. The build process relies on
  this to figure the location of the Freetype2 include files. 

  To rebuild the sources it is neccessary to have MMS/MMK installed on the
  system. 


Test Applications

  The following demo applications can be build with Freetype2: 

  ftbench 
    Benchmark for some common FreeType paths 
    -m 
      max cache size in kByte (default is 1024) 
    -t 
      max time per bench in seconds (default is 2)
    -p 
      preload font file in memory 
    -b tests 
      perform choosen tests (default is all) 
      a 
      Load 
      b 
      Load + Get_Glyph 
      c 
      Load + Get_Glyph + Get_CBox 
      d 
      Get_Char_Index 
      e 
      CMap cache 
      f 
      Outline cache 
      g 
      Bitmap cache 
      h 
      SBit cache 
      
  ftchkwd 
    Check if a given font is fixed or proportional.
    Options: 
    fontname[.ttf|.ttc] [fontname2... 
      Name of the file containing the font to be processed

  ftdump 
    This program is a very simple font dumper. In its current incarnation, it
    will only output a font's name table, character encoding maps IDs and total
    memory consumption. For TrueType Open files, the available GSUB tables are
    also shown.
    Options: 
    fontname[.ttf|.ttc] 
      Name of the file containing the font to be processed 

  ftlint 
    This application is used to execute all glyphs instructions found in a font
    file at a given char size size. 
    No graphics subsystem required.
    Options: 
    ppem 
      Pointsize of the font 
    fontname[.ttf|.ttc] [fontname2...] 
      Name of the file containing the font to be processed

  ftmemchk 
    Simple memory tester
    Options: 
    ppem 
      Pointsize of the font 
    fontname[.ttf|.ttc] [fontname2...] 
      Name of the file containing the font to be processed 

  ftmulti 
    Multiple masters font viewer
    Options: 
    -e encoding 
      select encoding (default: no encoding) 
    -r R 
      use resolution R dpi (default: 72 dpi) 
    -f index 
      specify first glyph index to display 
    ppem 
      Pointsize of the font 
    fontname[.ttf|.ttc] 
      Name of the file containing the font to be rendered

  ftstring 
    This program demonstrates string text generation. It only displays a given
    message on the screen, and lets you resize it.
    Options: 
    -e enc 
      specify encoding tag (default: unic) 
    -r R 
      use resolution R dpi (default: 72 dpi) 
    -m message 
      message to display 
    ppem 
      Pointsize of the font 
    fontname 
      Name of the file containing the font to be rendered

  fttimer 
    This program is used to benchmark FreeType's scan-converter (the component
    in charge of translating a vectorial shape description into a bitmap). It
    does so in preloading all glyphs from a font file, then rendering them as
    fast as possible in a 640x450 buffer. The glyphs are rendered at size 
    400pt / 96dpi, which is _quite_ big.
    Options: 
    -r 
      repeat count to be used (default is 1) 
    -s 
      character pixel size (default is 600) 
    -m 
      render monochrome glyphs (default is anti-aliased) 
    -a 
      use smooth anti-aliaser 
    -l 
      force low quality even at small sizes 
    fontname[.ttf|.ttc] 
      Name of the file containing the font to be processed 

  ftview 
    A font viewer that supports hinting and font smoothing. 
    Options: 
    -r R 
      use resolution R dpi (default: 72 dpi) 
    -f index 
      specify first index to display 
    -e enc 
      specify encoding tag (default: no encoding) 
    -D 
      dump cache usage statistics 
    ppem 
      Pointsize of the font 
    fontname[.ttf|.ttc] 
      Name of the file containing the font to be rendered 

  testname 
    Prints the names of the glyphs in a font
    Options: 
    fontname 
      Name of the file containing the font to be processed 


The latest version of the OpenVMS port of Freetype2 should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/freetype2.htmlx

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FREEWARE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
FREEWARE, FREEWARE, The Master OpenVMS Freeware README File

                        OpenVMS Freeware CD-ROM ReadMe
                        ------------------------------

Welcome to the HP OpenVMS Freeware V7.0 CD-ROM.

All the software included on this CD-ROM is also available for (free)
download at the OpenVMS web site:

   http://www.hp.com/go/openvms/freeware/

This document contains a general introduction to the OpenVMS Freeware as
well as notes specific to the Freeware V7.0 distribution.

                             General Introduction
                             --------------------

The OpenVMS Freeware CD-ROM contains free software tools and utilities to aid
software developers, partners and OpenVMS Hobbyists in creating applications,
and in managing and using OpenVMS systems, as well as packages that can serve
as programming source code examples.

Contained on this CD-ROM are of packages for OpenVMS VAX, OpenVMS Alpha, and
OpenVMS I64, divided into general categories including the following:

         AFFINITY             Interoperation with Microsoft Windows systems
         BUILD_TOOLS          Build tools
         WEB_TOOLS            CGI and HTML tools
         GAMES                Games (also see Motif Toys)
         GRAPHICS             Graphics tools
         LANGUAGES            Compilers, assemblers, and language-related
         MISCELLANEOUS        Or ask for the creation of a new category
         MOTIF_TOYS           X Windows, CDE, and Motif toys (see Games)
         NETWORKING           Networking and network-related tools
         PROGRAMMING          Source Code Examples, APIs, etc
         SYSTEM_MANAGEMENT    Tools related to system management, security
         STORAGE_MANAGEMENT   Tools related to storage management
         UTILITIES            Random Utilities unrelated to other categories
         FREEWARE             Reserved for use by Freeware CD-ROM constructs

Many of these tools are popular packages already widely known and in use, 
while others are internally developed HP OpenVMS tools our engineers are 
making available to you, our OpenVMS customers. For example, the OpenVMS 
Freeware CD-ROM includes Bliss compilers for various OpenVMS platforms.

The Freeware CD-ROM includes the following features:

	o  Includes an easy-to-use 4GL-based menu system for
	   examining the contents of the CD-ROM.

  	o  Is in Files-11 format to make it readable on OpenVMS
           systems.

	o  Contains binaries, source code (except for the Bliss
           compilers and specific other HP-provided packages),
           and documentation.

	o  Represents some of the most popular, most often
           requested free packages, plus new items never before
           made public.

Disclaimer on Testing, Quality, and Licensing

The OpenVMS Freeware CD-ROM set is provided "AS IS" without warranty.  HP
adds no Freeware-specific restrictions on the distribution or redistribution
of the contents of these disks, nor adds any specific restrictions onto the 
redistribution of any packages on it. Be aware, however, that various of the 
individual packages on the CD-ROM may carry restrictions on their use or on
their redistribution, as imposed by the original author(s) or owner(s) of 
the package(s). Therefore, you should carefully read the documentation 
accompanying any products of interest. 

HP is providing this software free of charge and without warranty -- copies
of packages (and various package updates that might become available) can 
usually be downloaded from http://www.hp.com/go/openvms/freeware, and 
(additional) copies of this CD-ROM set can be ordered from HP for a small
media replication, handling, and distribution charge.

Included in the [FREEWARE] directory on this CD are various GNU software 
licenses.

HP makes no claims concerning this software, and provides this CD-ROM 
distribution to the OpenVMS community and to HP customers as a free 
service.


  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

         Remember, all packages contained herein are supplied AS IS.

         All packages are without any warranty, expressed or implied.

      HP has performed no verification, no code reviews, and no testing.

     You are solely responsible for support, debug, test and remediation.

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



                     General Freeware V7.0 release notes
                     -----------------------------------

  o There were the usual problems building the distributions due to errors
    found in various FREEWARE_README.TXT files, and due to submissions that
    were missing the (required) FREEWARE_README.TXT file.  The Keeper of the
    OpenVMS Freeware (KoF) apologizes for these changes.

  o The menu system is (still) (over)due to be replaced -- probably with a
    Lynx-based system of HTML files, or otherwise -- while the current
    menu environment is not expected to operate on OpenVMS I64.

  o Several BACKUP saveset submissions were unpacked only with difficulty, due
    to problems with the ZIP archive files.  Various file attributes were reset
    to match OpenVMS expectations, but there may well be additional files that
    do not have the expected file attributes.  One tool that may be useful for
    this [000TOOLS]RESET_BACKUP_SAVESET_ATTRIBUTES.COM.

  o The menu system is deliberately not requiring all CD-ROMs in the Freeware
    set to be mounted at the same time -- this avoids the requirement to have
    multiple CD-ROM drives.  This also unfortunately makes it somewhat more
    difficult to rummage around on the various disks.

  o Please take the time to examine the following files and directories:

      [000000]AAAREADME.*
      [000000]OPENVMS_FREQUENTLY_ASKED_QUESTIONS_FAQ.TXT
      [000000]00FREEWARE_ABSTRACT.TXT
      [000TOOLS]*.*
      [FREEWARE]*.*
      [VMSFAQ]*.*

    These files are replicated on all Freeware CD-ROM disks.

  o Current copies of the OpenVMS Frequently Asked Questions (FAQ) document
    are available at:

      http://www.hp.com/go/openvms/faq/


  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thank you,

Stephen Hoffman
Keeper of the Freeware
HP OpenVMS Engineering
December, 2004

+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FSHELP]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
FSHELP, utilities, A full screen help utility with lots of extra's

  FSHELP is a screen-oriented help utility. It makes use of SMG routines to 
  display help on video terminals. It has the following features

  - Full screen display of normal .HLB files (scrolling in both directions).
    Fshelp can also display data from .TLB, .OLB and .MLB files including
    an analyze/object of a module in an .OLB file
    (analyze/object for IA64 .OLBs can only be done on IA64 platform).
  - Selecting subtopics by just typing the name of the subtopic or enter.
  - Allows cross-referencing of help modules via extra info in help file.
  - Allows header lines to remain on screen when scrolling.
  - Allows you to look back at the last 20 topics.
  - Allows you to mark some help topics for easy return to this topic
  - Allows you to toggle 132/80 columns
  - On all screens help can be displayed via the HELP or PF2 key
  - FSHELP checks for all libraries via the hlp$library* logicals
     and lets you select one of them via the TAB key.
  - FSHELP also interfaces to the HELP/MESSAGE databases so you can
     define FSHELP as your normal help utility (HELP:=$'directory'FSHELP)
  - There is a sharable image that can be called from any other application
     to display help (lib$find_image_symbol), so you can display help
     in FSHELP format from any image.
  - FSHELP messages are in English, Nederlands(Dutch) or Frysk (A language
     spoken in the north of Holland). You can easily add you own language
     (see the .MSG file for help). FSHELP does not translate text in helpfiles,
     only the FSHELP messages are in the selected language.
  - You can search text within a help page ((PF1-)PF3), or on this page and all 
    deeper levels ((PF1-)FIND). If you are on the top page of the help library, 
    you can search through the whole library, or even in all loaded 
    libraries.
  
  Help files and libraries are in the same format as normal VMS help files. 
  The format is described in the 
  VMS LIBRARIAN UTILITY MANUAL, chapter 5 : HELP Libraries
  with the following additions. All these commands start with an ! so
  VMSHELP will ignore them.

  a. !# Signal the end of header lines in a help text. Th(is)(ese) lines
        (upto 4) will remain on screen, even when the rest of the text
        is scrolled.
  b. ![text on screen]@library topic topic ...
        FSHELP will save this information, and when you type the 
        F12 key, a list of topics will be displayed, from which you 
        can select one. @library is optional. This gives a possibility to
        make see-also entries.
  c. !@[text on screen]DCL command|dcl command...
	FSHELP will save this information, and when you type the
	PF1-E (execute) command, FSHELP will let you select one of the 
        execute-scripts.
        FSHELP will generate a batch-job in the queue FSHELP_QUEUE (default
        SYS$BATCH) containing the above lines (separated by |). In these
        commands you can specify symbols to be asked from you.
        These symbols are separated by '. FSHELP will check if there is
        a symbol with that name. If this symbol exists FSHELP will substitute
        the value of that symbol, otherwise FSHELP will ask you for
        a substitution.
        Example  !@[header]$compute 'test'/out=q.q|$print/delete q.q
        will try to find the symbol test, and if not found will ask you
        to specify a new value for 'test'. Then a batchjob will be 
        submitted in the queue in the symbol FSHELP_QUEUE (default SYS$BATCH)
        containing the lines:
         $compute new_value/out=q.q
         $print/delete q.q
        where new_value is the value found in the symbol TEST or the value
        given by you.

  VMS HELP will ignore all lines starting with ! (as will FSHELP), so these
  lines can be included without interfering with VMS HELP.

  You can enter help topics on the command line, just as VMS HELP.
  The format is

  fshelp [@libraryname] [topic [topic...]]

 FSHELP does not only display help files, it can also display data from
  .TLB, .OLB (object and shareable image files) and .MLB files
  via the qualifier(s) /text, /object, /image and /macro

 For further help look at the FSHELP help file, you can do that by typing
 fshelp=$'directory'fshelp_alpha  (or _vax or _ia64)
 fshelp/ownhelp
  Where 'directory' is the directory where fshelp (and its help file )
  can be found

 When looking at a help page, you can display the deeper topics by
 typing a Return, a /,  or a letter. This will display a menu containing
 the deeper topics. The / or letter will jump to the first topic containing
 that letter (or starting with that letter if you specified /NOSEARCHWILD).
 Typing FIND will jump to the next topic that matches.
 By typing more letters you can make your search more exact.
 PF4 or F10 returns to the previous screen. For more help type PF2 or HELP.

Usage:

Define fshelp as a foreign command
$FSHE*LP:=$'diretory'FSHELP_ALPHA   or FSHELP_VAX  or FSHELP_IA64

Start it as normal help

$FSHELP [topic [subtopic...]]]	!give normal help
$FSHELP/OWNHELP			!give help info about FSHELP
$FSHELP/TEXT [module] 		!Display [the module in] FORSYSDEF.TLB
$FSHELP/IMAGE  [module]		!display [the module in] IMAGELIB.OLB library
$FSHELP/OBJECT [module]         !Display [the module in] STARLET.OLB library
				! in the deeper help you can get analyze/object info
$FSHELP/MACRO  [module]		!display [the module in] LIB.MLB
$FSHELP/LIBR=*.HLB		!Display help about all .HLB files in SYS$HELP
$FSHELP/LIBR=*.HLB/LOAD		!Read all info from all .HLB files to memory for
				! fast access (this takes a while, but if you do
				! not leave FSHELP, access is fast).
				!  select libraries via the TAB key.
$FSHELP/MESSAGE Accvio          !give help/mess about the ACCVIO item

The libraries chosen for the /text, /objext, /macro ,/image can be changed.
  See the .MSG file for more info

There are a lot more qualifiers, see the FSHELP/OWNHELP for more info.

Note: Of course you can also define FSHELP as HELP.

Also included is a shareable image that can be called from any application
See the FSHELP_OUTPUT_HELP_EXAMPLE.FOR for more info. 
Contents:

This package contains the following files 

In the home directory
README.FIRST		This file
CREATE_FSHELP.COM	The command file to compile/link FSHELP and 
			the sharable image
FSHELP_ALPHA.EXE	The main executable alpha
FSHELP_SHR_ALPHA.EXE    The sharable image alpha
FSHELP_VAX.EXE      	The main executable vax
FSHELP_SHR_VAX.EXE      The sharable image vax
FSHELP_IA64.EXE      	The main executable ia64
FSHELP_SHR_IA64.EXE     The sharable image ia64
FSHELP.HLB		The help library

in the [.src] directory

a. The fortran sources

FSHELP.FOR		The main program
FSHELP_MAIN.FOR         The body for the sharable image
FSHELP_DISP_INFO.FOR	Display info about open libraries/modules
FSHELP_MSGHELP.FOR      The help/message routines
FSHELP_UTIL.FOR         Utility routines
FSHELP_SCR.FOR          SMG routines
FSHELP_FILES.FOR        FIle handling (lbr)
FSHELP_OBJECT.FOR       The module for analyze/object
FSHELP_OBJECT_VAX.FOR   The module for analyze/object of vax object
FSHELP_OBJECT_ALPHA.FOR The module for analyze/object of alpha object
FSHELP_OBJECT_IA64.FOR  The module for analyze/object of IA64 object on IA64
FSHELP_OBJECT_NOT_IA64.FOR The module for analyze/object of IA64 on vax/alpha
FSHELP_OUTPUT_HELP_EXAMPLE.FOR Example how to call the sharable image
VM_LIBRARY.FOR		Interface to LIB$GET_VM

b. the include files

ELFDEF.INC		The ELF object definitions (adapted from FORSYSDEF)
FSHELP_DEF.FOR		The definitions for the interface to FSHELP_SHR
FSHELP.INC		Internal definitions to fshelp
FSHELP_MSGHELP.INC	Internal definitions to fshelp for messagehelp files
VM_RECORD.INC		Definitions for VM_LIBRARY

c. The .cld file

FSHELP_CLD.CLD

d. The message file (includes all screen messages in all languages)

FSHELP_MSG.MSG

e. The help file

FSHELP.HLP

f. The jump vector (for VAX) for the sharable image

FSHELP_SHR.MAR

in the [.vax] subdirectory
 All the vax-objects of the sources

in the [.alpha] subdirectory
 All the alpha objects of the sources

in the [.ia64] subdirectory
 All the IA64 objects of the sources

Instructions:

unpack the .BCK file

The executables are included in the kit, but if you want to rebuild
FSHELP, do the following:
  If you have a fortran compiler you can compile and link

  $@create_fshelp 

  Otherwise, just link

  $@create_fshelp LINK

This will create the FSHELP_'architecture' and the FSHELP_SHR_'architecture'
images and the FSHELP.HLB help file.

I included the objects so you can adapt messsage files even if you do not have
a fortran compiler.

The most recent version can be donwloaded from oooovms.dyndns.org.

Author : Fekko Stubbe

If you have suggestions or questions, plaese mail to te address below
Email  : fshelpdev (at) oooovms.dyndns.org

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FTSO]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
FTSO, Utilities, File Transfer Tools for FTP Networks

This is the FTSO File Transfer environment for OpenVMS VAX and
OpenVMS Alpha.  This tool allows FTP transfers to be stopped
and restarted across network interruptions, among many other
features.

Also see FTSV.

A license PAK is provided.

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[FTSV]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
FTSV, Utilities, File Transfer Tools for DECnet Networks

This is the FTSV File Transfer environment for OpenVMS VAX and
OpenVMS Alpha.  This tool allows DECnet transfers to be stopped
and restarted across network interruptions, among many other
features.

Also see FTSO.

A license PAK is provided.

+++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[GD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++
 
GD, Utilities, gd 2.0.28 graphics library for fast image creation

This is a graphics library for fast image creation.

The most recent version of gd and of gd documentation is available
via http://www.boutell.com/gd/.


++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[GDCHART]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
GDCHART, utilities, GDCHART for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[GETCMD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
GETCMD V4.0, UTILITIES, Display others' command recall buffers

GETCMD V4.0
Copyright  1992--2004, Hunter Goatley.  All rights reserved.

This kit contains all the files necessary for installing the GETCMD utility.
Requires VMS V5.0 or later (VAX), OpenVMS Alpha V1.0 or later, or
OpenVMS IA64 V8.1 or later.

GETCMD.B32 is a BLISS-32 program that will display the DCL command
recall buffer for any interactive process on the system.

BUILDING
--------
To build GETCMD, just execute the LINK.COM procedure:

$ @LINK

If you have BLISS and want to build from the sources, an MMS file is
provided in [.SOURCE].


USAGE
-----
To set up GETCMD, just define a foreign symbol to run it:

$ getcmd :== $dev:[dir]getcmd.exe

where "dev:[dir]" is the device and directory where GETCMD lives.

To use it, simply specify a PID on the command line:

$ getcmd 202000AF

Qualifiers that may be specified are /PAGE, to do pause the output
after each full screen, and /OUTPUT=xxx, to redirect the output to a
file.

LIMITATIONS
-----------
GETCMD will not yet work with processes on other nodes in a cluster,
though this functionality is planned for a future release.

--------------------------------------------------------------------------------
Files in this directory:

AAAREADME.DOC		This file
AAAREADME.TOO		Change history
LINK.COM		Command procedure to link the image
GETCMD.ALPHA_OLB	GETCMD object library for Alpha AXP
GETCMD.ALPHA_OPT	Options file for Alpha AXP
GETCMD.HLP		On-line help for GETCMD
GETCMD.OLB		GETCMD object library for VAX
GETCMD.OPT		Options file for VAX

Files in [.SOURCE]:

CVTHELP.TPU		TPU source to convert .HELP file to .RNH
DESCRIP.MMS		Description file for building GETCMD
GETCMD.B32		BLISS source for main GETCMD routines
GETCMD.ALPHA_OPT	Options file for Alpha AXP
GETCMD.HELP		Source for GETCMD HELP file
GETCMD.OPT		Options file for VAX
GETCMD_CLD.CLD		CLI$ definitions file
GETCMD_MSG.MSG		Messages used by GETCMD
HG_OUTPUT.B32		BLISS source for output routines

--------------------------------------------------------------------------------
CONTACTING THE AUTHOR

Comments, suggestions, and questions about this software can be
directed to the author at one of the following addresses:

Mail:	Hunter Goatley
	P.O.  Box 51745
	Bowling Green, KY 42102-6745

Email:  goathunter@GOATLEY.COM

--------------------------------------------------------------------------------
COPYRIGHT NOTICE

This software is COPYRIGHT  1992--2004, HUNTER GOATLEY.  ALL RIGHTS RESERVED.

Permission is granted for not-for-profit redistribution, provided all
source and object code remain unchanged from the original
distribution, and that all copyright notices remain intact.

DISCLAIMER

This software is provided "AS IS".  The author and Process Software make no
representations or warranties with respect to the software and
specifically disclaim any implied warranties of merchantability or fitness
for any particular purpose.

++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[GNM]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
GNM, LANGUAGES, Common-sources tool for messages and documentation

This is GNM V2.3.

The GNM compiler allow you to have a common source file for both an 
OpenVMS message file (.MSG) and for DOCUMENT (.SDML) documentation.

GNM V2.0 was an overhaul of previous GNM versions, with improvements 
in the tool and its operations.  The command operations also differ 
from previous versions, and particularly with better diagnostics and
with a single executable image now used for both .MSG and .SDML output.

V2.3 fixes various problems found since V2.0, and adds GNM_COMPONENT
logical name translation, and includes support for building for both
OpenVMS Alpha V7.3-2 and later, and for OpenVMS I64.  (Please see 
the comments over in GNM.C for additional details.)

GNM makes extensive use of a finite-state parsing table based on the
OpenVMS lib$table_parse routine; the syntax and processing of the GNM
language is based entirely on this RTL routine.

Here is the basic foreign-command sequence:

  $ gnm :== $ddcu:[dir]gnm.exe
  $ gnm gnm-in-file.gnm msg-out-file.msg sdml-out-file.sdml

GNM converts a .GNM file into a standard OpenVMS message file, which
can then be processed by the MESSAGE compiler and then (optionally)
with MESSAGE/SDL (undocumented) and the SDL tool (Freeware) to create
language-specific include files.  GNM also converts the .GNM file into
an .SDML file for use with the TTI DECdocument package.

The .GNM file can be thought of as a series of directives:

   .NAME	    - The message symbol without the VDE$_
   .MESSAGE	    - The message text, it may be wrapped
   .EXPLANATION    - The description that appears in the document
   .USER_ACTION    - The recovery section that appears in the document.
   .BREAK	    - May be used to start a new paragraph in the
		      .explanation or .user_action
   .DESTINATION    - Which file the following appears in, parameters are
		      both, message
   .SEVERITY       - informational, success, warning, error, or fatal

The first 4 directives: .name, .message, .explanation, .user_action,
occur as a group in that order for each message.  .explanation and
.user_action are optional.  The FAO arguments within the .message
are contained within <>.  Within the <> there are 2 arguments, the
first is a word which will be emphasized in that position in the
document, the second is the FAO argument which will appear in the
message file in that position.  

The .destination directive must appear between message groups and is
in effect until another .destination directive occurs.  Thus, when
one message is to goto the message file only a .destination message
will precede the message group and a .destination both will follow
the group.  

.FACILITY and .END frame the contents of the GNM file.  The arguments
on the .FACILITY directive indicate the facility name and the facility
number, and the directive also accepts qualifiers to pass through to 
the MESSAGE file .FACILITY directive.

Use spaces for the indentation of the message text and explanations.

The following is an example of a GNM file:


.facility	facnam,facnum /PREFIX=prefix$_
!
! Success messages go here.  DO NOT REORDER.
!
.severity success
.destination message

.name	    SUCCESS1
.message	successful
.explanation	This message indicates success
.user_action	None required
!
! Informational messages go here.  DO NOT REORDER.
!
.base 500
.severity informational
.destination both

.name	    INFO1
.message	information <text, !AC> is displayed
.explanation	This message informs you of something, and shows how
		to include some text in the message using a standard
                FAO directive.
.user_action	None required

!
! Warning messages go here.  DO NOT REORDER.
! 
.base 1000
.severity warning
.destination both

.name	    WARNING1
.message	ambiguous '<text,!AC>'
.explanation	Cannot complete the command because '<EMPHASIS>(text)' 
		is ambiguous in the context of this command.
.user_action	None required

!
! Error messages go here.  DO NOT REORDER.
!
.base 1500
.severity error
.destination both

.name	    ERROR1
.message	whoops, something unusual this way walked
.explanation	a part of the magical unknown mystery tour,
                with seats still available.
.user_action	Wave a rubber chicken over the application.
                If that fails, upgrade to Rubber Chicken V2.0.

!
! Fatal messages go here.  DO NOT REORDER.  Very few messages should
! be of fatal severity.
!
.base 2000
.severity fatal
.destination both

.name	    FATAL1
.message	a fatal crash has occured, film at 11
.explanation	unknown fatal mystery error
.user_action	Dance for the computer.  It might help.

.end

++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[GNU-ZIP]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
GNUZIP, Utilities, gzip 1.2.4 file compression and Decompression

This package contains the GNU Zip software tool, and this tool
is used to compress or decompress files; if you have files with
a GZ in the file extension, these are probably files that have
been packaged and compressed with GNU Zip.

For additional details and for usage information, please see the
provided documentation, starting with the file named README.

This package contains versions of gzip and gunzip built for
OpenVMS Alpha and for OpenVMS I64.


++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[HEXCALC_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++
 
Hexcalc, Utilities, Multi-Radix Calculator


Building

  To build the Hexcalc application simply execute the supplied make.com. This
  should create the executable without further input.
  The program does need a copy of the Xaw library to be available on the system.
  In case make.com complains about this please check below for notes how to
  setup  the library for general use (check esp. the definition of the X11
  logical name).


Installation of Xaw3d/Xmu

Shareable Images


  The result of the built are two shareable images, one for Xaw3d and one for
  Xmu. Although one can give a full path for a shareable image at link time,
  OpenVMS does expect to find the file in sys$share at runtime. OTOH for various
  reasons one might not want/be able to place the files in this location. To
  solve this problem just define a logical with the same name as the shareable
  image and point with this to the location of the image in the filesystem, e.g.
  on my system I have: 

$ sh log xmulibshr
   "XMULIBSHR" = "PUBBIN:XMULIBSHR" (LNM$PROCESS_TABLE)
$ sh log xaw3dlibshr
   "XAW3DLIBSHR" = "PUBBIN:XAW3DLIBSHR" (LNM$PROCESS_TABLE)


Header files

  Source files ported from a Unix system often contain include statements like
  this #include <X11/Xmu/file.h>, which reflects the organization of these files
  on this OS, i.e. the header files for Xmu/Xaw(3d)/... are located in a
  sub-directory of the one containing the X11 header files. To be able to work
  with syntax like this on an OpenVMS system one has to tweak the usual
  definition of the logical X11 a bit ;-). 
  One thing is that one has to make X11 a rooted logical, so that a path like
  x11:[xmu] (which is what the above translates to on OpenVMS) makes sense. The
  second is that once again one might want to separate the header files delivered
  by Digital from the ones coming with this package. To do this create a toplevel
  directory as the home for non-DEC header files and add to this subdirectories
  named xmu and xaw. Copy the header-files from the distribution to these new
  directories. 
  As an example the definition on my system looks like this: 

$ sh log x11
   "X11" = "X11ADD" (LNM$PROCESS_TABLE)
        = "X11ADD:[XPM.LIB]"
        = "DECW$INCLUDE"
        = "PUBBIN"
1  "X11ADD" = "DKA300:[PUBLIC.XTOOLS.LIBS.]" (LNM$PROCESS_TABLE)
1  "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"
1  "PUBBIN" = "PUBLIC$ROOT:[AEXE]" (LNM$PROCESS_TABLE)
   "X11" = "DECW$INCLUDE" (DECW$LOGICAL_NAMES)
1  "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"

  x11add
    Rooted logicals have to be first in the list (in this case x11add), also note
    that a rooted logical may not contain another rooted logical in its
    definition. 
  x11add:[xpm.lib]
    Location of the X Pixmap Library header files. On Unix they are stored
    directly in the X11 directory. 
  decw$include 
    Also get the standard header files ;-) 
  pubbin 
    Actually not the location of header files, but rather the place where I keep my
    libraries. In some circumstances usefull for linking purposes. 

The latest version of the OpenVMS port of Hexcalc should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/hexcalc.htmlx


++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[HGFTP]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
HGFTP, NETWORKING, An FTP client/server for VMS

   This is HGFTP V3.1-2

   [4-MAR-2004]

   HGFTP is an FTP client and server for OpenVMS VAX and OpenVMS
   AXP. HGFTP works with MadGoat's NETLIB TCP/IP library, which
   means that it works with virtually every implementation of TCP/IP for
   VMS.  HGFTP used to be known as MGFTP (MadGoat FTP).

   HGFTP started life as the CMU-Tek FTP client and server. Many
   thanks go to John Clement and Henry Miller, who made the CMU FTP much
   better than it used to be. The MadGoat version was modified to work
   with NETLIB and includes numerous enhancements and bug fixes. The
   MadGoat version was done by Darrell Burkhead and Hunter Goatley.
   The HGFTP version is solely maintained by Hunter Goatley.

   TCP/IP Services sites, in particular, should find HGFTP of interest.
   Some of the features include:

     * The client features a VMS CLI$ interface, with support for normal
       UNIX-style commands. For example, SET DEFAULT and CD both change
       the remote working directory. Unlike MultiNet's client, which
       offers a TOPS-20-style interface, HGFTP provides a VMS-style
       interface with the case preservation, etc., of a UNIX-style
       interface.

     * Full UNIX systme emulation in the FTP server, allowing virtually
       any client to work with the server.

     * The HGFTP client and server support STRU O VMS. When both a
       server and a client support STRU VMS, VMS file attributes are
       retained when files are transferred.

       UCX does not support STRU VMS, making HGFTP ideal for UCX
       sites connecting to anonymous FTP sites running MultiNet.

     * The HGFTP server fully supports ANONYMOUS FTP accounts.
       Anonymous accounts can be restricted to certain directories, etc.,
       as you expect from an anonymous FTP server. The HGFTP server
       is running on ftp.wku.edu, if you'd like to see its output.

     * The HGFTP server implements the REIN command, which lets you
       log out of an account and log in to another without disconnecting
       from the remote server.

     * FTP/ANONYMOUS on the DCL command line automatically logs you in as
       an anonymous user.

     * The client automatically senses the file type, so you don't have
       to remember to say "Image" or "Ascii" before transferring a file.

     * May be started without the server, supplying a client-only option.

     * Works in batch mode.

   HGFTP installs using VMSINSTAL. It is distributed with full
   documentation in the form of on-line help, PostScript, ASCII text,
   HTML, and Bookreader files. The BLISS sources are also distributed
   with the software.

     _________________________________________________________________

  CONTACTING THE AUTHORS

   HGFTP is maintained and enhanced by Hunter Goatley. To report bugs,
   please send mail to goathunter@goatley.com.

++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[HGLOGIN]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
HGLOGIN, UTILITIES, Log in to an account without a password

HGLOGIN (Hunter's LOGIN)
Copyright  1997, 2004, Hunter Goatley.  All rights reserved.

------------------------------
HGLOGIN is a rewrite and enhancement of the GLOGIN utility written by
Anthony C. McCracken, Northern Arizona University, in 1992.

HGLOGIN uses the PTD$ routines supplied by VMS and may not work on
older versions of VMS.
------------------------------

HGLOGIN lets privileged users log in to a named account without having
to know the password for that account.  A process running under the
target username is created.  Its input and output are read from a
pseudo-terminal, which is controlled by HGLOGIN.

Unlike BECOME and SWAP, the process created by HGLOGIN is a full
process, with all the privileges, rights identifiers, quotas, DCL
symbols, logical names, etc., as well as anything else that is set up
in the target user's LOGIN.COM.

HGLOGIN requires the target username as a parameter.  If there is
other text on the line, HGLOGIN enters "single command mode." The
remaining text is passed to the new process to be executed by DCL. 
When the command execution completes, the process is automatically
logged out and control returns to the original process.

You can use HGLOGIN to log into DISUSERed accounts by specifying the
qualifier /NOUAF.


INSTALLING HGLOGIN
------------------
To build the executable:

* Execute the following command to produce HGLOGIN.EXE from the supplied
  binaries:

	$ @LINK.COM

* If you have the BLISS sources and the MMS description file available,
  use MMK to compile and link the executable.

* You can install the online help in a help library using a command like
  the following:

        $ LIBRARY/HELP/INSERT SYS$HELP:HELPLIB.HLB HGLOGIN.HLP

Once you have the HGLOGIN.EXE file, you can set up a DCL foreign command
to run HGLOGIN:

	$ hglogin :== $disk:[directory]HGLOGIN.EXE

To log in as user SYSTEM, simply issue:

	$ hglogin system

The effect will be similar to using SET HOST 0 or TELNET to log in to
local system.

To execute a single command under the target username, issue a command
like:

	$ hglogin system mail

In the example above, you will be logged in as SYSTEM and the MAIL
command will be executed in the SYSTEM process.  When you QUIT or EXIT
MAIL, you're automatically logged out of the SYSTEM process.

HGLOGIN and SET TERM/INQUIRE
----------------------------
HGLOGIN's single-command mode will not work properly if either
SYLOGIN.COM or the target user's LOGIN.COM include the command SET
TERMINAL/INQUIRE.  Normally, the commands sent to the process are
purged when the SET TERMINAL/INQUIRE command executes.

In cases like this, you must use the /PROMPT qualifier to tell HGLOGIN
what the DCL prompt will be once the process is logged in.  HGLOGIN
will then wait for the given prompt (which defaults to "$") before
sending its commands to the process.

	$ hglogin/prompt="What?" system mail

There is also a /NOQUIET qualifier that can be given to override
HGLOGIN's "quiet mode" in single-command mode.  HGLOGIN/NOQUIET will
display all the output from the process.

IF you try to use single-command mode and never see any output, type
LOGOUT and then use HGLOGIN/NOQUIET to see the output and prompt.  You
can then use /PROMPT to force HGLOGIN to wait for the DCL prompt.

--------------------------------------------------------------------------------
CONTACTING THE AUTHOR

HGLOGIN was written by Hunter Goatley.  Comments, suggestions, and
questions about this software can be directed to this e-mail address:

	goathunter@GOATLEY.COM

--------------------------------------------------------------------------------
COPYRIGHT NOTICE

This software is COPYRIGHT  1997, 2004 HUNTER GOATLEY. ALL RIGHTS
RESERVED. Permission is granted for not-for-profit redistribution, provided
all source and object code remain unchanged from the original distribution,
and that all copyright notices remain intact.

DISCLAIMER

This software is provided "AS IS".  The author and Process Software make
no representations or warranties with repsect to the software and
specifically disclaim any implied warranties of merchantability or fitness
for any particular purpose.

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[HGSD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
HGSD, UTILITIES, Yet another smart SET DEFAULT replacement

SD V2.3-1  [11-FEB-2004]
Copyright  1998, 2004, Hunter Goatley.  All rights reserved.

This is my version of SD, a SET DEFAULT replacement based on an old DECUS
submission by Alan Zirkle.  This version implements a stack of the last 16
directories visited, as well as short-cuts for specifying directory specs.

  Set/Show Default Directory

  SD ^      Go up one subdirectory level
  SD @      Go to top level of current directory (enter TOP for help)
  SD .      Go to login default directory and disk
  SD #n     Go to directory in n'th entry of the SD stack
  SD #      Set default to stack entry #1 (toggle stack entries)
  SD >X     Set default to [z.X] when currently in [z.y]
  SD >      Move to alphabetically next directory at same level
  SD <      Move to alphabetically previous directory at same level
  SD .X     Set default to [current.X]
  SD X.Y.Z  Set default to [X.Y.Z] (enter X for help)
  SD %      Push the current default onto the stack
  SD *      Show the SD stack (enter STACK for help)
  SD ?      Show this SD help information
  SD &      Unconceal a directory specification
  SD        Show the current default

SD can also set your prompt equal to the default directory name if the
logical HG_SD_SET_PROMPT is defined.

INSTALLING SD
-------------
To build the executables:

* Execute the following command to produce SD.EXE and SD_PROMPT.EXE from
  the supplied binaries:

	$ @LINK.COM

* If you have the BLISS sources and the MMS description file available,
  use MMK or MMS to compile and link the executable.

Once you have the SD*.EXE files, you can set up a DCL foreign command
to run SD:

	$ sd :== $disk:[directory]SD.EXE

For SD to find its help file, you should set its protection to W:RE
and define the following logical:

	$ copy sd.hlb dev:[dir]/prot=w:re
	$ define/system/exec HG_SD_HLB dev:[dir]SD.HLB

You can also include the file SD.HLP in a local help library to make
it available via the HELP command.

SD ? gets you help.

SETTING THE DCL PROMPT
----------------------
The SET_PROMPT.EXE image contains code to set the DCL prompt to the
name of the current default directory.

	$ sd :== $disk:[directory]SD_PROMPT.EXE

To actually have SD set your prompt, the following logical must be
defined:

	$ DEFINE HG_SD_SET_PROMPT TRUE

Note that you must have CMEXEC privilege in order to set the DCL
prompt. To allow non-privileged users to set their prompts,
SD_PROMPT.EXE can be INSTALLed with CMEXEC privilege:

	$ install add disk:[dir]sd_prompt.exe/open/header/share-
		/priv=(noall,cmexec)

--------------------------------------------------------------------------------
CONTACTING THE AUTHOR

HGSD was written by Hunter Goatley.  This version is a C rewrite
of the original MACRO32 program, written March 14, 1987. Comments,
suggestions, and questions about this software can be directed to the
author at this e-mail address:

	goathunter@goatley.com

--------------------------------------------------------------------------------
COPYRIGHT NOTICE

This software is COPYRIGHT  1987, 1997, 2004 HUNTER GOATLEY. ALL RIGHTS
RESERVED. Permission is granted for not-for-profit redistribution, provided
all source and object code remain unchanged from the original distribution,
and that all copyright notices remain intact.

DISCLAIMER

This software is provided "AS IS".  The author, Hunter Goatley, and
Process Software make no representations or warranties with repsect to
the software and specifically disclaim any implied warranties of
merchantability or fitness for any particular purpose.

++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[HTMLDOC]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
HTMLDOC, UTILITIES, Translate HTML pages into Postscript or PDF

This is a port of EasySW HTMLDOC, a freeware tool which converts HTML 
documents or webpages into .PS or .PDF files.

HTMLDOC is distributed under the GNU General Public License (GPL) without
restrictions on usage or redistribution. The file, COPYING.TXT, contains the 
GNU GPL License and other copyright information.

The OpenVMS port does not have a GUI interface but supports all HTMLDOC's 
command-line options. See Chapter 8 of the HTMLDOC Software Users Manual
for details: http://www.easysw.com/htmldoc/htmldoc.html#CMDREF

Example usage:

$ htmldoc --webpage -f output.pdf input.html

The above command generates OUTPUT.PDF from INPUT.HTML. Any linked images in 
the html file will be included in the PDF. 

$ htmldoc --webpage -f yahoo.pdf http://www.yahoo.com

translates the internet web page into a PDF. If behind a firewall, use the
option --proxy http://xxx.xx.com:(port)

The OpenVMS HTMLDOC kit contains:

FREEWARE_README.TXT         (this file)
HTMLDOC-AXPVMS-V0100-1.EXE  A self-extracting Alpha OpenVMS archive containing a PCSI Kit
HTMLDOC-1_8_23_SRC.ZIP      ZIP file with HTML sources and OpenVMS build scripts

pat.moran@hp.com

+++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[HTTPD_WASD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++
 
WASD_Web_Package, UTILITIES, VMS HTTP Server and CGI applications

The "WASD VMS Hypertext Services" package is a collection of World Wide Web
software for supporting hypertext within a VMS environment.

Provides a multi-threaded HTTP server, for VMS 6.n, 7.n, 8.n Alpha, Itanium and
VAX platforms, and the TCP/IP BG: driver (i.e. supported for UCX v3/4.n,
OpenVMS TCP/IP Services v5.n, MultiNet, TCPware, and anything else supporting
the BG: QIO API). It features integrated pre-processed HTML (Server Side
Includes) and image-mapping, and a versatile VMS directory listing capability. 
Includes CGI applications providing extensive access to VMS oriented
information, including HELP and TEXT libraries, and Bookreader documentation. 
Supports high efficiency and throughput, *persistant* scripts, including
scripting environments such as Perl, PHP, FastCGI and Java.

Access the HTML documentation using a browser on the local system.  First
ensure the freeware CD is mounted /SYSTEM, then enter

        file:///cd-device/httpd_wasd/index.html

into the "Location:" field of the browser.

Alternatively, print a copy of the Technical Overview.

        $ PRINT /QUEUE=postscript-queue cd-device:[HTTPD_WASD.DOC.HTD]HTD.PS

This is a large document, so if you have a printer providing two pages per
sheet and/or double-sided it is recommended to submit the job with the
appropriate parameters!

Mark.Daniel@wasd.vsm.com.au
(Mark.Daniel@dsto.defence.gov.au)
November 2004

++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[IMAGEMAGICK]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
IMAGEMAGICK, GRAPHICS, Package for display/manipulation of images

ImageMagick is an X11 package for display and interactive manipulation
of images.  The package includes tools for image conversion,
annotation, compositing, animation, and creating montages.  ImageMagick
can read and write many of the more popular image formats (e.g. JPEG,
TIFF, PNM, XPM, etc.).



+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[INFO-ZIP]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
INFO-ZIP, Utilities, File Compression and Decompression Tools

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.



++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[INFOMON]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
InfoServer Monitor, SYSTEM_MGMT, InfoServer disk mount utility

InfoServer Monitor will keep CDs and hard disks on InfoServers mounted properly.

This version, V2.2A, is identical to V2.2.  The only difference is addition of
support for OpenVMS I64 systems.  Updated release notes are at
INFOMONA022.RELEASE_NOTES and the installation guide at INFOMON.PS (PostScript)
and INFOMON.TXT (text).

++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[JED]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
JED, Utilities, The JED Text Editor

JED is a freely available text editor written by John E. Davis. It is available
from "http://www.jedsoft.org/jed/".

This is a binary kit for OpenVMS/VAX (V7.1) -/Alpha (V7.3-2) and -/I64 (FT8.2)
based on JED version B0.99-17 as of 19-Jul-2004. The only difference is the
packaging, an enhancement to access files via DECnet, changes to the DCL mode
(now with syntax highlighting) and a BLISS mode (just syntax highlighting).

Please note, B0.99-17 is a pre-release. Check the JED home page for the
upcoming official release (which should have the above enhancements included).

The package is the original distribution but without the sources. Additional
files are placed in the SITE sub directory tree.

To use JED, after unpacking the kit, invoke the [.SITE]SETUP.COM command
procedure to define a JED_ROOT logical and the foreign command JED.

Features of the JED Editor (extracted from the JED home page)

* Color syntax highlighting on color terminals, e.g., Linux console or a remote
  color terminal via dialup (as well as Xjed).
* Folding support
* Drop-down menus on _ALL_ terminals/platforms.
* Emulation of Emacs, EDT, Wordstar, Borland, and Brief editors.
* Extensible in the C-like S-Lang language making the editor completely
  customizable.
* Capable of reading GNU info files from within JED's info browser
* A variety of programming modes (with syntax highlighting) are available
  including C, C++, FORTRAN, TeX, HTML, SH, python, IDL, DCL, NROFF...
* Edit TeX files with AUC-TeX style editing (BiBTeX support too).
* Asynchronous subprocess support allowing one to compile from within the editor
* Built-in support for the GPM mouse driver on Linux console.
* Abbreviation mode and Dynamic abbreviation mode.
* 8 bit clean with mute/dead key support.
* Supported on most Unix, VMS, OS/2, MSDOS (386+), win9X/NT, QNX, and BeOS
  systems.
* Rectangular cut/paste; regular expressions; incremental searches; search
  replace across multiple files; multiple windows; multiple buffers; shell
  modes; directory editor (dired); mail; rmail; ispell; and much, much more. 

JED and file access via DECnet

- from the command line:
	$ jed "node""username password""::filename"
  The outer double quotes are required to let DCL pass one argument instead of
  two, separated by ' ', the inner doubled double quotes are DCL conventions for
  having a single double quote in a quoted string.

- with the open or find file command:
	Find file: node"username password"::filename

Please be aware, JED is doing C style I/O over the net. For large files this
is not as efficient as a DECnet copy.

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[JPEG]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
JPEG, utilities, JPEG Image Compression and Decompression

The Collector of OpenVMS Freeware has provided this file to
satisfy the Freeware menu requirements; this package provides
JPEG Image Compression and Decompression.


++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[TTI_INTOUCH]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
INTOUCH, LANGUAGES, High-performance 4GL for OpenVMS VAX/AXP systems

INTOUCH 4GL is the high-performance 4GL for OpenVMS VAX and AXP systems. 

INTOUCH 4GL runs on all versions of OpenVMS -- VAX/VMS V4.5 to 6.x,
AXP/VMS V1.5 and 6.x.

INTOUCH 4GL interfaces to RMS, Rdb, DEC DBMS, ORACLE, dBASE, and other
database engines.  However, this {freeware} version only includes the RMS
interface.

INTOUCH 4GL comes complete with a "Guided Query Language" (GQL) and 
a "GQL On-line Tutorial".  However, this {freeware} GQL version only
supports ten (10) columns of reporting information.  The fully-featured
GQL supports reports of unlimited complexity!


                       INTOUCH 4GL Documentation

The complete INTOUCH 4GL documentation (in Postscript form) is located
on this CD-ROM in [TTI_INTOUCH.DOC].  

For the complete hard-copy set of INTOUCH 4GL documentation ($95.00 US), 
contact us at:

  INTOUCH 4GL
  Touch Technologies, Inc.
  9988 Hibert #310
  San Diego, CA  92131

  Voice: 800-525-2527  or  619-566-3603
  FAX# : 619-566-3663
  Internet: intouch@ttisms.com


               Installing INTOUCH 4GL to your Hard Disk

To install INTOUCH 4GL from this CD-ROM: to your hard disk (called
{mydisk:} in this example):

  $ create/dir/prot=w:re {mydisk:[intouch]}
  $ copy freeware$cd:[tti_intouch]*.*; {mydisk:[intouch]}
  $ set default {mydisk:[intouch]}
  $ @intouch_build

Then, add this line to your system-wide LOGIN.COM file:

   {$ @mydisk:[intouch]intouch.com}

The INTOUCH 4GL installation will take less than 10 minutes.


                   INTOUCH 4GL Full-Feature Upgrade

For information on how to upgrade this {freeware} copy of INTOUCH 4GL to
the fully-featured, 7/24 supported version, or for the full set of
hardcopy INTOUCH 4GL documentation, contact us at:

  INTOUCH 4GL
  Touch Technologies, Inc.
  9988 Hibert #310
  San Diego, CA  92131

  Voice: 800-525-2527  or  619-566-3603
  FAX# : 619-566-3663
  Internet: intouch@ttisms.com


...Interested in a FREE "Born to Code" Polo shirt?


Yes?

Please see the file [TTI_INTOUCH]SURVEY.TXT.  (Offer limited to the
first 1,000 respondents!)


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_1:[VMSFAQ]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
VMSFAQ, FREEWARE, The OpenVMS Frequently Asked Questions (FAQ)

This directory contains an edition of the OpenVMS FAQ, and in
various document formats.

The FAQ contains answers to many of the more commonly-asked 
questions associated with OpenVMS and with its various related 
hardware platforms, and pointers to many of the available 
OpenVMS resources, to tutorials and training materials, and 
to many other supporting materials.

The text-format version of the FAQ is very likely the easiest
to serve, to download, and particularly to search.  (If you
want to download and use just one of the various FAQ formats, 
pick the text-format FAQ.)

The OpenVMS FAQ is updated once or twice per year, and sometimes 
more or less often.  Please check for the latest version of the 
OpenVMS FAQ, as available in the comp.os.vms, news.answers and 
comp.answers newsgroups, and is served from, or is linked from,
various websites including the following:

    http://www.hp.com/go/openvms/faq/
    ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/
    news://comp.answers
    news://news.answers
    http://www.faqs.org/
    http://www.google.com/
    http://www.kjsl.com/vmsfaq
    http://eisner.decus.org/vms/faq.htm
    http://www.hoffmanlabs.org/


+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[000TOOLS]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
000TOOLS, FREEWARE, Various Useful Tools

This directory contains a DEFINE_TOOLS.COM procedure used to
establish DCL foreign commands for a collection of useful DCL 
command procedures and executable images, and this particularly
contains the Unzip tools necessary to unpack the Zip archives.

This directory tree is duplicated on all OpenVMS Freeware disks.


+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[FREEWARE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
FREEWARE, FREEWARE, The Master OpenVMS Freeware README File

                        OpenVMS Freeware CD-ROM ReadMe
                        ------------------------------

Welcome to the HP OpenVMS Freeware V7.0 CD-ROM.

All the software included on this CD-ROM is also available for (free)
download at the OpenVMS web site:

   http://www.hp.com/go/openvms/freeware/

This document contains a general introduction to the OpenVMS Freeware as
well as notes specific to the Freeware V7.0 distribution.

                             General Introduction
                             --------------------

The OpenVMS Freeware CD-ROM contains free software tools and utilities to aid
software developers, partners and OpenVMS Hobbyists in creating applications,
and in managing and using OpenVMS systems, as well as packages that can serve
as programming source code examples.

Contained on this CD-ROM are of packages for OpenVMS VAX, OpenVMS Alpha, and
OpenVMS I64, divided into general categories including the following:

         AFFINITY             Interoperation with Microsoft Windows systems
         BUILD_TOOLS          Build tools
         WEB_TOOLS            CGI and HTML tools
         GAMES                Games (also see Motif Toys)
         GRAPHICS             Graphics tools
         LANGUAGES            Compilers, assemblers, and language-related
         MISCELLANEOUS        Or ask for the creation of a new category
         MOTIF_TOYS           X Windows, CDE, and Motif toys (see Games)
         NETWORKING           Networking and network-related tools
         PROGRAMMING          Source Code Examples, APIs, etc
         SYSTEM_MANAGEMENT    Tools related to system management, security
         STORAGE_MANAGEMENT   Tools related to storage management
         UTILITIES            Random Utilities unrelated to other categories
         FREEWARE             Reserved for use by Freeware CD-ROM constructs

Many of these tools are popular packages already widely known and in use, 
while others are internally developed HP OpenVMS tools our engineers are 
making available to you, our OpenVMS customers. For example, the OpenVMS 
Freeware CD-ROM includes Bliss compilers for various OpenVMS platforms.

The Freeware CD-ROM includes the following features:

	o  Includes an easy-to-use 4GL-based menu system for
	   examining the contents of the CD-ROM.

  	o  Is in Files-11 format to make it readable on OpenVMS
           systems.

	o  Contains binaries, source code (except for the Bliss
           compilers and specific other HP-provided packages),
           and documentation.

	o  Represents some of the most popular, most often
           requested free packages, plus new items never before
           made public.

Disclaimer on Testing, Quality, and Licensing

The OpenVMS Freeware CD-ROM set is provided "AS IS" without warranty.  HP
adds no Freeware-specific restrictions on the distribution or redistribution
of the contents of these disks, nor adds any specific restrictions onto the 
redistribution of any packages on it. Be aware, however, that various of the 
individual packages on the CD-ROM may carry restrictions on their use or on
their redistribution, as imposed by the original author(s) or owner(s) of 
the package(s). Therefore, you should carefully read the documentation 
accompanying any products of interest. 

HP is providing this software free of charge and without warranty -- copies
of packages (and various package updates that might become available) can 
usually be downloaded from http://www.hp.com/go/openvms/freeware, and 
(additional) copies of this CD-ROM set can be ordered from HP for a small
media replication, handling, and distribution charge.

Included in the [FREEWARE] directory on this CD are various GNU software 
licenses.

HP makes no claims concerning this software, and provides this CD-ROM 
distribution to the OpenVMS community and to HP customers as a free 
service.


  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

         Remember, all packages contained herein are supplied AS IS.

         All packages are without any warranty, expressed or implied.

      HP has performed no verification, no code reviews, and no testing.

     You are solely responsible for support, debug, test and remediation.

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



                     General Freeware V7.0 release notes
                     -----------------------------------

  o There were the usual problems building the distributions due to errors
    found in various FREEWARE_README.TXT files, and due to submissions that
    were missing the (required) FREEWARE_README.TXT file.  The Keeper of the
    OpenVMS Freeware (KoF) apologizes for these changes.

  o The menu system is (still) (over)due to be replaced -- probably with a
    Lynx-based system of HTML files, or otherwise -- while the current
    menu environment is not expected to operate on OpenVMS I64.

  o Several BACKUP saveset submissions were unpacked only with difficulty, due
    to problems with the ZIP archive files.  Various file attributes were reset
    to match OpenVMS expectations, but there may well be additional files that
    do not have the expected file attributes.  One tool that may be useful for
    this [000TOOLS]RESET_BACKUP_SAVESET_ATTRIBUTES.COM.

  o The menu system is deliberately not requiring all CD-ROMs in the Freeware
    set to be mounted at the same time -- this avoids the requirement to have
    multiple CD-ROM drives.  This also unfortunately makes it somewhat more
    difficult to rummage around on the various disks.

  o Please take the time to examine the following files and directories:

      [000000]AAAREADME.*
      [000000]OPENVMS_FREQUENTLY_ASKED_QUESTIONS_FAQ.TXT
      [000000]00FREEWARE_ABSTRACT.TXT
      [000TOOLS]*.*
      [FREEWARE]*.*
      [VMSFAQ]*.*

    These files are replicated on all Freeware CD-ROM disks.

  o Current copies of the OpenVMS Frequently Asked Questions (FAQ) document
    are available at:

      http://www.hp.com/go/openvms/faq/


  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thank you,

Stephen Hoffman
Keeper of the Freeware
HP OpenVMS Engineering
December, 2004

++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LATEX2RTF_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Latex2RTF, Utilities, Translate Latex to RTF

Installation


Just execute @vms_make to build the program. This checks if a C compiler is 
installed and will exit with an error message if non can be found. 


Build options


VMS_make.com currently accepts the following options in arbitrary order: 

DEBUG
  Build the library with debug information and without optimization. 
lopts=<value>
  Options to pass to the link command e.g. lopts=/tracback 
ccopt=<value>
  Options to pass to the C compiler e.g. ccopt=/float=ieee 
LINK
  Do not compile, just link Latex2RTF. 
CC=<DECC||VAXC||GNUC>
  Force usage of the given C compiler over the intrinsic selection (which is 
  DEC C, VAX C, and finally GNU C). 

Environment


The operation of Latex2RTF is governed by a number of configuration files, 
which the program tries to locate using the following logical names: 

L2RCFGDIR
  This logical should point to the system wide configuration files. 
RTFPATH
  This logical should point to user customized configuration files, which the 
  particular user wants to use on a regular basis. 

Additional for specific customisations you may use the "-P path" commandline 
qualifier while invoking Latex2RTF 


A reasonable set of standard configuration files may be found in the [.cfg] 
subdirectory. 

The latest version of this document should always be
accessible via

http://zinser.no-ip.info/vms/sw/latex2rtf.htmlx

+++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++
 
LD071, SYSTEM_MGMT, OpenVMS VAX and Alpha Virtual Disk Driver

This LD kit and its contents are not supported.

This is an update to the versions of the LDDRIVER kit found on previous
Freeware releases, and this kit installs on OpenVMS Alpha V7.3, V7.3-1,
and V7.3-2, and on OpenVMS VAX V7.3.

This kit supercedes the LD063 and LD731 kits.

This kit will not install on OpenVMS Alpha V8.2 and later, as that and
subsequent releases contain integrated support for LD.  (Releases OpenVMS 
Alpha V7.3-1 and later do have all necessary pieces of LD latent, but the
command verb is not registered in DCLTABLES by default prior to V8.2.
Please see SYS$MANAGER:CDRECORD.COM for related details.)

Before installing this on OpenVMS Alpha V7.3-1 and V7.3-2, please first 
ensure that there are no newer ECO kits for LDDRIVER.

OpenVMS I64 V8.2 and later contains integrated support for LD; there is
no need for a kit on these releases.

It is presently expected that this LD kit will be the final separate 
release for OpenVMS Alpha.

This kit may or may not operate on releases older than OpenVMS Alpha
V7.3, nor on releases earlier than OpenVMS VAX V7.3.

Releases LD063 and prior have a hard upper volume size limit of four 
gigabytes (4 GB), and larger volumes should not be configured.  This 
kit, as well as the integrated LD implementation available in OpenVMS
Alpha and OpenVMS I64 V8.2 and later (and potentially also the most
current LD ECO kits for V7.3-2, if any), do not contain this volume
capacity limit.


++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LGILDAP]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
LGILDAP, System_Mgmt, LDAP External Authentication Module for OpenVMS

Open Source Software

Version 1.1


News: Tested together with Active Directory running on W2K. If AD4Unix is
installed on W2K server no modifications are needed to get it to work. License

This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc., 59 Temple
Place, Suite 330, Boston, MA 02111-1307 USA

Author

Jonas Lindholm, 2004-05-25, <jlhmATusaDOTnet>

Why

Why doing this when HP very soon will release its own LDAP authentication
software?  Well, why not doing it? It is fun and perhaps this software has
functions that the software from HP lacks.  And, you do not need to use it.

Download

You can download the latest version here:

http://vms.dnsalias.com

The zipped file contains 4 zip files with the source code.

There is currently no precompiled version available.

This software enable LDAP authentication to OpenVMS using loginout callable
interface.

It can add users automatically whenever a user, specified during login, is
allowed to logon to the host. This addition is done even if the user specifies
an invalid password.

Users added by the LGI LDAP Server process is target for removal if the DN used
when adding the user is no longer available on the LDAP server. Note that the
removal is done only if the LDAP server is fully reachable and the DN is
missing. This removal process is run at 00:15 or at another time specified by a
logical name.

When a user is added a command procedure can be executed to create the login
directory for the user and/or any other required operations for a new user.

When a user is the target to be removed from SYSUAF.DAT another command file can
be executed to do any additional steps such as initiate a backup of the users
files.

When a user change the password during login or with SET PASSWORD the password
on the LDAP server can be updated. This allow common user administration for
single and cluster OpenVMS hosts and Unix / Linux hosts.

Prerequisites

You must have installed Compaq/HP SSL version 1.0 or later before you can use
this software as it protect all data transfer between the OpenVMS host and the
LDAP server using SSL.

This software has been tested against an OpenLDAP server running on Linux.

 

+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LIBBZ2]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
LIBBZ2, Programming, Compression and Decompression Library

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.



+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LIBEXT]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
LIBEXT, LANGUAGES, Library reference copy extraction utility 

The LIBEXT utility extracts all modules from a user named library and 
writes those modules to separate files based on the module name and on
a destination directory and default extension provided by the user.

+++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LIBIMAGING]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++
 
LIBIMAGING, utilities, LIBIMAGING for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LIBPNG]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
LIBPNG, utilities, LIBPNG for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file 
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LIBTIFF]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
LibTIFF, DECwindows, TIFF Library and Utilities

Home Page: http://www.remotesensing.org/libtiff/
Home Page Mirror: http://libtiff.maptools.org/
Latest Stable Release: v3.7.0
Latest Development Release: v3.7.0
Master Download Site: ftp.remotesensing.org , directory pub/libtiff
Mirror Download Site: http://libtiff.maptools.org/dl/
Windows Binaries: GnuWin32 Project
Mailing List: tiff@remotesensing.org, Subscription, Archive. 
Please, read the FAQ before asking questions.
Anonymous CVS:

        export CVSROOT=:pserver:cvsanon@cvs.maptools.org:/cvs/maptools/cvsroot
        cvs login # use empty password" 
        cvs checkout libtiff

This software provides support for the Tag Image File Format (TIFF), a widely
used format for storing image data. The latest version of the TIFF specification
is available on-line in several different formats.

Included in this software distribution is a library, libtiff, for reading and
writing TIFF, a small collection of tools for doing simple manipulations of TIFF
images on UNIX systems, and documentation on the library and tools. A small
assortment of TIFF-related software for UNIX that has been contributed by others
is also included.

The library, along with associated tool programs, should handle most of your
needs for reading and writing TIFF images on 32- and 64-bit machines. This
software can also be used on older 16-bit systems though it may require some
effort and you may need to leave out some of the compression support.

The software was orginally authored and maintained by Sam Leffler. While he
keeps a fatherly eye on the mailing list, he is no longer responsible for day to
day maintenance.

Questions should be sent to the TIFF mailing list: tiff@remotesensing.org, with
a subscription interface at http://remotesensing.org/mailman/listinfo/tiff.

The persons responsible for putting up this site and putting together versions
>= 3.5.1 are Frank Warmerdam, Andrey Kiselev and Mike Welles.


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LIBXML]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
Libxml2, Utilities, XML C parser

      Libxml2 V2.6.13

Libxml2 is the XML C parser and toolkit developed for the Gnome project.
It is used by several software packages, including Python.

By default, the installation procedure installs this library package in
the |SYS$COMMON:[LIBXML2]| directory. To install it in another
directory, dev:[dir], use the |/DESTINATION| parameter of the |PRODUCT|
command. In this case, the library package will be installed in the
|dev:[dir.LIBXML2]| directory.


        Installation

   1. Make the directory which holds the ZIP file your default directory
   2. Extract the PCSI kit from the ZIP archive.

$ UNZIP "-V" LIBXML2-V0206-13-1.ZIP

   3. Install the library package to your chosen destination.

$ PRODUCT INSTALL libxml2  /(default)/

  or ...

$ PRODUCT INSTALL libxml2 /DESTINATION=dev:[dir]

   4. Finally, run the DCL procedure |STARTUP.COM| to define the
      necessary logicals.

(You might want to add the relevant line to your |SYSTARTUP_VMS.COM| file.)

$ @SYS$COMMON:[LIBXML2]STARTUP  /(default)/

or ...

$ @dev:[dir.LIBXML2]:STARTUP


+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[LYNX]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
LYNX, UTILITIES, Text Web Browser
This is Lynx version 2.8.6dev.6, snapshot November 7, 2004.

WHAT IS LYNX?

   Lynx is a fully-featured World Wide Web (WWW) client for users running
   cursor-addressable, character-cell display devices such as vt100
   terminals, vt100 emulators running on PCs or Macs, or any other
   character-cell display.  It will display Hypertext Markup Language
   (HTML) documents containing links to files on the local system, as well
   as files on remote systems running http, gopher, ftp, wais, nntp,
   finger, or cso/ph/qi servers, and services accessible via logins to
   telnet, tn3270 or rlogin accounts.  Current versions of Lynx run on
   Unix, VMS, Windows95/NT, 386DOS and OS/2 EMX.

   Lynx can be used to access information on the WWW, or to establish
   information systems intended primarily for local access.  Lynx has been
   used to build several Campus Wide Information Systems (CWIS).  Lynx can
   also be used to build systems isolated within a single LAN.

   Links to the current sources and support materials for Lynx are
   maintained at:
			  "Lynx links"
	     <URL:http://www.subir.com/lynx.html>
   and at the Lynx homepage:
			"Lynx Information"
		  <URL:http://lynx.isc.org/>.
   View these pages for information about Lynx, including new updates.

   Lynx is distributed under the GNU General Public License (GPL) without
   restrictions on usage or redistribution.  The Lynx copyright statement,
   "COPYHEADER", and GNU GPL, "COPYING", are included in the top-level
   directory of the distribution.  Lynx is supported by the Lynx user
   community, an entirely volunteer (and unofficial) organization.

   Certain portions of the Lynx source distribution were originally created
   by CERN and have been modified during the development of Lynx.  See
   WWW/Copyright.txt for copyright info regarding CERN products used in
   Lynx.

YEAR 2000 COMPLIANCE

   We believe Lynx works properly for the Year 2000 issues, since it does
   not store dates in 2-digit form.  Since it must communicate with a wide
   range of web servers, it interprets dates in a variety of formats.  In
   particular, if Lynx receives a date with a 2-digit year, it assumes that
   values less than 70 are in the range 2000-2069.

DOCUMENTATION

   A users guide is included in this distribution along with a man page for
   Unix systems and a help file for VMS systems.  All documentation is
   contained in the top directory and the docs, samples and lynx_help
   subdirectories.

   While running Lynx, type 'h', 'H', or '?' to invoke the help menu
   system.  From the help menu you may access several useful documents
   pertaining to Lynx and the World Wide Web.  The most important of these
   is the Lynx Users Guide.  By default, Lynx will use the Lynx Enhanced
   Pages, which includes http links for help and FAQs concerning Lynx.  It
   is recommended that you install your own help menu system at your site
   in order to lessen the load on http servers.  This also will allow you
   to customize the help menu system for your site and greatly speed up
   access for those using Lynx over a slow connection.

   For Unix and related systems which support the autoconf configure
   script, the help menu system is installed by the "make install-help"
   command.

   For other systems (such as VMS), copy COPYHEADER and COPYING into the
   lynx_help/ subdirectory.  Then copy the lynx_help subdirectory to a
   public place on your system, or into your $HOME directory if you are a
   single user.  Finally, edit the lynx.cfg file so that the HELPFILE line
   is defined as follows:

      HELPFILE:file://localhost/[public_path]/lynx_help/lynx_help_main.html

   where [public_path] is the absolute path to the lynx_help directory.
   Customizing the help menu system is just a matter of editing a set of
   HTML files.

INSTALLING LYNX

   To install Lynx, follow the steps in the INSTALLATION file, which is
   located in the top directory of the source distribution.

PROBLEMS

   If you experience problems configuring, compiling or installing Lynx,
   please read Section VI.  "General installation instructions" in the
   INSTALLATION file.  Instructions are given there for reporting your
   problem to the "lynx-dev" mailing list, which is frequented by
   experienced Lynx users.

LYNX-DEV MAILING LIST

   To subscribe to lynx-dev, send email to majordomo@sig.net with only the
   following message in the body:

      SUBSCRIBE LYNX-DEV address

   where inclusion of your email address is optional if it can be obtained,
   correctly, from the mail headers of your subscription request.

   If you wish to unsubscribe from lynx-dev, send email to
   majordomo@sig.net with only the following message in the body:

      UNSUBSCRIBE LYNX-DEV address

   where inclusion of your email address is optional if it can be obtained,
   correctly, from the mail headers of your request.

   Also, to get a list of useful majordomo commands, send email to
   majordomo@sig.net with the following command:
   ^^^^^^^^^
      HELP

   PLEASE!!! do not send commands to the lynx-dev mailing list itself.

   Any messages you wish to post should be sent to lynx-dev@sig.net. 
   PLEASE use the lynx-dev list, NOT private email to the developers,
   for questions or discussion about Lynx, or contributions of patches. 
   Patches should use the context diff format (diff -c).

   You need not be subscribed to the lynx-dev list in order to post.  If
   you post without subscribing, though, you should read replies to your
   questions or comments in the archive since more often than not nobody
   will send a carbon copy to you.  View the archives at:

		    "lynx-dev Mailing list archives"
		<URL:http://lists.gnu.org/pipermail/lynx-dev/>


++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[MBU]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
MBU, UTILITIES, A Utility for VMS Mailboxes
  MBU is a utility for VMS mailboxes. MBU can create mailboxes,
  delete mailboxes, read and write mailbox messages, and display and 
  change the characteristics of mailboxes. It can also view messages in a 
  mailbox without reading them.

  There is support for command files and scripts of mailbox messages to be
  repeated.

  This program was written by Ian Miller.

  Bug reports and comments to

	miller@encompasserve.org


  WARNING

  The SET, SHOW and VIEW commands execute some kernel mode code to access
  system data structures. This requires CMKRNL privilege. This code appears
  to work on my system (AlphaVMS V7.3-2) but I can't say if it will work on 
  yours. It may crash your system. If you run without CMKRNL privilege then
  MBU will work except for VIEW and SET MAILBOX commands. (SHOW MAILBOX works
  but displays less information).
    
  MBU has been built on the following versions of AlphaVMS and appears to work
  V6.2, V7.1, V7.2-1, V7.3-1, V7.3-2.

  MBU does not build or work on VAX/VMS. I hope to fix this one day - any help
  appriciated.

  CHANGES
  V1.3 	Port to Alpha, display extra information 
  V1.4 	Show if mailbox is permanent or temporary. 
 	Display mailboxes matching specified criteria e.g. not empty.
	Display I/O queues for mailbox.
	Implement SET VERIFY, SHOW VERSION commands.

  TO BUILD MBU

  Either use MMK/MMS and MBU.MMS 

	MMK/DESCRIP=MBU.MMS
  
  (add /MACRO=DEBUG=1 to build a debug version)

  or use the DCL procedure B_MBU.COM

  	@B_MBU.COM

  (add a parameter of DEBUG to build a debug version)

  There is a MBU.HLP for insertion into SYS$LIBRARY:HELPLIB.HLB

  COPYRIGHT NOTICE

  This software is COPYRIGHT  2004, Ian Miller. ALL RIGHTS RESERVED.
  Permission is granted for not-for-profit redistribution, provided all source
  and object code remain unchanged from the original distribution, and that all
  copyright notices remain intact.

  DISCLAIMER

  This software is provided "AS IS". The author makes no representations or
  warranties with respect to the software and specifically disclaim any implied
  warranties of merchantability or fitness for any particular purpose.

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[MINESEEK]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
MINESEEK, Games, Mineseek for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[MKISOFS]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
MKISOFS, utilities, Make ISO-9660 File System for OpenVMS

This is a port of the mkisofs Make ISO-9660 file system 
tool for OpenVMS.

For details of the operation of this package, please see
the provided source code.

++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[MMK]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
MMK, BUILD_TOOLS, MadGoat Make Utility (Compatible with HP MMS)


MadGoat Make Utility (MMK)

MMK is a "make" utility for VMS systems.  It is used for building software
systems based on a "description file" (or "makefile") you create that lists
the sources and objects of a system and the dependencies between them.

MMK is similar in functionality to Digital's DEC/Module Management System (MMS),
and understands a syntax in its description files which is mostly compatible
with MMS.

MMK runs on VAX/VMS, OpenVMS VAX, OpenVMS AXP, and OpenVMS IA64 systems.  It
requires VAX/VMS V5.2 or later, or OpenVMS AXP V1.5 or later.

MMK is written entirely in C (with a little Macro).  Complete source code is
provided.


Files included in MMK.ZIP:
--------------------------

AAAREADME.DOC             This file.
AAAREADME.INSTALL         Installation instructions.
AAAREADME.TOO             Revision information.
CROSS_ALPHA.MMS           Description file for use in building VAX+AXP systems.
LINK.COM                  Command procedure for creating the MMK executable.
MMK_DEFAULT_RULES.MMS     File listing MMK built-in default rules (VAX).
MMK_DEFAULT_RULES_AXP.MMS File listing MMK built-in default rules (AXP).
MMK_DEFAULT_RULES_I64.MMS File listing MMK built-in default rules (IA64).
MMK_DOC.PS                Documentation, in PostScript form.
MMK_DOC.TXT               Documentation, in plain text.
MMK_HELP.HLP              Help file for MMK.
MMK.ALPHA_OLB             Object library for building MMK (AXP).
MMK.ALPHA_OPT             Linker options file for building MMK (AXP).
MMK.OLB                   Object library for building MMK (VAX).
MMK.OPT                   Linker options file for building MMK (VAX).

The following files are under the [.SOURCE] subdirectory:

AAAREADME.DOC             This file.
BUILD_TARGET.C            Routines for building targets.
CLIDEFS.H                 CLI$ interface definitions.
CMS_INTERFACE.C           DEC/CMS interface routines.
DEFAULT_RULES.C           Setup routines for compiled-in default rules.
DESCRIP.MMS               Description file for building MMK.
FILEIO.C                  File I/O routines.
GENSTRUC.C                Routines for generating structures for built-in rules.
GET_RDT.C                 Routines for getting revision date stamps.
GLOBALS.H                 Include file for MMK globals.
MAKE_ZIP.C                Program for packaging MMK using ZIP.
MAKE_ZIP.CLD              Command language definition for MAKE_ZIP.
MAKE_ZIP.OPT              Linker options file for MAKE_ZIP.
MEM.C                     Memory management routines.
MHDDEF.H                  Library module structure definitions.
MISC.C                    Miscellaneous support routines.
MMK.ALPHA_OPT             Linker options file for building MMK (AXP).
MMK.C                     MMK main routine.
MMK.H                     Include file for MMK definitions.
MMK.OPT                   Linker options file for building MMK (VAX).
MMK_CLD.CLD               MMK command language definition.
MMK_COMPILE_RULES.ALPHA_OPT  Linker options file for rules compiler. (AXP)
MMK_COMPILE_RULES.C       Rules compiler main program.
MMK_COMPILE_RULES.I64_OPT Linker options file for rules compiler. (IA64)
MMK_COMPILE_RULES.OPT     Linker options file for rules compiler (VAX).
MMK_COMPILE_RULES_CLD.CLD Command language definition for rules compiler.
MMK_DEFAULT_RULES.MMS     Default rules for compiling into MMK (VAX).
MMK_DEFAULT_RULES_AXP.MMS Default rules for copmiling into MMK (AXP).
MMK_DEFAULT_RULES_I64.MMS Default rules for copmiling into MMK (IA64).
MMK_DOC.SDML              VAX DOCUMENT source for MMK documentation.
MMK_HELP.RNH              RUNOFF source for MMK help file.
MMK_MSG.H                 Include file containing MMK message code definitions.
MMK_MSG.MSG               MMK message definitions.
OBJECTS.C                 Routines for managing the object tree.
PARSE_DESCRIP.C           Routines for parsing description files.
PARSE_OBJECTS.C           Routines for parsing object references.
PARSE_TABLES.MAR          LIB$TPARSE table for parsing description files.
READDESC.C                Routines for reading in description files.
SP_MGR.C                  Subprocess management routines.
SYMBOLS.C                 Routines for managing the symbol tables.
TPADEF.H                  Include file containing LIB$TPARSE definitions.


--------------------------------------------------------------------------------
CONTACTING THE AUTHOR

Comments, suggestions, and questions about this software can be directed to
the author at one of the following addresses:

Mail:   Matthew Madison
    	MadGoat Software
    	PO Box 556
    	Santa Cruz, CA 95061-0556
        USA

E-Mail: madison@MadGoat.Com


COPYRIGHT NOTICE

This software is COPYRIGHT  1992-2004 by MADGOAT SOFTWARE.
ALL RIGHTS RESERVED.  Permission is granted for not-for-profit
redistribution, provided all source and object code remain unchanged
from the original distribution, and that all copyright notices
remain intact.

DISCLAIMER

This software is provided "AS IS".  The author and MadGoat Software
make no representations or warranties with repsect to the software and
specifically disclaim any implied warranties of merchantability or fitness for
any particular purpose.

+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[MOSAIC]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
MOSAIC, WEB_TOOLS, The Mosaic Web Browser

VMS Mosaic V3.8-1, 21-NOV-2004

VMS Mosaic is a GUI web browser.  It supports HTML V4.0 (including
tables and frames), animated GIFs, cookies, secure connections, etc.
It does not support Java, JavaScript or style sheets.  A C compiler
is required to build it.

VMS Mosaic has been generated and tested on VAXes running OpenVMS
5.4 thru 7.3, on Alpha systems using OpenVMS V1.5 thru 7.3-2, and
on IA64 systems running OpenVMS V8.1 thru E8.2.  The systems have
used UCX, CMU, MultiNet, Pathway, TCPware or SOCKETSHR with NETLIB.
CMU TCP/IP is supported via LIBCMUII or SOCKETSHR.  The program has
been compiled with VAX C, DEC C and GNU C (VAX version 2.7.1 only).
Versions 1.1 thru 1.5 of DECwindows Motif are supported.  Both HP
SSL and OpenSSL are supported for secure connections.

The files MOSAIC3_8.ZIP and MOSAIC3_8-1.ZIP contain the sources,
documentation and build procedure.  Note that the files are ZIP
archives, so the UNZIP program is needed to unpack them.  MOSAIC3_8.ZIP
should be unzipped first, and then MOSAIC3_8-1.ZIP should be unzipped
in the same directory.  The file README.VMS-3_8 contains the
installation instructions.

See http://vaxa.wvnet.edu/vmswww/vms_mosaic.html for updates and
bug fixes beyond this release.

Changes from the previous release (V3.7) in V3.8:

 o Added support for Motif 1.5
 o Added Stop button to toolbar to stop loading or animations.
 o Added open in new window option to Open Document dialog
 o Added support for ID in all tags
 o Added support for image alpha channel transparency
 o Added support for compressed (4 and 8 bit) BMP images
 o Added support for OS/2, 16 bit, and 32 bit BMP images
 o Added support for MIME types "image/x-bmp" and "image/x-ms-bmp"
 o Added cookie permissions file (MOSAIC.HOSTPERM) and preference
 o Added Cookie Jar Manager option to update the cookie files
 o Added cookie and cookie domain counters to Cookie Jar Manager
 o Added Map and Auction search selections to Navigate menu
 o Added support for crimson and indigo as named colors
 o Added support for &apos, &circ, &minus and &ndash
 o Added partial support for &dagger, &lowast, &ldquo, &lsaquo,
   &lsquo, &rdquo, &rsaquo and &rsquo
 o Added preference setting for text blink time
 o Added preference setting for form button background color
 o Changed the default background color from gray to white
 o Changed cookie domain list to a balanced binary tree
 o Changed to display and store cookie domains in alphabetical order
 o Changed to strip carriage returns, linefeeds and tabs out of URLs
 o Changed to escape blanks in image URLs
 o Changed default web search engine to Google
 o Fixed problem with busy cursor not resetting after window resize
 o Improved the about: URL feature
 o Improved news memory allocation
 o Updated the comment card
 o Eliminated several Informational compiler error messages in LIBJPEG
 o Corrected problems in MAKE_MOSAIC.COM detected by DCL_CHECK
 o Speeded up table width calculation

Changes in V3.8-1:

 o Added architecture type to /VERSION information
 o MAKE_MOSAIC.COM sets DCL parse style to TRADITIONAL
 o Fixed crashes caused by empty cookie file
 o Various bug fixes


George Cook, West Virginia Network (WVNET)
Email address: cook@wvnet.edu

++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[MYSQL]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
MySQL, utilities, MySQL database for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[NEDIT_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
Nedit, Utilities, GUI based multi-platform editor

Introduction


The distribution from this server is enriched compared to the original
one at the Nedit WWW Server. Added parts either to be found separatly
on this server or created/modified by me are: 

 * Third pass on a pattern for DCL (this is still in an Alpha stage, no
   pun intended). 
 * Converted Unix man-pages to OpenVMS help files. 
 * Descrip.mms and example DCL for integration with VUE.  
 * Additonal icons 

Installation

The normal source distribution contains a number of DCL procedures,
which can be used to build Nedit on OpenVMS. Assuming one is located in
the top-level directory of Nedit the build requires in this case to
execute the following commands: 

$ set def [.util]
$ @comutil
$ set def [-.source]
$ @comnedit

In case MMS/MMK is installed it is sufficient to just execute this in
the top-level directory. 


Customization


The actual operations of Nedit/nc can be influenced by a number of
files located in the home directory of the user. These are: 

.neditdb 
This file contains a list of the 30 files edited most recently with
nedit. These will be presented for selection in the menu item File ->
Open Previous 

.nedit 
This file contains (almost) all of the setting customizing the
behaviour of Nedit. It has the format of an Xresource file. 

X resources


There is one additonal Xresource which you might want to set, but is
not in the .nedit file. 

nc.autoStart: <false|true> 
If the default setting false is in effect, nc will request a
confirmation before starting a new Nedit server in case there is not
yet one executing. Since at least I tend to answer Yes to this question
in 99.9999% of all cases, setting it to true saves me some work. 

Installing DCL pattern


To install the experimental DCL syntax highlighting pattern for Nedit
execute the following command: 

nedit -import dcl.pats


If you got the Zip achive from this server dcl.pats is located in the
main directory of Nedit. Once the Nedit window pops up use
"Preferences-->Save Defaults..." to commit the pattern to your personal
.nedit file. After this the DCL pattern will be available everytime you
start Nedit without further need for import statements. 


As noted earlier this pattern is an early release, i.e. it contains
only a limited number of rules. These are: 

Comments 
  Comments in DCL do start with an exclamation mark. They will be
  displayed in light gray italic. 
Keywords 
  A start of a list of kewords (verbs) in DCL has been added to the
  pattern. Currently this is still pretty short but most probably will
  grow considerably with the next release of the pattern. Keywords are
  displayed in black bold. 
Labels 
  Labels used as targets for GOTO statements will be displayed in red italic. 
Strings 
  Strings in DCL are enclosed in double quotation marks. They will be
  displayed in darkGreen. 
Qualifiers 
  Qualifiers to DCL commands (and programs using a DCL conformant command
  line interface) are displayed in brown. 

To illustrate this, there is a screenshot of Nedit while working on a
(silly) DCL procedure in this directory named nedit.png.  


All this assumes that you have not changed the standard highlight
styles of Nedit, but if you have, you most probably do not need this
explanation anyhow ;-) 

The latest version of the OpenVMS port of Nedit should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/nedit.htmlx

++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[NOTES]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
NOTES, Utilities, Notes Conferencing Software

Also please see the [NOTES_FT] kit on the OpenVMS Freeware V7.0.

This kit contains the OpenVMS VAX and OpenVMS Alpha kits for the
Notes conferencing system, and a client for Microsoft Windows.

Notes is now officially a retired and an unsupported product.

Present here are the main release and an ECO kit containing a complete
distribution with updates.  Depending on the application, one or the
other might be preferable.

Due to changes made in OpenVMS V7.3 and later, the NOTES/DECWINDOWS
command does not operate correctly when using these kits -- you can 
use the command NOTES/NODECWINDOWS to start and run Notes in this
configuration, or load the appropriate provided replacement images.

Included is an updated version of the [.ALPHA]DDIF$VIEWSHR.EXE image 
for Notes operations with DECwindows on certain configurations with 
OpenVMS Alpha V7.3 and later.

For OpenVMS VAX V7.3 and later, the images [.VAX]DDIF$VIEWSHR.EXE and 
[.VAX]NOTES$DWSHARE.EXE are provided. 

The [.WINDOWS]NOTES-V15CI.ZIP is a Microsoft Windows NT Intel IA-32 kit, 
and [.WINDOWS]NOTES-V15CA.ZIP is a Microsoft Windows NT Alpha kit.  Please 
see the instructions within these Zip kits for details on installation and 
operation of Notes on Microsoft Windows.

The associated Software Product Description (SPD) files (for the 
now-retired OpenVMS VAX and OpenVMS Alpha products) are provided, and
a license PAK needed for operations on OpenVMS VAX and OpenVMS Alpha.

Documentation for the Notes shareable image callable API is also provided.


+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[NOTES_FT]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
NOTES_FT, Utilities, Notes Conferencing Software

Also please see the [NOTES] kit on the OpenVMS Freeware V7.0.

A port of Notes to IA64 and an updated Alpha version. This is a field test
version and will be updated in 2005. 

Do note, that while the installation procedure asks for a valid license (LMF)
the requirement for a license key has been removed from the Notes executable
images (client and server).

Send any comments, bug reports or enhancement requests to ankan@hp.com.


++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[OMI]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
OMI, PROGRAMMING, A feature rich and well documented menu development tool

OMI v2.3 - 1997-2004, Oscar van Eijk, support@oveas.com
========================================================

Oscar's Menu Interface is a DCL procedure that reads menu files and
represents the menu structure on a ChUI based window.

OMI does not perform any actions on its own. Additional procedures
are required to handle upon the users input. OMI is strictly created
to create a standard user interface for all kinds of actions, with a
clear structure, support for different security levels and password
protection.

The additional procedures that are required for any actions are
referred to 'callable jobs'. A section in the help file describes
how several commands, defined in OMI, can be used to create such
procedures.

Documentation and support
-------------------------
Full documentation for OMI can be found (PostScript or PDF) or viewed
online (HTML) at the OMI site:
http://freeware.oveas.com/omi.
An online HELP is also provided, but since v2.0 the printable documentation
is completely reviewed. This has not (yet?) been done with the online
HELP, except for the interactive OMI command section.

This site also offers a forum (http://freeware.oveas.com/omi/forum.html)
where you can get support.
Please note OMI comes without any warranty, but I'll try to give as much
support as possible via this forum.

New in this version
-------------------
* Added keywords DCLERRORS and DCLFATALS to the /IGNORE qualifier 
* The keyword BLANKS in STRING formatting type is now deprecated,
  it's replaced by COLLAPSE 
* Added the keyword ALFANUM in the STRING formatting type 
* Made the answers 'Yes' and 'No' configurable using the values
  ANSWER_YES and ANSWER_NO in the [QUESTIONS] section of the
  configuration file.
  NOTES: 
  - The default answer when using OMI$CONFIRM should be changed in
    your applications from "Y" to 'QUESTIONS$ANSWER_YES' and from
    "N" to 'QUESTIONS$ANSWER_NO' is you want to change the values
    in the configuration file as well.
  - The message %OMI-W-IVANS now requires 2 parameters. If you use
    this message in your software, you will need to change it to:
    OMI$SIGNAL OMI IVANS,QUESTIONS$ANSWER_YES,QUESTIONS$ANSWER_NO
    
    Refer to the documentation for more information. 
* Bugfix the last page when scrolling select lists 
* Bugfix in the INFO command 
* Added the commands CLS and OMI$CLEAR_SCREEN 
* Added the option NOWAIT to the OMI$POPUP command 
* Bugfix in reading TAG- and SELect lists from a file; files where
  not found when they located in the OMI$MENU_DIRECTORY searchpath,
  but not in the first index.
  This is because the VMS lexical F$PARSE() expands to the first
  index only. 
* Allow submenus on-the-fly menus.
* Added the error messages OUTOFRA and PROOUTRA that signals when
  an intermediate value in the calculater is or might be out of
  range. This prevents random result when a temporary value exceeds
  the DCL limit (2,147,483,647)

Installation instructions
-------------------------
To install OMI, download one of the distributions: either
the ZIP file (download in BINary format) or the COM file
(download in ASCII format).
Also, download OMI$INSTALL.COM in ASCII format.

Next, set default to the directory where the installation
script is located, and issue the command:
$ @OMI$INSTALL

Follow the instruction to install OMI.
The procedure extracts the distribution and moves all
files to the desired location (that you will be prompted for).
Site specific files will not be overwritten.
If the file OMI$TOOLBOX.INI exists, it will be patched.

The installation procedure also creates the HELP library,
and repairs message datafiles, which have been corrupted
by the distribution.

If this is a new installtion, let all the users who will be
using OMI execute the procedure OMI$USER_INSTALL once.
This is not required for upgrades of existing OMI installations.

Installation is now complete. All users can optionally change
the behaviour of OMI by modifying the file OMI$MENU.CFG, located
in their SYS$LOGIN:.

To test OMI, you can use the example menu file OMI$EXAMPLE.MNU
which comes with this distribution. Start this menu with the command
OMI OMI$EXAMPLE.

This menu performs no other action than displaying information.
The 'Protected menu' is protected with the password "test123456789".
(Note: passwords are case sensitive!)

More information can be obtained from the online HELP and the documentation.

++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[OPENSSL_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++
 
OpenSSL, Utilities, Library implementing the Secure Socket Layer SSL

Installation

  Just execute @makevms to build the library. This procedure accepts the
  following parameters: 

  1. Build options 
     ALL 
     Just build "everything". 
     
     CONFIG 
     Just build the "[.CRYPTO]OPENSSLCONF.H" file. 
     
     BUILDINF 
     Just build the "[.CRYPTO]BUILDINF.H" file. 
     
     SOFTLINKS 
     Just fix the Unix soft links. 
     
     BUILDALL 
     Same as ALL, except CONFIG, BUILDINF and SOFTILNKS aren't done 
     
     RSAREF 
     Just build the "[.xxx.EXE.RSAREF]LIBRSAGLUE.OLB" library. 
     
     CRYPTO/x 
     Just build the x part of the "[.xxx.EXE.CRYPTO]LIBCRYPTO.OLB" library. 
     
     CRYPTO 
     Just build the "[.xxx.EXE.CRYPTO]LIBCRYPTO.OLB" library. 
     
     SSL 
     Just build the "[.xxx.EXE.SSL]LIBSSL.OLB" library. 
     
     SSL_TASK 
     Just build the "[.xxx.EXE.SSL]SSL_TASK.EXE" program. 
     
     TEST 
     Just build the "[.xxx.EXE.TEST]" test programs for OpenSSL. 
     
     APPS 
     Just build the "[.xxx.EXE.APPS]" application programs for OpenSSL. 

  2. RSAREF option
     Specify RSAREF as P2 to compile using the RSAREF Library. If you
     specify NORSAREF, it will compile without using RSAREF. (If in the
     United States, You Must Compile Using RSAREF). 
     Note: The RSAREF libraries are NOT INCLUDED and you have to
     download it from ftp.rsa.com. You have to get the ".tar-Z" file as
     the ".zip" file dosen't have the directory structure stored. You
     have to extract the file into the [.RSAREF] directory as that is
     where the scripts will look for the files. 

  3. Debug option
     Speficy DEBUG or NODEBUG as P3 to compile with or without
     debugging information. 

  4. Compiler option

     Specify which compiler at P4 to try to compile under. 

     VAXC   For VAX C 
     DECC   For DEC C 
     GNUC   For GNU C 
     LINK   To only link the programs from existing object files.
            (not yet implemented)

     If you don't speficy a compiler, it will try to determine which
     "C" compiler to use. 

  5. TCP/IP option

     P5, if defined, sets a TCP/IP library to use, through one of the
     following keywords: 

     UCX         for UCX or UCX emulation
     SOCKETSHR   for SOCKETSHR+NETLIB

  6. Thread option
 
     P6, if defined, sets a compiler thread NOT needed on OpenVMS 7.1 (and up) 

  Apart from the commandline options the following logical names can be
  used to customize the build process: 

  OPENSSL_NO_ASM 
    If this logical is defined with any value the assembler parts of
    OpenSSL will be replaced by plain C implementations 

  OPENSSL_NO_'alg' 
    If this logical is defined with any value the corresponding crypto
    algorithm will not be implemented.
    Algorithms you can exclude this way are: RSA, DSA, DH, MD2, MD5,
    RIPEMD, SHA, SHA0, SHA1, DES, MDC2, RC2, RC4, RC5, IDEA, BF, CAST,
    HMAC, and SSL2. 
    Example: Defining OPENSSL_NO_DES will create a LIBCRYPTO.OLB
    without an DES implementation. 

Building shareable images (Alpha only)

  After the build of the object libraries has finished, you can
  additionally create shareable images by invoking [.vms]mkshared.com in
  the root directory of the source distribution. This will create
  [.AXP.EXE.CRYPTO]LIBCRYPTO.EXE and [.AXP.EXE.SSL]LIBSSL.EXE 


Tests

  To check if the newly created programs work fine execute @[.test]tests,  
  which will execute loads of tests actually (expect them to take some
  time). 


Package contents

  The main result of the compilation are the object libraries/shareable
  images libcrypto.[olb||exe] and libssl.[olb||exe], which other
  applications need to link against. Additionally a command-line driven
  interface to the cryptography and certificate functions is build, which
  can be invoked as openssl. 

Setup

  To setup the necessary logicals for the operation of OpenSSL and to
  define some handy symbols one can use [.vms]openssl_startup.com and
  [.vms]openssl_utils.com. 

The latest version of the OpenVMS port of the OpenSSL library should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/openssl.htmlx

+++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[OSCOMMERCE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++
 
osCommerce, Utilities, PHP Web eCommerce Storefront

This is a prototype OpenVMS port of the osCommerce eCommerce web storefront.

This package expects the VAMP environment (VMS, Apache, MySQL and PHP), and
should be installed and operated on an ODS-5 disk.

The directories and files here are often located under the [PHP.SCRIPTS.O...]
directory, or as otherwise configured under Apache and PHP.

If you are accessing files here using ODS-2 semantics, you will have to use
rooted logical names as the directory structure required for this package is
otherwise too deep for ODS-2 limits.

For information and documentation on osCommerce and the associated environment,
please visit the http://www.osCommerce.Org/ website.


+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[PERL]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
Perl, Languages, Perl Language for OpenVMS

This is Perl for OpenVMS, Gathered from various sources.

Also see the "Easy Build" PERLBUILD584.ZIP.

Also see http://www.grootersnet.nl/perl

Derived from http://www.sidhe.org/vmsperl/requirements.html

Requirements for building Perl on OpenVMS:

For OpenVMS VAX:

    * OpenVMS VAX V5.5-2 or later
    * DEC C.  DEC C version 5.3 or better is preferred
    * A Make tool.  HP DECset MMS, MMK from MadGoat software,
      or GNU Make can be used.
    * Either: VMSTAR and GnuZip to uncompress the standard Perl
      distribution, or UnZip to uncompress the development versions
      on genetics.upenn.edu.
    * For socket support, a network stack.  TCP/IP Services (UCX)
      and Multinet are both known to work.
    * If you're compiling with VAX C, Gnu C, or a version of DEC C
      less than 5.2, you will also need the latest version of the
      SOCKETSHR library.
    * If you're using SOCKETSHR and not using UCX, you'll also need
      MadGoat's NETLIB 

For OpenVMS Alpha:

    * OpenVMS Alpha V6.1 or Better
    * DEC C.  DEC C version 5.3 or better is preferred
    * A Make tool.  HP DECset MMS, MMK from MadGoat software,
      or GNU Make can be used.
    * Either: VMSTAR and GnuZip to uncompress the standard Perl 
      distribution, or UnZip to uncompress the development versions
      on genetics.upenn.edu.
    * For socket support, a network stack.  UCX and Multinet are
      both known to work.
    * If you're compiling with a version of DEC C less than 5.2, 
      or don't want to use the DEC C RTL socket interface, you
      will also need the latest version (0.9D-4) of the SOCKETSHR
      library.
    * If you're using SOCKETSHR and not using UCX, you'll also need
      MadGoat's NETLIB 

For OpenVMS in general

    * At least 30,000 blocks of disk space for the final install
    * At least 70,000 blocks of disk space for the build
    * A PRCLM process quota of 3 for the build, 5 for the test
    * A PRCLM process quota of at least 1 to run Perl scripts. 



++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[TTI_INTOUCH]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
INTOUCH, LANGUAGES, High-performance 4GL for OpenVMS VAX/AXP systems

INTOUCH 4GL is the high-performance 4GL for OpenVMS VAX and AXP systems. 

INTOUCH 4GL runs on all versions of OpenVMS -- VAX/VMS V4.5 to 6.x,
AXP/VMS V1.5 and 6.x.

INTOUCH 4GL interfaces to RMS, Rdb, DEC DBMS, ORACLE, dBASE, and other
database engines.  However, this {freeware} version only includes the RMS
interface.

INTOUCH 4GL comes complete with a "Guided Query Language" (GQL) and 
a "GQL On-line Tutorial".  However, this {freeware} GQL version only
supports ten (10) columns of reporting information.  The fully-featured
GQL supports reports of unlimited complexity!


                       INTOUCH 4GL Documentation

The complete INTOUCH 4GL documentation (in Postscript form) is located
on this CD-ROM in [TTI_INTOUCH.DOC].  

For the complete hard-copy set of INTOUCH 4GL documentation ($95.00 US), 
contact us at:

  INTOUCH 4GL
  Touch Technologies, Inc.
  9988 Hibert #310
  San Diego, CA  92131

  Voice: 800-525-2527  or  619-566-3603
  FAX# : 619-566-3663
  Internet: intouch@ttisms.com


               Installing INTOUCH 4GL to your Hard Disk

To install INTOUCH 4GL from this CD-ROM: to your hard disk (called
{mydisk:} in this example):

  $ create/dir/prot=w:re {mydisk:[intouch]}
  $ copy freeware$cd:[tti_intouch]*.*; {mydisk:[intouch]}
  $ set default {mydisk:[intouch]}
  $ @intouch_build

Then, add this line to your system-wide LOGIN.COM file:

   {$ @mydisk:[intouch]intouch.com}

The INTOUCH 4GL installation will take less than 10 minutes.


                   INTOUCH 4GL Full-Feature Upgrade

For information on how to upgrade this {freeware} copy of INTOUCH 4GL to
the fully-featured, 7/24 supported version, or for the full set of
hardcopy INTOUCH 4GL documentation, contact us at:

  INTOUCH 4GL
  Touch Technologies, Inc.
  9988 Hibert #310
  San Diego, CA  92131

  Voice: 800-525-2527  or  619-566-3603
  FAX# : 619-566-3663
  Internet: intouch@ttisms.com


...Interested in a FREE "Born to Code" Polo shirt?


Yes?

Please see the file [TTI_INTOUCH]SURVEY.TXT.  (Offer limited to the
first 1,000 respondents!)


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_2:[VMSFAQ]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
VMSFAQ, FREEWARE, The OpenVMS Frequently Asked Questions (FAQ)

This directory contains an edition of the OpenVMS FAQ, and in
various document formats.

The FAQ contains answers to many of the more commonly-asked 
questions associated with OpenVMS and with its various related 
hardware platforms, and pointers to many of the available 
OpenVMS resources, to tutorials and training materials, and 
to many other supporting materials.

The text-format version of the FAQ is very likely the easiest
to serve, to download, and particularly to search.  (If you
want to download and use just one of the various FAQ formats, 
pick the text-format FAQ.)

The OpenVMS FAQ is updated once or twice per year, and sometimes 
more or less often.  Please check for the latest version of the 
OpenVMS FAQ, as available in the comp.os.vms, news.answers and 
comp.answers newsgroups, and is served from, or is linked from,
various websites including the following:

    http://www.hp.com/go/openvms/faq/
    ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/
    news://comp.answers
    news://news.answers
    http://www.faqs.org/
    http://www.google.com/
    http://www.kjsl.com/vmsfaq
    http://eisner.decus.org/vms/faq.htm
    http://www.hoffmanlabs.org/


+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[000TOOLS]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
000TOOLS, FREEWARE, Various Useful Tools

This directory contains a DEFINE_TOOLS.COM procedure used to
establish DCL foreign commands for a collection of useful DCL 
command procedures and executable images, and this particularly
contains the Unzip tools necessary to unpack the Zip archives.

This directory tree is duplicated on all OpenVMS Freeware disks.


+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[FREEWARE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
FREEWARE, FREEWARE, The Master OpenVMS Freeware README File

                        OpenVMS Freeware CD-ROM ReadMe
                        ------------------------------

Welcome to the HP OpenVMS Freeware V7.0 CD-ROM.

All the software included on this CD-ROM is also available for (free)
download at the OpenVMS web site:

   http://www.hp.com/go/openvms/freeware/

This document contains a general introduction to the OpenVMS Freeware as
well as notes specific to the Freeware V7.0 distribution.

                             General Introduction
                             --------------------

The OpenVMS Freeware CD-ROM contains free software tools and utilities to aid
software developers, partners and OpenVMS Hobbyists in creating applications,
and in managing and using OpenVMS systems, as well as packages that can serve
as programming source code examples.

Contained on this CD-ROM are of packages for OpenVMS VAX, OpenVMS Alpha, and
OpenVMS I64, divided into general categories including the following:

         AFFINITY             Interoperation with Microsoft Windows systems
         BUILD_TOOLS          Build tools
         WEB_TOOLS            CGI and HTML tools
         GAMES                Games (also see Motif Toys)
         GRAPHICS             Graphics tools
         LANGUAGES            Compilers, assemblers, and language-related
         MISCELLANEOUS        Or ask for the creation of a new category
         MOTIF_TOYS           X Windows, CDE, and Motif toys (see Games)
         NETWORKING           Networking and network-related tools
         PROGRAMMING          Source Code Examples, APIs, etc
         SYSTEM_MANAGEMENT    Tools related to system management, security
         STORAGE_MANAGEMENT   Tools related to storage management
         UTILITIES            Random Utilities unrelated to other categories
         FREEWARE             Reserved for use by Freeware CD-ROM constructs

Many of these tools are popular packages already widely known and in use, 
while others are internally developed HP OpenVMS tools our engineers are 
making available to you, our OpenVMS customers. For example, the OpenVMS 
Freeware CD-ROM includes Bliss compilers for various OpenVMS platforms.

The Freeware CD-ROM includes the following features:

	o  Includes an easy-to-use 4GL-based menu system for
	   examining the contents of the CD-ROM.

  	o  Is in Files-11 format to make it readable on OpenVMS
           systems.

	o  Contains binaries, source code (except for the Bliss
           compilers and specific other HP-provided packages),
           and documentation.

	o  Represents some of the most popular, most often
           requested free packages, plus new items never before
           made public.

Disclaimer on Testing, Quality, and Licensing

The OpenVMS Freeware CD-ROM set is provided "AS IS" without warranty.  HP
adds no Freeware-specific restrictions on the distribution or redistribution
of the contents of these disks, nor adds any specific restrictions onto the 
redistribution of any packages on it. Be aware, however, that various of the 
individual packages on the CD-ROM may carry restrictions on their use or on
their redistribution, as imposed by the original author(s) or owner(s) of 
the package(s). Therefore, you should carefully read the documentation 
accompanying any products of interest. 

HP is providing this software free of charge and without warranty -- copies
of packages (and various package updates that might become available) can 
usually be downloaded from http://www.hp.com/go/openvms/freeware, and 
(additional) copies of this CD-ROM set can be ordered from HP for a small
media replication, handling, and distribution charge.

Included in the [FREEWARE] directory on this CD are various GNU software 
licenses.

HP makes no claims concerning this software, and provides this CD-ROM 
distribution to the OpenVMS community and to HP customers as a free 
service.


  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

         Remember, all packages contained herein are supplied AS IS.

         All packages are without any warranty, expressed or implied.

      HP has performed no verification, no code reviews, and no testing.

     You are solely responsible for support, debug, test and remediation.

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



                     General Freeware V7.0 release notes
                     -----------------------------------

  o There were the usual problems building the distributions due to errors
    found in various FREEWARE_README.TXT files, and due to submissions that
    were missing the (required) FREEWARE_README.TXT file.  The Keeper of the
    OpenVMS Freeware (KoF) apologizes for these changes.

  o The menu system is (still) (over)due to be replaced -- probably with a
    Lynx-based system of HTML files, or otherwise -- while the current
    menu environment is not expected to operate on OpenVMS I64.

  o Several BACKUP saveset submissions were unpacked only with difficulty, due
    to problems with the ZIP archive files.  Various file attributes were reset
    to match OpenVMS expectations, but there may well be additional files that
    do not have the expected file attributes.  One tool that may be useful for
    this [000TOOLS]RESET_BACKUP_SAVESET_ATTRIBUTES.COM.

  o The menu system is deliberately not requiring all CD-ROMs in the Freeware
    set to be mounted at the same time -- this avoids the requirement to have
    multiple CD-ROM drives.  This also unfortunately makes it somewhat more
    difficult to rummage around on the various disks.

  o Please take the time to examine the following files and directories:

      [000000]AAAREADME.*
      [000000]OPENVMS_FREQUENTLY_ASKED_QUESTIONS_FAQ.TXT
      [000000]00FREEWARE_ABSTRACT.TXT
      [000TOOLS]*.*
      [FREEWARE]*.*
      [VMSFAQ]*.*

    These files are replicated on all Freeware CD-ROM disks.

  o Current copies of the OpenVMS Frequently Asked Questions (FAQ) document
    are available at:

      http://www.hp.com/go/openvms/faq/


  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thank you,

Stephen Hoffman
Keeper of the Freeware
HP OpenVMS Engineering
December, 2004

++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[PWAIT$SDA]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++
 
PWAIT$SDA,UTILITIES, a SDA extension to display info about a waiting process 
PWAIT$SDA is a SDA extension (using the API first documented for VMS V7.2) 
which displays information about a process waiting and what it is waiting for.

It is intended to help investigating why a process appears hung.

TO USE
When analyzing a crash dump or the current running system using SDA enter the 
command PWAIT (at the SDA> prompt) and information will be displayed about the
currently selected process. 

The currently selected process is the process most recently displayed with
SHOW PROCESS or the current process in a crash or the process selected with
SET PROCESS.

If you specify any parameters or qualifiers to PWAIT they are passed to
a SDA SET PROCESS command to change the currently selected process e.g.

To look at process with pid 321
PWAIT /ID=321

To look at the process named SERVER
PWAIT SERVER

The information displayed varies depending on the process state.
EFW
- the number of the event flag(s)
- the local event flags and common event flags (if relevent)
- the active I/O channels and related I/O requests
- the timer requests for this process
JIBWAIT i.e. waiting a pooled quota such as BYTLM
- name of quota and initial and current values
RWAST
- name of quota (if BIOLM/DIOLM appears to be 0)
- pc at which process is waiting
- the active I/O channels and related I/O requests
RWMBX
- name of mailbox that process is waiting for space in
MUXTEX
- address of mutex inc related symbolic name if known

AUTHOR
This program was written by Ian Miller.

Bug reports and comments to

	miller@encompasserve.org


CHANGES
  V0.1	Initial version.
  V0.2  more info
  V0.3  For RWMBX try and workout which mailbox
  V0.4	Look at Kernel Thread Blocks instead of PCB, various tidy up
  V0.5  Display active channels. Allow specification of process.
  V0.6	Display some IRPs
  V0.7	Display Timer Queue and how long process has been waiting
  V0.8	Fix build on VMS V7.2-1

  TO BUILD
  A C compiler is required. I use DEC C V6.5

  @B_PWAIT$SDA.COM

  INSTALLATION
  Either copy PWAIT$SDA.EXE to SYS$SHARE or define a logical name PWAIT$SDA
  as the current location.

  DEFINE PWAIT$SDA DISK:[DIR.SUBDIR]PWAIT$SDA.EXE

  COPYRIGHT NOTICE

  This software is COPYRIGHT  2004, Ian Miller. ALL RIGHTS RESERVED.

  This software is released under the licence defined below.

LICENSE

The Artistic License

Preamble

The intent of this document is to state the conditions under which a Package
may be copied, such that the Copyright Holder maintains some semblance of
artistic control over the development of the package, while giving the users of
the package the right to use and distribute the Package in a more-or-less
customary fashion, plus the right to make reasonable modifications.

Definitions:

    * "Package" refers to the collection of files distributed by the Copyright
Holder, and derivatives of that collection of files created through textual
modification.
    * "Standard Version" refers to such a Package if it has not been modified,
or has been modified in accordance with the wishes of the Copyright Holder.
    * "Copyright Holder" is whoever is named in the copyright or copyrights for
the package.
    * "You" is you, if you're thinking about copying or distributing this
Package.
    * "Reasonable copying fee" is whatever you can justify on the basis of
media cost, duplication charges, time of people involved, and so on. (You will
not be required to justify it to the Copyright Holder, but only to the
computing community at large as a market that must bear the fee.)
    * "Freely Available" means that no fee is charged for the item itself,
though there may be fees involved in handling the item. It also means that
recipients of the item may redistribute it under the same conditions they
received it.

1. You may make and give away verbatim copies of the source form of the
Standard Version of this Package without restriction, provided that you
duplicate all of the original copyright notices and associated disclaimers.

2. You may apply bug fixes, portability fixes and other modifications derived
from the Public Domain or from the Copyright Holder. A Package modified in such
a way shall still be considered the Standard Version.

3. You may otherwise modify your copy of this Package in any way, provided that
you insert a prominent notice in each changed file stating how and when you
changed that file, and provided that you do at least ONE of the following:

    a) place your modifications in the Public Domain or otherwise make them
Freely Available, such as by posting said modifications to Usenet or an
equivalent medium, or placing the modifications on a major archive site such as
ftp.uu.net, or by allowing the Copyright Holder to include your modifications
in the Standard Version of the Package.

    b) use the modified Package only within your corporation or organization.

    c) rename any non-standard executables so the names do not conflict with
standard executables, which must also be provided, and provide a separate
manual page for each non-standard executable that clearly documents how it
differs from the Standard Version.

    d) make other distribution arrangements with the Copyright Holder.

4. You may distribute the programs of this Package in object code or executable
form, provided that you do at least ONE of the following:

    a) distribute a Standard Version of the executables and library files,
together with instructions (in the manual page or equivalent) on where to get
the Standard Version.

    b) accompany the distribution with the machine-readable source of the
Package with your modifications.

    c) accompany any non-standard executables with their corresponding Standard
Version executables, giving the non-standard executables non-standard names,
and clearly documenting the differences in manual pages (or equivalent),
together with instructions on where to get the Standard Version.

    d) make other distribution arrangements with the Copyright Holder.

5. You may charge a reasonable copying fee for any distribution of this
Package. You may charge any fee you choose for support of this Package. You may
not charge a fee for this Package itself. However, you may distribute this
Package in aggregate with other (possibly commercial) programs as part of a
larger (possibly commercial) software distribution provided that you do not
advertise this Package as a product of your own.

6. The scripts and library files supplied as input to or produced as output
from the programs of this Package do not automatically fall under the copyright
of this Package, but belong to whomever generated them, and may be sold
commercially, and may be aggregated with this Package.

7. C or perl subroutines supplied by you and linked into this Package shall not
be considered part of this Package.

8. The name of the Copyright Holder may not be used to endorse or promote
products derived from this software without specific prior written permission.

9. THIS PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" 
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The End.

+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[PYTHON]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
Python, Languages, Python Language for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[QBTOTP]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
QBTOTP, Utilities, QBTOTP for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.



++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[REGEDIT]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
REGEDIT, Utilities, A program to look at or modify the registry database

Regedit is a program to look at or modify the registryserver database.
It is a full screen (SMG) program and looks like the (MS-)Windows regedit.
If you use the DecWindows environment, you can use mouse-clicks, 
otherwise you must use keyboard-keys.
Because the registry-server exists only on alpha and IA64, 
there is no VAX version.

Usage:

Run regedit

Once in the program you can use PF2/HELP for help info
F10 or ^z will return you to DCL. If you have a Decwindows/VXT display, you
can use the mouse, otherwise you must use the keyboard.

Building
The Alpha and IA64 executables are in the kit, but if you want to rebuild 
REGEDIT, go to the regedit directory and use @create_regedit


Contents:

Ths package contains the following files
In the home directory

 REGEDIT_ALPHA.EXE	The executable
 REGEDIT_IA64.EXE	The executable
 CREATE_REGEDIT.COM	The command file to compile/link
 FREEWARE_README.TXT    This file

In the [.SRC] directory
 REGEDIT.FOR		The Fortran source
 REGEDIT.INC		The include file

In the [.ALPHA] directory
 REGEDIT.OBJ		The Alpha object

In the [.IA64] directory
 REGEDIT.OBJ		The IA64 object

There is no VAX equivalent, since the registry server only 
runs on Alpha and IA64.

Instructions:

Unpack the save set.
If you want to rebuild:
 If you have a fortran compiler
  @CREATE_REGEDIT
 Else to link only
  @CREATE_REGEDIT LINK

On oooovms.dyndns.org is a link to the most recent version.

Author : Fekko Stubbe
Email  : regeditdev@oooovms.dyndns.org

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[RUBY]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
Ruby, Languages, Ruby Object Oriented Programming Language for OpenVMS

  Welcome to Ruby for OpenVMS.

  Documents and software kit for Ruby installation on OpenVMS are available
  at http://www.geocities.jp/vmsruby/en/.

  This directory contains Ruby for OpenVMS Alpha X1.8-1X014, based on the
  Ruby 1.8.1 (2003-12-25) distribution.

  Documents included here are the installation gude and a preliminary
  release notes document.  

  Ruby language documentation is available at:

    http://www.ruby-lang.org/en/20020107.html

  with additional information available at:

    http://www.ruby-lang.org/en/

  This is the first release of Ruby for OpenVMS, and as such the kit has not
  been fully tested.

  Currently, the only extension library included is the Socket library. 
  Many of the core ruby libraries (written in Ruby) are included; however,
  these libraries have not been thoroughly tested on OpenVMS. 

  The next release of Ruby for OpenVMS will likely be based on a stable
  version 1.8.2.

  Ruby/MySQL extension library (made by Tomita, Masahiro) has been compiled
  on OpenVMS.  During testing, it accessed MySQL 4.1.3 beta on OpenVMS and
  MySQL 4.0.12 on Windows XP.


++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[SAMBA]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
SAMBA, MS_Tools, SMB File and Print Services

This is the SAMBA server software for OpenVMS, and it provides
SMB-based File and Print services for Microsoft Windows clients.


++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[SDL]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
SDL, LANGUAGES, Data Structure/Interface Definition Language

  Version Info:

  Alpha PL/I SDL for OpenVMS VAX, EV1-39
  Alpha PL/I SDL for OpenVMS Alpha, EV1-69
  Alpha C++ SDL for OpenVMS VAX, Alpha and I64, V2.1-5

  Alpha PL/I SDL VAX EV1-39 has not been changed from the version
  found Freeware V6.0, while the Alpha PL/I SDL Alpha EV1-69 images,
  and the Alpha C++ SDL VAX, Alpha and I64 V2.1-5 kit, are new.
  The PL/I source code to Alpha PL/I SDL EV1-69 is provided.  No
  code for the C++ port is presently provided.

  The SDL Tool:

  This tool is a data definition language and is used to convert a 
  language-independent definition file (an SDL input file) into a 
  language-dependent definition file.  Alone or in conjunction with 
  mechanisms such as the OpenVMS MESSAGE/SDL command (a latent and
  undocumented qualifier which converts the .MSG file into an SDL
  file) and the Freeware GNM tool, the SDL tool can be used to 
  maintain common sources for a wide variety of language files.

  Directory Organization:

  This version of SDL includes PL/I sources and images for use on 
  OpenVMS VAX systems (in [.SDL_PLI_VAX_IMAGES]) and on OpenVMS 
  Alpha (in [.SDL_PLI_ALPHA_IMAGES]) systems.  These images were
  built with/for/on OpenVMS V7.3 and V7.3-2, respectively.

  Also present here is a PCSI installation kit containing the C++
  port of Alpha SDL for OpenVMS VAX, OpenVMS Alpha, and OpenVMS I64
  systems.  To use this kit, use PRODUCT INSTALL to install the PCSI
  kit, and the kit will install and register the kit, including 
  adding the SDL verb definition to the command tables.

  To use the Alpha SDL PL/I tool, the provided SDL.COM procedure 
  will create logical names for the correct set of images for the
  local system architecture, and will also load the SDL.CLD command
  definition into the current process.   (No DCL procedure is 
  needed for use of the C++ port; with the version of SDL in the
  PCSI kit.)

  The two version of Alpha SDL here -- the PL/I version and the C++
  version -- are expected to be source compatible, though additional
  work, enhancements and operations on OpenVMS I64 are probably only 
  reasonably (likely?) expected within the Alpha SDL C++ variant.

  Usage:

  To invoke the Alpha SDL PL/I variant:

  $ @SDL  ! needed once, and then only for the PL/I version

  then

  $ SDL/ALPHA/LANGUAGE=CC filedef.SDL

  or

  $ SDL/VAX/LANGUAGE=CC filedef.SDL

  Also available is SDL/NOPARSE, which converts the intermediate
  files (.SDI files) found in STARLETSD.TLB into language-specific
  definition files.


+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[SOLARDYN]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
SolarDyn, Utilities, Solar System Simulator

                   Solar System Simulator 2.0 Standard 8086
                  

Copyright (c) 2002 by Bla Valek

e-mail: bvalek2@ttk.pte.hu
        bvalek2@gamma.ttk.pte.hu

CPU detection original author: Thomas Gohel

Created on PowerBASIC for DOS 3.50

Made in Hungary, Pcs

03-21-2002   08:00

This program shows a shematic real-time representation of the Solar System.
The planets, the greater moons, and every planets's and moons's orbits are
displayed. Their positions are dynamic. In the menu system you have many ways
to control your computer. The program displays the Date, Time, Timer infos,
the Julian Date, and the Moon's Phase too.

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; version 2 of the License.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

If you have problems with the program, it displays invalid data or graphics,
or you start SolarDyn with ERROR option, and you get a SOLARDYN.ERR report
file, then please send it, and your opinion to the given e-mail addresses.
Thanks.


                                    Files:
                                   

Ŀ
 SOLARDYN.BAS    - PB/DOS 3.5 source code         - Basic source code file 
Ĵ
 SOLARDYN.EXE    - executable program             - executable file        
Ĵ
 SOLARSYS.TXT    - short documentation            - text file              
Ĵ
 README.TXT      - this document                  - text file              
Ĵ
 COPYING         - GNU General Public License     - text file              
Ĵ
 TIMEZONE.CFG    - timezone                       - configuration file     
Ĵ
 WINDOW.DAT      - last window state              - data file              
Ĵ
 SOLARDYN.ERR    - error report (optional)        - error report file      



                             Command line options:
                            

                           VER  : display version
                           MONO : disable menu color
                           ERROR: enable extra error handler
                           DATE : display Date
                           TIME : display Time
                           TIMER: display Timer
                           HELP : display help


                             System requirements:
                            
hardware:

- IBM or compatible PC
- 8086 Processor
- 101344 bytes of free base memory
- 166173 bytes of disk space
- keyboard
- graphic screen

software:

- MS-DOS 2.0


                            Version descriptions:
                           

- SolarDyn (SSS 2.0 Standard 8086):

Date: 03-21-2002 08:00

License: GNU Geleral Public License.

Simple command line options were added.

A menu system was added with several useful options and astronomical infos.
It is self explaining and harmless, so just try it and you will see what it
can.

A CPU detection function was included. Original author: Thomas Gohel.

The simulation is now real-time dynamic.

The screen mode initialization part has a default error detecting and
reporting routine.

The filehandling has also a default silent error detecting.

A configuration file is used: TIMEZONE.CFG

An optional error report file is used: SOLARDYN.ERR


- SolarSys (SSS 1.0 Auto 8086):

Date: 03-07-2002 08:00

License: Public Domain.

This program represents the Solar System at 01-01-2000. The planets, the
greater moons, and every planets's and moons's orbits are displayed. Their
positions are static.

It autodetects the videocard, and writes the WINDOW.DAT file.

+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[SPIDER_Z]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
Spider, Games, Solitaire

Installation

  To rebuild spider from the sources just execute @make.com. This will check for the
  availability of MMS/MMK and use either one of these or perform a pure DCL build. The
  build process depends on a correct installation of the Xaw library, as well as
  definitions(see below) for the associated shareable images and include files. In case you haven't
  upgraded to OpenVMS 7.x yet also the Xvmsutils are needed. The installation procedure
  will check for the libraries if necessary and issue appropriate messages before
  attempting to build spider. During the build no further input is required. 


Setup

  During runtime you should have a logical named SPIDER_DIR defined, which points to the
  directory where you keep the documentation for Spider (doc.* files of the
  distribution). These are needed by the help system of Spider. 


Hints

  The random algorithm to select the cards is seeded with the process id, i.e. if you
  invoke Spider twice from the same session you'll get the same sequence of games. To
  avoid this you might want to spawn a new process to run Spider in. The command I
  usually use for this is spawn/nowait/notify/input=nl:/output=sys$scratch:do.log (and
  since I'm lazy I do have a symbol named DO to avoid typing this long command over and
  over again). 

Installation of Xaw3d/Xmu

Shareable Images


  The result of the built are two shareable images, one for Xaw3d and one for
  Xmu. Although one can give a full path for a shareable image at link time,
  OpenVMS does expect to find the file in sys$share at runtime. OTOH for various
  reasons one might not want/be able to place the files in this location. To
  solve this problem just define a logical with the same name as the shareable
  image and point with this to the location of the image in the filesystem, e.g.
  on my system I have: 

$ sh log xmulibshr
   "XMULIBSHR" = "PUBBIN:XMULIBSHR" (LNM$PROCESS_TABLE)
$ sh log xaw3dlibshr
   "XAW3DLIBSHR" = "PUBBIN:XAW3DLIBSHR" (LNM$PROCESS_TABLE)


Header files

  Source files ported from a Unix system often contain include statements like
  this #include <X11/Xmu/file.h>, which reflects the organization of these files
  on this OS, i.e. the header files for Xmu/Xaw(3d)/... are located in a
  sub-directory of the one containing the X11 header files. To be able to work
  with syntax like this on an OpenVMS system one has to tweak the usual
  definition of the logical X11 a bit ;-). 
  One thing is that one has to make X11 a rooted logical, so that a path like
  x11:[xmu] (which is what the above translates to on OpenVMS) makes sense. The
  second is that once again one might want to separate the header files delivered
  by Digital from the ones coming with this package. To do this create a toplevel
  directory as the home for non-DEC header files and add to this subdirectories
  named xmu and xaw. Copy the header-files from the distribution to these new
  directories. 
  As an example the definition on my system looks like this: 

$ sh log x11
   "X11" = "X11ADD" (LNM$PROCESS_TABLE)
        = "X11ADD:[XPM.LIB]"
        = "DECW$INCLUDE"
        = "PUBBIN"
1  "X11ADD" = "DKA300:[PUBLIC.XTOOLS.LIBS.]" (LNM$PROCESS_TABLE)
1  "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"
1  "PUBBIN" = "PUBLIC$ROOT:[AEXE]" (LNM$PROCESS_TABLE)
   "X11" = "DECW$INCLUDE" (DECW$LOGICAL_NAMES)
1  "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"

  x11add
    Rooted logicals have to be first in the list (in this case x11add), also note
    that a rooted logical may not contain another rooted logical in its
    definition. 
  x11add:[xpm.lib]
    Location of the X Pixmap Library header files. On Unix they are stored
    directly in the X11 directory. 
  decw$include 
    Also get the standard header files ;-) 
  pubbin 
    Actually not the location of header files, but rather the place where I keep my
    libraries. In some circumstances usefull for linking purposes. 


The latest version of the OpenVMS port of Spider should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/spider.htmlx

++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[SWISH_E]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
SWISH_E, Web_Tools, Indexing Tool

SWISH-E is a fast, powerful, flexible, free, and easy to use system for
indexing collections of Web pages or other files. Python include a
SWISH-E query interface.

By default, the installation procedure installs this library package in
the |SYS$COMMON:[SWISH-E]| directory. To install it in another
directory, dev:[dir], use the |/DESTINATION| parameter of the |PRODUCT|
command. In this case, the library package will be installed in the
|dev:[dir.SWISH-E]| directory.


        Installation

   1. Make the directory which holds the ZIP file your default directory
   2. Extract the PCSI kit from the ZIP archive.

$ UNZIP "-V" SWISH_E-V0204-2-1.ZIP

   3. Install the tool package to your chosen destination.

$ PRODUCT INSTALL swishe  /(default)/

  or ...

$ PRODUCT INSTALL swishe /DESTINATION=dev:[dir]

   4. Finally, run the DCL procedure |STARTUP.COM| to define the
      necessary logicals.

(You might want to add the relevant line to your |SYSTARTUP_VMS.COM| file.)

$ @SYS$COMMON:[SWISH-E]STARTUP  /(default)/

or ...

$ @dev:[dir.SWISH-E]:STARTUP


+++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[TO]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++
 
TO, UTILITIES, SET DEFAULT program and (far) more

TO.COM is a SET DEFAULT program that works on Files-11 ODS-2 volumes.
I haven't tried it on an ODS-5 disk so I don't know how well it would
work with ODS-5. 

Features:

o  Correct processing of nested logical names.
o  Smart Logical-Name Recall Stack... 
   - holds last 9 defaults plus the current default (the stack size 
     is adjustable)
   - assigns convenient logical names to stack entries
   - uses numbers to reference stack entries in TO.COM
   - avoids duplicate entries 
o  User option to have current default in the DCL prompt.
o  New default is checked for validity and existence.
o  Filename stripping: If P1 is a logical name pointing to a file, 
   TO.COM looks for the file and sets default to the directory in 
   which that file resides. If no file is found, the device and 
   directory are extracted from P1 and TO.COM sets default to the 
   result.
o  Has logic to handle situations in which the default was changed by 
   another program. 
o  Directory brackets are optional (logical names must still be 
   defined properly).
o  Shortcuts for MFD, top level of current tree, up n levels, up 1 
   level (for use with or without a disk-spec), SYS$LOGIN
o  Two-step default function (saves typing)
o  Superfluous 000000's are removed from new defaults if not specified
   explicitly 
o  23-line quick-help page function
o  Ineractive mode
o  If the first translation of a logical name starts with "@", the @ 
   is removed and processing continues.


See README.TXT or the beginning of MANUAL.TXT for easy installation
and Quick Start instructions. 

++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[TTI_INTOUCH]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
INTOUCH, LANGUAGES, High-performance 4GL for OpenVMS VAX/AXP systems

INTOUCH 4GL is the high-performance 4GL for OpenVMS VAX and AXP systems. 

INTOUCH 4GL runs on all versions of OpenVMS -- VAX/VMS V4.5 to 6.x,
AXP/VMS V1.5 and 6.x.

INTOUCH 4GL interfaces to RMS, Rdb, DEC DBMS, ORACLE, dBASE, and other
database engines.  However, this {freeware} version only includes the RMS
interface.

INTOUCH 4GL comes complete with a "Guided Query Language" (GQL) and 
a "GQL On-line Tutorial".  However, this {freeware} GQL version only
supports ten (10) columns of reporting information.  The fully-featured
GQL supports reports of unlimited complexity!


                       INTOUCH 4GL Documentation

The complete INTOUCH 4GL documentation (in Postscript form) is located
on this CD-ROM in [TTI_INTOUCH.DOC].  

For the complete hard-copy set of INTOUCH 4GL documentation ($95.00 US), 
contact us at:

  INTOUCH 4GL
  Touch Technologies, Inc.
  9988 Hibert #310
  San Diego, CA  92131

  Voice: 800-525-2527  or  619-566-3603
  FAX# : 619-566-3663
  Internet: intouch@ttisms.com


               Installing INTOUCH 4GL to your Hard Disk

To install INTOUCH 4GL from this CD-ROM: to your hard disk (called
{mydisk:} in this example):

  $ create/dir/prot=w:re {mydisk:[intouch]}
  $ copy freeware$cd:[tti_intouch]*.*; {mydisk:[intouch]}
  $ set default {mydisk:[intouch]}
  $ @intouch_build

Then, add this line to your system-wide LOGIN.COM file:

   {$ @mydisk:[intouch]intouch.com}

The INTOUCH 4GL installation will take less than 10 minutes.


                   INTOUCH 4GL Full-Feature Upgrade

For information on how to upgrade this {freeware} copy of INTOUCH 4GL to
the fully-featured, 7/24 supported version, or for the full set of
hardcopy INTOUCH 4GL documentation, contact us at:

  INTOUCH 4GL
  Touch Technologies, Inc.
  9988 Hibert #310
  San Diego, CA  92131

  Voice: 800-525-2527  or  619-566-3603
  FAX# : 619-566-3663
  Internet: intouch@ttisms.com


...Interested in a FREE "Born to Code" Polo shirt?


Yes?

Please see the file [TTI_INTOUCH]SURVEY.TXT.  (Offer limited to the
first 1,000 respondents!)


++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[UNRAR]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
UNRAR, utilities, UNRAR for OpenVMS

No FREEWARE_README.TXT was provided with this submission.

The Collector of OpenVMS Freeware has provided this file
to satisfy the Freeware menu requirements; please see the
provided source code for details on this package.


++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[UNZIP_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++
 
UnZip, Utilities, Info-ZIP pack and unpack Zip archives

Building


The behaviour of the build procedure [.vms]make_unz.com can be
influenced in two ways. One ist to invoke it with parameters from the
DCL level. The other one involves setting the global symbol
local_unzip. 


Commandline parameters


make_unz.com accepts the following parameters in arbitrary order: 

DECC, GNUC, VAXC
 Normal behaviour of make_unz.com is to check the system for the
 availability of C compilers in the following order: DEC C (on Alpha the
 only supported compiler), GNU C, and VAX C. Using one of the parameters
 given above one can enforce the usage of a certain compiler. 
VMSCLI, CLI
 Doesn't do much. At the end of the build make_unz.com defines two
 symbols and gives advice how to define them in the future. If this
 parameter is set it will use the Unzip version with the VMS-like
 commandline interface for this. 
NOVMSCLI, NOCLI
 See above, but use the version with the Unix-like interface (This is
 the default). 



LOCAL_UNZIP

Define a global symbol LOCAL_UNZIP as a coma separated list of the
options given below. make_unz.com analyses the symbol and passes its
contents in a define statement to the C compiler. 

VMSCLI
 See VMSCLI above. 
WILD_STOP_AT_DIR
 Modifies the pattern matching routine so that both '?' (single-char
 wildcard) and '*' (multi-char wildcard) do not match the directory
 separator character '/'. Examples: 
   "*.c" matches "foo.c" but not "mydir/foo.c"
   "*/*.c" matches "bar/foo.c" but not "baz/bar/foo.c"
   "??*/*" matches "ab/foo" and "abc/foo" but not "a/foo" or "a/b/foo" 
 This modified behaviour is equivalent to the pattern matching style
 used by the shells of some of UnZip's supported target OSs (one example
 is Acorn RISC OS). 
VMSWILD
 Use parentheses rather than brackets to delimit sets (ranges), and use
 '%' instead of '?' as the single-character wildcard for internal
 filename matching. (External matching of zipfile names always uses the
 standard VMS wildcard facilities; character sets are disallowed.) 
CHECK_VERSIONS
 Check if the extra RMS-Fields stored for Files originating on OpenVMS
 systems match the RMS-version on the current system. Since RMS is
 pretty stable this is not enabled by default. 
RETURN_CODES
 Provide human readable translations of UnZips return codes 
NOTIMESTAMP
 This option disables the -T option, which basically does exactly what
 Zip's -go options do (i.e., set the timestamp of the zipfile to that of
 the newest file in the archive without rewriting the archive). Unlike
 Zip, however, UnZip supports wildcard specifications for the archive
 name; for example, "unzip -T *.zip" will set the dates of all zipfiles
 in the current directory. (UnZip's option is also much faster.) 
DATE_FORMAT=DF_DMY or DF_MDY or DF_YMD
 This option controls the order in which date components are printed in
 listings: day-month-year or month-day-year or year-month-day. 
DATE_SEPCHAR=' -' or '.' or '/' etc.
 This option controls the character that separates the date components
 shown in (non-ZipInfo-mode) listings. The Win32 port obtains the
 separator automatically from the operating system's locale settings;
 all others default to '-'. 
OS2_EAS
 List the sizes of OS/2 EAs and ACLs for each file as two extra columns
 in "unzip -l" output. This is primarily useful for OS/2 systems, but
 because zipfiles are portable, OS2_EAS can be defined for any system. 
DELETE_IF_FULL
 If a write error is encountered (most likely due to a full disk),
 enabling this option will cause the incomplete file to be deleted
 instead of closed normally. 
SFX_EXDIR
 Enable the "-d <extract_dir>" option for UnZipSFX. This is now enabled
 by default (since UnZip 5.5) to facilitate use with automated
 installation scripts and the like. For disabling this feature, use the
 NO_SFX_EXDIR option. 
CHEAP_SFX_AUTORUN
 Enable a simple "run command after extraction" feature for the (command
 line) UnZipSFX stub. This feature is currently incompatible with the
 "-d <extract_dir>" command line option, therefore CHEAP_SFX_AUTORUN
 implicitely sets the NO_SFX_EXDIR option. 
NO_ZIPINFO
 Compile without ZipInfo mode (-Z) enabled; makes a smaller executable
 because many text strings are left out 
USE_DEFLATE64 (default for UnZip and fUnZip)
 NO_DEFLATE64 (default for UnZipSFX stub)
 The "deflate64" algorithm from PKZIP 4.0 (or newer) is an enhanced
 variant of the deflate algorithm that achieves slightly better
 compression ratios on highly redundant data. Normally, UnZip should be
 compiled with support for this compression algorithm enabled. And for
 the SFX stub, "deflate64" support might be unnessessary as long as the
 Info-ZIP Zip utility does not support it (quite likely, this will never
 get implemented). So, the NO_DEFLATE64 option is provided to allow
 exclusion of the deflate64 support. . 
MULT_VOLUME (experimental for 5.5x, do NOT use in production versions!)
 The symbol MULT_VOLUME is used to flag code portions needed for support
 of multi-volume archives. For now, this flag MUST NOT be used to
 compile a production versions of UnZip. This flag has been introduced
 to allow integration of experimental code for multi-volume support in
 the master source tree. This feature will become a default option in
 the future 6.0 release of UnZip. 
LZW_CLEAN (now default) / USE_UNSHRINK
 The "shrinking" algorithm from PKZIP 1.0 is an LZW variant. Unisys
 patented the Lempel-Ziv-Welch algorithm in 1985 and has publicly
 claimed that decompression is covered by it. (IBM also patented the
 same thing in a filing 3 weeks prior to Unisys's.) Therefore
 unshrinking is disabled by default, but those with LZW licenses can
 enable it by defining USE_UNSHRINK. (Unshrinking was used by PKZIP 1.0
 and 1.1, and Zip 1.0 and 1.1. All newer archives use only the deflation
 method.) 
COPYRIGHT_CLEAN (now default) / USE_SMITH_CODE
 The last chunk of code in UnZip that was blatantly derived from Sam
 Smith's unzip 2.0 (as in, "substantially similar") is in unreduce.c.
 Since reducing was only used by very early PKZIP beta versions (0.9x),
 support for it is now omitted by default (COPYRIGHT_CLEAN). To include
 unreducing capability, define USE_SMITH_CODE. Note that this subjects
 UnZip to any and all restrictions in Smith's copyright; see the UnZip
 COPYING file for details. 
USE_CRYPT
 Enable decryption support for all binaries. The default setting is to
 disable decryption support for the SFX stub to keep its size as small
 as possible. For other binaries of the UnZip distribution, decryption
 support is enabled by default. 
NO_CRYPT
 Disable decryption support for all binaries. 
PASSWD_FROM_STDIN (with full crypt sources only)
 Used to allow the password on encrypted files to be read from stdin
 rather than the default stderr. This was useful for those who wished to
 automate the testing or decoding of encrypted archives (say, in a shell
 script via ``echo "password" | unzip -tq archive''), but as of version
 5.3, UnZip has a -P option for passing a password directly to the
 program. PASSWD_FROM_STDIN will therefore probably be phased out in
 future versions. Note that the same security warnings given in the
 description of the -P option apply here as well. 
DEBUG
 Used for debugging purposes; enables Trace() statements. Generally
 it's best to compile only one or two modules this way. 
DEBUG_TIME
 Used for debugging the timezone code in fileio.c; enables TTrace()
 statements. This code is only used for the freshen/update options (-f
 and -u), and non-Unix compilers often get it wrong. 

The latest version of the OpenVMS port of UnZip should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/unzip.htmlx

+++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[USB_FREEWARE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++++++
 
USB_FREEWARE, System_Mgmt, various unsupported USB device drivers

	Attached are a number of unsupported but potentially usefull USB device
drivers that have been built for various purposes over the last couple of
years.  Some of the code is shipped with small examples used to test that the
device is working.  These programs are also intended as examples of how talk 
to the devices.  

	Now time for some cautions:

	1) The code is as is and the interfaces may change at any time.
	2) Source code for the drivers is not being provided at this time.
	   The files needed to correctly build them is not part of the OpenVMS
	   kit.
	3) I do not have time provide support them you can post questions and 
	   problems comp.os.vms and I will attempt to correct problems as time
	   permits.

	Attached are drivers for the following devices:

		JOYSTICKS	
		USB keyboards with consumer controls/buttons
		USB storage devices does not include floppies or CD burning
		USB serial controllers based on the Prolific PL2303 see
		directory for a list of devices that use this controller.

	Before installing and using any you should have the latest EV7 updates
for V7.3-1 or V7.3-2 on your system.


Forrest Kenney

++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VDE]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++
 
VDE, UTILITIES, OpenVMS Source Code Control System

The VDE tools allow you to maintain and to control multiple CMS
libraries as a single unit.

Full documentation of VDE is available in Postscript, HTML, and
Bookreader formats.

VDE requires the presence of various software tools, including CMS 
and Oracle Rdb.  Complete details are in the installation manual.

PLMENU is a set of procedures layered on VDE and CMS that provide
various functions.  A subset of PLMENU tools are included here.


+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VILE]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
VILE, UTILITIES, VI-LIKE-EMACS text editor
vile is a text editor which is extremely compatible with vi in terms of
"finger feel".  In addition, it has extended capabilities in many areas,
notably multi-file editing and viewing, key rebinding, and real X window
system support.

Version 5.4 appeared on the second OpenVms Freeware CDROM.  Version 6.1,
which appeared on the third Freeware CDROM upgraded the source to ANSI C
(from extended C).

Version 8.2 (on the 4th CDROM) added support for user-definable modes and
makes procedures executable just like the builtin commands.  The
minibuffer (aka the ex command line) is editable with vi-style commands.

Version 9.2 (on the 5th CDROM) focused on syntax highlighting
(not yet ported to VMS).  However, as usual, there are lots of bug fixes.

This is a pre-release version of vile 9.5

The authors of vile are Tom Dickey (current maintainer), Paul Fox, Kevin
Buettner, Rick Sladkey and Clark Morgan.

Send bugs to "dickey@invisible-island.net".

+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VMSFAQ]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
VMSFAQ, FREEWARE, The OpenVMS Frequently Asked Questions (FAQ)

This directory contains an edition of the OpenVMS FAQ, and in
various document formats.

The FAQ contains answers to many of the more commonly-asked 
questions associated with OpenVMS and with its various related 
hardware platforms, and pointers to many of the available 
OpenVMS resources, to tutorials and training materials, and 
to many other supporting materials.

The text-format version of the FAQ is very likely the easiest
to serve, to download, and particularly to search.  (If you
want to download and use just one of the various FAQ formats, 
pick the text-format FAQ.)

The OpenVMS FAQ is updated once or twice per year, and sometimes 
more or less often.  Please check for the latest version of the 
OpenVMS FAQ, as available in the comp.os.vms, news.answers and 
comp.answers newsgroups, and is served from, or is linked from,
various websites including the following:

    http://www.hp.com/go/openvms/faq/
    ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/
    news://comp.answers
    news://news.answers
    http://www.faqs.org/
    http://www.google.com/
    http://www.kjsl.com/vmsfaq
    http://eisner.decus.org/vms/faq.htm
    http://www.hoffmanlabs.org/


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VMSTAR]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
VMSTAR, Utilities, tar tools for OpenVMS

*******
VMSTAR V3.3-2   Includes modifications by:
		Hunter Goatley <goathunter@WKUVX1.WKU.EDU>
		Jamie Hanrahan <jeh@cmkrnl.com>
		Richard Levitte <levitte@e.kth.se>
*******

The build procedure tweaked for OpenVMS I64 cross-builds, and a compiler
warning latent in SRH:[TAR]VMSMUNCH.C has been resolved
  -- Stephen Hoffman, OpenVMS Engineering, December 2004, Freeware V7.0

--

General information
-------------------

VMSTAR  is  a  TAR  reader/writer  for  VMS.  It can read archives ("tarfiles")
created  by  the Un*x command "tar" and also create such archives. Tarfiles can
be disk files or directly on tape.

This version supports both VMS-style and UNIX-style command lines.

VMSTAR is based on the TAR2VMS and VMS2TAR programs written by:

phone (613) 545-2925

BITNET:         PENSTONE@QUCDNEE1       (Preferred)
                PENSTONE@QUCDN  (If the other doesn't work)

The extra work has been done by:

Alain Fauconnet
SIM/INSERM U194         (complete address at the end of this file)
PARIS - FRANCE

Bitnet: FAUCONNE@FRSIM51

TAR2VMS and VMS2TAR have been merged into a  single  program.  I  made  several
improvements, bug fixes and message cleanup. For those  who  know  TAR2VMS  and
VMS2TAR, the main differences are:

- everything is now in a single program that can be used for extracting files
from tar archives, listing the contents of tar archives or creating them.

- VMSTAR now accepts a `f tarfile' option to explicitely specify the tarfile
name (either a VMS file name or a VMS device name).

- if this option is not used, the logical name "$TAPE" is translated.

- checksums are verified at file extraction.

- VMSTAR will extract files from archives as VMS rfm=stream_lf, rat=cr files,
except if new option `b' is specified. In this case, extracted files ared
created as rfm=fixed, mrs=512, rat=none i.e. suitable for compressed files to
be decompressed using LZDCMP or for VMS images.

- VMSTAR has a more Un*x-like syntax, if several file names are specified as
command line parameters they must be separated by spaces (not commas) and there
is not context propagation "a la BACKUP".

- VMSTAR allows VMS-style wildcarded strings for Un*x-style file  names  to  be
specified when extracting from a tar archive, e.g. :

$ tar xvf foo.tar */source/*/sa%%%.c

- VMSTAR will attempt to create relative tar archives i.e. archives where
filenames are recorded as "./foo/bar/baz" whenever possible. This can be
specifically avoided by having a device name in file name argument, e.g. :

$ tar cvf foo.tar DISK$USERS[...]*.c

or specifying an absolute VMS file specification, e.g. :

$ tar cvf foo.tar [SMITH.C...]

- VMSTAR will handle tar archives which when restored would create more than 8
levels of directories (the X11 distribution from MIT for instance !). Excessive
levels of directories will be resolved as follows:

d1/d2/d3/d4/d5/d6/d7/d8/d9/foo -> [D1.D2.D3.D4.D5.D6.D7.D8$D9]FOO

- VMSTAR no longer requires the creation of an intermediate scratch file when
archiving text files as VMS2TAR did.

- VMSTAR does *not* allow to read tarfiles past the EOF mark as TAR2VMS did.

- the `w' option (same as "/CONFIRM" for VMS commands) has been implemented for
create archive and extract functions.

- VMSTAR has a VMS help file (VMSTAR.HLP) that can be added to your HELPLIB.HLB
to provide online help.

- normally, VMSTAR will convert dots in the Un*x directory specifications
to underscores, like this:

emacs-19.22/src/buffer.c -> [EMACS-19_22.SRC]BUFFER.C

If you want to suppress this feature, use the option `d'.

- VMSTAR now comes with a DCL interface as well.  It recognises quite well
if you're using the Un*x interface, or the DCL interface.

- many other differences, the code has been extensively reworked with
simplification as a goal. This probably caused the introduction of some bugs...


Build instructions
------------------

Compile and link VMSTAR.C as follows:

$ @BUILD

or if you have MMS (the free clone MMK should work as well):

$ MMS/IGNORE=WARNING

Installation instructions
-------------------------

When you're done building, define a foreign command symbol in SYLOGIN.COM:

$ VMSTAR :== $ <wherever>VMSTAR

I used VAX/VMS C V3.1 to build VMSTAR. I have no idea whether it can be built
using other versions or other compilers...

You can optionally add VMSTAR in your VMS help library as follows:

$ LIBRARY/HELP/INSERT SYS$COMMON:[SYSHLP]HELPLIB.HLB VMSTAR.HLP

        Usage
        -----

        tar h|x|t|c[v][w][b][d][f tarfile] [file [file...]]
	h - print a description and then exit.
        x - extract from tarfile, create VMS files
        t - type directory of tarfile
        c - create tarfile, archive VMS files
        v - verbose (list names of files being archived/extracted)
        w - wait for confirmation before extracting/archiving
        b - binary mode extract, create (rfm=fixed, rat=none, mrs=512) files
        d - keep trailing dots in file names
        f - specify tarfile name, default is $TAPE
        file - space-separated list of file names, can include VMS-style
               string wildcards on extract, can be any VMS file name
               specification (except DECnet) on create archive.


Tapes for reading/writing of tarfiles should be mounted
/FOREIGN/RECORD=512/BLOCK=10240

Example:

$ MOUNT/FOREIGN/RECORD=512/BLOCK=10240 MUA0: "" $TAPE
$ VMSTAR/EXTRACT/VERBOSE MUA0:

NOTE:  VMSTAR is only guaranteed to work with TU81 and similar tape devices.
VMSTAR has been shown to work on DEC TLZ04 (DAT) and some odd DAT player
from Hewlett Packard.

Restrictions
------------

Because of diffrences in the Un*x and VMS filesystems, some files may  fail  to
be correctly  transferred  to/from  the  tarfile.  This  can  be  caused  by  :

- restrictions in VMS file naming scheme: extra dots in file names will be
mapped to underscores, dummy directory names will be generated if archive
contains more than 8 levels of subdirectories, links are extracted as empty
files containing only a short message "this file is only a link to...", all
file names are mapped to uppercase etc.

- restrictions of the Un*x filesystem: tar will only get the latest version of
a VMS file to enter it into the archive, no trace of the orginal file device
name is kept in the archive.

- VMS strong file typing: VMSTAR can only safely tranfer back and forth 
VMS "text" files (rfm=vfc or stream_lf with rat=cr) or VMS fixed size record,
512 bytes/record, rat=none files (e.g. .EXE image files).
VMSTAR will skip other file types (this includes .OBJ, they *can't* be
archived.  Library files may work, but be cautious with them).

Other restrictions:

RMS file attributes are lost in the archive process, text files are archived as
<record><LF><record><LF>, fixed files are archived as is.

VMSTAR  will always restore files relative to your current RMS default if names
in  tarfile do not begin by `/'. If file names in tarfile begin with a `/' (bad
practice), an attempt will be made to restore files to the absolute path. There
is currently no way to explicitely specify the target VMS directory where files
should be extracted.

No  attempt  has  been  made to handle search list as RMS defaults (e.g. SYSTEM
account). Be very careful about that.

The  current  version  of  VMSTAR  has  *not*  been  fully  tested.  I probably
introduced  many  bugs  not  existing  in  Sid  Penstone's  programs. VMSTAR is
provided "as-is", I cannot guarantee it will do what you want or even what it's
supposed  to  do  but  I'd  like  to hear about it if you have problems. If you
report  a  problem,  don't  bother  with  providing me a fix but *do* try to be
precise on what happened and how it happened.

	BUGS
	----

No known bugs.

+-------------------------------------------------------------------------+
|  Alain ("HAL 1") Fauconnet   Research laboratory in medical informatics |
|  System Manager              (expert systems, NL proc., statistics...)  |
|  SIM/INSERM U194             EARN/Bitnet:       FAUCONNE@FRSIM51        |
|  Faculte de Medecine         VMS PSI Mail: PSI%+208075090517::FAUCONNET |
|  91 Boulevard de l'Hopital   FAX:          (+33) 1-45-86-56-85          |
|  75634 PARIS CEDEX 13 FRANCE PTT net:      (+33) 1-45-85-15-29          |
|  "HAL... open the door, please!" (2001 Space Odyssey)                   |
|  Disclaimer: This is machine-generated random text, no meaning at all.  |
+-------------------------------------------------------------------------+
!++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++!
! Richard Levitte, GNU on VMS hacker   ! tel: int+46-8-83 12 15            !
! Sdra Lnggatan 39, II               ! fax: none for the moment          !
! S-171 49  SOlna                      ! Internet: levitte@e.kth.se        !
! SWEDEN                               !                                   !
!--------------------------------------------------------------------------!

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VTFM]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
VTfm,Utilities,OpenVMS File Manager for VT-series terminals
VTfm is a Norton Commander style file manager for Digital
VT-series terminals or terminal emulators which can emulate
such terminals (PowerTerm, for example). VTfm works under
OpenVMS on VAX, Alpha and IA64 processors.

Author: Vladimir K. Vershinin, Moscow, Russia
E-mail: vershinin-vk@tochka.ru

+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VTSTAR]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
VTStar, Utilities, VTStar Terminal Emulator

VTStar versions 1.3 and 1.4

System Requirements - a Microsoft Windows IA-32 system running 
Windows 95, 98, ME, NT, 2000 or XP.


Installing VTStar
-----------------

1) Create a directory to hold the VTStar files.

2) Copy the kit files to the directory created in step (1).

3) Install the fonts.  From the Start menu, launch Settings/
   Control Panel/Fonts.  From the File menu select "Install New
   Font...".  Point the file browsing dialog at the directory
   created in step (1).  Make sure the "Copy fonts to Fonts folder"
   box is checked.  Choose "Select All" and then 'OK'.

4) To run VTStar, launch program vt320e.exe (for VTStar version
   1.3) or vt320e_v14.exe (for VTStar version 1.4).


About VTStar Version 1.4
------------------------

Version 1.3 was the last official release of VTStar.  It has
the property that its window icons minimize to the desktop
surface rather than to the task bar.  Some find this
behavior annoying.  Version 1.4 fixes this problem -- it
places its icons in the canonical place on the task bar --
but in the process a bug has been introduced.  If VTStar
1.4's session list window is minimized, then keyboard
cut and paste to the Windows clipboard (Ctrl+Alt+C,
Ctrl+Alt+V) don't work reliably.  They seem to work just
fine if the session list window is normalized, however.

Because VTStar 1.4 has this bug, this kit supplies both
versions (1.3 and 1.4).  You may choose which bug (strange
icon placement vs. the cut/paste problem) you wish to
tolerate.


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[VTTEST]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
VTTEST, UTILITIES, VT100/VT220 Terminal/emulator test program
VTTEST tests the compatibility (or demonstrates the non-compatibility)
of so-called "VT100-compatible" terminals.  This is a new version using
a configure script, in ANSI C, with tests for ISO 6429 color, VT220,
VT420, and xterm extensions.  VTTEST has been tested on several UNIX
platforms as well as VAX/VMS.

++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[XAW_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
Xaw3d/Xmu, Programming, Xaw3d/Xmu libraries

Note: All the hard work in porting these libraries has been done by Johannes 
      Plass serveral years back in conjunction with the development of GV.
      I only maintain and support the libraries in the sense that I do make
      sure the sources compile cleanly with the latest and greatest versions
      of OpenVMS/CC/Motif.
--------------------------------------------------------------------------------
Building

The Xaw3d/Xmu libraries were ported by Johannes Plass as part of his 
Ghostview project on OpenVMS. This is also reflected in the filestructure on 
the original server. Since both libraries are required for many other programs 
as well I've created a new archive containing all the necessary files to 
recreate the libraries. To build using this version execute the following 
commands:

$  unzip -o xawxmu.zip
$  @[.command]setup distrib compile
$  xmake xmu,xaw3d

This should built the libraries without error and further interaction.

Installation

Shareable Images

The result of the built are two shareable images, one for Xaw3d and one for 
Xmu. Although one can give a full path for a shareable image at link time, 
OpenVMS does expect to find the file in sys$share at runtime. OTOH for various 
reasons one might not want/be able to place the files in this location. To 
solve this problem just define a logical with the same name as the shareable 
image and point with this to the location of the image in the filesystem, 
e.g. on my system I have:

$ sh log xmulibshr
   "XMULIBSHR" = "PUBBIN:XMULIBSHR" (LNM$PROCESS_TABLE)
$ sh log xaw3dlibshr
   "XAW3DLIBSHR" = "PUBBIN:XAW3DLIBSHR" (LNM$PROCESS_TABLE)

Header files

Source files ported from a Unix system often contain include statements like 
this #include <X11/Xmu/file.h>, which reflects the organization of these files 
on this OS, i.e. the header files for Xmu/Xaw(3d)/... are located in a 
sub-directory of the one containing the X11 header files. To be able to work 
with syntax like this on an OpenVMS system one has to tweak the usual 
definition of the logical X11 a bit ;-).
One thing is that one has to make X11 a rooted logical, so that a path like 
x11:[xmu] (which is what the above translates to on OpenVMS) makes sense. The 
second is that once again one might want to separate the header files 
delivered by Digital from the ones coming with this package. To do this create 
a toplevel directory as the home for non-DEC header files and add to this 
subdirectories named xmu and xaw. Copy the header-files from the distribution 
to these new directories.

As an example the definition on my system looks like this:

$ sh log x11
   "X11" = "X11ADD" (LNM$PROCESS_TABLE)
        = "X11ADD:[XPM.LIB]"
        = "DECW$INCLUDE"
        = "PUBBIN"
1  "X11ADD" = "DKA300:[PUBLIC.XTOOLS.LIBS.]" (LNM$PROCESS_TABLE)
1  "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"
1  "PUBBIN" = "PUBLIC$ROOT:[AEXE]" (LNM$PROCESS_TABLE)
   "X11" = "DECW$INCLUDE" (DECW$LOGICAL_NAMES)
1  "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)
        = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"

x11add
    Rooted logicals have to be first in the list (in this case x11add), also 
    note that a rooted logical may not contain another rooted logical in its 
    definition. 
x11add:[xpm.lib]
    Location of the X Pixmap Library header files. On Unix they are stored 
    directly in the X11 directory. 
decw$include
    Also get the standard header files ;-) 
pubbin
    Actually not the location of header files, but rather the place where I 
    keep my libraries. In some circumstances usefull for linking purposes. 

Programs depending on the Xaw3d/Xmu library

Asclock
    AfterStep Clock 
Emiclock
    Hyper animated face analog clock 
GV (Ghostview)
    GV is a viewer application for Postscript files interpreted by 
    Ghostscript. This application was the reason via Johannes ported the 
    package to OpenVMS. 
Mapedit
    Program to create imagemaps 
Spider
    Patience game 
T1lib
    The example application for T1lib needs Xaw 
Xeyes
    Big X is watching you ... ;-) 
xfd
    Select and display X fonts     

The latest version of the OpenVMS port of Xaw3d/Xmu should always be
accessible via

http://zinser.no-ip.info/vms/sw/xaw.htmlx

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[XMADDRESSBOOK_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
XmAddressbook, DECwindows, Addressbook

Building


To build XmAddressBook just execute make.com. This will check the system setup
and then invoke MMS/MMK with the correct parameters. (Note: No DCL-only build
procedure is currently available) At the time of this writing also the
Xvmsutils are required (at least at version 2.0) to work around the incomplete
implementation of getpwuid in the the C-RTL. 


New features added with 1.5.4

* New qualifier -file (or -f) to read arbitrarily named addressbook files
 (usefull to e.g. keep business and private contacts separated) 

* Added new field to record mobile phone numbers. Attention: This requires an
  extension of the file format used by XmAddressbook. You need to convert older
  files using the new -convert1.2 (or -c1.2) option. The new files can not be
  read by previous versions of XmAddressbook. 

Files


Locations of filenames used by XmAddressBook are defned in main.h. The
following files are used 

xmaddressbook.output 
   Default name when printing the address list to a file 

xmaddressbook.dat 
   Name of the file used to store the address information 

XMADDRESSBOOK_HLP 
   Logical name pointing to the file containing the on-line help for
   XmAddressBook. 

   This file is not in OpenVMS help format. Use xmaddressbook.vmshlp, if you 
   want to insert something in your OpenVMS help library. 

mail.signature 
   Signature file used by XmAddressBook Introduction



The latest version of the OpenVMS port of XmAddressbook should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/xmaddressbook.htmlx

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[XMCD]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
XMCD, MultiMedia, CD Player and Ripper

 Xmcd is a full-featured CD Player and Ripper software package. It includes
 two programs:

 * xmcd - for the X window system using the Motif graphical user interface

 * cda - a shell command-line utility which also features a curses-based,
   screen-oriented mode 

 Both utilities transform your computer's CD or DVD drive into a stereo CD
 player, allowing you to play music CDs on your computer. Moreover, they
 also work as a CD ripper which allows you to extract full-quality digital
 audio data from your CDs and play them real time, save them to files or
 pipe them to other utilities for processing. Many file formats are
 supported, including WAV, AU, AIFF, MP3, AAC, MP4, Ogg Vorbis and FLAC.

 Xmcd is designed to be attractive, feature-rich yet intuitive to use, and
 takes advantage of many CD drive capabilities that are not accessible via
 other software. Unlike other general media players that tries to do it all,
 xmcd focuses on the CD, and strives to be the best with this medium.

 Xmcd supports CD recognition via Gracenote CDDB. It can connect to the
 CDDB servers on the Internet to get the artist, disc title, song titles and
 other information about the CD you're playing. Xmcd uses the enhanced CDDB
 service on some platforms to provide even richer content. The CDDB concept,
 originally pioneered for xmcd, is now the de facto standard source for
 online music information. Xmcd works with many firewall proxy
 configurations for CDDB server access. Moreover, xmcd supports CD-TEXT on
 drives that has this capability.

 Xmcd contains "wwwWarp", a portal to the web browser that offers search and
 dynamic content capabilities based on the CD you're listening to. "Local
 Discography" is a sub-feature of wwwWarp, and provides a browser-based
 means of navigating and maintaining your CD collection, sound files, and
 other related data. There is also a feature-specific help and documentation
 system, command-line control, remote control, plus much more!

 Xmcd has the most extensive platform support of any CD player and ripper
 software. It runs on virtually all Linux and UNIX OS flavors, as well as
 OpenVMS. A vast spectrum of CD drive brand/models are supported, including
 multi-disc CD changers and older SCSI-1 drives.

 See screen-shots of xmcd in action. Also, read this rawmeat.org CD players
 review for UNIX and Linux. Note that it covered xmcd version 2.4. There has
 been many major enhancements to xmcd since then.

 Xmcd is FREE, Open Source software. It is released with the freedom
 provided to you under the GNU General Public License.

 Guided by a philosophy of "maximum functionality with minimum flash", xmcd
 has been enhanced and refined continuously since 1993, and each release is
 backed by an extensive alpha and beta test program. It is robust, reliable,
 secure, and is being enjoyed by thousands of users on a daily basis.

 Xmcd has been included on CD-ROMs from Compaq/Digital, Hewlett Packard, Red
 Hat, SuSE, Walnut Creek, InfoMagic, SCO Skunkware, SGI, Sun, Tams, and
 others. Download the latest version (source code and/or pre-compiled
 binaries), and give it a spin!



+++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[XPHOON_Z]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++++
 
Xphoon, DECwindows, Display moon in X root window

Building

Building Xphoon should be really easy. Just execute make.com and everything 
else should be taken care of automatically. The procedure auto-detectes the 
available C-compiler and Xwindows version and then proceedes to rebuild xphoon 
from the sources. No options and/or user inputs are required. This should work 
on both OpenVMS Alpha and VAX.

Usage

Simply running Xphoon puts a picture of the moon according to the current date 
into the root window of your X server. The phase of the moon is taken into 
account for this. If you do want to get regular updates on these write a short 
script executing Xphoon repeatedly in the background at regular intervalls.


The latest version of this document should always be
accessible via

http://zinser.no-ip.info/vms/sw/xphoon.htmlx

++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[XPORT]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++
 
XPORT, Programming, Bliss XPORT Library

This is a version of the Bliss XPORT API; for details, please see the
provided source code.


++++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[XVMSUTILS_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++++
 
Xvmsutils, Languages, Routines useful for porting UNIX programs to VMS

Installation


To compile the xvmsutils is pretty straightforward. Unpack the sources and 
execute make.com. This should take care about all the dependencies on platform,
OpenVMS version and C compiler version. These actually impose a pretty 
complicated set of conditions on the compilation and quite a bit of effort went 
into working them out.
Since this is getting more and more complicated (i.e. by now it happens that 
functions which are part of an older Compaq C version do vanish in more 
current ones) I have embarked to rebuild the procedure to use small 
testprograms to determine if a specfic function is implemented or not. This is 
currently work in progress, i.e. the procedure uses currently a mixture of 
both approaches.
In case MMS/MMK is installed this will be used to perform the actual compile, 
otherwise make.com will handle it by itself. 


Version 2.03 is the first one in quite a while that actually has been tested 
on OpenVMS VAX. A number of bugs in the build procedure have been squashed for 
this release and it should build cleanly now on VAX systems again. 


If you install a new DEC C compiler/OpenVMS version and receive messages about 
multiply defined symbols using a previously compiled version of the Xvmsutils 
object library, delete it and rebuild the file. Just reexecuting make.com won't 
help since this will reuse the existing library file and therefore modules once 
inserted won't vanish from it. 


Setup


To be able to refer to the include files of the library without too much hassle 
you might want to define a logical X11VMS, which points to the directory where 
you've installed the Xvmsutils. 


Starting with version 2.0 on OpenVMS Alpha also a shareable image version of 
the Xvmsutils is created, which should be refrenced by the logical name 
X11VMSSHR. 


History


Actually this library was developed first about 1989 to support a port of the 
X11R3/R4 applications to VMS. I am taking care of the code since 1995. Mostly 
this means nowadays removing bits and pieces either in the makefiles or in the 
code (i.e. using appropriate #ifdefs in this case) since the DEC C compiler 
contains more and more of the functions in the meantime by itself. If you have 
suggestions how to improve the library still drop me a note, I shall be happy 
to discuss the topic with you. 


Applications using the Xvmsutils

Blockade
  Logic game: (Re-)Move blocks from the board 

Emiclock
  Clock with various characters displayed in the face 

Xmaddressbook
  You have guessed it, a graphical addressbook 

Xsnow
  Have it snow on your Xscreen and spy Santa on his way 

Xsokoban
  Logic game: Japanese Warehouse keeper Installation


The latest version of the Xvmsutils library should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/xvmsutils.htmlx

++++++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[YAHMAIL_Z]FREEWARE_README.TXT;1
++++++++++++++++++++++++++++++++++++++++++++++++++
 
Yahmail, Utilities, Yet another Hypermail

Disclaimer
==========
While this Yahmail distribution for the hp OpenVMS freeware CD was
packaged  by Martin P.J. Zinser (zinser@dzinser.no-ip.info) and I am
certainly willing to help  with questions and problems concerning its
usage I am in no way at all remotely anything like the author of this
very fine piece of software. Mark Daniels has done this pretty much
alone and deserves all due credit for  his effort.

================================================================================
Installation

The procedure build_yahmail.com can be called with up to four parameters in 
arbitrary order.

BUILD||COMPILE||LINK
    BUILD compiles and links the Yahmail executable, COMPILE and LINK just 
    perform the respective actions. If no parameter is given a compile and 
    link is performed by default. 
MIME
    Build Yahmail with support for MIME encoded messages. 
PMDF
    Build Yahmail with support for PMDF mail in case this is installed on your 
    system. 
LANG <EN||DE||ES||RU>
    Build Yahmail with Userinterface in: English, German, Spanish, or Russian 

Setup

To copy the freshly build scripts to the CGI directory of your Webserver use 
@install <INSTALL||UPDATE> <WASD||OSU||APACHE||CGI>.
INSTALL should be used for new installations (providing a initial 
configuration and startup file), while UPDATE is appropriate to upgrade an 
existing Yahmail installation to the latest version.
For OSU and using an account other than the one the Webserver runs on one 
might need to define www_root to an appropriate value before invoking the 
procedure.

Config files

It might be neccessary to change the configuration of your Webserver to 
account for the new scripts. Some hints on this come with the source code for

    * Apache        (readme_apache.html)
    * generic CGI   (readme_cgi.html)
    * OSU           (readme_osu.html)
    * WASD          (readme_wasd.html)

The latest version of this document should always be
accessible via

http://zinser.no-ip.info/vms/sw/yahmail.htmlx

+++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[ZLIB]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++
 
Zlib, Utilities, Compression/Decompression Library

Zlib is a compression/decompression library used by several software
packages, including MySQL and Python.

By default, the installation procedure installs this library package in
the |SYS$COMMON:[LIBZ]| directory. To install it in another directory,
dev:[dir], use the |/DESTINATION| parameter of the |PRODUCT| command. In
this case, the library package will be installed in the |dev:[dir.LIBZ]|
directory.


        Installation

   1. Make the directory which holds the ZIP file your default directory
   2. Extract the PCSI kit from the ZIP archive.

$ UNZIP "-V" ZLIB-V0102-1-1

   3. Install the Zlib package to your chosen destination.

$ PRODUCT INSTALL zlib  /(default)/

or ...

$ PRODUCT INSTALL zlib /DESTINATION=dev:[dir]

   4. Finally, run the DCL procedure |STARTUP.COM| to define the
      necessary logicals.

(You might want to add the relevant line to your |SYSTARTUP_VMS.COM| file.)

$ @SYS$COMMON:[LIBZ]STARTUP  /(default)/

  or ...

$ @dev:[dir.LIBZ]:STARTUP


+++++++++++++++++++++++++++++++++++++++++++++++
DISK$FREEWARE70_3:[ZLIB_Z]FREEWARE_README.TXT;1
+++++++++++++++++++++++++++++++++++++++++++++++
 
Zlib_Z, Programming, General compression library

Installation


Just execute @make_vms to build the library. This checks for available 
compilers as well as for MMS/MMK and uses them for the build if available.
 
 The procedure accepts the following options in arbitrary order: 

DEBUG
  Build Zlib with Debug information enabled 
CCOPT=<Value>
  Pass the given options to the C compiler 
LINK
  Do not compile, just link the Zlib shareable image 
LOPTS=<Value>
  Pass the given options to the Linker 
CC=<DECC||VAXC||GNUC>
  Force usage of the given C compiler over the intrinsic selection (which 
  is DEC C, VAX C, and finally GNU C). 
MAKE=<MMK||MMS>
  Force usage of MMK or MMS over the intrinsic detection (which prefers
  MMK over MMS). 

Together with the source for the library two small sample applications are 
delivered, which are build automatically with the library. Note: Minigzip 
depends on the abailability of the Xvmsutils library and will only be created 
if this package is available. This does not affect the correct creation of the 
Zlib library at all. 


Package contents


The main results of the compilation are the object library libz.olb, and on 
OpenVMS Alpha the shareable image libzshr.exe, which other applications need 
to link against. Additionally two small executable programs are created in 
the main source directory: 

example
This essentially is a hello world program for Zlib. If you do get output like 
the following from it, the library should work fine on your system: 

$ run example
uncompress(): hello, hello!
gzread(): hello, hello!
gzgets() after gzseek: hello!
inflate(): hello, hello!
large_inflate(): OK
after inflateSync(): hello, hello!
inflate with dictionary: hello, hello!

minigzip
This is a bare-bones version of the GNU Gzip program, showing how such 
functionality can be implemented using Zlib. 

Applications that use Zlib


Remark: All applications using Libpng implicitly also use Zlib. 

Fly
  Generate graphics files on the fly from ASCII-descriptions 
Freetype 2
  Free TrueType font rendering engine 
GD
  Library for on-the-fly graphics generation. 
GDchart
  Library for on-the-fly chart generation 
Gnuplot
  Gnuplot is a popular package for doing graphs. 
VMS Mosaic
  HTML 3.2 compliant Webbrowser. Libpng is bundeled with the source. 
Xanim
  Display animations encoded in several formats (FLI, QT, etc.) 

The latest version of the OpenVMS port of the Zlib library should always be 
accessible via 

http://zinser.no-ip.info/vms/sw/zlib.htmlx
