© 1995–2010 National Instruments Corporation. All rights reserved.
NATIONAL INSTRUMENTS HOLDS MULTIPLE COPYRIGHTS, TRADEMARKS, AND PATENTS FOR THIS PRODUCT.
Supported Development Environments
Installing and Uninstalling NI-VISA 5.0.2
LabWindows™/CVI™ Run-Time Engine
PXI Geographic Addressing Support
Using viPeekXX/viPokeXX Macros
Creating and Digitally Signing Catalog Files
NI-VISA for Windows supports the following platforms:
While this distribution targets all these platforms, you can run setup.exe only on the Windows variants.
1 NI-VISA does not support the Windows Server non-R2 editions.
2 Support for Windows Server 2003 R2 may require disabling physical address extensions (PAE). To learn how this might affect your use of Windows Server 2003 and what actions you might need to take, visit ni.com/info and enter the info code PAESupport.
NI-VISA for Windows supports the following development environments:
NI-VISA 5.0.2 does not support Windows 9x/NT/2000. To run your VISA application on Windows 95, you must install NI-VISA 2.6.1 or lower. To run your VISA application on Windows 98/Me, you must install NI-VISA 3.0.1 or lower. To run your VISA application on Windows NT, you must install NI-VISA 3.3.1 or lower. To run your VISA application on Windows 2000, you must install NI-VISA 4.6.2 or lower.
Before you install NI-VISA 5.0.2, we strongly recommend that you uninstall any versions of VISA prior to NI-VISA 2.0.1. NI-VISA 5.0.2 should upgrade properly over NI-VISA 2.0.1 through 4.6.2.
After uninstalling NI-VISA, some DLLs and executables may remain in the NI-VISA directories. To complete the uninstall process, you must restart your machine.
Note: The uninstaller application does not notify you when rebooting is necessary. If you plan to reinstall NI-VISA, you always should reboot the machine after running the uninstaller.
You can programmatically or "silently" install NI-VISA. You also can programmatically control which features of NI-VISA are enabled for installation, allowing you to install a subset of the NI-VISA feature list. Refer to the spec.ini file in the same directory as this readme for more information about installing NI-VISA programmatically and selecting which features to install.
The Setup program now automatically installs the LabWindows/CVI Run-Time Engine when necessary. The NI-VISA interactive utility, VISAIC, requires the LabWindows/CVI Run-Time Engine 8.0 or later to be installed. When you install this utility, Setup also installs the LabWindows/CVI Run-Time Engine if it is not already present.
Starting with NI-VISA 3.0, NI-VISA supports geographic addressing for PXI resources. Geographic addressing includes the ability to identify the chassis number and slot number for a PXI module. To support geographic addressing, the following attributes have been implemented on the PXI INSTR resource type:
|
Using these attributes, PXI resources can be located based on their geographic address in a system. For example, you can use the resource description string "PXI?*INSTR{VI_ATTR_PXI_CHASSIS==1 && VI_ATTR_SLOT==3}" to locate a PXI device in chassis 1, slot 3.
Starting with NI-VISA 3.0, NI-VISA includes a new PXI resource format based on the traditional bus number/device number/function number addressing scheme:
PXI0::<busNum>-<devNum>[.<funcNum>]::INSTR
For example, given a PXI device at bus 2, device number 17, function number 1, the corresponding resource name for this device would be PXI0::2-17.1::INSTR.
In this new resource name, the 0 in PXI0 represents the PCI interface number for the PXI system. Currently, this interface number is always 0. Note that the interface number is not necessarily the same as a device's PCI bus number.
Of course, NI-VISA continues to support the legacy PXI naming convention:
PXI<busNum>::<devNum>[::funcNum]::INSTR
Note that for a single-function PXI device on PCI bus 0, both of these resource formats yield an identical string.
To enable geographic addressing, a PXI system description file (pxisys.ini) must be present on the system. Beginning with NI-VISA 3.0, Measurement & Automation Explorer (MAX) includes the ability to identify components in a PXI system. Through the hardware identification process, MAX collects the information necessary to generate a PXI system description file.
Follow these steps to configure your PXI system for geographic addressing:
Note: If you are using an external PC to control the PXI system via a PXI bridge such as MXI-3, select this option from the menu.
Once the controller and chassis have been identified, a pxisys.ini file is created. This file conforms to the PXI specification and allows drivers (including NI-VISA) and other configuration software to enable geographic addressing and other features of PXI. On Windows, this file is in the Windows directory. For LabVIEW RT systems, the pxisys.ini file is automatically copied to the remote system's c:\ni-rt\system directory.
NI-VISA now works with Agilent/HP GPIB and VXI controller cards. To use this feature, go into MAX, select Tools»NI-VISA»VISA Options, choose the Passports tab, and enable the NiVisaTulip.dll Passport. NI-VISA automatically finds and accesses any GPIB or VXI devices. However, NI-VISA does not configure the Agilent/HP hardware; you still must do that with the Agilent/HP I/O Config utility.
If you have both National Instruments and Agilent/HP controllers in the same system, you must configure the cards at different system addresses, such as GPIB0 and GPIB1. If both vendors try to use the same interface address, NI-VISA reports an error from viFindRsrc or VISA Find Resources.
Users who want to use the viPeekXX/viPokeXX macros for platforms on which the macros are available must define a macro called NIVISA_PEEKPOKE before including visa.h. Note that the macros are currently available on only the Win32 platform (all C/C++ compilers).
If you have used these macros with a version of NI-VISA prior to 2.0, your application will continue to run, but the peek/poke performance decreases. You should relink with the libraries supplied with this installation to regain the prior peek/poke performance.
To WHQL (Windows Hardware Quality Labs) sign your USB hardware using the NI-VISA driver for Windows XP/2000, as part of this process you need a PDB (Program DataBase) file for the underlying driver (NiViUsbK.sys).
NiViUsbK.pdb is provided for this purpose. It is in <NI-VISA Installation Directory>\WinNT\NIvisa\USB. This is typically C:\VXIPNP\WinNT\NIvisa\USB.
On Windows Vista and Windows 7, if you generate an INF file using the NI-VISA Driver Wizard, the INF file installs correctly by itself. However, a warning dialog notifies you that Windows cannot verify the publisher of this driver software. To avoid this dialog, you must create and digitally sign a Windows Catalog (.cat) file.
For more information about creating and signing catalog files, Microsoft has a Kernel-Mode Code Signing Walkthrough whitepaper that describes the details of this process. The generated catalog file should reference only the INF file.
If you are using interrupts with a PXI card that uses an NI-VISA-based driver on an NI RT Hypervisor system, independent reboot of the RT system might hang if the driver does not have the Interrupt Disarm sequence defined. Stop any VISA application on the RT system that might have enabled interrupts for such cards before attempting independent reboot of the RT system. Do a full system reboot if the RT system hangs.
IVI driver developers can use the new VISA COM API. NI-VISA does not yet document this API, so only those developers familiar with the specification should use it in this release. The relevant COM classes for getting started include IResourceManager and IVisaSession, registered in GlobMgr.dll. The VISA COM API is functionally equivalent to the VISA C API. It does not add features; it is just another language interface. You can install the VISA COM API only if you have Internet Explorer 4.01 or higher on your system.
If you are using NI-VISA with the VisaNS .NET API, you may find that an existing project created with an older version of VisaNS now produces build errors that read error CS0011: Referenced class '<className>' has base class or interface 'NationalInstruments.ISynchronizeCallbacks' defined in an assembly that is not referenced. You must add a reference to assembly 'NationalInstruments.Common'. To eliminate this error, add a reference to the NationalInstruments.Common assembly to your project.
The NI-VISA Configuration component is not compatible with NI-RIO 2.1 and lower. The NI-VISA Installer shows a warning if the NI-VISA Configuration component is selected to be installed and NI-RIO 2.1 or lower currently is installed on the system.
If NI-VISA 4.2 or earlier is installed on a system with LabWindows/CVI 8.5 or later, and you then subsequently upgrade to NI-VISA 4.3 or later, the installer does not clean up some of the older files. In this installation scenario, to use the latest VISA API with LabWindows/CVI, you should manually remove the following files, after upgrading NI-VISA:
C:\Program Files\National Instruments\CVI85\bin\visa.lfp
C:\Program Files\National Instruments\CVI85\bin\visa.sub
C:\Program Files\National Instruments\CVI85\bin\msvc\visa.lib
C:\Program Files\National Instruments\CVI85\bin\borland\visa.lib
C:\Program Files\National Instruments\CVI85\extlib\msvc\visa.lib
C:\Program Files\National Instruments\CVI85\extlib\borland\visa.lib
C:\Program Files\National Instruments\CVI85\include\visa.h
C:\Program Files\National Instruments\CVI85\include\vpptype.h
C:\Program Files\National Instruments\CVI85\include\visatype.h
Bug ID 244124. USB communication timeout cannot be set to values greater than 60 seconds. This is fixed.
Added support for IPxi interface in VISA-COM layer.
Added the ability to launch Instrument Driver Finder from MAX.
Added a page in the Driver Development Wizard to auto-detect USB devices and auto-populate device info.
Added the ability to custom install VISA passports on Real-Time targets.
Added support for 64-bit formatted I/O.
Added the ability to configure IEEE 1588-2008 clocks on networks.
Dropped support for FireWire and GPIB-VXI.
Dropped support for Windows 2000.
Bug ID 154617. VISA does not recognize the serial number of some USB RAW devices. This is fixed.
Bug ID 173379. Real-time support of some NI software may fail to install if NI-VISA is already installed. This is fixed.
Bug ID 185549. GPIB passport always returns VI_SUCCESS_DEV_NPRESENT if ibln is disabled. This is fixed.
Added support for Windows 7 (32-bit version), Windows 7 x64 Edition (64-bit version), Windows Server 2003 R2 (32-bit version only), and Windows Server 2008 R2 (64-bit version only).
Bug ID 186322. When building installers from NI software, VISA 4.6 components were incorrectly labeled as version 4.5 in the installer properties dialog. This is fixed.
Installing NI PXI Platform Services version 2.5.2 with NI-VISA 4.5.1 or earlier on a system will cause 3rd party PCI/PXI cards leveraging NI-VISA based drivers to disappear from the Measurement & Automation Explorer (MAX) device tree. National Instruments R-series boards and Timing and Sync boards may also be affected if used with certain versions of the drivers. This version of NI-VISA fixes the problem. Please see KB 4Z9DMDSK for more details.
Bug ID 88858. On LabVIEW RT (Phar Lap ETS), trying to set the attribute VI_ATTR_TCPIP_NODELAY on a TCPIP SOCKET session to VI_FALSE returned an error. This is fixed.
Bug ID 165973. When closing a TCPIP INSTR session for which an interrupt channel has been established, NI-VISA would not explicitly close the interrupt channel. This is fixed.
Bug ID 177456. On Windows Vista, an NI-VISA application communicating to a USBTMC device may cause system crash (blue screen) if the device firmware hits a debug assertion. This is fixed.
Added support for 64-bit user mode in .NET 3.5 Framework. You can now create 64-bit applications with .NET Framework 3.5. For additional information, refer to Working with 64-bit .NET Support for NI-VISA in the NI-VISA .NET Framework 3.5 Help. This help file is installed by default at Start»All Programs»National Instruments»VISA»Documentation»NI-VISA .NET Framework 3.5 Help.
Bug ID 135045. The nimdnsResponder service may corrupt the routing table. This is fixed.
Added a page in MAX to allow viewing and changing the Conflict Resolution Manager settings.
Bug ID 89395. Searching for VXI-11 resources may not find some instruments when multiple Ethernet interfaces are present. This is fixed.
Bug ID 112150. Previously, it was not possible to disable 64-bit passports. This is fixed.
Bug ID 105351. Calling viFindRsrc using 64-bit VISA may cause a command window to flash on the screen. This is fixed.
Bug ID 121227. Previously, MAX would crash when expanding the "Serial & Parallel" tree item if the settings for a port in VISA are different than those in Windows Device Manager. This is fixed.
Bug ID 93245. VISA resources on a CVS target did not appear in the MAX tree. This is fixed.
Bug ID 132397. In the VISA COM driver, attribute accessing functions returning a VARIANT_BOOL now return VARIANT_TRUE (-1) instead of VI_TRUE (+1) when the specified attribute is true. This applies for all functions except the raw GetAttribute call, which will continue to return VI_TRUE.
Bug ID 119631. On Windows Vista, certain installation upgrade scenarios may cause a system crash (blue screen). This is fixed.
Added support for using NI-VISA with 64-bit applications on Windows Vista x64 Edition. VXI, GPIB-VXI, and FireWire resources are not currently supported for 64-bit applications.
Added automatic detection of LXI (TCP/IP) devices that support the mDNS and DNS-SD technologies.
Added support for USB and TCP/IP resources on VxWorks-based LabVIEW RT targets.
Bug ID 93267. VISA may crash when trying to close a session in use by a different thread. This is fixed.
Bug ID 92346. The C examples would build with warnings when using Microsoft Visual C++ 2005 or higher. This is fixed.
Bug ID 114300. In MAX, VISA options may not reflect manual modifications made to visaconf.ini. This is fixed.
Bug ID 103875. viPrintf and variants did not support the %@2 identifier when using short integer arrays nor the %@3 identifier when using any arrays. This is fixed.
When using the MAX Copy Configuration API, you can now specify "ni-visa" as the product. All documented modes are supported.
Bug ID 4DKBD6JW. For PXI/PCI INSTR resources that generate interrupts, VISA incorrectly reversed the logic for the Compare Mask and Compare Value fields in a Compare Interrupt Detection step. This is fixed. If the INF file generated by the Driver Wizard was modified to work around this bug, you should regenerate the INF file.
Bug ID 4FIETP7Z. On Pocket PC 2003/Windows Mobile 5.0 devices, when using USB resources, there was a memory leak when finding and opening a USB device. This is fixed.
Bug ID 4FEAIM00. viWaitOnEvent did not return a warning status when the event queue overflowed. Now viWaitOnEvent returns VI_WARN_QUEUE_OVERFLOW on the first call after an overflow occurs.
Bug ID 4E3DCFAB. In LabWindows/CVI, when user protection is enabled, the use of viMoveInXx and viMoveOutXx operations may incorrectly return user protection errors such as Argument too small or Insufficient buffer size. This is fixed.
Bug ID 4DCB1SJW. For Serial INSTR resources that access parallel ports, reading data from the parallel port may not work correctly. This is fixed.
Bug ID 4CRDPMX3. viPrintf and variants when using the %lf identifier may sometimes calculate an incorrect interpretation of the floating-point data. This is fixed.
Bug ID 4AIFF25E. Asynchronous operations that use the VI_QUEUE mechanism have been optimized and a quicker response time from viWaitOnEvent may be observed, especially on transfers that take a relatively short time to complete.
Bug ID 46N03T48. For PXI/PCI INSTR resources, the PXI_IS_EXPRESS attribute may have not returned VI_TRUE on some PXI Express devices. This is fixed.
Bug ID 4G9F2GWI. On Windows Vista, if MAX was not launched with administrator privileges, changes to the Run the VISA server on startup option would not be saved. This is fixed.
The default installation directory has changed from "C:\VXIPNP" to "C:\Program Files\IVI Foundation\VISA". Upgrades over previous versions of NI-VISA use the previous installation directory.
The default path to the configuration file visaconf.ini has changed to "C:\Documents and Settings\All Users\Application Data\National Instruments\NIvisa" on Windows XP/2000 and to "C:\ProgramData\National Instruments\NIvisa" on Windows Vista.
Added support for Windows Mobile 5.0 on x86 processors.
BasFrmIO.dll was not being registered correctly, which caused some IVI-based drivers not to initialize correctly. This is fixed.
Bug ID 48CE671R. On some Windows CE devices, VISA failed to open virtual serial ports used for Bluetooth. This is fixed.
Bug ID 46Q632QK. Each VISA session to a TCP/IP INSTR (VXI-11) resource created a new device link with the device even when using an identical device name. The TCP/IP INSTR device is more prone to run out of device links in this scenario. Now TCP/IP INSTR sessions share device links for the same TCP/IP device when an identical device name is used.
Bug ID 48ACG54U. viScanf and variants did not correctly support the %b enhanced format code in some cases. This is fixed.
Bug ID 477CTU00. In MAX, the NI-VISA Runtime version now appears in the Software section.
Bug ID 48NINM4U. In MAX, VISA aliases for TCP/IP resources previously were not saved correctly and would not persist. This is fixed.
Bug ID 46FB4OQ1. In MAX, VISA Options for Remote Systems would hang for minutes when there were network devices with corrupted DNS information on the subnet. The duration of this hang has been significantly reduced.
Bug ID 46D93RWI. In MAX, changing the hostname or IP address of a remote system that is enabled for finding resources was not being saved correctly and would result in an additional remote system that is not enabled for finding resources. This is fixed.
Bug ID 46F9LLWI. In MAX, for certain situations, the Port Settings Conflict page displayed erroneous values. This is fixed.
Added support for Windows Vista (32-bit version) and Vista x64 Edition (64-bit version).
The NI-VISA Driver Wizard generates new INF files that work on Vista. If you want to run your VISA based drivers on Vista that previously required an INF file, you will need to regenerate a new INF file using the new Driver Wizard.
On Pocket PC 2003/Windows Mobile 5.0 devices, the NI-VISA configuration file visaconf.ini was installed as read-only. This caused problems with serial port detection. Now it is writeable.
On some cRIO-based LabVIEW RT targets, Serial INSTR sessions may falsely time out when accessing a serial port after the system has been running for a few hours. This is fixed.
In MAX, the chassis and slot numbers displayed for Compact RIO devices may not be correct. This is fixed.
In MAX, a VISA FireWire resource was not displayed when Show Only Devices Registered to VISA is set. This is fixed.
In MAX, the IP address of TCPIP INSTR and SOCKET resources was not shown when the resource was configuring using a hostname. This IP address is now shown.
In MAX, exporting VISA Server settings and then importing would not save the state of the Run on Startup option. This is fixed.
In LabVIEW, if the I/O Filtering option is set to URL format, local resources were not included in the I/O control list. This is fixed.
NI Spy would not log VISA calls from some services. This is fixed.
NI-VISA Server now warns if it is launched and there are no permissions set to allow clients to connect.
The NI-VISA Driver Wizard now has an option for PXI Express devices that provide a way to read the slot number using a sequence of register-level accesses.
The enabled/disabled state of Passports is preserved across upgrades of NI-VISA.
In MAX, when creating a report, VISA details were not present. This is fixed.
64-bit data transfers in register-based operations was not available in CVI. This is fixed.
For GPIB INSTR resources, VISA would set only the GPIB I/O timeout and not the GPIB serial poll timeout. The serial poll timeout is used in viReadSTB. This is fixed.
For Serial INSTR resources, viRead would wait 1 ms when the timeout is set to immediate. This is fixed.
For GPIB INSTR resources, only one call to viWaitOnEvent could be outstanding at any given time. This is fixed.
Calling viFindRsrc with a nonempty, all-whitespace expression string would cause VISA to crash. This is fixed.
Calling viFindRsrc with an expression string that contained two sets of double quotes would not work. This is fixed.
For USB INSTR resources, viReadSTB could fail with a timeout error on some devices that are not completely compliant with the USB TMC specification. This is fixed.
Added support for 64-bit data transfers in register-based operations, to support the VISA 4.0 specification.
The I/O control in LabVIEW 8.0 would not always honor the parameters you specified in the filtering dialog, depending on the order in which you made changes. This is fixed.
viScanf would crash when reading indefinite-length block data. This is fixed.
For ENET-Serial INSTR sessions, framing errors were occasionally not detected. This is fixed.
Improved performance of NI Spy.
Improved performance of VISA in MAX, especially when expanding folders or exporting/importing configuration data.
In MAX, some strings in foreign languages would be displayed with invalid garbage characters. This is fixed.
For TCP/IP SOCKET sessions, re-enabling the termination character between read operations would incorrectly flush the internal buffer. This is fixed.
For TCP/IP SOCKET sessions, reading less than the entire amount of data that the device sent would not work correctly for asynchronous read operations. This is fixed.
In MAX, on LabVIEW RT systems, you can now import the Serial Advanced Settings that were exported on systems with NI-VISA 3.4.1 and older.
In MAX, on large LabVIEW RT systems, expanding Devices and Interfaces or clicking on the Serial category is much faster.
In MAX, improved usability for VXI-11 LAN/LXI instruments. The Create New wizard for detecting devices is easier to use. Also, the device detail views now show the model name and serial number, and also allow access to the device's web page.
In MAX, if you enabled the NiVisaTulip Passport, Agilent I/O GPIB and VXI resources would not show up in the Miscellaneous VISA Resources category. This is fixed.
The new PXI/PCI Express attributes are now implemented.
For TCP/IP INSTR sessions, viWrite would fail if the transfer size was more than 8 KB. This is fixed.
Significantly optimized PCI interrupts and block moves.
Significantly optimized calls to viFindRsrc and viOpen for all interface types.
After running MAX, GPIB-VXI controllers were not autodetected until after a reboot. This is fixed.
If NI-Motion was installed, trying to create a new VISA resource in MAX would hang. This is fixed.
Fixed compatibility issue with VISA I/O Control in LabVIEW 8.0 on Windows XP x64 Edition.
For USB RAW sessions, communication with nonzero control endpoints is now supported with the use of VI_ATTR_USB_CTRL_PIPE.
For USB RAW sessions, the default setting for VI_ATTR_USB_END_IN has been changed from VI_USB_END_SHORT to VI_USB_END_SHORT_OR_COUNT.
For USB RAW sessions, viReadAsync would fail if the transfer size was over 8 KB and not a multiple of the maximum packet size of the endpoint. This is fixed.
For USB RAW sessions, changing the USB Alternate Setting on a USB Interface number other than 0 would fail. This is fixed.
For USB RAW sessions, viOpen leaked a handle for each invocation. This is fixed.
For TCP/IP SOCKET sessions, VI_ATTR_SUPPRESS_END_EN set to VI_TRUE did not work in all cases. This is fixed. The default attribute setting for VI_ATTR_SUPPRESS_END_EN on TCP/IP SOCKET sessions is now VI_TRUE.
For PXI INSTR sessions, when enabling for VI_EVENT_PXI_INTR using VI_QUEUE, viDiscardEvents did not work properly. This is fixed.
Searching for VXI-11 resources would fail if the system had multiple Ethernet interfaces. This is fixed.
FireWire resources used to show up under the Miscellaneous VISA Resources category in MAX. There is now a new category for FireWire resources.
For Serial resources in MAX on LabVIEW RT systems, COM ports were not ordered sequentially. You also could not save changes to the port settings. These are fixed.
For GPIB INSTR sessions, when using a GPIB-USB controller, if you unplugged and replugged the GPIB-USB cable, you would have to exit and restart your application to communicate with it again. This is fixed.
For VXI resources, the minimum supported version of NI-VXI is now 3.x. NI-VISA 3.4 will no longer work with NI-VXI 2.x on Windows.
The maximum number of supported Serial ports on LabVIEW RT (Phar Lap ETS) was 32. It is now 128.
Opening a Serial port on LabVIEW RT (Phar Lap ETS) while also performing a VISA Write to the same port would cause a crash. This is fixed.
Performing asynchronous I/O to a remote VISA resource would return an incorrect transfer count and/or data. This is fixed.
Querying a PXI/PCI resource would return incorrect manufacturer information if that device's subsystem identification differed from its primary identification. Another symptom of the same problem is that trying to enable interrupts would return an error. This is fixed.
Added support for the FireWire (1394) INSTR resource on Windows and Phar Lap ETS platforms. This supports register-based device access. This is a new feature.
The PXI/PCI INSTR resource now supports a new "emergency termination" feature that will send a user-defined series of register reads and writes to the device in the event of a process crash.
For USB RAW sessions, now interrupt-out endpoints may be used for viWrite.
For USB RAW sessions, viReadAsync is now implemented.
Only up to 30 USB RAW devices could be used at one time. This arbitrary limitation has been removed.
For USB RAW resources, the procedure of resetting a pipe may not have been given enough time to complete if the VISA timeout was set very low. This could put some USB devices into a bad state. This is fixed.
viFindRsrc would crash when given long strings that use remote NI-VISA. This is fixed.
Calling viMoveAsync on a remote VISA session would return an error. This is fixed.
For Serial INSTR sessions, viClear previously would flush (discard) the I/O buffers and then send a break. According to the VISA spec, VISA must flush (discard) the I/O output buffer, send a break, and then flush (discard) the I/O input buffer. This is fixed.
viScanf and variants did not support the %u identifier for arrays. This is fixed.
viPrintf and variants did not support the %zy and %Zy identifiers for floating point data. This is fixed.
viPrintf and variants previously generated NaN, +Inf, and -Inf. It now generates NAN, INF, and NINF, respectively.
viScanf and variants did not correctly interpret the input values NAN, INF, and NINF. This is fixed.
Detecting a VXI-11 device without a name (IP address only) would crash MAX. This is fixed.
Reading PXI BAR addresses or the Model Name property from VISA would sometimes return incorrect values. This is fixed.
The function viMapAddress would hang when executed multiple times on PXI/PXI instruments when the CPU had hyperthreading enabled. This is fixed.
Remote VISA systems in MAX would use the IP address in cases where it should have used the hostname. This is fixed.
Guest users on Windows XP could not change VISA aliases. This is fixed.
Enabling the NiVisaTulip Passport would cause applications to crash on exit. This is fixed.
For a USB RAW resource, calling viEnableEvent on VI_EVENT_USB_INTR with the VI_HNDLR mechanism would cause a crash when the first interrupt arrived. This is fixed.
Added support in MAX for the standard Export and Import wizard. For NI-VISA, this allows you to transfer the VISA aliases and driver settings.
Calling viPrintf on a remote VISA session would return VI_ERROR_IO instead of VI_ERROR_RSRC_LOCKED when the remote resource was locked. This is fixed.
The VISA Interactive Control utility (VISAIC) now displays an error message box when viFindRsrc returns an error.
For a PXI INSTR resource, calling viDisableEvent and then viWaitOnEvent would cause a crash. On Windows, the application would exit; on LabVIEW RT (both Phar Lap ETS and RTX), the system would need to be rebooted. This is fixed.
The NI-VISA COM API now supports PXI (INSTR, MEMACC) and USB (INSTR, RAW).
Right-clicking on a PXI chassis in MAX now provides the option to open a VISA session to that PXI BACKPLANE resource.
Fixed various issues in MAX related to changing the IP address of a remote VISA system.
Calling viParseRsrcEx would in some cases output the resource class using the same case you used in the resource string in the input parameter. The output parameter should always be uppercase. This is fixed.
For a Serial INSTR resource, calling viGetAttribute on VI_ATTR_ASRL_WIRE_MODE would always output -1 if you had not yet set the mode for the given resource. Now if you have NI-Serial 1.6 or higher installed with supported hardware, it will output the default configured state rather than -1. Otherwise, it will still output -1. Note that NI-Serial 1.6 does not implement this feature on all currently supported NI RS-485 controllers.
NI-VISA 3.1 supports the PXI/PCI interface type in the RTX real-time environment in LabVIEW RT. This is a new feature.
The VISA Driver Development Wizard can install the generated INF file onto your local system. This is a new feature.
The BACKPLANE resource type is supported in the PXI resource class. This is a new feature.
For a VI running on LabVIEW RT, calling VISA Close on an ENET-Serial resource would occasionally either hang or return an error. This has been fixed.
Calling viClose on an Ethernet resource would leak a socket handle. This has been fixed.
In MAX, it was not possible to create static TCPIP resources on a LabVIEW RT system. This has been fixed.
On Windows NT, 2000, or XP, calling viEnableEvent on a PXI/PCI INSTR resource would occasionally cause a system crash. This has been fixed.
Reading data from a Serial port was slow. The performance has improved.
Using the Serial Break VI from LabVIEW did not work with remote NI-VISA. This has been fixed.
Querying VI_ATTR_ASRL_AVAIL_NUM on a parallel port would return a large random number. The correct value for this is always 0. This has been fixed.
If you created a TCPIP resource in MAX with an alias, it would not show up. This has been fixed.
In MAX, choosing the Tools»NI-VISA»VISA Options menu item would not always bring up the options. This has been fixed.
In MAX, if you disabled a COM port and clicked Refresh, the Serial resource would disappear completely. This has been fixed. The resource now continues to exist but has a black X overlay icon to indicate that it is disabled.
The VISA Driver Development Wizard now supports the PXI standard module.ini format. It will generate that file along with the .inf files for NI-VISA. You can also use this wizard to load module.ini files from other vendors.
In MAX, if you inserted a new Serial port, it would erroneously claim that the settings have a conflict. This has been fixed.
The VI_EVENT_USB_INTR event attributes did not work properly. This has been fixed.
If you unplugged a VISA USB device and plugged it back in, NI-VISA could not access the device properly. This has been fixed.
Calling viEnableEvent on a remote VISA session would leak memory in the server. This has been fixed.
Creating a new remote NI-VISA system would hang MAX. This has been fixed.
The hostname localhost or the IP address <IP_ADDRESS> did not work properly with remote NI-VISA. Only the DHCP name or network IP address would work. This has been fixed.
The remote NI-VISA server did not properly validate a hostname with an underscore. This has been fixed.
Calling viGetAttribute on VI_ATTR_INTF_INST_NAME on TCPIP resources with Internet Explorer 2 would crash. This has been fixed.
If you enabled a LabVIEW RT system that was using DHCP as a VISA remote system to search when finding resources, NI-VISA would use the IP address rather than the DNS name. Starting with LabVIEW RT 7.1, remote systems are correctly assigned DNS names, and NI-VISA can use the DNS name when finding remote resources. Any existing remote VISA system that was enabled for finding will remain listed using its IP address unless you disable and re-enable the system for finding. Enabling a remote system with LabVIEW RT 7.1 already installed will result in NI-VISA using the DNS name if it is the same as the name of the remote controller. Otherwise, if the remote system is not using DHCP, or if the DNS name does not match the controller name, NI-VISA will still use the IP address of the remote system.
In MAX, if you changed the VISA Options and browsed to another item, your changes would sometimes be lost. This has been fixed.
The manufacturer and model name for PXI/PCI resources were incorrectly reported as unknown. This has been fixed.
The global attributes on a GPIB INTFC resource were not properly shared across sessions. This has been fixed.
Calling viOpen on a remote NI-VISA resource did not honor the openTimeout parameter. This has been fixed.
For a PXI INSTR resource, calling viEnableEvent and viDisableEvent in a loop would leak memory. On LabVIEW RT, this would eventually cause a reboot.
For a GPIB INTFC resource, performing any asynchronous I/O would occasionally cause a crash when you later close the VISA session.
Installing NI-VISA 3.0 on a system with LabVIEW 6.1 would cause user VIs that use VISA Configure Serial Port to have a broken wire.
The driver now works properly with Fast User Switching on Windows XP/2000.
For a PXI INSTR resource, we now support PXI/PCI devices that rely on the subvendor ID and/or the subvendor model code. To use this functionality, you must create a new .inf file with the VISA Driver Development Wizard. The attributes VI_ATTR_PXI_SUB_MANF_ID and VI_ATTR_PXI_SUB_MODEL_CODE are no longer supported by the VISA driver. The correct attributes to query are now VI_ATTR_MANF_ID and VI_ATTR_MODEL_CODE. These will return the primary vendor information if no subvendor information is present, and they will return the subvendor information if it is present.
For a PXI MEMACC resource, viMemFree now frees all memory correctly.
For a Serial INSTR resource, viOpen on both Windows and LabVIEW RT will now accept COMx as a valid resource name even if MAX has not yet been run.
For a Serial INSTR resource, viOpen will now open a port if the process that had been using that port exited ungracefully (such as with <Ctrl-C>). The previous behavior had been that viOpen would return VI_ERROR_RSRC_BUSY.
For a Serial INSTR resource, viWriteAsync was not implemented. Now it is.
For a Serial INSTR resource, multiple sessions to the same port caused weird behavior if you tried to both write and read data simultaneously. This has been fixed.
For a Serial INSTR resource, if you enabled RTS/CTS flow control and then manually tried to set the state of the RTS line, some operating systems would generate VI_ERROR_NSUP_ATTR while others would return VI_SUCCESS but not actually modify the state of the line. Neither of these behaviors was correct. Now NI-VISA will return VI_ERROR_INV_SETUP in this case on all operating systems.
For a Serial INSTR resource, the RS-485 wire mode attribute now works properly on Windows XP/2000.
In GPIB, the attribute VI_ATTR_INTF_INST_NAME would report an unknown board type for some GPIB-USB and GPIB-ENET controllers. The symptom was also visible in the VISA Interactive Control utility. This attribute now reports the correct information.
In GPIB, the implementation of viFindRsrc could take up to 10 s if you had NI-488.2 version 2.0 installed. The symptom was also visible in LabVIEW when you dropped the first VISA resource control on the front panel. This now takes less than 1 s on most machines.
NI Spy occasionally would incorrectly report an output jobID of 0 for viReadAsync or viWriteAsync, even though the operation completed successfully with a valid nonzero jobID.
NI Spy would not restore the window location on a monitor other than the primary monitor. This now works as expected.
If you ran MAX as a guest user and edited the Passport settings, the new settings could not be saved to the registry, but MAX did not generate a warning. This has been fixed, and you will now get a warning.
For a TCPIP SOCKET resource, viReadAsync was not implemented. Now it is.
The remote NI-VISA server could not be started on the same machine as the remote DAQ server because they both used the same port. Now the remote NI-VISA server uses port 3537 by default.
viFindRsrc would crash on a complex expression with multiple | symbols. This has been fixed.
If you had a GPIB device at primary address 1 that generated a response to *IDN? that was longer than 100 characters, viFindRsrc would occasionally crash. This has been fixed.
Some VISA COM components were not being correctly registered.
The VISA COM API would return an incorrect string from ReadString if the number of bytes read was exactly what was requested.
The VISA COM API would not return output string parameters correctly if the variable passed into the function was uninitialized or had a garbage value. This problem was normally only seen from C++ when using a raw BSTR instead of CComBSTR. This has been fixed.
In GPIB, the implementation of viFindRsrc on LabVIEW RT would find GPIB resources only on GPIB0. It now finds GPIB resources on any configured GPIB interface number.
Calling viUnmapAddress when using an Agilent HP-E1406A GPIB-VXI controller would cause the application to crash. This has been fixed.
The attributes VI_ATTR_MANF_NAME and VI_ATTR_MODEL_NAME are now correctly implemented for GPIB-VXI regardless of whether NI-VXI is installed.
The maximum simultaneous number of GPIB-VXI controllers supported by NI-VISA has changed from 10 to 32.
The VISA Driver Development Wizard (formerly known as the PXI Driver Development Wizard) now allows multiple logical-OR PXI interrupt conditions.
You can now edit the binding properties of a VISA TCPIP resource in MAX. For example, you can change the hostname or IP address.
MAX can now auto-detect VXI-11 TCPIP resources on your subnet. When you right-click on Devices and Interfaces and choose Create New..., you then need to specify a VXI-11 instrument and click the option to have MAX browse your local subnet.
If you enabled the VISA COM API for VI_EVENT_SERVICE_REQ for a callback, it would crash when the event was being raised. This has been fixed.
If you tried to exit the VISA Interactive Control utility by right-clicking on the taskbar icon and choosing Close, the utility would hang. This has been fixed.
Using remote NI-VISA with asynchronous I/O did not properly transmit data asynchronously. This has been fixed.
In Serial on LabVIEW RT, you can now configure advanced settings (such as FIFO triggers and the default RS-485 wire mode) in MAX.
In Serial, if the Windows configuration settings for a given port were different from the NI-VISA settings, MAX would overwrite the Windows settings when you clicked Refresh. Now, MAX points out the different settings and lets you choose.
In MAX, selecting Rename on an alias and changing merely the case of the alias would cause an error. This has been fixed.
When calling viWaitOnEvent repeatedly with a timeout of 0 (immediate), some interfaces and event types would still consume excessive CPU time. Now doing this will yield the CPU regardless of the interface or event type.
For a Serial INSTR resource, if a parity or framing error occurred, NI-VISA would not return the correct error condition. This has been fixed.
viFindRsrc would return VI_ERROR_INV_EXPR if the expression exceeded 255 characters. Now it will accept resource expressions of any length.
If a PXI multifunction device did not have function 0 registered as an NI-VISA resource, viFindRsrc would not return any of the other functions of that device either, even if they were registered with NI-VISA. This now works properly.
Calling viFindRsrc would always assert REN on each GPIB board after finding devices. Now viFindRsrc will reassert REN on each board only if there is at least one open VISA INSTR session on that board.
For a TCPIP SOCKET resource, using viRead with termchar enabled was much slower than reading the exact number of bytes. The performance of using termchar with viRead is now much better than it was.
A. This product includes components that use the socket++ library. In regards to the socket++ library, the following notice applies:
Copyright © 1992, 1993, 1994 Gnanasekaran Swaminathan (University of Virginia). Certain modifications have been made by Gregory Lavender (University of Texas) and National Instruments Corporation to the version of the socket++ library used in this product.
B. This product includes components that were created using DriverWorks; such components are Copyright © 2004 Compuware Corporation.
C. This product includes components that use Xerces. In regards to the Xerces library, the following notice applies:
This product includes software developed by the Apache Software Foundation (http://www.apache.org/) that is subject to the Apache License, Version 2.0 (the "Xerces License"), a copy of which may be found at: http://www.apache.org/licenses/LICENSE-2.0. Copyright © 1999–2005 The Apache Software Foundation. All rights reserved. Certain modifications have been made by National Instruments Corporation to the version of the Xerces library used in this product; such modifications are Copyright © 2008 National Instruments Corporation. The content of this notice is for informational purposes only and does not modify the Xerces License. See the Xerces License for the specific language governing permissions and limitations relating to the Xerces library.
D. This product includes components that use mDNSResponder. In regards to the mDNSResponder library, the following notice applies:
This product includes software developed by the Apple Computer, Inc. that is subject to the Apache License, Version 2.0 (the "mDNSResponder License"), a copy of which may be found at: http://www.apache.org/licenses/LICENSE-2.0. Copyright © 2002–2003 Apple Computer, Inc. All rights reserved. Certain modifications have been made by National Instruments Corporation to the version of mDNSResponder library used in this product; such modifications are Copyright © 2008 National Instruments Corporation. The content of this notice is for informational purposes only and does not modify the mDNSResponder License. See the mDNSResponder License for the specific language governing permissions and limitations relating to the mDNSResponder library.


QUIZ BOARD
How do you link an external script file?
script href=script file name
script img=script file name
script type=text/javascript
script src=script file name
What is the dafault data type for variables in javascript
Boolean
Null
UndefinedNumber
Undefined
How do you declare variables in javascript
var MYVARIABLE;
var myvariable;
var MyVariable;
var myVariable;
Chose one that is not a data type
Number
String
Boolean
Array
Which one is not a javascript library
Angular
React
Meteor
Django
Is C++ a low level language
No
Yes
submit
Your Score Is:
© 2018 MIT License


Select or paste an image:
There are rows. (You can type J for 10 rows if they are enumerated by letters.)
Add lines between rows? (Mostly for my own debugging purposes.)
Intended for shuffling Zeger's ECE 109 past quiz answer options. Screenshot the answers without the letters and paste them here.


Introduction
- Build an EAGLE Analysis framework around the EAGLE Simulation
- Specs, Design&Build Analysis framework
- Mostly simulated items backtracking and comparison tools
- Could also benefit from using a workflow management system
- Will need BAM generation - Use EAGLE to Benchmark / Compare / Find tools weak points (bwa+gatk vs Isaac?)
Answers business needs:
- useful to know where to put efforts in the future
- useful to understand where our tools are better, and publicise our tools if they are actually better
- if we don't do it first, others may run other simulators and report Illumina 's deficiencies first before we could address them, then we will anyway need to verify the claims, then improve our tools. so better be prepared and do it first. - Simulate non-reality: identify and simulate features that lead to best analysis
- (Feedback from Come): Multi sample analysis
- Specs, Design&Build Analysis framework
From requirements to implementation
EAGLE Phase 2 - Analysis Framework - Requirements
EAGLE Phase 2 - Analysis Framework - Specifications
Notes
From running random simulation, the following things were worth remembering for when we want to do a proper analysis:
- Running a simulation that only generates SNP mismatches (not indel) and homopolymer deletions, we see that there may be a detectable probability for a base to look deleted in the middle of 2 homopolymers (via a combination of mismatch SNP + homo del?)


Please hold down
Ctrl and Click the Reload
button to reload the app!
Please enable JavaScript to continue using this application.


MENU
Toggle navigation
HEIMS Administrator
Back to Site
Students Applications
Accepted Admissions
Denied Admissions
Student Applications After Tests
Accepted Applications
Denied Applications


Kourses
An online learning hub. Lots of online courses and online learning websites are gathered in Kourses.
Home
Learn Anything
Learn Programming
Learn in Thai
About Me
×
About me
Learn Anything
These websites teach courses in various fields
Learn Programming
Lots of programming teaching websites
Free programming books
Learn in Thai
Thai online learning websites


| PERLHPUX(1) | Perl Programmers Reference Guide | PERLHPUX(1) |
swinstall -s /cdrom perl
assuming you have mounted that CD on /cdrom.
That build was a portable hppa-1.1 multithread build that supports large files compiled with gcc-2.9-hppa-991112.
If you perform a new installation, then (a newer) Perl will be installed automatically. Pre-installed HP-UX systems now have more recent versions of Perl and the updated modules.
The official (threaded) builds from HP, as they are shipped on the Application DVD/CD's are available on <http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=PERL> for both PA-RISC and IPF (Itanium Processor Family). They are built with the HP ANSI-C compiler. Up till 5.8.8 that was done by ActiveState.
To see what version is included on the DVD (assumed here to be mounted on /cdrom), issue this command:
# swlist -s /cdrom perl # perl D.5.8.8.B 5.8.8 Perl Programming Language perl.Perl5-32 D.5.8.8.B 32-bit 5.8.8 Perl Programming Language with Extensions perl.Perl5-64 D.5.8.8.B 64-bit 5.8.8 Perl Programming Language with Extensions
To see what is installed on your system:
# swlist -R perl # perl E.5.8.8.J Perl Programming Language # perl.Perl5-32 E.5.8.8.J 32-bit Perl Programming Language with Extensions perl.Perl5-32.PERL-MAN E.5.8.8.J 32-bit Perl Man Pages for IA perl.Perl5-32.PERL-RUN E.5.8.8.J 32-bit Perl Binaries for IA # perl.Perl5-64 E.5.8.8.J 64-bit Perl Programming Language with Extensions perl.Perl5-64.PERL-MAN E.5.8.8.J 64-bit Perl Man Pages for IA perl.Perl5-64.PERL-RUN E.5.8.8.J 64-bit Perl Binaries for IA
The HP porting centres are limited in what systems they are allowed to port to and they usually choose the two most recent OS versions available.
HP has asked the porting centre to move Open Source binaries from /opt to /usr/local, so binaries produced since the start of July 2002 are located in /usr/local.
One of HP porting centres URL's is <http://hpux.connect.org.uk/> The port currently available is built with GNU gcc. As porting modern GNU gcc is extremely hard on HP-UX, they are stuck at version gcc-4.2.3.
Perl can be compiled with either HP's ANSI C compiler or with gcc. The former is recommended, as not only can it compile Perl with no difficulty, but also can take advantage of features listed later that require the use of HP compiler-specific command-line flags.
If you decide to use gcc, make sure your installation is recent and complete, and be sure to read the Perl INSTALL file for more gcc-specific details.
HP's HP9000 Unix systems run on HP's own Precision Architecture (PA-RISC) chip. HP-UX used to run on the Motorola MC68000 family of chips, but any machine with this chip in it is quite obsolete and this document will not attempt to address issues for compiling Perl on the Motorola chipset. Even though PA-RISC hardware is not sold anymore, a lot of machines still running on these CPU's can be found in the wild.
The last order date for HP 9000 systems was December 31, 2008.
HP PA-RISC systems are usually referred to with model description "HP 9000". The last CPU in this series is the PA-8900. Support for PA-RISC architectured machines officially ended as shown in the following table:
PA-RISC End-of-Life Roadmap +--------+----------------+----------------+-----------------+ | HP9000 | Superdome | PA-8700 | Spring 2011 | | 4-128 | | PA-8800/sx1000 | Summer 2012 | | cores | | PA-8900/sx1000 | 2014 | | | | PA-8900/sx2000 | 2015 | +--------+----------------+----------------+-----------------+ | HP9000 | rp7410, rp8400 | PA-8700 | Spring 2011 | | 2-32 | rp7420, rp8420 | PA-8800/sx1000 | 2012 | | cores | rp7440, rp8440 | PA-8900/sx1000 | Autumn 2013 | | | | PA-8900/sx2000 | 2015 | +--------+----------------+----------------+-----------------+ | HP9000 | rp44x0 | PA-8700 | Spring 2011 | | 1-8 | | PA-8800/rp44x0 | 2012 | | cores | | PA-8900/rp44x0 | 2014 | +--------+----------------+----------------+-----------------+ | HP9000 | rp34x0 | PA-8700 | Spring 2011 | | 1-4 | | PA-8800/rp34x0 | 2012 | | cores | | PA-8900/rp34x0 | 2014 | +--------+----------------+----------------+-----------------+
A complete list of models at the time the OS was built is in the file /usr/sam/lib/mo/sched.models. The first column corresponds to the last part of the output of the "model" command. The second column is the PA-RISC version and the third column is the exact chip type used. (Start browsing at the bottom to prevent confusion ;-)
# model 9000/800/L1000-44 # grep L1000-44 /usr/sam/lib/mo/sched.models L1000-44 2.0 PA8500
The following systems contained PA-RISC 1.0 chips:
600, 635, 645, 808, 815, 822, 825, 832, 834, 835, 840, 842, 845, 850, 852, 855, 860, 865, 870, 890
The following systems contain with PA-RISC 1.1 chips:
705, 710, 712, 715, 720, 722, 725, 728, 730, 735, 742, 743, 744, 745, 747, 750, 755, 770, 777, 778, 779, 800, 801, 803, 806, 807, 809, 811, 813, 816, 817, 819, 821, 826, 827, 829, 831, 837, 839, 841, 847, 849, 851, 856, 857, 859, 867, 869, 877, 887, 891, 892, 897, A180, A180C, B115, B120, B132L, B132L+, B160L, B180L, C100, C110, C115, C120, C160L, D200, D210, D220, D230, D250, D260, D310, D320, D330, D350, D360, D410, DX0, DX5, DXO, E25, E35, E45, E55, F10, F20, F30, G30, G40, G50, G60, G70, H20, H30, H40, H50, H60, H70, I30, I40, I50, I60, I70, J200, J210, J210XC, K100, K200, K210, K220, K230, K400, K410, K420, S700i, S715, S744, S760, T500, T520
As of the date of this document's last update, the following systems contain PA-RISC 2.0 chips:
700, 780, 781, 782, 783, 785, 802, 804, 810, 820, 861, 871, 879, 889, 893, 895, 896, 898, 899, A400, A500, B1000, B2000, C130, C140, C160, C180, C180+, C180-XP, C200+, C400+, C3000, C360, C3600, CB260, D270, D280, D370, D380, D390, D650, J220, J2240, J280, J282, J400, J410, J5000, J5500XM, J5600, J7000, J7600, K250, K260, K260-EG, K270, K360, K370, K380, K450, K460, K460-EG, K460-XP, K470, K570, K580, L1000, L2000, L3000, N4000, R380, R390, SD16000, SD32000, SD64000, T540, T600, V2000, V2200, V2250, V2500, V2600
Just before HP took over Compaq, some systems were renamed. the link that contained the explanation is dead, so here's a short summary:
HP 9000 A-Class servers, now renamed HP Server rp2400 series. HP 9000 L-Class servers, now renamed HP Server rp5400 series. HP 9000 N-Class servers, now renamed HP Server rp7400. rp2400, rp2405, rp2430, rp2450, rp2470, rp3410, rp3440, rp4410, rp4440, rp5400, rp5405, rp5430, rp5450, rp5470, rp7400, rp7405, rp7410, rp7420, rp7440, rp8400, rp8420, rp8440, Superdome
The current naming convention is:
aadddd ||||`+- 00 - 99 relative capacity & newness (upgrades, etc.) |||`--- unique number for each architecture to ensure different ||| systems do not have the same numbering across ||| architectures ||`---- 1 - 9 identifies family and/or relative positioning || |`----- c = ia32 (cisc) | p = pa-risc | x = ia-64 (Itanium & Itanium 2) | h = housing `------ t = tower r = rack optimized s = super scalable b = blade sa = appliance
It is no longer possible to compile PA-RISC 1.0 executables on either the PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted, but the resulting executable will not run when transferred to a PA-RISC 1.0 system.
Although PA-RISC binaries can run on Itanium systems, you should not attempt to use a PA-RISC version of Perl on an Itanium system. This is because shared libraries created on an Itanium system cannot be loaded while running a PA-RISC executable.
HP Itanium 2 systems are usually referred to with model description "HP Integrity".
BL60p, BL860c, BL870c, BL890c, cx2600, cx2620, rx1600, rx1620, rx2600, rx2600hptc, rx2620, rx2660, rx2800, rx3600, rx4610, rx4640, rx5670, rx6600, rx7420, rx7620, rx7640, rx8420, rx8620, rx8640, rx9610, sx1000, sx2000
To see all about your machine, type
# model ia64 hp server rx2600 # /usr/contrib/bin/machinfo
HP-UX version Kernel Architecture End-of-factory support ------------- ------ ------------ ---------------------------------- 10.20 32 bit PA 30-Jun-2003 11.00 32/64 PA 31-Dec-2006 11.11 11i v1 32/64 PA 31-Dec-2015 11.22 11i v2 64 IPF 30-Apr-2004 11.23 11i v2 64 PA & IPF 31-Dec-2015 11.31 11i v3 64 PA & IPF 31-Dec-2020 (PA) 31-Dec-2025 (IPF)
See for the full list of hardware/OS support and expected end-of-life <https://h20195.www2.hpe.com/V2/getpdf.aspx/4AA4-7673ENW.pdf>
Shared libraries created on a platform using a particular PA-RISC version are not usable on platforms using an earlier PA-RISC version by default. However, this backwards compatibility may be enabled using the same +DAportable compiler flag (with the same PA-RISC 1.0 caveat mentioned above).
Shared libraries created on an Itanium platform cannot be loaded on a PA-RISC platform. Shared libraries created on a PA-RISC platform can only be loaded on an Itanium platform if it is a PA-RISC executable that is attempting to load the PA-RISC library. A PA-RISC shared library cannot be loaded into an Itanium executable nor vice-versa.
To create a shared library, the following steps must be performed:
1. Compile source modules with +z or +Z flag to create a .o module which contains Position-Independent Code (PIC). The linker will tell you in the next step if +Z was needed. (For gcc, the appropriate flag is -fpic or -fPIC.) 2. Link the shared library using the -b flag. If the code calls any functions in other system libraries (e.g., libm), it must be included on this line.
(Note that these steps are usually handled automatically by the extension's Makefile).
If these dependent libraries are not listed at shared library creation time, you will get fatal "Unresolved symbol" errors at run time when the library is loaded.
You may create a shared library that refers to another library, which may be either an archive library or a shared library. If this second library is a shared library, this is called a "dependent library". The dependent library's name is recorded in the main shared library, but it is not linked into the shared library. Instead, it is loaded when the main shared library is loaded. This can cause problems if you build an extension on one system and move it to another system where the libraries may not be located in the same place as on the first system.
If the referred library is an archive library, then it is treated as a simple collection of .o modules (all of which must contain PIC). These modules are then linked into the shared library.
Note that it is okay to create a library which contains a dependent library that is already linked into perl.
Some extensions, like DB_File and Compress::Zlib use/require prebuilt libraries for the perl extensions/modules to work. If these libraries are built using the default configuration, it might happen that you run into an error like "invalid loader fixup" during load phase. HP is aware of this problem. Search the HP-UX cxx-dev forums for discussions about the subject. The short answer is that everything (all libraries, everything) must be compiled with "+z" or "+Z" to be PIC (position independent code). (For gcc, that would be "-fpic" or "-fPIC"). In HP-UX 11.00 or newer the linker error message should tell the name of the offending object file.
A more general approach is to intervene manually, as with an example for the DB_File module, which requires SleepyCat's libdb.sl:
# cd .../db-3.2.9/build_unix # vi Makefile ... add +Z to all cflags to create shared objects CFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \ -I/usr/local/include -I/usr/include/X11R6 CXXFLAGS= -c $(CPPFLAGS) +Z -Ae +O2 +Onolimit \ -I/usr/local/include -I/usr/include/X11R6 # make clean # make # mkdir tmp # cd tmp # ar x ../libdb.a # ld -b -o libdb-3.2.sl *.o # mv libdb-3.2.sl /usr/local/lib # rm *.o # cd /usr/local/lib # rm -f libdb.sl # ln -s libdb-3.2.sl libdb.sl # cd .../DB_File-1.76 # make distclean # perl Makefile.PL # make # make test # make install
As of db-4.2.x it is no longer needed to do this by hand. Sleepycat has changed the configuration process to add +z on HP-UX automatically.
# cd .../db-4.2.25/build_unix # env CFLAGS=+DD64 LDFLAGS=+DD64 ../dist/configure
should work to generate 64bit shared libraries for HP-UX 11.00 and 11i.
It is no longer possible to link PA-RISC 1.0 shared libraries (even though the command-line flags are still present).
PA-RISC and Itanium object files are not interchangeable. Although you may be able to use ar to create an archive library of PA-RISC object files on an Itanium system, you cannot link against it using an Itanium link editor.
Even though HP-UX 10.20 and 11.00 are not actively maintained by HP anymore, updates for the HP ANSI C compiler are still available from time to time, and it might be advisable to see if updates are applicable. At the moment of writing, the latests available patches for 11.00 that should be applied are PHSS_35098, PHSS_35175, PHSS_35100, PHSS_33036, and PHSS_33902). If you have a SUM account, you can use it to search for updates/patches. Enter "ANSI" as keyword.
Most mentioned distributions are depots. H.Merijn Brand has made prebuilt gcc binaries available on <http://mirrors.develooper.com/hpux/> and/or <http://www.cmve.net/~merijn/> for HP-UX 10.20 (only 32bit), HP-UX 11.00, HP-UX 11.11 (HP-UX 11i v1), and HP-UX 11.23 (HP-UX 11i v2 PA-RISC) in both 32- and 64-bit versions. For HP-UX 11.23 IPF and HP-UX 11.31 IPF depots are available too. The IPF versions do not need two versions of GNU gcc.
On PA-RISC you need a different compiler for 32-bit applications and for 64-bit applications. On PA-RISC, 32-bit objects and 64-bit objects do not mix. Period. There is no different behaviour for HP C-ANSI-C or GNU gcc.
Building a 64-bit capable gcc on PA-RISC from source is possible only when you have the HP C-ANSI C compiler or an already working 64-bit binary of gcc available. Best performance for perl is achieved with HP's native compiler.
There are some drawbacks to this approach. One is that any extension which calls any file-manipulating C function will need to be recompiled (just follow the usual "perl Makefile.PL; make; make test; make install" procedure).
The list of functions that will need to recompiled is: creat, fgetpos, fopen, freopen, fsetpos, fstat, fstatvfs, fstatvfsdev, ftruncate, ftw, lockf, lseek, lstat, mmap, nftw, open, prealloc, stat, statvfs, statvfsdev, tmpfile, truncate, getrlimit, setrlimit
Another drawback is only valid for Perl versions before 5.6.0. This drawback is that the seek and tell functions (both the builtin version and POSIX module version) will not perform correctly.
It is strongly recommended that you use this flag when you run Configure. If you do not do this, but later answer the question about large files when Configure asks you, you may get a configuration that cannot be compiled, or that does not function as expected.
To compile Perl with threads, add -Dusethreads to the arguments of Configure. Verify that the -D_POSIX_C_SOURCE=199506L compiler flag is automatically added to the list of flags. Also make sure that -lpthread is listed before -lc in the list of libraries to link Perl with. The hints provided for HP-UX during Configure will try very hard to get this right for you.
HP-UX versions before 10.30 require a separate installation of a POSIX threads library package. Two examples are the HP DCE package, available on "HP-UX Hardware Extensions 3.0, Install and Core OS, Release 10.20, April 1999 (B3920-13941)" or the Freely available PTH package, available on H.Merijn's site (<http://mirrors.develooper.com/hpux/>). The use of PTH will be unsupported in perl-5.12 and up and is rather buggy in 5.11.x.
If you are going to use the HP DCE package, the library used for threading is /usr/lib/libcma.sl, but there have been multiple updates of that library over time. Perl will build with the first version, but it will not pass the test suite. Older Oracle versions might be a compelling reason not to update that library, otherwise please find a newer version in one of the following patches: PHSS_19739, PHSS_20608, or PHSS_23672
reformatted output:
d3:/usr/lib 106 > what libcma-*.1 libcma-00000.1: HP DCE/9000 1.5 Module: libcma.sl (Export) Date: Apr 29 1996 22:11:24 libcma-19739.1: HP DCE/9000 1.5 PHSS_19739-40 Module: libcma.sl (Export) Date: Sep 4 1999 01:59:07 libcma-20608.1: HP DCE/9000 1.5 PHSS_20608 Module: libcma.1 (Export) Date: Dec 8 1999 18:41:23 libcma-23672.1: HP DCE/9000 1.5 PHSS_23672 Module: libcma.1 (Export) Date: Apr 9 2001 10:01:06 d3:/usr/lib 107 >
If you choose for the PTH package, use swinstall to install pth in the default location (/opt/pth), and then make symbolic links to the libraries from /usr/lib
# cd /usr/lib # ln -s /opt/pth/lib/libpth* .
For building perl to support Oracle, it needs to be linked with libcl and libpthread. So even if your perl is an unthreaded build, these libraries might be required. See "Oracle on HP-UX" below.
As of the date of this document, Perl is fully 64-bit compliant on HP-UX 11.00 and up for both cc- and gcc builds. If you are about to build a 64-bit perl with GNU gcc, please read the gcc section carefully.
Should a user have the need for compiling Perl in the LP64 environment, use the -Duse64bitall flag to Configure. This will force Perl to be compiled in a pure LP64 environment (with the +DD64 flag for HP C-ANSI-C, with no additional options for GNU gcc 64-bit on PA-RISC, and with -mlp64 for GNU gcc on Itanium). If you want to compile Perl using gcc, you will have to get a version of the compiler that supports 64-bit operations.)
You can also use the -Duse64bitint flag to Configure. Although there are some minor differences between compiling Perl with this flag versus the -Duse64bitall flag, they should not be noticeable from a Perl user's perspective. When configuring -Duse64bitint using a 64bit gcc on a pa-risc architecture, -Duse64bitint is silently promoted to -Duse64bitall.
In both cases, it is strongly recommended that you use these flags when you run Configure. If you do not use do this, but later answer the questions about 64-bit numbers when Configure asks you, you may get a configuration that cannot be compiled, or that does not function as expected.
Configure -A prepend:libswanted='cl pthread ' ...
Do not forget the space before the trailing quote.
Also note that this does not (yet) work with all configurations, it is known to fail with 64-bit versions of GCC.
the error might show something like:
Pthread internal error: message: __libc_reinit() failed, file: ../pthreads/pthread.c, line: 1096 Return Pointer is 0xc082bf33 sh: 5345 Quit(coredump)
and Configure will give up.
When using the GUI version of SAM, click on the Kernel Configuration icon, then the Configurable Parameters icon. Scroll down and select the maxdsiz line. From the Actions menu, select the Modify Configurable Parameter item. Insert the new formula into the Formula/Value box. Then follow the instructions to rebuild your kernel and reboot your system.
In general, a value of 256MB (or "256*1024*1024") is sufficient for Perl to compile at maximum optimization.
#0 0xc004216c in () from /usr/lib/libc.2 #1 0xc00d7550 in __nss_src_state_destr () from /usr/lib/libc.2 #2 0xc00d7768 in __nss_src_state_destr () from /usr/lib/libc.2 #3 0xc00d78a8 in nss_delete () from /usr/lib/libc.2 #4 0xc01126d8 in endpwent () from /usr/lib/libc.2 #5 0xd1950 in Perl_pp_epwent () from ./perl #6 0x94d3c in Perl_runops_standard () from ./perl #7 0x23728 in S_run_body () from ./perl #8 0x23428 in perl_run () from ./perl #9 0x2005c in main () from ./perl
The key here is the "nss_delete" call. One workaround for this bug seems to be to create add to the file /etc/nsswitch.conf (at least) the following lines
group: files passwd: files
Whether you are using NIS does not matter. Amazingly enough, the same bug also affects Solaris.
--- /usr/include/inttypes.h 2001-04-20 18:42:14 +0200 +++ /usr/include/inttypes.h 2000-11-14 09:00:00 +0200 @@ -72,7 +72,7 @@ #define UINT32_C(__c) __CONCAT_U__(__c) #else /* __LP64 */ #define INT32_C(__c) __CONCAT__(__c,l) -#define UINT32_C(__c) __CONCAT__(__CONCAT_U__(__c),l) +#define UINT32_C(__c) __CONCAT__(__c,ul) #endif /* __LP64 */ #define INT64_C(__c) __CONCAT_L__(__c,l)
cc: "/usr/include/sys/socket.h", line 535: warning 562: Redeclaration of "sendfile" with a different storage class specifier: "sendfile" will have internal linkage. cc: "/usr/include/sys/socket.h", line 536: warning 562: Redeclaration of "sendpath" with a different storage class specifier: "sendpath" will have internal linkage.
They seem to be caused by broken system header files, and also other open source projects are seeing them. The following HP-UX patches should make the warnings go away:
CR JAGae12001: PHNE_27063 Warning 562 on sys/socket.h due to redeclaration of prototypes CR JAGae16787: Warning 562 from socket.h sendpath/sendfile -D_FILEFFSET_BITS=64 CR JAGae73470 (11.23) ER: Compiling socket.h with cc -D_FILEFFSET_BITS=64 warning 267/562
With much assistance regarding shared libraries from Marc Sabatella.
| 2019-10-21 | perl v5.30.3 |


How many users are affected?
How many users are there at the company?
Is the submitting user a VIP?
Is there an issue currently impacting productivity?
(Select "No" if this is an info request.)
Is the issue intermittent?
Did the issue start more than one day ago?
Is a critical business function unable to be performed?
Is a workaround available:


Money Play. How should Red play 31?
pips Red=162 White=93
(CorrectAnswer= 0/0, ErrorScore= 0)
There is not much between the various plays here but an eye for detail can always earn you a few extra milli-points.
By playing 20/17, 18/17 Red ensure that White’s 15 and 35 have to be played my moving the five 10/5 which will generate more gammons for Red.
By playing 20/17, 18/17 Red ensure that White’s 15 and 35 have to be played my moving the five 10/5 which will generate more gammons for Red.
1. Cubeful 2-ply 20/17 18/17 Eq.: +1.112 0.813 0.362 0.030 - 0.187 0.067 0.001 2. Cubeful 2-ply 18/14 Eq.: +1.101 (-0.011) 0.811 0.354 0.031 - 0.189 0.074 0.001 3. Cubeful 2-ply 21/17 Eq.: +1.092 (-0.019) 0.802 0.344 0.026 - 0.198 0.074 0.001 4. Cubeful 2-ply 21/18 20/19 Eq.: +1.091 (-0.020) 0.799 0.346 0.025 - 0.201 0.076 0.001 5. Cubeful 2-ply 21/20 21/18 Eq.: +1.088 (-0.024) 0.795 0.345 0.027 - 0.205 0.066 0.001


| Attribute |
Public New
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
|
Notes:
|
New order from Viper received.

Item is not assigned to a module yet and therefore not in production.

|
|
Public InProduction
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
|
Notes:
|
Item is assigned to a module and in production.
|
|
Public Cancelled
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
|
Notes:
|
A customer is allowed to cancel an Order. So we must not continue to produce it.
|
|
Public Failed
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
|
Notes:
|
We must reprint or do something with an Item when one of following reason is true:

Vision system detects error

Hardware fault detected (e.g. Printer) -> reproduce all affected Items in module

Item fails in quality inspection loop

Unexpected Item detected in wrong module (with RFID Sensor)

|
|
Public Fullfilled
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
|
Notes:
|
Item has been produced.
|
|


[PART XII.] ADOPTION ASSISTANCE
[§346-301] Adoption assistance program established. The department of human services shall maintain an adoption assistance program to facilitate the adoption of children with special needs. [L 1992, c 190, pt of §1]
Cross References
Adoption assistance compact, see chapter 350C.
Interstate compact on placement of children, see chapter 350E.


Chess Tournament Website
Multi-page website where you can find all the information about a fictitious chess tournament hosted in Hanoi. Built with HTML, CSS & Bootstrap. Github here | Live Demo here
Oh, hello, hola, xin chào nice to meet you!
Multi-page website where you can find all the information about a fictitious chess tournament hosted in Hanoi. Built with HTML, CSS & Bootstrap. Github here | Live Demo here
Capstone project - MasterChess Social Media - Ruby on Rails - Twitter clone for chess lovers to share opinions, tactics, events and learn. Github here | Live Demo here
JavaScript - A weather app that pulls from the OpenWeatherMap API to allow users to search for and view the forecast in cities worldwide. Github here | Live Demo here
A web app that allows the user to book training sessions with world class snooker players. Built with Ruby on Rails, React and Redux. Github here | Live Demo here
A bookstore web app for Magic-books Inc., a fictional company, where you can add books and track the percentage read, built with React&Redux. Github here | Live Demo here
A catalog where users will find everything related to Star Trek TV shows, built with React&Redux. Github here | Live Demo here
Xin chào, I'm Javier, a software developer born in Barcelona and based on planet earth. I’m
hard-working, analytical and very passionate about software development.
I decided to strengthen my skills and joined Microverse, where I acquired professional-level skills
including Ruby, Ruby on Rails, JavaScript, React, Redux, Bootstrap and Test-Driven development
techniques. During that time, I designed and developed more than 50 professional projects through pair
programming with different coding partners remotely from around the world, and completed +70 coding
challenges. I also mentored and assisted other students on their projects, which gave me more confidence
as a
professional full-stack developer.
Being a chess lover helps me to prevent possible future problems and to think carefully about each of my
next moves.
I am also passionate about science fiction books, which helps me to be a person who is always willing to
learn
and evolve. I love to play sports and all kinds of outdoor activities, and also to give back to the
community
helping whenever I can. Travelling and meeting people around the world is another of my passions, as I
am a
globally minded person who thrives on diverse teams. I'm learning Vietnamese now, and I love learning
new
things.
I Create Stunning Digital Experiences Fully Functional On All Devices.
My Creations Will Help Your Business Stand Out.


| merge_rev {bit} | R Documentation |
The merge_
functions allow unary and binary operations
on (ascending) sorted vectors of link{integer}
.
merge_rev(x)
will do in one scan what costs two scans in -rev(x)
, see also reverse_vector(x)
.
Many of these merge_
can optionally scan their input in reverse order (and switch the sign),
which again saves extra scans for calling merge_rev(x)
first.
merge_rev(x) merge_match(x, y, revx = FALSE, revy = FALSE, nomatch = NA_integer_) merge_in(x, y, revx = FALSE, revy = FALSE) merge_notin(x, y, revx = FALSE, revy = FALSE) merge_duplicated(x, revx = FALSE) merge_anyDuplicated(x, revx = FALSE) merge_sumDuplicated(x, revx = FALSE) merge_unique(x, revx = FALSE) merge_union( x, y, revx = FALSE, revy = FALSE, method = c("unique", "exact", "all") ) merge_setdiff(x, y, revx = FALSE, revy = FALSE, method = c("unique", "exact")) merge_symdiff(x, y, revx = FALSE, revy = FALSE, method = c("unique", "exact")) merge_intersect( x, y, revx = FALSE, revy = FALSE, method = c("unique", "exact") ) merge_setequal(x, y, revx = FALSE, revy = FALSE, method = c("unique", "exact")) merge_rangein(rx, y, revx = FALSE, revy = FALSE) merge_rangenotin(rx, y, revx = FALSE, revy = FALSE) merge_rangesect(rx, y, revx = FALSE, revy = FALSE) merge_rangediff(rx, y, revx = FALSE, revy = FALSE) merge_first(x, revx = FALSE) merge_last(x, revx = FALSE) merge_firstin(rx, y, revx = FALSE, revy = FALSE) merge_lastin(rx, y, revx = FALSE, revy = FALSE) merge_firstnotin(rx, y, revx = FALSE, revy = FALSE) merge_lastnotin(rx, y, revx = FALSE, revy = FALSE)
x |
a sorted set |
y |
a sorted set |
revx |
default |
revy |
default |
nomatch |
integer value returned for non-matched elements, see |
method |
one of "unique", "exact" (or "all") which governs how to treat ties, see the function descriptions |
rx |
These are low-level functions and hence do not check whether the set is actually sorted.
Note that the 'merge_*' and 'merge_range*' functions have no special treatment for 'NA'.
If vectors with 'NA' are sorted ith 'NA' in the first positions ('na.last=FALSE') and arguments 'revx=' or 'revy=' have not been used,
then 'NAs' are treated like ordinary integers.
'NA' sorted elsewhere or using 'revx=' or 'revy=' can cause unexpected results
(note for example that 'revx=' switches the sign on all integers but 'NAs').
The *binary* 'merge_*' functions have a 'method="exact"'
which in both sets treats consecutive occurrences of the same value as if they were different values,
more precisely they are handled as if the identity of ties were tuples of ties, rank(ties)
.
method="exact"
delivers unique output if the input is unique, and in this case works faster than method="unique"
.
merge_rev(x)
returns -rev(x)
for integer
and double
and !rev(x)
for logical
merge_match
: returns integer positions of sorted set x in sorted set y, see match(x, y, ...)
merge_in
: returns logical existence of sorted set x in sorted set y, see x %in% y
merge_notin
: returns logical in-existence of sorted set x in sorted set y, see !(x %in% y)
merge_duplicated
: returns the duplicated status of a sorted set x, see duplicated
merge_anyDuplicated
: returns the anyDuplicated status of a sorted set x, see anyDuplicated
merge_sumDuplicated
: returns the sumDuplicated status of a sorted set x, see bit_sumDuplicated
merge_unique
: returns unique elements of sorted set x, see unique
merge_union
: returns union of two sorted sets.
Default method='unique'
returns a unique sorted set, see union
;
method='exact'
returns a sorted set with the maximum number of ties in either input set;
method='all'
returns a sorted set with the sum of ties in both input sets.
merge_setdiff
: returns sorted set x minus sorted set y
Default method='unique'
returns a unique sorted set, see setdiff
;
ethod='exact'
returns a sorted set with sum(x ties) minus sum(y ties);
merge_symdiff
: returns those elements that are in sorted set y
xor
in sorted set y
Default method='unique'
returns the sorted unique set complement, see symdiff
;
method='exact'
returns a sorted set set complement with abs(sum(x ties) minus sum(y ties));
merge_intersect
: returns the intersection of two sorted sets x and y
Default method='unique'
returns the sorted unique intersect, see intersect
;
method='exact'
returns the intersect with the minium number of ties in either set;
merge_setequal
: returns TRUE
for equal sorted sets and FALSE
otherwise
Default method='unique'
compares the sets after removing ties, see setequal
;
method='exact'
compares the sets without removing ties;
merge_rangein
: returns logical existence of range rx in sorted set y, see merge_in
merge_rangenotin
: returns logical in-existence of range rx in sorted set y, see merge_notin
merge_rangesect
: returns the intersection of range rx and sorted set y, see merge_intersect
merge_rangediff
: returns range rx minus sorted set y, see merge_setdiff
merge_first
: quickly returns the first element of a sorted set x (or NA
if x is empty), hence x[1]
or merge_rev(x)[1]
merge_last
: quickly returns the last element of a sorted set x, (or NA
if x is empty), hence x[n]
or merge_rev(x)[n]
merge_firstin
: quickly returns the first common element of a range rx and a sorted set y, (or NA
if the intersection is empty), hence merge_first(merge_rangesect(rx,y))
merge_lastin
: quickly returns the last common element of a range rx and a sorted set y, (or NA
if the intersection is empty), hence merge_last(merge_rangesect(rx,y))
merge_firstnotin
: quickly returns the first element of a range rx which is not in a sorted set y (or NA
if all rx are in y), hence merge_first(merge_rangediff(rx,y))
merge_lastnotin
: quickly returns the last element of a range rx which is not in a sorted set y (or NA
if all rx are in y), hence merge_last(merge_rangediff(rx,y))
xx OPTIMIZATION OPPORTUNITY These are low-level functions could be optimized with initial binary search (not findInterval, which coerces to double).
merge_rev(1:9) merge_match(1:7, 3:9) #' merge_match(merge_rev(1:7), 3:9) merge_match(merge_rev(1:7), 3:9, revx=TRUE) merge_match(merge_rev(1:7), 3:9, revy=TRUE) merge_match(merge_rev(1:7), merge_rev(3:9)) merge_in(1:7, 3:9) merge_notin(1:7, 3:9) merge_anyDuplicated(c(1L,1L,2L,3L)) merge_duplicated(c(1L,1L,2L,3L)) merge_unique(c(1L,1L,2L,3L)) merge_union(c(1L,2L,2L,2L), c(2L,2L,3L)) merge_union(c(1L,2L,2L,2L), c(2L,2L,3L), method="exact") merge_union(c(1L,2L,2L,2L), c(2L,2L,3L), method="all") merge_setdiff(c(1L,2L,2L,2L), c(2L,2L,3L)) merge_setdiff(c(1L,2L,2L,2L), c(2L,2L,3L), method="exact") merge_setdiff(c(1L,2L,2L), c(2L,2L,2L,3L), method="exact") merge_symdiff(c(1L,2L,2L,2L), c(2L,2L,3L)) merge_symdiff(c(1L,2L,2L,2L), c(2L,2L,3L), method="exact") merge_symdiff(c(1L,2L,2L), c(2L,2L,2L,3L), method="exact") merge_intersect(c(1L,2L,2L,2L), c(2L,2L,3L)) merge_intersect(c(1L,2L,2L,2L), c(2L,2L,3L), method="exact") merge_setequal(c(1L,2L,2L), c(1L,2L)) merge_setequal(c(1L,2L,2L), c(1L,2L,2L)) merge_setequal(c(1L,2L,2L), c(1L,2L), method="exact") merge_setequal(c(1L,2L,2L), c(1L,2L,2L), method="exact")


- Italian 1560: |SUNWfirefoxl10n-ja-JP|web/browser/firefox/locale/ja_jp|Firefox localization - Japanese 1561: |SUNWfirefoxl10n-ko-KR|web/browser/firefox/locale/ko_kr|Firefox localization - Korean 1562: |SUNWfirefoxl10n-pl-PL|web/browser/firefox/locale/pl_pl|Firefox localization - Polish 1563: |SUNWfirefoxl10n-pt-BR|web/browser/firefox/locale/pt_br|Firefox localization - Portuguese Brazil 1564: |SUNWfirefoxl10n-ru-RU|web/browser/firefox/locale/ru_ru|Firefox localization - Russian 1565: |SUNWfirefoxl10n-sv-SE|web/browser/firefox/locale/sv_se|Firefox localization - Swedish 1566: |SUNWfirefoxl10n-zh-CN|web/browser/firefox/locale/zh_cn|Firefox localization - Simplified Chinese 1567: |SUNWfirefoxl10n-zh-TW|web/browser/firefox/locale/zh_tw|Firefox localization - Traditional Chinese 1568: |SUNWjre-config-plugin|web/browser/firefox/plugin/firefox-java|Java runtime integration - plugin 1569: |SUNWlinks|web/browser/links|links - WWW text browser 1570: |SUNWlynx|web/browser/lynx|Text-mode web browser 1571: |SUNWw3m|web/browser/w3m|A text-based web browser 1572: |SUNWcurl|web/curl|The C-URL Wrappers Library 1573: |SUNWfirefox-bookmark|web/data/firefox-bookmarks|Firefox’s default bookmark 1574: |SUNWbluefish|web/editor/bluefish|Bluefish, a powerful editor for experienced web designers. 1575: |SUNWspawn-fcgi|web/fastcgi/spawn-fcgi|Spawn-Fcgi utility for starting FCGI backends 1576: |SUNWtcat|web/java-servlet/tomcat|Tomcat Servlet/JSP Container 1577: |SUNWtcat-examples|web/java-servlet/tomcat/tomcat-examples|Tomcat Servlet/JSP Container - example applications 1578: |SUNWphp52|web/php-52|PHP Server 5.2.6 1579: |SUNWphp52d|web/php-52/documentation|PHP Server Documentation 1580: |SUNWphp52-apc|web/php-52/extension/php-apc|APC extension module for PHP 1581: |SUNWphp52-idn|web/php-52/extension/php-idn|IDN extension module for PHP 1582: |SUNWphp52-memcache|web/php-52/extension/php-memcache|Memcache extension module for PHP 1583: |SUNWphp52-mysql|web/php-52/extension/php-mysql|PHP 5.2.6 module for MySQL 1584: |SUNWphp52-pear|web/php-52/extension/php-pear|PHP Extension and Application Repository Components(root) 1585: |SUNWphp52-pgsql|web/php-52/extension/php-pgsql|PHP 5.2.6 module for PostgreSQL 1586: |SUNWphp52-suhosin|web/php-52/extension/php-suhosin|Suhosin extension module for PHP 1587: |SUNWphp52-tcpwrap|web/php-52/extension/php-tcpwrap|Tcpwrap extension module for PHP 1588: |SUNWphp52-xdebug|web/php-52/extension/php-xdebug|XDebug extension module for PHP 1589: |SUNWprivoxy|web/proxy/privoxy|Privoxy Web Proxy 1590: |SUNWsquid|web/proxy/squid|Squid Web Proxy Cache 1591: |SUNWapch|web/server/apache-13|Apache Web Server 1592: |SUNWapchd|web/server/apache-13/documentation|Apache Web Server Documentation 1593: |SUNWapch22|web/server/apache-22|Apache Web Server V2.2 1594: |SUNWapch22d|web/server/apache-22/documentation|Apache Web Server V2.2 Documentation 1595: |SUNWapch22m-dtrace|web/server/apache-22/module/apache-dtrace|DTrace plugin for Apache Web Server V2.2 1596: |SUNWapch22m-fcgid|web/server/apache-22/module/apache-fcgid|FastCGI plugin for Apache Web Server V2.2 1597: |SUNWapch22m-jk|web/server/apache-22/module/apache-jk|Tomcat Connector plugin for Apache Web Server V2.2 1598: |SUNWapch22m-php52|web/server/apache-22/module/apache-php5|PHP Server 5.2.6 module for Apache Web Server V2.2 1599: |SUNWapch22m-proxy-html|web/server/apache-22/module/apache-proxy_html|Proxy HTML plugin for Apache Web Server V2.2 1600: |SUNWapch22m-security|web/server/apache-22/module/apache-security|Mod Security plugin for Apache Web Server V2.2 1601: |SUNWapch22m-sed|web/server/apache-22/module/apache-sed|mod_sed plugin for Apache Web Server V2.2 1602: |SUNWapch22m-xml2enc|web/server/apache-22/module/apache-xml2enc|xml2nec plugin for Apache Web Server V2.2 1603: |SUNWejabberd|web/server/ejabberd|ejabberd - Jabber/XMPP instant messaging server 1604: |SUNWlighttpd14|web/server/lighttpd-14|Lighttpd Web Server 1605: |SUNWurlgrabber|web/urlgrabber|urlgrabber 1606: |SUNWwget|web/wget|wget - GNU wget 1607: |SUNWxwplt|x11/clients|X Window System platform software 1608: |SUNWxwrtl|x11/compatibility/links-svid|X Window System & Graphics Runtime Library Links in /usr/lib 1609: |SUNWxorg-compatlinks|x11/compatibility/links-xorg|X11 Compatibility Links 1610: |SUNWxcursor-themes|x11/data/xcursor-themes|X.Org Foundation X11 cursor themes 1611: |SUNWxwdem|x11/demo|X Window System demo programs 1612: |SUNWxwpmn|x11/developer/manual|X Window System programmers man pages 1613: |SUNWxorg-client-programs|x11/extension-clients|X.Org Foundation X Client Programs 1614: |SUNWxorg-client-docs|x11/extension-clients/manual|X.Org Foundation X client programs documentation 1615: |SUNWxwfsw|x11/font-utilities|X Window System platform required font software 1616: |SUNWxwinc|x11/header|X Window System include files 1617: |SUNWxorg-headers|x11/header/header-xorg|X.Org Foundation X11 client headers 1618: |SUNWxwmod|x11/kernel|X Window System kernel modules 1619: |SUNWxwacx|x11/keyboard/accessx|AccessX client program 1620: |SUNWxorg-xkb|x11/keyboard/data-xkb|X.Org Foundation Xserver keyboard layouts 1621: |SUNWxorg-clientlibs|x11/library/extension-clients|X.Org Foundation X Client Libraries 1622: |SUNWxwice|x11/library/libice|X Window System Inter-Client Exchange (ICE) Components 1623: |SUNWxwxft|x11/library/libxft|Xft (X Freetype) Library 1624: |SUNWxwslb|x11/library/lint|X Window System lint libraries 1625: |SUNWxorg-mesa|x11/library/mesa|Xorg Server Mesa Modules and Libraries 1626: |SUNWxwman|x11/manual|X Window System online user man pages 1627: |SUNWxwopt|x11/optional-clients|X Window System Optional Clients 1628: |SUNWxorg-server|x11/server/xorg|X.Org Foundation Xserver 1629: |SUNWefbw|x11/server/xorg/driver/xorg-efb|Sun XVR-300/XVR-100, XVR-50 Graphics Window System Configuration and Diagnostics 1630: |SUNWkfbw|x11/server/xorg/driver/xorg-kfb|X server loadable module for the PCI-E Bus Sun XVR-2500 graphics accelerator (64-bit) 1631: |SUNWxorg-graphics-ddx|x11/server/xorg/driver/xorg-misc|X.Org Foundation Xserver Graphics Device Modules 1632: |SUNWxvnc|x11/server/xvnc|X11/VNC server 1633: |SUNWxdm|x11/session/xdm|xdm Display Manager 1634: |SUNWxorg-tsol-module|x11/trusted/trusted-xorg|Trusted Extensions, Xorg 1635: |SUNWxwplr|x11/x11-config|X Window System platform software configuration 1636: |SUNWxcompmgr|x11/xcompmgr|xcompmgr provides a rudimentary compositing window manager 1637: |SUNWxwfs|x11/xfs|X Window System Font server
Search
Collectives
Community Group
Academic and Research
Accessibility
Advocacy
Appliances
Approachability
Architecture Process and Tools
BrandZ
Chinese Users
Community Advisory Board
Databases
Desktop
Device Drivers
Distribution
Documentation
DTrace
Emerging Platforms
Fault Management
Games on OpenSolaris
HA Clusters
HPC Developer
Installation and Packaging
Internationalization and Localization
Laptop
Logical Domains
Modular Debugger (MDB)
Networking
NFS
Observability
OpenSolaris Governing Board (OGB)
OpenSolaris Printing
OS/Net (ON)
Performance
Power Management
PowerPC
Security
Service Management Facility (smf(5))
Software Porters
Solaris Volume Manager
Storage
Systems Administration Community Group
Testing
Tools Home
Unix File Systems (UFS)
Website Community
X Window System
Xen
ZFS
Zones
Project
ADSL Modem Enhancement
ARC Process Definition
ARM Platform Port
Automatic Data Migration
BIND Update
Bluetooth Stack & Drivers
Brocade FC HBA - Initiator
Brocade FC HBA - Target
Brussels - unified network link configuration
Caiman, Solaris Install Revisited
Celeste
Český portál
Chime Visualization Tool for DTrace
CIFS client for Solaris
CIFS Server
Clearview: Network Interface Coherence
Cluster Agent: Informix Dynamic Server
Cluster Agent: OpenSolaris Container
Cluster Agent: OpenSolaris xVM
Cluster Agent: Oracle E-Business Suite
Cluster agent: PostgreSQL
Cluster Agent: Samba
Cluster Agent: Tomcat
CMT
Coarse Data Flow Parallelism
Colorado: Open HA Cluster on OpenSolaris
Command Assistant
Common Array Manager
Companion - /opt/sfw: Free and Open Source software
COMSTAR: Common Multiprotocol SCSI Target
Content
Contest
CPU Observability
Credentials Process Groups
Crossbow: Network Virtualization and Resource Control
Crypto KMS Agent Toolkit
Cryptographic Framework
Data Migration Manager
Data Tethers
Deutsches Portal
Device Detection Tool
Device Driver Utility
Device Manager
Device Mapper
Direct Rendering Infrastructure & 3D drivers
DTrace Guide
Duckwater: Simplified name services management
Easy Tools
Emancipation
Emulex Fibre Channel Device Driver
Emulex Advanced Ethernet Device Driver
Enable/Enhance Solaris support for Intel Platform
Enhance the support of USB webcams
Enhanced SMF Profiles
Enhancements for AMD-based Platforms
Erlang DTrace Integration
Ethernet bridge module for Solaris
Evaluate Conary
Events Registry
Ext3 file system support
F/OSS Package Base
Facilitation
Fibre Channel over Ethernet
Fine Grained Access Policy (FGAP)
Fingerprint Authentication
Flexible Mandatory Access Control
Forensic Tools
Fully Open X Project
Fuse on Solaris
gcore
Generic Machine Check Architecture Improvements
Google SOC
HA-JBoss
HA-MySQL
Hadoop Live CD
Hitachi
HoneyComb Fixed Content Storage
Hotplug Framework
HPC Stack
Image Packaging System
Immutable Service Containers
Improved Performance MIB
Indiana
Innovation Awards
Input Method
Intel Graphics
Internet Key Exchange, version 2
Interrupt Resource Management
IP Datapath Refactoring
IP over Infiniband
IPsec Tunnel Reform
iSCSI Extensions for Remote DMA (iSER)
iSNS Server
JeOS - Just enough Operating System
JKstat - a java binding for libkstat
Journaled File System (JFS)
K Desktop Environment
Kerberos
Kernel Sockets
Kernel SSL Enhancements
Key Management Framework
Korn Shell 93 integration/migration project
Labeled IPsec
LatencyTOP
Layer 2 Filtering
LDoms Manager
Lending
libMicro - portable microbenchmarks
Link Layer Discovery
Live Media: Technologies for distributions running from CD and other media
Locale Data
lofi compression and cryptography support
lx64 brand
Media Management System
Mega_sas
Mexico
MilaX minimal Live Distribution
MIPS Platform Port
Mozilla DTrace
MRSL.NONsharedDevice
Multi-lingual Glossary
Multi-pathing software (MPxIO)
Multiple disk sector size support
Multiple DOI
Muskoka: An open repository for OpenSolaris technical content
Navigator
Nemo: A Framework for High-Performance Networking
Network Auto-Magic
Network Data Management Protocol
Network MIBs
Network Performance Projects
Network Power Management
Network Storage
Network Time Protocol (NTP)
Nevada Globalization
New Design of 4over6 Mechanism Based on OpenSolaris
NFS RDMA transport update and performance analysis
NFS Server in non-Global Zones
NFS version 4.1 pNFS
NFSv4 namespace extensions
Nightingale: Port Songbird to OpenSolaris
NPort ID Virtualization (NPIV)
NUMA
Object Storage Device (OSD) support for Solaris
OHACGE Script Based Plug-in
ON/Nevada (ONNV) Project
Open Development Infrastructure
Open HA Cluster Utilities
Open Sound System
OpenGrok
OpenPegasus CIM Server
OpenRTI
OpenSolaris Busybox
OpenSolaris Desktop
OpenSolaris Hispano
OpenSolaris Security Audit
OpenSolaris support for the QEMU processor emulator: host and guest
PEF: Packet Event Framework
Performance Wrappers
Pkgfactory
Polski Portal
Portail Francophone
Portal Brasil
Portals
Power Management Usability Interfaces
Presto: Automatic Printing Configuration
Printable Many Page Solaris Manuals
Promise SuperTrak RAID HBA Driver
QLogic Converged Network Adapter GLDv3 NIC Driver
Quagga Routing Protocol Suite Integration
RAID Configuration Utility
RBridge (IETF TRILL) support
RDMA Offload Framework
Release Notes
Reno: Login Process Enhancements for Interop
Resource Management
s10brand
SAM/QFS
SCM Migration Project
SCSI RDMA Protocol
SDcard Drivers
Sensor Abstraction Layer
Session Initiation Protocol
SFW
Shell: bourne shell, korn shell, C shell, etc.
Sierra: Intel WiFi Chipsets Support
Simple Panels
SM-HBA Based SAS HBA Management
SMF Documentation
Solaris iSCSI Target
Solaris PowerPC Port
SourceJuicer
Sparks: name service switch/nscd enhancements
Squashfs
Star integration/migration project
Starfish
Starter Kit
Storage Power Management
Sun Security Toolkit
Sun StorageTek Availability Suite
Support for OpenFabrics User Verbs / API on OpenSolaris OS
Support gcc4/GCCfss in Solaris
Suspend/Resume
SVR4 Packaging
Systemz
Tamarack: Removable Media Enhancements in Solaris
Tesla: OpenSolaris Enhanced Power Management
Test Development
Tickless Kernel Architecture
TIPC
Trademarks
Trusted networking interface policy database for Trusted Extensions
Trusted Platform Module support
Use Case
Userland
Validated Execution Project
Virtual Console
Virtual Network Machines
Visual Panels
Visualization for HPC
Volo
VRRP: Virtual Router Redundancy Protocol Implementation
VSCAN service
Web Stack
Website
Winchester: Schema mapping and ID mapping for AD Interoperability
Wireless USB Support
Wireless Wide Area Network
X Consolidation
x86 Generic FMA Topology Enumerator
Xen Gate
Xfce: A lightweight desktop environment
X Keyboard Layout
ZFS Boot and Install
ZFS on disk encryption support
Zone Manager
Zone Statistics
Русский портал
البوابة العربية
भारतीय पोर्टल
中国门户
日本ポータル
한국 포탈
User Group
Adelaide
Argentina
Arizona
Atlanta
Baltimore-Washington
Bangalore
Bangkok
Bangladesh
Brasilia
Beijing
Bélem
Berlin
Bhimavaram
Bloomington
Capital Region
Cardiff
Ceara
Charlotte
Chengdu
Chennai
Chihuahua
Chile
Cleveland
Colombia
Columbus
Connecticut
Cracow
Czech
Dallas/Ft. Worth
Danish
Delaware
Edinburgh
Egypt
Finland
Florida
Frankfurt
Front Range
FuZhou
Great Lakes
Greece
Hangzhou
Hawaii
HeFei
Houston
Hong Kong
Hyderabad
Indonesia
Irish
Israel
Istanbul
Italian
Jinan
Jogja
Kabul
Kansas City
Latvia
London
Madrid
Madurai
Manchester
Mato Grosso
Melbourne
Minas Gerais
Minnesota
Montreal
Moscow
Mumbai
Munich
NEA
Netherlands
New England
New York City
New Zealand
NIT Hamirpur
Noroeste
Nuremberg-Erlangen
Oklahoma City
Osnabrück
Peru
Philadelphia
Piaski
Pittsburgh
Porto Alegre
Puget Sound
Pune
Queensland
Rio de Janeiro
Research Triangle Park
Romania
Russia
San Antonio
San Diego
San Francisco
São Paulo
Scottish
Serbia
Shanghai
Shenzhen
Silicon Valley
Singapore
Slovak
South African
Southern Connecticut
St. Louis
Stavanger
Sweden
Switzerland
Sydney
Szczecin
Taiwan
Tecum
Thames Valley
Tokyo
Toronto
Trondheim
Tulsa
Turkey
Ufa
Ukraine
University of Melbourne
Vale do Paraíba
Vancouver
Venezuela
Vladivostok
Welsh - Cymru
Wisconsin
Xi'an
Subsites
Code Reviews
SCM Management
Package Search
Bugster
Bugzilla
Test Machines
Planet
Mailing Lists
Elections & Polls
ARC Case Logs
Source Juicer
Package Factory
User Authentication
Project indiana Pages
Renamed Packages in Builds 133, 134 and 134a
Building and testing ON
Documentation
Files
Get OpenSolaris 2008.05
Upgrading OpenSolaris 2008.05 to Later Versions of OpenSolaris
Resources
Documentation Deliverables
Glossary
Problem Statement
Release Notes
Reporting Bugs
Restoring system to original installation
Start Page
Status
Accessibility
ReleaseNotes2008.11
x86


Automated Inventory Management and Alert System
| Sl.No. |
Time |
Number of box present |
";
echo "" . $row['id'] . " | ";
echo "" . $row['time'] . " | ";
echo "" . $row['value'] . " | ";
echo "";
}
mysqli_close($con);
?>
Note:
1.Maximum capacity are 8 boxes.
2.Each box is of 0.5kg weight(approx.).
3.You will get alert as number of boxes fall below 4.


| Package | Description |
|---|---|
| list | |
| negotiator.tournament |
| Modifier and Type | Interface and Description |
|---|---|
interface |
Permutations<E>
Permutations contains a list of permutations of some
ImmutableList . |
| Modifier and Type | Class and Description |
|---|---|
class |
AbstractImmutableList<E> |
class |
AbstractPermutations<E>
Abstract base class for Permutations, common providing standard functions.
|
class |
FlatList<E>
Assumes that inner lists all contain just 1 element, and turns a nested list
into plain list.
|
class |
ImArrayList<E>
ArrayList implementation of
ImmutableList . |
class |
JoinedList<E>
Creates conjunction of two lists.
|
class |
ListWithRemove<E>
Turns immutable list into a list from which elements can be marked as
"removed".
|
class |
MapList<IN1,OUT> |
class |
MapThreadList<OUT,IN1,IN2> |
class |
Outer<T>
creates all possible combinations of one element from each of the provided
lists
|
class |
PermutationsOrderedWithoutReturn<E>
Creates all ordered permutations without return.
|
class |
PermutationsWithoutReturn<E>
Creates all permutation without return (WOR).
|
class |
PermutationsWithReturn<E>
Creates all permutations with return (WR).
|
class |
ShuffledList<E>
makes a shuffled version of provided list.
|
class |
Tuples<T1,T2>
Generate list of Tuple[T1, T2] with all combinations of 1 element from list1
and one from list2.
|
| Modifier and Type | Field and Description |
|---|---|
protected ImmutableList<E> |
AbstractPermutations.drawlist |
| Modifier and Type | Method and Description |
|---|---|
ImmutableList<E> |
PermutationsWithReturn.get(java.math.BigInteger index) |
ImmutableList<E> |
PermutationsWithoutReturn.get(java.math.BigInteger index) |
ImmutableList<E> |
PermutationsOrderedWithoutReturn.get(java.math.BigInteger index) |
ImmutableList<T> |
Outer.get(java.math.BigInteger index) |
| Constructor and Description |
|---|
AbstractPermutations(ImmutableList<E> list,
int n)
all permutations of a given list, drawing n items from the list
|
FlatList(ImmutableList<ImmutableList<E>> list)
gives a list of the form [a1,a2,...,an]
|
JavaList(ImmutableList<E> list) |
JoinedList(ImmutableList<E> list1,
ImmutableList<E> list2) |
JoinedList(ImmutableList<E> list1,
ImmutableList<E> list2) |
ListWithRemove(ImmutableList<E> list) |
MapList(Function<IN1,OUT> f,
ImmutableList<IN1> list1)
creates a list [f(a1), f(a2) ,.
|
MapThreadList(Function2<IN1,IN2,OUT> f,
ImmutableList<IN1> list1,
ImmutableList<IN2> list2)
creates a list [f(a1,b1), f(a2, b2) ,.
|
MapThreadList(Function2<IN1,IN2,OUT> f,
ImmutableList<IN1> list1,
ImmutableList<IN2> list2)
creates a list [f(a1,b1), f(a2, b2) ,.
|
Outer(ImmutableList<T>... lists) |
PermutationsOrderedWithoutReturn(ImmutableList<E> list,
int n) |
PermutationsWithoutReturn(ImmutableList<E> list,
int n) |
PermutationsWithReturn(ImmutableList<E> list,
int n) |
ShuffledList(ImmutableList<E> l) |
Tuples(ImmutableList<T1> list1,
ImmutableList<T2> list2)
contains all possible tuples with first element from list1 and second
from list2
|
Tuples(ImmutableList<T1> list1,
ImmutableList<T2> list2)
contains all possible tuples with first element from list1 and second
from list2
|
| Constructor and Description |
|---|
FlatList(ImmutableList<ImmutableList<E>> list)
gives a list of the form [a1,a2,...,an]
|
| Modifier and Type | Class and Description |
|---|---|
class |
SessionConfigurationList
a list of
SessionConfiguration s for running. |