Copyright © 2007 Symantec
Corporation. All rights reserved. Symantec, the Symantec Logo are trademarks or
registered trademarks of Symantec Corporation or its affiliates in the
The Licensed Software and
Documentation are deemed to be “commercial computer software” and “commercial
computer software documentation” as defined in FAR Sections 12.212 and DFARS
Section 227.7202.
--------------------------------------------------------
Installation Notes Read Me: February 2007
--------------------------------------------------------
PLEASE READ THIS DOCUMENT CAREFULLY;
it contains important installation information about Norton 360.
TOPICS
Topics include:
Other Third-party Acknowledgements
Listed below are the minimum system
requirements for installing Norton 360.
Operating System: Windows® XP Home/XP Pro/XP Media 2005/Vista 32-bit/Vista
64-bit + Phishing Protection feature requires Microsoft® Internet Explorer*
v6.0 or higher Email scanning supported for POP3-compatible email clients
Norton 360 cannot be installed on
Windows 95, Windows 98, Windows ME, or Windows 2000.
Minimum
Hardware Requirements
300MHz or higher processor
256MB of RAM minimum; 512 MB recommended
300MB of free hard disk space
REQUIRED FOR ALL INSTALLATIONS
Internet Explorer 6.0
Internet connection (high-speed connection required for Online Backup)
You can download the most current
version of Internet Explorer at:
http://download.microsoft.com
Email scanning for viruses is
supported for most standard POP3 email clients.
How to save a MSI log file to troubleshoot install and
uninstall issues
If Norton 360 fails to install, we
recommend saving the Norton 360 2006 (Date/Time).LOG file that is generated by
default during your installation of Norton 360. This will help the Symantec
Support Team to resolve your issue faster. After uninstalling Norton 360, there
should be two Norton 360.log files. The install log should show an earlier
date, time and smaller KB size. The uninstall log should show a later date,
time and bigger KB size.
To locate this log file:
1. Click on "Start > Run."
2. Type the following command "%temp%".
3. This should automatically launch the Windows temporary directory.
4. Find a file called "Norton 360 (Date/Time).log."
Supported
Ports for Norton 360 email protection
Norton 360 supports email scanning
only on the default port of 110 (POP3). Currently, we do not provide Email
protection for any other ports.
Digitally
signing emails in Outlook Express 6.x and Office XP
Outlook Express 6.x offers the
ability to digitally sign emails to ensure that they are not modified during
transfer. Norton 360 email protection will modify the emails during virus
repair. This will create an Outlook alert stating the message has been
modified.
Restoring Network Connectivity on Vista 64-bit Edition using
Norton 360
Norton 360 will not be able to
automatically restore network connectivity on
1.
On the Windows Start menu, click Control Panel.
(If Control Panel isn't already in Classic
View mode, click the Classic View link on the left.)
2. In the Control Panel window, double-click
the System icon.
3. In the System properties, in the task list
on the left, click the Device Manager link.
4. If the User Account Control prompt appears,
click Continue.
5. In the System Properties list, under
Network Adapters, for each item with a red "X" right-click and select
Enable.
Firewall Rules
There
is an issue that prevents double-bit character set-enabled systems from
displaying typed characters in the Firewall General and Firewall Program rules
editing windows.
The
suggested remedy is to temporarily change the default language.
Help Addendum
Norton
360 Help refers to Event Log
In
the Firewall Protection Settings - Firewall General Rules, on the Tracking tab,
the Help refers to the ability to create an Event Log. Norton 360 does not
include an Event Log.
Norton 360 does not fully support
Dynamic Volumes. Scanning these drives may result in the error message,
"Unable to read boot record on drive." This error occurs because
these drives are not bootable. However, Norton 360 will scan the drive for
infected files.
Using Norton 360 with directory symbolic links/NTFS
junctions
Using directory symbolic links, also
known as NTFS junctions, on Windows XP machines may increase hard drive
scanning times due to repeated scanning.
NORTON 360 BACKUP - SUPPORTED MEDIA & COMPATIBILITY
Norton
360 Backup - CD and DVD capacities and definition of MB and GB sizes
Norton 360 Backup estimates the
number of CDs or DVDs required for backups using the following commonly
available capacities:
* CD: 700 MB (80-minute)
650 MB (74-minute)
* DVD: 4.37 GB (single layer, +/-R)
7.96 GB (dual-layer, +/-R)
Backup calculations are based on a 700MB CD and 4.37GB DVD. When you insert a
disc that has a different capacity, Norton 360 Backup will recalculate the
estimated number of discs required.
For local and online backup storage,
Symantec uses the following definitions of megabytes and gigabytes:
*1 MB = 1,048,576 (2^20) bytes
*1 GB = 2^30
Norton 360 Backup - Supported file types
Special
characters in filenames
In order to preserve the integrity
of backup files Norton 360 Backup does not back up files with certain
characters in their names. This includes:
--Files with names that start with '~' are generally considered to be temporary
files.
Jpeg
digital photograph files selected for backup
Norton 360 will backup all Jpeg files from common
locations across all users on the system, such as Desktop, My Documents, My
Pictures.
In any other location, Norton 360 uses a filtering
criteria to decide if a jpeg file came from a camera or not. The filter checks for
the presence of an information header, EXIF header, in the file. Most
digital cameras save EXIF headers. When an image is edited, sometimes the
EXIF header may be removed by the editing software. If you use the standard
Windows recommended locations for your pictures, you can be sure all of your
pictures, regardless of source or edits, are backed up.
If you store pictures that you wish to back up, from
sources other than a digital camera, in locations other than Desktop, My Documents
or My Pictures, you may need to configure backup to add that folder to your
backup set.
Backups
and file encryption
Encrypted files will not be backed
up,
Sonic
DLA Drives
Sonic DLA drives are not supported
by Norton 360 Backup
To prevent backup errors caused by Norton 360 unsuccessfully attempting to
access Sonic DLA drives, it is recommended that these drives be disabled.
To disable Sonic DLA drives:
On the CD image Properties dialog, on the DLA tab, uncheck the "Enable DLA
on your drives" checkbox.
Gear
Software
For a list of hardware storage
devices and media types supported by Norton 360 Backup, please look up your
device on the following Web site:
http://www.gearsoftware.com/support/recorders/index.cfm
If you encounter a problem connecting to the Symantec
Support web site, an external firewall problem may be blocking your Internet
access to Symantec's Remote Assist. To access Remote Assist, Port 653 must be
open. Please consult your external firewall manual for information on how to
ensure that this port is open.
--------------------------------------------------------
Other Third Party Acknowledgements
Appspeed Software
Portions of this product were developed using SkinMagic
Toolkit from Appspeed Software.
Terra Informatica
Portions of this product contain code licensed from Terra
Informatica Software Inc., which software is based in part on the work of the
Independent JPEG Group.
--------------------------------------------------------
ICU License - ICU 1.8.1 and later
Portions of this software
redistributed with permission.
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2003
International Business Machines Corporation and others All rights reserved.
Permission is hereby granted, free
of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of the
Software and that both the above copyright notice(s) and this permission notice
appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS
IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING
FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice,
the name of a copyright holder shall not be used in advertising or otherwise to
promote the sale, use or other dealings in this Software without prior written
authorization of the copyright holder.
--------------------------------------------------------
CXIMAGE README
This copy of the CxImage notices is
provided for your convenience. In case of any discrepancy between this copy and
the notices in the file ximage.h that is included in the CxImage distribution,
the latter shall prevail.
If you modify CxImage you may insert
additional notices immediately following this sentence.
COPYRIGHT NOTICE, DISCLAIMER, and
LICENSE:
CxImage version 5.99c 17/Oct/2004
CxImage : Copyright (C) 2001 - 2004,
Davide Pizzolato
Original CImage and CImageIterator
implementation are: Copyright (C) 1995, Alejandro Aguilar Sierra
asierra(at)servidor(dot)unam(dot)mx)
Covered code is provided under this
license on an "as is" basis, without warranty of any kind, either
expressed or implied, including, without limitation, warranties that the
covered code is free of defects, merchantable, fit for a particular purpose or
non-infringing. The entire risk as to the quality and performance of the
covered code is with you. Should any covered code prove defective in any
respect, you (not the initial developer or any other contributor) assume the
cost of any necessary servicing, repair or correction. This disclaimer of
warranty constitutes an essential part of this license. No use of any covered
code is authorized hereunder except under this disclaimer.
Permission is hereby granted to use,
copy, modify, and distribute this source code, or portions hereof, for any
purpose, including commercial applications, freely and without fee, subject to
the following restrictions:
1. The origin of this software must
not be misrepresented; you must not claim that you wrote the original software.
If you use this software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
2. Altered source versions must be
plainly marked as such, and must not be misrepresented as being the original
software.
3. This notice may not be removed or
altered from any source distribution.
Other information: about CxImage,
and the latest version, can be found at the CxImage home page:
http://www.xdp.it
--------------------------------------------------------
JPEG README
The Independent JPEG Group's JPEG
software
==========================================
README for release 6b of 27-Mar-1998
====================================
This distribution contains the sixth
public release of the Independent JPEG Group's free JPEG software. You are
welcome to redistribute this software and to use it for any purpose, subject to
the conditions under LEGAL ISSUES, below.
Serious users of this software
(particularly those incorporating it into larger programs) should contact IJG
at jpeg-info@uunet.uu.net to be added to our electronic mailing list. Mailing
list members are notified of updates and have a chance to participate in
technical discussions, etc.
This software is the work of Tom
Lane, Philip Gladstone, Jim Boucher, Lee Crocker, Julian Minguillon, Luis
Ortiz, George Phillips, Davide Rossi, Guido Vollbeding, Ge' Weijers, and other
members of the Independent JPEG Group.
IJG is not affiliated with the
official ISO JPEG standards committee.
DOCUMENTATION
ROADMAP
This file contains the following
sections:
|
· OVERVIEW |
General description of JPEG and
the IJG software. |
|
· LEGAL ISSUES |
Copyright, lack of warranty, terms
of distribution. |
|
· REFERENCES |
Where to learn more about JPEG. |
|
· ARCHIVE LOCATIONS |
Where to find newer versions of
this software. |
|
· RELATED SOFTWARE |
Other stuff you should get. |
|
· FILE FORMAT WARS |
Software *not* to get. |
|
· TO DO |
Plans for future IJG releases. |
|
|
|
Other documentation files in the
distribution are:
User documentation:
install.doc How to configure and install the IJG software.
usage.doc Usage instructions for cjpeg, djpeg, jpegtran, rdjpgcom, and
wrjpgcom.
*.1 Unix-style man pages for programs (same info as usage.doc).
wizard.doc Advanced usage instructions for JPEG wizards only.
change.log Version-to-version change highlights.
Programmer and internal
documentation:
libjpeg.doc How to use the JPEG library in your own programs.
example.c Sample code for calling the JPEG library.
structure.doc Overview of the JPEG library's internal structure.
filelist.doc Road map of IJG files.
coderules.doc Coding style rules --- please read if you contribute code.
Please read at least the files
install.doc and usage.doc.
Useful information can also be found in the JPEG FAQ (Frequently Asked
Questions) article. See ARCHIVE LOCATIONS below to find out where to obtain the
FAQ article.
If you want to understand how the
JPEG code works, we suggest reading one or more of the REFERENCES, then looking
at the documentation files (in roughly the order listed) before diving into the
code.
This package contains C software to
implement JPEG image compression and decompression. JPEG (pronounced
"jay-peg") is a standardized compression method for full-color and
gray-scale images. JPEG is intended for compressing "real-world"
scenes; line drawings, cartoons and other non-realistic images are not its
strong suit. JPEG is lossy, meaning that the output image is not exactly
identical to the input image. Hence you must not use JPEG if you have to have
identical output bits. However, on typical photographic images, very good
compression levels can be obtained with no visible change, and remarkably high
compression levels are possible if you can tolerate a low-quality image. For
more details, see the references, or just experiment with various compression
settings.
This software implements JPEG
baseline, extended-sequential, and progressive compression processes. Provision
is made for supporting all variants of these processes, although some uncommon
parameter settings aren't implemented yet. For legal reasons, we are not
distributing code for the arithmetic-coding variants of JPEG; see LEGAL ISSUES.
We have made no provision for supporting the hierarchical or lossless processes
defined in the standard.
We provide a set of library routines
for reading and writing JPEG image files, plus two sample applications
"cjpeg" and "djpeg", which use the library to perform
conversion between JPEG and some other popular image file formats. The library
is intended to be reused in other applications.
In order to support file conversion
and viewing software, we have included considerable functionality beyond the
bare JPEG coding/decoding capability; for example, the color quantization
modules are not strictly part of JPEG decoding, but they are essential for
output to colormapped file formats or colormapped displays. These extra
functions can be compiled out of the library if not required for a particular
application. We have also included "jpegtran", a utility for lossless
transcoding between different JPEG processes, and "rdjpgcom" and
"wrjpgcom", two simple applications for inserting and extracting
textual comments in JFIF files.
The emphasis in designing this
software has been on achieving portability and flexibility, while also making
it fast enough to be useful. In particular, the software is not intended to be
read as a tutorial on JPEG. (See the REFERENCES section for introductory
material.) Rather, it is intended to be reliable, portable, industrial-strength
code. We do not claim to have achieved that goal in every aspect of the
software, but we strive for it.
We welcome the use of this software
as a component of commercial products. No royalty is required, but we do ask
for an acknowledgement in product documentation, as described under LEGAL
ISSUES.
In plain English:
1. We don't promise that this
software works. (But if you find any bugs, please let us know!)
2. You can use this software for whatever you want. You don't have to pay us.
3. You may not pretend that you wrote this software. If you use it in a
program, you must acknowledge somewhere in your documentation that you've used
the IJG code.
In legalese:
The authors make NO WARRANTY or
representation, either express or implied, with respect to this software, its
quality, accuracy, merchantability, or fitness for a particular purpose. This
software is provided "AS IS", and you, its user, assume the entire
risk as to its quality and accuracy.
This software is copyright (C)
1991-1998,
Permission is hereby granted to use,
copy, modify, and distribute this software (or portions thereof) for any
purpose, without fee, subject to these conditions:
(1) If any part of the source code for this software is distributed, then this
README file must be included, with this copyright and no-warranty notice
unaltered; and any additions, deletions, or changes to the original files must
be clearly indicated in accompanying documentation.
(2) If only executable code is distributed, then the accompanying documentation
must state that "this software is based in part on the work of the
Independent JPEG Group".
(3) Permission for use of this software is granted only if the user accepts
full responsibility for any undesirable consequences; the authors accept NO
LIABILITY for damages of any kind.
These conditions apply to any
software derived from or based on the IJG code, not just to the unmodified
library. If you use our work, you ought to acknowledge us.
Permission is NOT granted for the
use of any IJG author's name or company name in advertising or publicity
relating to this software or products derived from it. This software may be
referred to only as "the Independent JPEG Group's software".
We specifically permit and encourage
the use of this software as the basis of commercial products, provided that all
warranty or liability claims are assumed by the product vendor.
ansi2knr.c is included in this
distribution by permission of L. Peter Deutsch, sole proprietor of its
copyright holder, Aladdin Enterprises of Menlo Park, CA. ansi2knr.c is NOT
covered by the above copyright and conditions, but instead by the usual
distribution terms of the Free Software Foundation; principally, that you must
include source code if you redistribute it. (See the file ansi2knr.c for full
details.) However, since ansi2knr.c is not needed as part of any program
generated from the IJG code, this does not limit you more than the foregoing
paragraphs do.
The Unix configuration script
"configure" was produced with GNU Autoconf. It is copyright by the
Free Software Foundation but is freely distributable. The same holds for its
supporting scripts (config.guess, config.sub, ltconfig, ltmain.sh). Another
support script, install-sh, is copyright by M.I.T. but is also freely
distributable.
It appears that the arithmetic
coding option of the JPEG spec is covered by patents owned by IBM, AT&T,
and Mitsubishi. Hence arithmetic coding cannot legally be used without
obtaining one or more licenses. For this reason, support for arithmetic coding
has been removed from the free JPEG software. (Since arithmetic coding provides
only a marginal gain over the unpatented Huffman mode, it is unlikely that very
many implementations will support it.) So far as we are aware, there are no
patent restrictions on the remaining code.
The IJG distribution formerly
included code to read and write GIF files. To avoid entanglement with the
Unisys LZW patent, GIF reading support has been removed altogether, and the GIF
writer has been simplified to produce "uncompressed GIFs". This
technique does not use the LZW algorithm; the resulting GIF files are larger
than usual, but are readable by all standard GIF decoders.
We are required to state that
"The Graphics Interchange Format(c) is the Copyright property of
CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe
Incorporated."
We highly recommend reading one or
more of these references before trying to understand the innards of the JPEG
software.
The best short technical
introduction to the JPEG compression algorithm is Wallace, Gregory K. "The
JPEG Still Picture Compression Standard", Communications of the ACM, April
1991 (vol. 34 no. 4), pp. 30-44. (Adjacent articles in that issue discuss MPEG
motion picture compression, applications of JPEG, and related topics.) If you
don't have the CACM issue handy, a PostScript file containing a revised version
of Wallace's article is available at ftp://ftp.uu.net/graphics/jpeg/wallace.ps.gz.
The file (actually a preprint for an article that appeared in IEEE Trans.
Consumer Electronics) omits the sample images that appeared in CACM, but it
includes corrections and some added material. Note: the Wallace article is copyright
ACM and IEEE, and it may not be used for commercial purposes.
A somewhat less technical, more
leisurely introduction to JPEG can be found in "The Data Compression
Book" by Mark Nelson and Jean-loup Gailly, published by M&T Books (
The best full description of JPEG is
the textbook "JPEG Still Image Data Compression Standard" by William
B. Pennebaker and Joan L. Mitchell, published by Van Nostrand Reinhold, 1993,
ISBN 0-442-01272-1. Price US$59.95, 638 pp. The book includes the complete text
of the ISO JPEG standards (DIS 10918-1 and draft DIS 10918-2). This is by far
the most complete exposition of JPEG in existence, and we highly recommend it.
The JPEG standard itself is not
available electronically; you must order a paper copy through ISO or ITU.
(Unless you feel a need to own a certified official copy, we recommend buying
the Pennebaker and Mitchell book instead; it's much cheaper and includes a
great deal of useful explanatory material.) In the
Some extensions to the original JPEG
standard are defined in JPEG Part 3, a newer ISO standard numbered ISO/IEC IS
10918-3 and ITU-T T.84. IJG currently does not support any Part 3 extensions.
The JPEG standard does not specify
all details of an interchangeable file format. For the omitted details we
follow the "JFIF" conventions, revision 1.02. A copy of the JFIF spec
is available from:
Literature Department
C-Cube Microsystems, Inc.
phone (408) 944-6300, fax (408) 944-6314
A PostScript version of this document is available by FTP at
ftp://ftp.uu.net/graphics/jpeg/jfif.ps.gz. There is also a plain text version
at ftp://ftp.uu.net/graphics/jpeg/jfif.txt.gz, but it is missing the figures.
The TIFF 6.0 file format
specification can be obtained by FTP from
ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme
found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems. IJG
does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
(Compression tag 7). Copies of this Note can be obtained from ftp.sgi.com or
from ftp://ftp.uu.net/graphics/jpeg/. It is expected that the next revision of
the TIFF spec will replace the 6.0 JPEG design with the Note's design. Although
IJG's own code does not support TIFF/JPEG, the free libtiff library uses our library
to implement TIFF/JPEG per the Note. libtiff is available from
ftp://ftp.sgi.com/graphics/tiff/.
The "official" archive
site for this software is ftp.uu.net (Internet address 192.48.96.9). The most
recent released version can always be found there in directory graphics/jpeg.
This particular version will be archived as
ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz. If you don't have direct
Internet access, UUNET's archives are also available via UUCP; contact
help@uunet.uu.net for information on retrieving files that way.
Numerous Internet sites maintain
copies of the UUNET files. However, only ftp.uu.net is guaranteed to have the
latest official version.
You can also obtain this software in
DOS-compatible "zip" archive format from the SimTel archives
(ftp://ftp.simtel.net/pub/simtelnet/msdos/graphics/), or on CompuServe in the
Graphics Support forum (GO CIS:GRAPHSUP), library 12 "JPEG Tools".
Again, these versions may sometimes lag behind the ftp.uu.net release.
The JPEG FAQ (Frequently Asked
Questions) article is a useful source of general information about JPEG. It is
updated constantly and therefore is not included in this distribution. The FAQ
is posted every two weeks to Usenet newsgroups comp.graphics.misc,
news.answers, and other groups. It is available on the World Wide Web at
http://www.faqs.org/faqs/jpeg-faq/ and other news.answers archive sites,
including the official news.answers archive at rtfm.mit.edu:
ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/. If you don't have Web or
FTP access, send e-mail to mail-server@rtfm.mit.edu with body send
usenet/news.answers/jpeg-faq/part1 send usenet/news.answers/jpeg-faq/part2
Numerous viewing and image
manipulation programs now support JPEG. (Quite a few of them use this library
to do so.) The JPEG FAQ described above lists some of the more popular free and
shareware viewers, and tells where to obtain them on Internet.
If you are on a Unix machine, we
highly recommend Jef Poskanzer's free PBMPLUS software, which provides many
useful operations on PPM-format image files. In particular, it can convert PPM
images to and from a wide range of other formats, thus making cjpeg/djpeg
considerably more useful. The latest version is distributed by the NetPBM
group, and is available from numerous sites, notably
ftp://wuarchive.wustl.edu/graphics/graphics/packages/NetPBM/. Unfortunately
PBMPLUS/NETPBM is not nearly as portable as the IJG software is; you are likely
to have difficulty making it work on any non-Unix machine.
A different free JPEG
implementation, written by the PVRG group at Stanford, is available from
ftp://havefun.stanford.edu/pub/jpeg/. This program is designed for research and
experimentation rather than production use; it is slower, harder to use, and
less portable than the IJG code, but it is easier to read and modify. Also, the
PVRG code supports lossless JPEG, which we do not. (On the other hand, it
doesn't do progressive JPEG.)
Some JPEG programs produce files
that are not compatible with our library. The root of the problem is that the
ISO JPEG committee failed to specify a concrete file format. Some vendors
"filled in the blanks" on their own, creating proprietary formats
that no one else could read. (For example, none of the early commercial JPEG
implementations for the Macintosh were able to exchange compressed files.)
The file format we have adopted is
called JFIF (see REFERENCES). This format has been agreed to by a number of
major commercial JPEG vendors, and it has become the de facto standard. JFIF is
a minimal or "low end" representation. We recommend the use of
TIFF/JPEG (TIFF revision 6.0 as modified by TIFF Technical Note #2) for
"high end" applications that need to record a lot of additional data
about an image. TIFF/JPEG is fairly new and not yet widely supported,
unfortunately.
The upcoming JPEG Part 3 standard
defines a file format called SPIFF. SPIFF is interoperable with JFIF, in the
sense that most JFIF decoders should be able to read the most common variant of
SPIFF. SPIFF has some technical advantages over JFIF, but its major claim to
fame is simply that it is an official standard rather than an informal one. At
this point it is unclear whether SPIFF will supersede JFIF or whether JFIF will
remain the de-facto standard. IJG intends to support SPIFF once the standard is
frozen, but we have not decided whether it should become our default output
format or not. (In any case, our decoder will remain capable of reading JFIF
indefinitely.)
Various proprietary file formats
incorporating JPEG compression also exist. We have little or no sympathy for
the existence of these formats. Indeed, one of the original reasons for
developing this free software was to help force convergence on common, open
format standards for JPEG files. Don't use a proprietary file format!
The major thrust for v7 will
probably be improvement of visual quality. The current method for scaling the
quantization tables is known not to be very good at low Q values. We also
intend to investigate block boundary smoothing, "poor man's variable
quantization", and other means of improving quality-vs-file-size
performance without sacrificing compatibility.
In future versions, we are
considering supporting some of the upcoming JPEG Part 3 extensions ---
principally, variable quantization and the SPIFF file format.
As always, speeding things up is of
great interest.
Please send bug reports, offers of
help, etc. to jpeg-info@uunet.uu.net.
--------------------------------------------------------
PNG README
This copy of the libpng notices is
provided for your convenience. In case of any discrepancy between this copy and
the notices in the file png.h that is included in the libpng distribution, the
latter shall prevail.
COPYRIGHT NOTICE, DISCLAIMER, and
LICENSE:
If you modify libpng you may insert
additional notices immediately following this sentence.
libpng version 1.2.6, December 3,
2004, is Copyright (c) 2004 Glenn Randers-Pehrson, and is distributed according
to the same disclaimer and license as libpng-1.2.5 with the following
individual added to the list of Contributing Authors
Cosmin Truta
libpng versions 1.0.7, July 1, 2000,
through 1.2.5 - October 3, 2002, are Copyright (c) 2000-2002 Glenn
Randers-Pehrson, and are distributed according to the same disclaimer and
license as libpng-1.0.6 with the following individuals added to the list of
Contributing Authors
Simon-Pierre Cadieux
Eric S. Raymond
Gilles Vollant
and with the following additions to
the disclaimer:
There is no warranty against
interference with your enjoyment of the library or against infringement. There
is no warranty that our efforts or the library will fulfill any of your
particular purposes or needs. This library is provided with all faults, and the
entire risk of satisfactory quality, performance, accuracy, and effort is with
the user.
libpng versions 0.97, January 1998,
through 1.0.6, March 20, 2000, are Copyright (c) 1998, 1999 Glenn
Randers-Pehrson, and are distributed according to the same disclaimer and
license as libpng-0.96, with the following individuals added to the list of
Contributing Authors:
Tom Lane
Glenn Randers-Pehrson
Willem van Schaik
libpng versions 0.89, June 1996,
through 0.96, May 1997, are Copyright (c) 1996, 1997 Andreas Dilger
Distributed according to the same disclaimer and license as libpng-0.88, with
the following individuals added to the list of Contributing Authors:
John Bowler
Kevin Bracey
Sam Bushell
Magnus Holmgren
Greg Roelofs
Tom Tanner
libpng versions 0.5, May 1995,
through 0.88, January 1996, are Copyright (c) 1995, 1996 Guy Eric Schalnat,
Group 42, Inc.
For the purposes of this copyright
and license, "Contributing Authors" is defined as the following set
of individuals:
Andreas Dilger
Dave Martindale
Guy Eric Schalnat
Paul Schmidt
Tim Wegner
The PNG Reference Library is
supplied "AS IS". The Contributing Authors and Group 42, Inc.
disclaim all warranties, expressed or implied, including, without limitation,
the warranties of merchantability and of fitness for any purpose. The
Contributing Authors and Group 42, Inc. assume no liability for direct,
indirect, incidental, special, exemplary, or consequential damages, which may
result from the use of the PNG Reference Library, even if advised of the
possibility of such damage.
Permission is hereby granted to use,
copy, modify, and distribute this source code, or portions hereof, for any
purpose, without fee, subject to the following restrictions:
1. The origin of this source code
must not be misrepresented.
2. Altered versions must be plainly
marked as such and must not be misrepresented as being the original source.
3. This Copyright notice may not be
removed or altered from any source or altered source distribution.
The Contributing Authors and Group
42, Inc. specifically permit, without fee, and encourage the use of this source
code as a component to supporting the PNG file format in commercial products.
If you use this source code in a product, acknowledgment is not required but
would be appreciated.
A "png_get_copyright"
function is available, for convenient use in "about" boxes and the
like:
printf("%s",png_get_copyright(NULL));
Also, the PNG logo (in PNG format,
of course) is supplied in the files "pngbar.png" and "pngbar.jpg
(88x31) and "pngnow.png" (98x31).
Libpng is OSI Certified Open Source
Software. OSI Certified Open Source is a certification mark of the Open Source
Initiative.
Glenn Randers-Pehrson
glennrp at users.sourceforge.net
December 3, 2004
-------------------------------------------------------
OpenSSL
Project
This product
includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit
(http://www.openssl.org/)