<COMMENT>(--------------------------------------------------------------------)

<FRONT_MATTER>
<TITLE_PAGE>

<TITLE>(HFRD VMS Hypertext Services\
<HELLIPSIS> <EMPHASIS>(read this first))

<LINE>

<HEAD>(1st January 1996\head_date)

<HEAD>(Abstract\head_abstract)

<P> This document is an essential read prior to further investigating the 
freeware HFRD VMS Hypertext Services software package. 

<P> It covers the version 3 release of the HFRD VMS HTTPd server and 
associated software. 

<HEAD>(Author\head_author)

<P> Mark G. Daniel
<LINE> Senior Information Technologist

<P> Mark.Daniel@dsto.defence.gov.au

<P> +61 (8) 2596031 (bus) 
<LINE> +61 (8) 2596673 (fax)

<P> Mark G. Daniel
<LINE> High Frequency Radar Division
<LINE> Defence Science and Technology Organisation
<LINE> PO Box 1500
<LINE> Salisbury
<LINE> South Australia 5108

<ENDTITLE_PAGE>

<COPYRIGHT_PAGE>

<P> <EMPHASIS>(HFRD VMS Hypertext Services, Copyright (C) 1996 Mark G. 
Daniel.\BOLD) 

<P> This package is free software; you can redistribute it and/or modify it 
under the terms of the <EMPHASIS>(GNU General Public License\BOLD) as published
by the Free Software Foundation; version 2 of the License, or any later version.

<P> This package 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. 

<P> You should have received a copy of the GNU General Public License along 
with this package; if not, write to the Free Software Foundation, Inc., 675 
Mass Ave, Cambridge, MA 02139, USA. 

<LINE>
<LINE>

<P> <EMPHASIS>(DEC TCP/IP Services for OpenVMS),
    <EMPHASIS>(VAX C),
    <EMPHASIS>(DEC C),
    <EMPHASIS>(VAX) and
    <EMPHASIS>(AXP) 

<LINE>
are registered trademarks of Digital Equipment Corporation. 

<P> <EMPHASIS>(MultiNet) is a registered trademark of TGV, Inc.

<LINE>
<LINE>

<P> <EMPHASIS>(<OPAREN>how's that for legalese?)
    <EMPHASIS>(:^<CPAREN>\SMALLCAPS)
    <EMPHASIS>(<CPAREN>)
<ENDCOPYRIGHT_PAGE>

<CONTENTS_FILE>

<ENDFRONT_MATTER>

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Disclaimer\chapter_disclaimer)

<P> As High Frequency Radar Division currently employs some useful (and in 
that sense valuable) <EMPHASIS>(freeware) and <EMPHASIS>(public-domain) 
software, its management has consented, in the spirit of wishing to 
<QUOTE>(pay its dues) and encourage this environment, to make some of its own, 
locally implemented hypertext services software available to the broader VMS 
community. 

<P> The Division recognises that although having no commercial value, this 
software can never-the-less be valuable to other sites because of its low 
cost (usually media only) and in that it may address niche requirements not 
viable for commercial vendors.  It should be emphasized that this is not a 
commercial-grade package, has not been designed with that in mind, should not 
be recognised as such, nor is it in any way endorsed by the High Frequency 
Radar Divison or its management. 

<P> This package is <EMPHASIS>(free software) provided under the 
<EMPHASIS>(GNU General Public License\BOLD), there is 
<EMPHASIS>(ABSOLUTELY NO WARRANTY\BOLD) of any kind.  See 
<REFERENCE>(chapter_gnu_license).  If you are not familiar with this approach 
to licensing please take the time to read it. 

<HEAD>(Author's Note\head_intro_authors_note)

<P> It definitely is not a commercial-grade package but I still think it works 
well (and am only moderately reticent to let others scrutinize my work)! 

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Overview\chapter_overview)

<P> This <EMPHASIS>(read this first) is a quick <QUOTE>(throw-together) 
providing an introduction and some guidance for support external to HFRD.  It 
does not pretend to be as exhaustive as is necessary, but hey I'm not getting 
paid for this <EMPHASIS>(:^<CPAREN>\SMALLCAPS) 

<P> The implementation of the internal hypertext environment started off as a 
Divisional management action-item, <QUOTE>(<EMPHASIS>(make it easier to access 
information-systems-based documentation and other data in a multi-platform 
environment)).  Gopher was a first and brief stop, just as the power of the 
WWW technologies was becoming obvious (mid 1994).  Like many others, I became 
impressed with the potential to integrate disparate data formats and platforms 
with the ease of the point-and-click functionality of the browser. 

<P> After evaluating the CERN (live) and an earlier OSU DEC-threads (by 
documentation) servers I decided some of the limitations and other 
idiosyncracies of these warranted investing a little in our own (how's that 
for <EMPHASIS>(hubris)!)  The upshot was that although the Divison provided 
core time and justification for development and implementation of this 
environment, I spent considerable of my own time on the package as well.  The 
HTTPd server's multi-threading is done using VMS ASTs, and this is by far the 
largest AST-driven system I have designed and built.  In short, I found it a 
challenge, I learned a remarkable amount (particularly about VMS' ASTs), and 
gained a great deal of satisfaction from it.  I hope its of some use to 
someone out there other than us. 

<P> Without apology, the server and its environment has been designed to
support an intra-organisational hypertext environment and has been tailored to 
the requirements of the High Frequency Radar Divison and its VMS environment.  
Any other usefulness is purely coincidental!  All this not-with-standing, it 
should prove useful in the broader context.  As mentioned above, it is not a 
commercial-grade product and as this is its first public release a little 
fiddling and experimentation may be required. 

<HEAD>(Documentation\head_overview_doc)

<P> Some documentation is provided, but again this is mainly for internal, 
Divisional support purposes.  If external readers find it useful then that's a 
bonus!  It is basically unaltered from its original, internal purpose, apart 
from more extensive author contact information, the copyright notices, and 
some small disclaimers in the introductions.  If the software should become 
more widely used the author would consider making the documentation more 
generic. 

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<P> See the <A HREF="/ht_root/doc/"><TT>[.DOC]</TT></A> directory.
)

<COMMENT>(HTML/OFF)
<P> See the <BOX>([.DOC]) <EMPHASIS>((hypertext link)) directory.
<COMMENT>(HTML/ON) 

<COMMENT>(....................................................................)

You should find HTML, Bookreader (and HyperReader), plain-text and PostScript 
versions (all generated from <EMPHASIS>(SDML\SMALLCAPS) sources using DEC 
Document and the <EMPHASIS>(SDM2HTM\SMALLCAPS) application found in this 
package). 

<P> The <QUOTE>(Proceedings of the Twenty-Fifth Annual DECUS Australia 
Symposium, 1995) contain a paper by the author summarising a presentation made 
during that event, titled <QUOTE>(Introduction to World Wide Web Technologies 
<EMPHASIS>(... what the surfboard is made from)).  I have taken the liberty of 
including it for informational purposes, in PostScript format, in the 

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<A HREF="/ht_root/doc/"><TT>[.DOC]</TT></A>
)

<COMMENT>(HTML/OFF)
<BOX>([.DOC]) <EMPHASIS>((hypertext link))
<COMMENT>(HTML/ON) 

<COMMENT>(....................................................................)

directory.  Partly it documents some of the uses  HFRD has made of the
hypertext environment, although even now (1996) it may be  getting a little
dated.

<HEAD>(Feedback\head_feedback)

<P> It would be interesting to know who is using what parts of this package 
and where.  If you find it of use could you please make a moment to drop an
e-mail (or even snail-mail) listing: 

<LIST>(UNNUMBERED)
<LE> name
<LE> organisation and address
<LE> e-mail address
<LE> components and version of HFRD VMS Hypertext Services in use
<LE> platform(s) (AXP/VAX, VMS version, network software and version)
<LE> any other comments
<ENDLIST>

<P> This information will be confidential.  I may use it to feedback to you
any monumental changes in the package <EMPHASIS>(:^<CPAREN>\SMALLCAPS)  With 
thanks.

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<P> <A HREF="mailto:Mark.Daniel@dsto.defence.gov.au">E-Mail me now!</A> 
)

<COMMENT>(HTML/OFF)
<P> <BOX>(E-Mail me now!) <EMPHASIS>((hypertext mailto: anchor))
<COMMENT>(HTML/ON) 

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Scripts\chapter_scripts)

<P> The script applications have all been designed to be (more-or-less) CGI 
compliant.  The HTTPd server passes request data only via CGI variables.  In a 
similar fashion to the CERN implementation these CGI variables are implemented 
as DCL symbols, with the standard CGI variable names prefixed by 
<QUOTE>(<EMPHASIS>(WWW_\SMALLCAPS)).  Script applications usually return a 
full HTTP response (i.e. generate their own header and a full data stream, 
and could be considered the equivalent of <EMPHASIS>(no-parse-header) 
scripts), although server generation of headers is also available.

<P> It may be possible to adapt these applications to other server 
environments.  As the author considers some of the scripts to be quite useful
(e.g. HyperReader, a hypertext Bookreader application) this is encouraged.  
The <EMPHASIS>(GNU General Public License\BOLD) still applies of course.

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Requirements\chapter_requirements)

<P> <QUOTE>(Out-of-the-box) the package executes using DEC TCP/IP Services on
both AXP and VAX platforms.  The VMD HTTPd server itself is specifically
tailored to DEC TCP/IP Services for OpenVMS (v3.3, a.k.a. UCX), particularly
its QIO interface.

<P> The software was originally written in a VAX C (v3.2) and 
later DEC C (v5.<EMPHASIS>(n)) environments, under VMS 6.<EMPHASIS>(n).  No 
consideration has been given to any other environments.  The DEC C run-time 
environment is prefered to the VAX C run-time environment because the former's 
greater integrity and improved performance over the latter.

<HEAD>(Executables\head_requirements_executables)

<P> The executables provided with the package have been compiled using DEC C
v5.0 and linked against the VMS v6.2 <EMPHASIS>(DECC$SHR.EXE\SMALLCAPS) RTL,
with the following implications:

<LIST>(UNNUMBERED)

<LE> <EMPHASIS>(AXP Systems\BOLD)

<P> For AXP systems with VMS v6.<EMPHASIS>(n) this should not present any
problems.

<COMMENT>(HTML=<P>)

<LE> <EMPHASIS>(VAX Systems\BOLD)

<P> For VAX systems there will be an incompatibility for VMS VAX versions prior
to 6.2, as noted in the <EMPHASIS>(Open VMS Version 6.2 Release Notes\BOLD):

<CODE_EXAMPLE>
  4.5.2.2  DECC$SHR.EXE (VAX Only)

  V6.2

  A new package of internationalization routines has been
  added to the DEC C RTL (see Section 4.5.1.3) and the trans-
  fer vector has been extended, necessitating an increase in the
  minor ident (GSMATCH) of the image.  Because of this, pro-
  grams using the DEC C RTL (DECC$SHR.EXE) linked on
  OpenVMS VAX Version 6.2 systems will not run on prior
  versions of OpenVMS VAX.
<ENDCODE_EXAMPLE>

<P> <EMPHASIS>(Solutions:\BOLD)

<COMMENT>(HTML=<P>)

<LIST>(NUMBERED)

<LE> If your VAX site does not support the DEC C compiler or run-time 
environment (check here for the run-time, shareable image: 

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<A HREF="/sys$common/syslib/decc$shr.exe;*">
<TT>SYS$COMMON:[SYSLIB]DECC$SHR.EXE</TT></A>
)

<COMMENT>(HTML/OFF)
<BOX>(SYS$COMMON:[SYSLIB]DECC$SHR.EXE) <EMPHASIS>((hypertext link))
<COMMENT>(HTML/ON) 

<COMMENT>(....................................................................)

), the run-time components alone can be installed and used without additional 
licensing.  This is a simple and short duration exercise.  The DEC C/C++
Run-Time Components kit is available on the Digital consolidated distribution 
CD-ROM (last seen in the same CD and directory as the DEC C compiler).  For 
your convenience, and within Digital's permitted redistribution guidelines, 
the run-time kit is also provided as part of this package.  The saveset and 
documentation are located in the 

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<A HREF="/ht_root/aacrt060/"><TT>[.AACRT060]</TT></A>
)

<COMMENT>(HTML/OFF)
<BOX>([.AACRT060]) <EMPHASIS>((hypertext link))
<COMMENT>(HTML/ON) 

<COMMENT>(....................................................................)

directory.  Please read the installation instructions provided in that 
directory. 

<COMMENT>(HTML=<P>)

<LE> Relink all of the applications against you current
<EMPHASIS>(DECC$SHR.EXE\SMALLCAPS), sorry.  The build procedures all accept
<QUOTE>(LINK) as a command-line parameter, skipping the compilation phase and
just linking.  The procedure

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<A HREF="/ht_root/src/relink_all.com"><TT>[.SRC]RELINK_ALL.COM</TT></A>
)

<COMMENT>(HTML/OFF)
<BOX>([.SRC]RELINK_ALL.COM) <EMPHASIS>((hypertext link))
<COMMENT>(HTML/ON) 

<COMMENT>(....................................................................)

will execute all the build procedures through the link phase.

<ENDLIST>

<ENDLIST>

<P> Needless-to-say (but I will anyway), the server requires a privileged 
environment (either account or image) in which to execute. 

<NOTE>

To give this software an opportunity to be useful to a larger number of sites 
I ported it to TGV MultiNet TCP/IP (v3.4) over New Year 95-96.  This has been 
tested under VMS VAX 6.2 and seems to work OK.  It is basically the DEC TCP/IP 
QIO adapted to MultiNet's QIO interface.  It is not as exhaustively tested as 
the DEC TCP/IP version.  I have not compiled or tested it using MultiNet on 
AXP, we have only the one VAX architecture system using TGV's product, other 
VAX and AXP systems use bundled DEC TCP/IP.  Just to emphasize once again, 
HFRD does not need a MultiNet version, so this is strictly a bonus.  I would 
appreciate (but may not end up implementing) any suggestions on improving the 
networking code. 

<ENDNOTE>

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Building\chapter_building)

<P> All of the applications are written in <EMPHASIS>(C\BOLD).

<P> As the software has been written to the requirements of DEC C 
(in an <EMPHASIS>(uncritical), VAXC-backward-compatible compilation mode, i.e. 
<EMPHASIS>(/STANDARD=VAXC\SMALLCAPS) <EMPHASIS>((when moving from VAXC C to 
DEC C the author discovered he wasn't the rigorous software engineer he 
had hoped he was <EMPHASIS>(:^<CPAREN>\SMALLCAPS))) its build and run-time 
behaviour in other compiler environments is unpredictable. 

<P> All applications are linked against the DEC C 
<EMPHASIS>(DECC$SHR.EXE\SMALLCAPS) RTL.  The DEC C run-time environment is 
prefered to the VAX C run-time environment because the former's greater 
integrity and improved performance over the latter.  See the section 
<REFERENCE>(head_requirements_executables) for further information on this 
component.  In all probability, if you're considering re-compiling, this 
environment will already be available on your site somewhere. 

<P> <EMPHASIS>(Brute-force) build procedures are provided in each software 
application source directory.  They are named 
<QUOTE>(BUILD_<EMPHASIS>(whatever).COM).

<P> Two procedures can be used to rebuild or relink all applications in the 
package.  Because of some dependencies the HTTPd server should be built first.

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<UL>
<LI> <A HREF="/ht_root/src/build_all.com"><TT>[.SRC]BUILD_ALL.COM</TT></A>
<LI> <A HREF="/ht_root/src/relink_all.com"><TT>[.SRC]RELINK_ALL.COM</TT></A>
</UL>
)

<COMMENT>(HTML/OFF)
<LIST>(UNNUMBERED)
<LE> <BOX>([.SRC]BUILD_ALL.COM) <EMPHASIS>((hypertext link))
<LE> <BOX>([.SRC]RELINK_ALL.COM) <EMPHASIS>((hypertext link))
<ENDLIST>
<COMMENT>(HTML/ON) 

<COMMENT>(....................................................................)

<P> Also, the HTTPd server itself is specifically tailored to DEC TCP/IP 
Services for OpenVMS (primarily) and TGV MultiNet (secondarily), particularly 
their QIO interfaces, so again its build and run-time behaviour in other 
environments is indeterminate.  The HTTPd server build procedure detects the 
MultiNet environment and builds accordingly.  The executable in this 
environment is specifically named <EMPHASIS>(HTTPD_MULTINET.EXE\SMALLCAPS) so 
as to clearly indicate which build has occured.  This can be renamed to 
<EMPHASIS>(HTTPD.EXE\SMALLCAPS) or left unchanged and procedures modified to 
reflect that name. 

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Can't Wait?\chapter_cant_wait)

<P> Can't wait to try it out?  (You should definitely have first read the 
section <REFERENCE>(chapter_requirements).) This will give you a minimal, non-
custom, hypertext environment, with the server running from the command line.  
You will need a privileged account and the general requirements of the server 
package (see <REFERENCE>(chapter_requirements)).  This assumes the server has 
been built for the local environment. 

<P> <EMPHASIS>(Device:) is the disk device on which the package has been 
placed.  <EMPHASIS>(Architecture) is either <QUOTE>(AXP) or <QUOTE>(VAX) 
depending on your platform.  <EMPHASIS>(Port) is the IP port for the server to 
use (defaults to 80, but can be bound elsewhere allowing the evaluation of 
this environment against an existing one on the same host). 

<P> Enter the following DCL commands:

<CODE_EXAMPLE>
  $ DEFINE /JOB /TRANSLATION=CONCEALED HT_ROOT device:[HT_ROOT.]
  $ DEFINE /JOB HT_EXE HT_ROOT:[architecture]
  $ DEFINE /JOB HTTPD$CONFIG HT_ROOT:[HTTPD.EXAMPLE]HTTPD$CONFIG.CONF
  $ DEFINE /JOB HTTPD$MAP HT_ROOT:[HTTPD.EXAMPLE]HTTPD$MAP.CONF
  $ HTTPD == "$HT_EXE:HTTPD"
  $ HTTPD /NOLOG /PORT=port
<ENDCODE_EXAMPLE>

<P> Then bring up your browser and access this URL:

<CODE_EXAMPLE>
  http://<EMPHASIS>(host[:port])/
<ENDCODE_EXAMPLE>

<HEAD>(Alternatively <HELLIPSIS>\head_cant_wait_alt)

<COMMENT>(....................................................................)

<COMMENT>(HTML=
<P> Execute
<A HREF="/ht_root/freeware_demo.com">
<TT>@device:[HT_ROOT]FREEWARE_DEMO.COM</TT></A>
)

<COMMENT>(HTML/OFF)
<P> Execute <BOX>(<EMPHASIS>(@device:[HT_ROOT]FREEWARE_DEMO.COM\SMALLCAPS))
<EMPHASIS>((hypertext link)) 
<COMMENT>(HTML/ON) 

(which will do all of the above, and a bit more, for you
<EMPHASIS>(:^<CPAREN>\SMALLCAPS) )

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(Support\chapter_support)

<P> The HFRD VMS hypertext services have become an integral component of the 
High Frequency Radar Division's documentation access strategy.  During 1995 
the environment has also achieved a high degree of integration of available 
documentation and software resources for the VMS user and software development 
environment.  Although always in need of further development and refinement 
the level of functionality probably meets the Division's current
intra-organisational hypertext environment requirements, and so it will not be 
driving any further significant (foreseeable) developments.

<P> This not-with-standing, the author may, if demand, or requirements, or 
inclination arises, further develop the package, either by refining the 
existing server or scripts, or by adding additional functionality or scripts. 

<P> TGV MultiNet support is tenuous.  HFRD has it only on one, older and 
obsolescent VAX system, which may not be on maintenance tomorrow!

<P> Investigation of bug reports/fixes and implementation of additional 
functionality will be completely contingent on its impact or relevance to 
HFRD's use of or desirability for the instance in question.  Anything other 
than this would need to be done in the author's own time and therefore is also 
contingent on the circumstances.

<P> The author welcomes bug reports (I don't really) and any other feedback 
or comments, particularly if they are not too damaging to his fragile ego.
E-mail is preferable.  Every effort will be made to respond, as is possible at 
the time (sooner better than later), but no guarantees.  For a more formal 
request see <REFERENCE>(head_feedback) in <REFERENCE>(chapter_overview). 

<P> Of course, because this package is <EMPHASIS>(free software) provided 
under the <EMPHASIS>(GNU General Public License\BOLD), there is 
<EMPHASIS>(ABSOLUTELY NO WARRANTY\BOLD) of any kind.  See 
<REFERENCE>(chapter_gnu_license).

<COMMENT>(--------------------------------------------------------------------)

<CHAPTER>(GNU General Public License\chapter_gnu_license)

<P>
<CODE_EXAMPLE>
                    GNU GENERAL PUBLIC LICENSE
                       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
                          675 Mass Ave, Cambridge, MA 02139, USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

  When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

  We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

  Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and
modification follow.

                    GNU GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License.  The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language.  (Hereinafter, translation is included without limitation in
the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices
    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in
    whole or in part contains or is derived from the Program or any
    part thereof, to be licensed as a whole at no charge to all third
    parties under the terms of this License.

    c) If the modified program normally reads commands interactively
    when run, you must cause it, when started running for such
    interactive use in the most ordinary way, to print or display an
    announcement including an appropriate copyright notice and a
    notice that there is no warranty (or else, saying that you provide
    a warranty) and that users may redistribute the program under
    these conditions, and telling the user how to view a copy of this
    License.  (Exception: if the Program itself is interactive but
    does not normally print such an announcement, your work based on
    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable
    source code, which must be distributed under the terms of Sections
    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three
    years, to give any third party, for a charge no more than your
    cost of physically performing source distribution, a complete
    machine-readable copy of the corresponding source code, to be
    distributed under the terms of Sections 1 and 2 above on a medium
    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer
    to distribute corresponding source code.  (This alternative is
    allowed only for noncommercial distribution and only if you
    received the program in object code or executable form with such
    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it.  For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.  However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

  5. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Program or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

  7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all.  For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time.  Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number.  If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation.  If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

  10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission.  For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this.  Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

                            NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

                     END OF TERMS AND CONDITIONS
<ENDCODE_EXAMPLE>

<COMMENT>(--------------------------------------------------------------------)

