NI-488.2Driver17.0.0f0 Linux 美国国家仪器IEEE488.2仪器驱动17.0.0f0 Linux系统版下载
Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html
NI-488.2Driver17.0.0f0 Linux 美国国家仪器IEEE488.2仪器驱动17.0.0f0 Linux系统版下载
NI-488.2为使用NI GPIB控制器和带有GPIB端口的NI嵌入式控制器的客户提供支持。
NI-488.2仪器驱动程序包含了几个实用程序，用于应用程序开发和调试。NI-488.2包含了可自动处理所有总线管理的高级命令，因而用户就无需了解GPIB硬件产品或IEEE 488.2协议的编程细节。为了提供最大灵活性和功能，NI-488.2还包含了底层命令。
百度网盘下载：
链接：请注册视觉论坛会员登录后购买附件下载查看
提取码：请购买附件下载查看
NI官方下载地址（可能无效或无法下载完成）：
请购买附件下载查看链接
NI-488.2 for Linux readme
Version 17.0.0
May 2017
This file contains important information about the NI-488.2 software
for Linux, including installation issues, compatibility issues, API
changes from previous drivers, and a list of FAQs. Refer to the
Installation Guide in the Documentation directory on your NI-488.2 for Linux
media for information about installing the software.
-----------------------------------------------------------------------------
This file supersedes any discrepant information presented in other NI-488.2
documentation. Refer to www.ni.com/linux for the most recent information
about Linux support at National Instruments.
-----------------------------------------------------------------------------
System Requirements
Supported GPIB Interfaces
Installation
Description of Utilities
C/C++ Language Interface
Compatibility with LabVIEW
Compatibility with Previous NI-488.2 Drivers
Uninstallation
FAQs
Documentation and Help
Bug Fixes and Enhancements
Linux Limitations
Legal Information
-------------------
System Requirements
-------------------
This release of NI-488.2 for Linux software supports the following
x64 distributions:
CentOS 7
openSUSE LEAP 42.2
openSUSE LEAP 42.1
Red Hat Enterprise Linux 6
Red Hat Enterprise Linux 7
Scientific Linux 6
An X Windows graphical environment is required to run graphical configuration
and troubleshooting utilities.
For more information about supported Linux versions and distributions supported
by NI, refer to ni.com/linux.
-------------------------
Supported GPIB Interfaces
-------------------------
PCI-GPIB
PCI-GPIB/LP
NI PCIe-GPIB
PCI-8212*
PCI-8232
PXI-GPIB
PXI-8212*
PXI-8232
GPIB-ENET/100*
GPIB-ENET/1000
To configure a supported GPIB interface, refer to the Installation Guide
located in /usr/local/natinst/ni4882/docs/.
* This hardware is end-of-life and not recommended for new designs.
------------
Installation
------------
To install NI-488.2 software for Linux, log in as root, and run the INSTALL
script from the mounted drive or tarball directory, as follows:
./INSTALL
The INSTALL script ensures that all requirements are met, checks and
uninstalls existing installations if necessary, and then installs the NI-488.2
software.
The script uses rpm to install the packages on systems that support it or
extracts the files directly on other systems.
------------------------
Description of Utilities
------------------------
gpibexplorer - GPIB Explorer is used to browse, add, and delete GPIB
interfaces.
gpibtsw - GPIB Troubleshooting Wizard is used to verify your
hardware and software installation.
gpibintctrl - GPIB Interactive Control is used to communicate with
GPIB devices interactively.
firmwareupdate- GPIB Firmware Update is used to upgrade firmware
on a GPIB-ENET/100 interface.
Refer to the NI-488.2 User Manual for more information about using these
utilities.
------------------------
C/C++ Language Interface
------------------------
ni4882.h - NI-488.2 header file
libni4882.so - Dynamic library
ni4882.o - Object file that allows explicit loading of libni4882.so
NI4882 API Examples:
To have the ni4882 library loaded implicitly on program startup:
gcc prog.c -lni4882
g++ prog.cpp -lni4882
To have the ni4882 library loaded explicitly when the program makes the
first call into the library:
gcc prog.c ni4882.o -ldl
g++ prog.cpp ni4882.o -ldl
For more NI-488.2 API use examples, refer to
/usr/local/natinst/ni4882/examples/Readme.txt.
The legacy GPIB API, libgpibapi.so, is still available for compatibility with
existing applications. It provides only 32-bit support, and is not recommended
for new development.
--------------------------
Compatibility with LabVIEW
--------------------------
This driver version was tested with LabVIEW 2015, LabVIEW 2016,
and LabVIEW 2017.
--------------------------------------------
Compatibility with Previous NI-488.2 Drivers
--------------------------------------------
This installation of NI-488.2 software may have issues installing over
some previous versions of the NI-488.2 drivers.You should manually uninstall
previous NI-488.2 drivers before installing this software.
--------------
Uninstallation
--------------
To uninstall the NI-488.2 software for Linux, log in as root and run the
UNINSTALL script from the mounted drive or tarball directory, as follows:
./UNINSTALL
----
FAQs
----
Q1: What action do I need to take if I upgrade/change my kernel?
A1: Some action is required to make the existing NI-488.2 installation
work for the new kernel. After upgrading your kernel, run
updateNIDrivers utility as root. The utility is located in
/usr/local/bin. Be sure to have sources for your new kernel properly
installed on your system before running the utility. The utility
rebuilds the driver using the new kernel sources and copies it into
the appropriate location for the new kernel. For the changes to take
place, you will be asked to reboot your machine after the utility
completes.Note that NI-488.2 supports only kernels provided as part
of the supported distributions listed above.
Q2: When I try to open Help from GPIB Explorer, I am prompted for my default
web browser. What does this do?
A2: This problem only occurs on systems where htmlview is not installed.
Each user's response to this dialog box is stored in "~/natinst/.lvbrowser"
(where ~ is the user's home directory). If you need to change this
response, you can edit this file or simply delete it so that you will
be prompted again when entering help.
Q3: When I launch GPIB Explorer from a prompt opened using 'su', I am unable to
launch Interactive Control from the GPIB Explorer menu.
A3: When elevating to root privileges, use 'su -' instead of 'su'. This will
properly configure the environment for the root user, and will resolve the
issue launching Interactive Control.
Q4: When launching 'gpibexplorer' or 'gpibtsw' using 'sudo', I see an error
similar to "Unable to open X display."
A4: This can be resolved by granting access to the root user to utilize the
current display, and passing the display information to the 'sudo'
command, as shown below:
xhost local:root
sudo DISPLAY=$DISPLAY gpibexplorer
Q5: Why can't I discover a GPIB-ENET/100 or GPIB-ENET/1000 device in GPIB
Explorer?
A5: It is likely that your firewall is blocking the discovery of the
device. You can get around this by disabling the firewall during
discovery. This can be reverted after you have added the device.
Q6: During installation, I get a message similar to the following one:
"Kernel source does not appear to be configured for the running kernel.
Configuration of kernel source is required to continue installation."
I do have kernel sources installed. Is there anything else I need to do?
A6: This problem is known to affect SUSE Linux, but it is possible that other
distributions require similar steps to resolve this problem.
On openSUSE, complete the following steps:
1. Ensure you have installed kernel-source and kernel-syms packages
corresponding to the version of the currently running kernel. You
can determine the currently running kernel version by issuing the
command "uname -r".
2. Change the directory to the /usr/src/linux-<version> directory,
where <version> corresponds to the currently running kernel version.
3. Run "zcat /boot/symvers-<version>.gz > Module.symvers" as root to
prepare modversion support.
4. Run "make cloneconfig" as root to configure the sources for the
currently running kernel.
5. Run "make modules_prepare" as root to prepare the headers for
compilation.
6. Run the NI-488.2 for Linux INSTALL script.
Q7: When launching GPIB Explorer or GPIB Troubleshooting Wizard on 64 bit
Linux, I get an error message about missing "libXinerama.so.1" or other
libraries.
A7: The runtime engine for the applications depends on 32 bit version of
libXinerama and several other libraries. These are not installed by
default on some 64 bit Linux distributions. To solve this error, the 32
bit version of the reported libraries should be installed.
Q8: When launching GPIB Explorer on 32 bit Linux with 4GB of memory or more, I
get an error message about "libnipalu.so failed to initialize. Perhaps you
need to run updateNIDrivers. Aborted".
A8: The NI-488.2 core driver is not able to run on a 32-bit system with more
than 4GB of addressable memory. The work around for this problem is to
limit the usable memory in the system to 4GB of addressable space.
To limit the system memory, complete the following steps:
1. In the grub boot menu, select the Linux version and press 'e' to edit
the commands.
2. Append "mem=4GB", with space before the option, to the Linux kernel
executable (vmlinuz) line.
3. Boot the Linux OS.
Q9: When installing NI-488.2 2.9.1 or later with NI-VISA pre-installed, I
receive the error message: "ERROR: failed to build nipxirmk.ko. nipxirmk.ko
failed to update."
A9: NI-VISA prior to version 5.2.0 has a compatibility issue with one of the
core components of NI-488.2 2.9.1 or later. To avoid this error, please
upgrade NI-VISA to 5.2.0 or above before installing NI-488.2.
Q10: Launching ethernetconfig or gpibintctrl through GPIB Explorer causes the
text utilities to launch twice in different terminals.
A10: This problem is due to a bug (#646317 bugzilla) in gnome-terminal
(2.32.1-6.1). This causes GPIB Explorer to believe that gnome-terminal
has failed to launch, so it re-launches the utility in another terminal.
You can simply close the duplicated window or update gnome-terminal to
version 3.2.1 or above.
Q11: Why can't I discover GPIB-ENET/1000 devices connected through a Link-Local
address in GPIB Explorer?
A11: This problem occurs if the network connection on the system has been
configured for DHCP but there is no available DHCP server on the network.
To fix this issue, complete the following steps:
1. Install avahi-autoipd.
2. Configure the current network connection to allow Link-Local
addresses. This can be achieved through the network connection
configuration utility on the system. Either create a new connection
or edit the currently active connection. Under IPv4 settings set
the connection method to Link-Local only.
Q12: Why is NI I/O Trace not working with NI-488.2 17.0 or later?
A12: NI I/O Trace 17.0 and later support NI-488.2 17.0. Previous versions of
NI I/O Trace do not support NI-488.2 17.0 or later.
----------------------
Documentation and Help
----------------------
You can access NI-488.2 Help from GPIB Explorer.
-----------------
Linux Limitations
-----------------
Some features discussed in the NI-488.2 documentation and help (for example,
GPIB Analyzer, GPIB Ethernet Wizard) are unavailable on Linux.
Power Management
NI-488.2 software for Linux does not support power management.
You must disable the power management settings or make sure all GPIB handles
are offline before the system enters the power management modes.
fork() System Call
NI-488.2 software for Linux does not work with the fork() system call.
Specifically, the interface and device handles opened by the parent process
are not properly inherited by the child process. Any attempt to use already
opened handles in the child process will result in a Segmentation Fault for
the child process.A workaround is either to open a new interface/device
handle in the child process or use threads instead of processes to implement
multitasking. Linux provides a POSIX-compliant thread library called pthreads.
---------------------------
Bug Fixes and Enhancements
---------------------------
The following items are a subset of issues fixed in this and previous NI-488.2
releases. If you have a CAR ID, you can search this list to validate the issue
has been fixed.
----
NI-488.2 17.0
----
Adds support for LabVIEW 2016 and 2017.
----
NI-488.2 FOR LINUX 15.1
----
Updated Linux distribution support.
NI-488.2 now reports GPIB controller interfaces through the NI System
Configuration API.
The following specific issues were fixed in this release:
121091: Calling ibonl when a board level ibwait is in progress could result
in application crash.
121181: A deadlock might occur when attempting to use a board handle with
pending ibonl call on another thread.
----
NI-488.2 FOR LINUX 3.2
----
Updated Linux distribution support.
Modified the integer types used in ni4882.h and libni4882.so. All uses of
'unsigned long' have been replaced with 'unsigned int' to improve compatibility
with 64-bit compilers. This API has never been documented with prior versions
of NI-488.2 for Linux, but ni4882.h and a 32-bit version of libni4882.so were
installed on the system. Any user utilizing these files should update their
applications according to the updated function prototypes in ni4882.h. This
change does not impact ni488.h or libgpibapi.so.
Added 64-bit Application Interface. NI-488.2 for Linux, Version 3.2, adds a
64-bit application interface that allows users to create 64-bit applications
using libni4882.so. Using the 32-bit version of libni4882.so, users can use
the same NI4882 API to build corresponding 32-bit applications with no source
code changes. For more information about the new NI4882 API, refer to the
NI-488.2 Help. You can access NI-488.2 Help from GPIB Explorer. To start GPIB
Explorer from a terminal, enter the following command,
/usr/local/bin/gpibexplorer. In GPIB Explorer, select
Help>>NI-488.2 Help from the menu bar.
NI I/O Trace functionality is limited to use with 32-bit GPIB APIs. As of this
release, it does not function with 64-bit applications.
The command line utility ethernetconfig has been replaced with an interactive
utility accessible through gpibexplorer. Several usability improvements and bug
fixes were also made in gpibexplorer.
The following specific issues were fixed in this release:
122997: The EOIP status bit could remain set incorrectly if an ibwrta or
ibrda call returns an EDVR error.
171688: An ibnotify callback could fail to be triggered by END if the notify
condition included END but not CMPL.
205182: Asynchronous transfers could sometimes report EABO even though the
transfer completed successfully.
359887: GPIB Help could not be opened from the GPIB Troubleshooting Wizard
if it had not already been opened from GPIB Explorer.
372832: A callback from ibnotify might not be invoked after an asynchronous
transfer was completed if the notify mask only contained END.
374822: Calling ibonl while ibnotify is pending could cause the process to
crash under some circumstances.
380705: Aborting an ibrda very quickly after starting it could allow a
PCI-based GPIB interface to receive data when addressed as a
listener, without a read in progress. This data was lost, and
could not be recovered.
404267: In some situations, the GPIB-ENET/1000 could hang while performing
asynchronous transfers. This included fixes in both the NI-488.2
driver and the GPIB-ENET/1000 firmware. Users of the GPIB-ENET/1000
should update the GPIB-ENET/1000 firmware to version 1.1.0 to
receive the full benefit of this fix.
405414: In some cases the DCAS bit was not correctly cleared after being
reported, causing it to be reported with subsequent calls.
406437: GPIB Explorer and GPIB Troubleshooting Wizard could fail silently if
needed libraries were missing from the system. They now provide more
explicit error information if supporting libraries are missing.
418661: In some situations, when an ibnotify callback function was triggered
due to the completion of an asynchronous transfer, the ibcnt and
ibcntl variables would be incorrect.
425931: Calling ibstop with an asynchronous operation in progress would
sometimes not report an EABO error as expected.
------------
Known Issues
------------
----------------------------------------------------------------
NI-488.2 Drops Support for 32-bit Linux Distributions in 2016
----------------------------------------------------------------
NI-488.2 will drop support for Intel 32-bit versions of Linux distributions
as of July 1, 2016. Versions of NI-488.2 that ship after July 1, 2016 may
install and execute on Intel 32-bit distributions, but official support is
not provided.
-----------------
Legal Information
-----------------
----
COPYRIGHT:
----
(c) 2007–2017 National Instruments.
All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted
in any form, electronic or mechanical, including photocopying, recording,
storing in an information retrieval system, or translating, in whole or in
part, without the prior written consent of National Instruments Corporation.
NI respects the intellectual property of others, and we ask
our users to do the same. NI software is protected by copyright and other
intellectual property laws. Where NI software may be used to reproduce
software or other materials belonging to others, you may use NI software
only to reproduce materials that you may reproduce in accordance with the
terms of any applicable license or other legal restriction.
For end-user license agreements (EULAs) and copyright notices, conditions, and
disclaimers, including information regarding certain third-party components
used in LabVIEW, refer to the Copyright topic of the LabVIEW Help.
U.S. Government Restricted Rights
If you are an agency, department, or other entity of the United States
Government ("Government"), the use, duplication, reproduction, release,
modification, disclosure or transfer of the technical data included in this
manual is governed by the Restricted Rights provisions under Federal
Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal
Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for
military agencies.
IVI Foundation Copyright Notice
Content from the IVI specifications reproduced with permission from the IVI
Foundation.
The IVI Foundation and its member companies make no warranty of any kind with
regard to this material, including, but not limited to, the implied warranties
of merchantability and fitness for a particular purpose. The IVI Foundation and
its member companies shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing,
performance, or use of this material.
-------
Credits
-------
The following section summarizes the third party software used by this product.
DOCUMENTATION NOTICE FOR SOCKET++ LICENSE
This product includes code from Socket++ 1.10 licensed by a third party or
parties pursuant to the Socket++ License, and that is subject to the following
notice(s):
Copyright (C) 1992,1993,1994 Gnanasekaran Swaminathan
Permission is granted to use at your own risk and distribute this software in
source and binary forms provided the above copyright notice and this paragraph
are preserved on all copies. This software is provided "as is" with no express
or implied warranty.
********************************************************************************
DOCUMENTATION NOTICE FOR THE ZLIB LICENSE
This product includes code from TinyXML 2.6.1 licensed by a third party or
parties pursuant to the zlib software license, and that is subject to the
following notice(s):
Original code (2.0 and earlier)copyright (c) 2000-2006
Lee Thomason (www.grinninglizard.com)
This software is provided 'as-is', without any express or implied warranty.In
no event will the authors be held liable for any damages arising from the use of
this software.
Permission is granted to anyone to use this software for any purpose, including
commercial applications, and to alter it and redistribute it freely, 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.
********************************************************************************
DOCUMENTATION NOTICE FOR THE BSD 2-CLAUSE LICENSE
This product includes code from tinydir 1.0 licensed by a third party or parties
pursuant to the 2-clause BSD license, and that is subject to the following
notice(s):
Copyright (c) 2013, Cong Xu
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.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ''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 HOLDER 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 views and conclusions contained in the software and documentation are those
of the authors and should not be interpreted as representing official policies,
either expressed or implied, of THE COPYRIGHT HOLDER.
********************************************************************************
DOCUMENTATION NOTICE FOR APACHE LICENSE (2.0)
This product includes code from mDNSResponder licensed by a third party or
parties pursuant to the Apache License, Version 2.0, and that is subject to the
following notice(s):
Licensed under the Apache License, Version 2.0 (the "License"); you may not use
this file except in compliance with the License. You may obtain a copy of the
License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for the
specific language governing permissions and limitations under the License.
Copyright (c) 1997-2006 Apple Computer, Inc. All rights reserved.
********************************************************************************
DOCUMENTATION NOTICE FOR THE BSD 3-CLAUSE LICENSE
This product includes code from mDNSResponder licensed by a third party or
parties pursuant to the 3-clause BSD license, which can be found below and that
is subject to the following notice(s):
Copyright (c) 1997-2006 Apple Computer, Inc. All rights reserved.
Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimer.
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.
Neither the name of Apple Computer, Inc. nor the names of its contributors may
be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE 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 HOLDER 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.
********************************************************************************
DOCUMENTATION NOTICE FOR THE NICTA PUBLIC SOFTWARE LICENSE
This product includes code from mDNSResponder licensed by a third party or
parties pursuant to the NICTA Public Software License, which can be found below
and that is subject to the following notice(s):
Copyright (c) 1997-2006 Apple Computer, Inc. All rights reserved.
This software is licensed under the NICTA Public Source License version 1.0
NICTA Public Software Licence
Version 1.0
Copyright © 2004 National ICT Australia Ltd
All rights reserved.
By this licence, National ICT Australia Ltd (NICTA) grants permission, free of
charge, to any person who obtains a copy of this software and any associated
documentation files ("the Software") to use and deal with the Software in source
code and binary forms without restriction, with or without modification, and to
permit persons to whom the Software is furnished to do so, provided that the
following conditions are met:
Redistributions of source code must retain the above copyright notice, this list
of conditions and the following disclaimers.
Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimers in the documentation and/or
other materials provided with the distribution.
The name of NICTA may not be used to endorse or promote products derived from
this Software without specific prior written permission.
EXCEPT AS EXPRESSLY STATED IN THIS LICENCE AND TO THE FULL EXTENT PERMITTED BY
APPLICABLE LAW, THE SOFTWARE IS PROVIDED "AS-IS" AND NICTA MAKES NO
REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATIONS, WARRANTIES OR CONDITIONS
REGARDING THE CONTENTS OR ACCURACY OF THE SOFTWARE, OR OF TITLE,
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, THE ABSENCE
OF LATENT OR OTHER DEFECTS, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
DISCOVERABLE.
TO THE FULL EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL NICTA BE LIABLE
ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) FOR ANY LOSS OR
DAMAGE WHATSOEVER, INCLUDING (WITHOUT LIMITATION) LOSS OF PRODUCTION OR
OPERATION TIME, LOSS, DAMAGE OR CORRUPTION OF DATA OR RECORDS; OR LOSS OF
ANTICIPATED SAVINGS, OPPORTUNITY, REVENUE, PROFIT OR GOODWILL, OR OTHER ECONOMIC
LOSS; OR ANY SPECIAL, INCIDENTAL, INDIRECT, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY
DAMAGES ARISING OUT OF OR IN CONNECTION WITH THIS LICENCE, THE SOFTWARE OR THE
USE OF THE SOFTWARE, EVEN IF NICTA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
If applicable legislation implies warranties or conditions, or imposes
obligations or liability on NICTA in respect of the Software that cannot be
wholly or partly excluded, restricted or modified, NICTA's liability is limited,
to the full extent permitted by the applicable legislation, at its option, to:
a. in the case of goods, any one or more of the following:
i. the replacement of the goods or the supply of equivalent goods;
ii. the repair of the goods;
iii. the payment of the cost of replacing the goods or of acquiring equivalent
goods;
iv. the payment of the cost of having the goods repaired; or
b. in the case of services:
i. the supplying of the services again; or
ii. the payment of the cost of having the services supplied again.
********************************************************************************
DOCUMENTATION NOTICE FOR OPENSSL
This product includes code from mDNSResponder licensed by a third party or
parties pursuant to the OpenSSL software license, which can be found below and
that is subject to the following notice(s):
Copyright (c) 1998-2008 The OpenSSL Project.All rights reserved.
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
/* ====================================================================
* Copyright (c) 1998-2008 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-core@openssl.org.
*
* 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
* (eay@cryptsoft.com). This product includes software written by Tim
* Hudson (tjh@cryptsoft.com).
*
*/
-----------------------
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young (eay@cryptsoft.com).
* 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 (tjh@cryptsoft.com).
*
* 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 (eay@cryptsoft.com)"
* 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 (tjh@cryptsoft.com)"
*
* 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
*
*/
----
TRADEMARKS:
----
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for
information on NI trademarks. Other product and company names
mentioned herein are trademarks or trade names of their respective companies.
----
PATENTS:
----
For patents covering the NI products/technology, refer to the
appropriate location: Help» Patents in your software, the patents.txt file on
your media, or the NI Patent Notice at ni.com/patents.
页:
[1]