$Id: README,v 1.20 2004/06/10 15:55:08 lhoward Exp $

                           *   ANNOUNCE   *

The HylaFAX development team is pleased to announce our 4.2.0
feature release!  As always, our sincerest thanks go to all who
participate and provide feedback.

                               *   *   *

This document is intended to describe the significant differences
between hylafax-4.2.0 and older releases, point out any known
incompatibilites and issues, and provide the reader with directions to
further resources regarding HylaFAX. 

                          *   NEW FEATURES   *
* added Class 1 ECM and MMR support
* added Class 1.0 V.34-Fax (SuperG3) Support
* added software-driven real-time format compression conversion
* added extended resolution support
* removed the requirement for a case-sensitive filesystem to build
* unified the queue file numbering mechanism
* integrated Caller-ID/DID support throughout the software
* numerous other enhancements and bugfixes (see CHANGES)

                         *   KNOWN ISSUES   *

* A low-priority job can block a high priority job to the same destination.
** Please refer to HylaFAX Bugzilla for a detailed list of issues.

                       *   INCOMPATIBILITIES   *

* Due to tighter adherance to ITU-T T.32 and the older Class 2 
  specifications, HylaFAX copy-quality checking and ECM support now 
  operates slightly different in Class 2/2.0/2.1 than in previous 
  versions.  This change will not effect users of most modems, but 
  because the Eicon Diva Server follows T.32 yet uses the older 
  Class 2 command interface, Diva Server users will probably need 
  to add:
    Class2ECMType:    2.0
    Class2CQQueryCmd: !3
    Class2CQCmd:      AT
  to their respective modem config files.
* libtiff-3.6.1 is fatally flawed when dealing with Group 3 images.  
  Don't use it as-is.  
  See: http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=500

                      *   WHO SHOULD UPGRADE?   *

This release includes nearly a year's worth of truly exceptional
contributions from HylaFAX developers and users alike, and everyone
should consider migrating to a HylaFAX-4.2.x release as soon as
possible. While every attempt has been made to retain backwards
compatibility with the 4.1.x series, it's possible that assumptions
your local installation depends upon may no longer be true. Whenever
possible, test test test before upgrading a production server!!

HylaFAX-4.2.0 will be of particular benefit to anyone running their
modems in Class 1 due to the addition of native ECM and V.34 support
(useful features that were previously available only in the
notoriously buggy Class 2 firmware of modem manufacturers).


                     *   HYLAFAX BINARY PACKAGES   *

Binary packages for some operating systems and platforms are available.  
Please see ftp://ftp.hylafax.org/binary/ and 
http://www.hylafax.org/howto/install.html#ss2.3.3  If you are able and 
willing to produce a binary package of HylaFAX for general distribution, 
then you are invited to join hylafax-devel@hylafax.org and solicit your 
binary package.

                    *   COMMERCIAL SUPPORT   *

iFax Solutions, Inc. (http://www.ifax.com) provides commercial support
to HylaFAX users. Single-incident and annual support options are
available, as well as a variety of consulting services. Contact
HylaFAX Sales <sales@ifax.com> for more information.

                       *   FREE SUPPORT   *

HylaFAX has numerous public support resources available.  The user is
encouraged to utilize the manpage documentation before turning to
other support arenas.  However, if other support is desired, or if you
would like to actively take part in the HylaFAX community, you are
invited to:

  * join and participate in a HylaFAX mailing list
    See: http://www.hylafax.org/mailing-lists.html

    When corresponding about this software, please always specify:
    - what version of HylaFAX you have,
    - what system you're running on (if it is Linux please name the
      distribution)
    - if the problem is modem-related, identify it and the firmware rev
    For example: "HylaFAX v4.0pl2 under RedHat Linux 4.2 with gcc 2.7.2;
    ZyXEL 1496E with 6.11a firmware."

  * read the on-line documentation and resources
    See: http://www.hylafax.org and http://www.hylafax.org/howto

  * review HylaFAX CVS
    See: http://www.hylafax.org/cvs.html

  * report confirmed bugs, feature requests, and submit patches
    See: http://bugs.hylafax.org/bugzilla



Thanks,

  The HylaFAX development team

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

And now, a note from HylaFAX's original author ;-)

Silicon Graphics has seen fit to allow me to give this work away.  It
is free.  There is no support or guarantee of any sort as to its
operations, correctness, or whatever.  If you do anything useful with
all or parts of it you need to honor the copyright notices.   I would
also be interested in knowing about it and, hopefully, be acknowledged.

Finally, note that this software is called ``HylaFAX'', not ``Hylafax'',
``hylafax'', and certainly not ``FlexFAX'' (the old name which someone
else has a copyright on).  If you want to refer to this software use
``HylaFAX (tm)'' and be sure to honor the Silicon Graphics trademark.

	Sam Leffler

Use and Copyright
-----------------

Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.
HylaFAX is a trademark of Silicon Graphics

    Permission to use, copy, modify, distribute, and sell this software and 
    its documentation for any purpose is hereby granted without fee, provided
    that (i) the above copyright notices and this permission notice appear in
    all copies of the software and related documentation, and (ii) the names of
    Sam Leffler and Silicon Graphics may not be used in any advertising or
    publicity relating to the software without the specific, prior written
    permission of Sam Leffler and Silicon Graphics.

    THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, 
    EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY 
    WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  

    IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
    ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
    OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
    WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF 
    LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE 
    OF THIS SOFTWARE.
