END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest possible
use to the public, we recommend making it free software that everyone
can redistribute and change. You can do so by permitting redistribution
under these terms (or, alternatively, under the terms of the ordinary General
Public License).
To apply these terms, attach the following notices to the library. It is safest
to attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
“copyright” line and a pointer to where the full notice is found. one line to
give the library’s name and an idea of what it does.
Copyright (C) year name of author
This library is free software; you can redistribute it and/or modify it under
the terms of the GNU Lesser General Public License as published by the
Free Software Foundation; either version 2.1 of the License, or (at your
option) any later version.
This library 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 Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301
USA Also add information on how to contact you by electronic and paper
mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a “copyright disclaimer” for the library, if necessary.
Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the library ‘Frob’
(a library for tweaking knobs) written by James Random Hacker.
signature of Ty Coon, 1 April 1990 Ty Coon, President of Vice.
OpenSSL LICENSE
Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgment: “This product includes software
developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://
www.openssl.org/)”
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be
used to endorse or promote products derived from this software without
prior written permission. For written permission, please contact openssl-
[email protected].
5. Products derived from this software may not be called “OpenSSL” nor
may “OpenSSL” appear in their names without prior written permission of
the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following
acknowledgment: “This product includes software developed by the
OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.
org/)”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ‘‘AS IS’’
AND ANY EXPRESSED 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
OpenSSL PROJECT OR ITS 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.This product includes cryptographic software written by Eric
Young ([email protected]). This product includes software written by Tim
Hudson ([email protected]).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young ([email protected]) All rights
reserved. This package is an SSL implementation written by Eric Young
([email protected]). The implementation was written so as to conform
with Netscapes SSL. This library is free for commercial and non-
commercial use as long as the following conditions are aheared to. The
following conditions apply to all code found in this distribution, be it the
RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL
documentation included with this distribution is covered by the same
copyright terms except that the holder is Tim Hudson ([email protected]).
Copyright remains Eric Young’s, and as such any Copyright notices in the
code are not to be removed.
If this package is used in a product, Eric Young should be given attribution
as the author of the parts of the library used. This can be in the form of a
textual message at program startup or in documentation (online or textual)
provided with the package.Redistribution and use in source and binary
forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list
of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgement: “This product includes
cryptographic software written by Eric Young ([email protected])” The
word ‘cryptographic’ can be left out if the rouines from the library being
used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from
the apps directory (application code) you must include an
acknowledgement: “This product includes software written by Tim Hudson
([email protected])”
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ‘‘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 AUTHOR 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 licence and
distribution terms for any publically available version or derivative of this
code cannot be changed. i.e. this code cannot simply be copied and put
under another distribution licence [including the GNU Public Licence.
Summary of Contents for ZN-D2MAP
Page 1: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...
Page 11: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...
Page 31: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00 10 3 Mapping...
Page 46: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...
Page 47: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...
Page 48: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...
Page 49: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...
Page 50: ...Pixel Pro Benutzerhandbuch ZN D2MAP ZN D1MAP ZN D1A Ver1 00...