Problem installing LabVIEW 8.2 on Fedora Core 7

[m-s]

Hello,

After an initial abortive experience with installing LabVIEW 8.2 on Kubuntu 7.04, I decided to bite the bullet, reformat the lab machine and install Fedora Core 7 on it. The hope was that since Fedora uses rpm as its packaging format, it might be better suited to handling the installation foibles of LabVIEW.

Well, I was partly right. Things seemed to go normal until LabVIEW install issued the following error messages :

******************************** ERROR ****************************************
* Kernel source in /lib/modules/2.6.21-1.3194.fc7/source does not appear to be
* for the 2.6.21-1.3194.fc7 kernel.
* Ensure that kernel source for the 2.6.21-1.3194.fc7 kernel is installed
* and configured.  Refer to the README file for the product you are           *
* installing for information about configuring your kernel source.            *
******************************** ERROR ****************************************

Now, I did have kernel-devel package installed. Then I remembered reading that LabVIEW has a problem with the new more efficient 4K stacks option of the kernel, which indeed was present in the .config of the default Fedora kernel above. And my own past experience with LabVIEW 7.1 on Debian has taught me that LabVIEW does not respond well to the presence of EXTRAVERSION strings in the kernel Makefile. So, I downloaded kernel 2.6.22 from www.kernel.org, copied the config file for Fedora 2.6.22.1-27.fc7 kernel, ran make xconfig, removed 4K stacks option and compiled. Now when I retried completing my LabVIEW 8.2 installation, I get :

By installing LabVIEW software packages, you agree to the terms of the included
NI Software License Agreement (LICENSE.txt). Type 'v' to view the agreement,
'y' to consent to the agreement, or 'n' to decline the agreement and skip
LabVIEW installation.  [Vynq] y

NOTE: LabVIEW will install by default in /usr/local/natinst/LabVIEW-8.2,
or in the natinst/LabVIEW-8.2 subdirectory if you specify an alternate location.

Preparing for installation...
C runtime library (glibc) version: 2.6.
Red Hat Package Manager (RPM) version: 4.4.2.
Please indicate whether you would like to install the following components:

All available LabVIEW packages have already been installed or cannot
be installed due to package conflicts.


Package niexfinder-base-1.0-7 is already installed.

Would you like to install the LabVIEW web browser plugin? [Ynq] y

Checking for Mozilla/Firefox/Netscape 6+ installation...
Copying plugin to /usr/lib/mozilla/plugins

LabVIEW package installation complete.

LabVIEW installation complete.

================================================================================

Beginning hardware driver installation.

Depending on your system configuration, some drivers may require you to reboot
after installation before you can access the driver.

Note that some drivers may require the Linux kernel source to be installed.
This can be found on your Linux distribution install CD as a package called
'kernel-source'.  Make sure to install the version matching the kernel you are
running.  If you need to install kernel source, press 'q' to abort installation,
and re-run this install script after you have installed the kernel source.


Would you like to install NI-VISA (4.0) for GNU/Linux? [Ynq] y

  **********************************
  * NI-VISA 4.0.0 for Linux/x86
  **********************************

rpm 4.4.2 will be used with a default installation path

National Instruments products support the following Linux distributions:
   Mandriva Linux
   SUSE Linux
   Red Hat Enterprise Linux WS
Refer to readme.txt for the latest information at the time of release.
Refer to www.ni.com/linux for the most recent information about Linux
support at National Instruments.

Continue? [Yn] y

Retrieving license agreement.  Please wait...
NATIONAL INSTRUMENTS SOFTWARE LICENSE AGREEMENT (LINUX DRIVER SOFTWARE)
<mega snip>

By installing this software, you are acknowledging acceptance
of the terms of the included license file (LICENSE.txt).

Do you accept the license? [ynq] y       

Searching for installed components ...

Do you wish to install NI-VISA Runtime 4.0.0? [Ynq] y

Do you wish to install NI-VISA Development 4.0.0? [Ynq] y

Do you wish to install NI-VISA Configuration 4.0.0? [Ynq] y

Do you wish to install NI-VISA Server 4.0.0? [Ynq] y

Do you wish to install PXI Services 1.6.0? [Ynq] y

Do you wish to install NI Spy 2.4.0? [Ynq] y

NI-VISA Development 4.0.0 requires CVI Runtime 8.0.
NI-VISA Configuration 4.0.0 requires CVI Runtime 8.0.
This component has been selected automatically.

NI-VISA Runtime 4.0.0 requires NI-ORB 1.5.0.
PXI Services 1.6.0 requires NI-ORB 1.5.0.
This component has been selected automatically.

PXI Services 1.6.0 requires NI-DIM 1.5.0.
This component has been selected automatically.

NI-ORB 1.5.0 requires NI-RPC 3.3.0.
This component has been selected automatically.

NI-VISA Runtime 4.0.0 requires NI-PAL 1.11.1.
PXI Services 1.6.0 requires NI-PAL 1.11.1.
NI-DIM 1.5.0 requires NI-PAL 1.11.1.
NI-ORB 1.5.0 requires NI-PAL 1.11.1.
This component has been selected automatically.

NI-PAL 1.11.1 requires NI-KAL 1.4.0.
This component has been selected automatically.

NI-VISA Development 4.0.0 requires LabVIEW Runtime 8.0.1.
NI Spy 2.4.0 requires LabVIEW Runtime 8.0.1.
This component has been selected automatically.

The following components will be installed using rpm:
  NI-VISA Runtime 4.0.0              5703 KB  (in /usr/local/vxipnp)
  NI-VISA Development 4.0.0          4477 KB  (in /usr/local/vxipnp)
  NI-VISA Configuration 4.0.0         658 KB  (in /usr/local/vxipnp)
  NI-VISA Server 4.0.0                227 KB  (in /usr/local/vxipnp)
  PXI Services 1.6.0                  791 KB  (in /usr/local/natinst/nipxi)
  NI Spy 2.4.0                       2171 KB  (in /usr/local/natinst/nispy)
  CVI Runtime 8.0                    8510 KB  (in /usr/local/natinst/cvirte)
  LabVIEW Runtime 8.0.1             32695 KB  (in /usr/local/lib/LabVIEW-8.0)
  NI-ORB 1.5.0                        459 KB  (in /usr/local/natinst/.nicore)
  NI-DIM 1.5.0                        594 KB  (in /usr/local/natinst/.nicore)
  NI-RPC 3.3.0                        102 KB  (in /usr/local/natinst/.nicore)
  NI-PAL 1.11.1                      1768 KB  (in /usr/local/natinst/nipal)
  NI-KAL 1.4.0                        229 KB  (in /usr/local/natinst/nikal)
Total space required:               58384 KB
Space available:                 12276628 KB

Continue? [Yn] y

******************************** ERROR ****************************************
* Kernel source in /lib/modules/2.6.22/source does not appear to be
* for the 2.6.22 kernel.
* Ensure that kernel source for the 2.6.22 kernel is installed
* and configured.  Refer to the README file for the product you are           *
* installing for information about configuring your kernel source.            *
******************************** ERROR ****************************************

Installation aborted.


Would you like to install NI-GPIB (NI-488.2 2.5.1) for GNU/Linux? [Ynq] n

View the LabVIEW 8.2 Upgrade Notes now? [Yn] n

Installation complete.

I would really appreciate it if Shaun or someone else could point out what is going on. The error message above is obviously wrongly triggered as I compiled 2.6.22 from source myself (which is sitting symlinked to /usr/src/linux in /usr/src/linux-2.6.22).

I do remember that a long time ago there was some issue with LabVIEW 7.1 with respect to the asm_offsets.h file, but I have completely forgotten about that, and assume that LabVIEW 8.2 would have a work around that problem.

My kernel .config (gzipped) is attached, should that help in narrowing down the issue.

[Elizabeth_S]

Hello,

LabVIEW 8.2 runs on Red Hat Enterprise Linux WS 3, SuSE Linux Professional 9.1, and Mandrake Linux 10.0 or later. LabVIEW can run without hardware driver support on any other distributions that provide GNU C Library (glibc, also known as libc.so.6) Version 2.2.4 or later.

1)      Does Fedora Core 7 fit this description? 

2)      Has anyone in the community installed LabVIEW 8.2 on this OS?

Regards,

Elizabeth S.

Applications Engineer

National Instruments

[trallala]

on Mandriva 2007, it works

But couldnt use the serial port.....


"Elizabeth S" <x@no.email> a écrit dans le message de news:
1185208809294-554595@exchange.ni.com...
> Hello,
>
> &nbsp;
>
> LabVIEW 8.2 runs on Red Hat Enterprise Linux WS 3, SuSE Linux Professional
> 9.1, and Mandrake Linux 10.0 or later. LabVIEW can run without hardware
> driver support on any other distributions that provide GNU C Library
> (glibc, also known as libc.so.6) Version 2.2.4 or later.
>
> &nbsp;
>
> 1)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does Fedora Core 7 fit this
> description?&nbsp;
>
> &nbsp;
>
> 2)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Has anyone in the community installed
> LabVIEW 8.2 on this OS?
>
> &nbsp;
>
> Regards,
>
> Elizabeth S.
>
> Applications Engineer
>
> National Instruments

[m-s]

Hello,

    Well, obviously I have read the system requirements for LabVIEW. But thanks for reiterating that fact.

    Fedora Core 7 - does it fit the description ? I daresay it does because it is the basis for future releases of Redhat Enterprise Linux (more cutting edge, nothing more).

    Now, my question was quite, quite specific - why is the LabVIEW installer not able to detect the presence of a properly configured linux kernel along with its source. I have been compiling Linux kernels for close to 5 years now, so I am absolutely certain that the mistake is not at the kernel configuration / compilation end.

    Your comment about lack of hardware support would make sense if the error message indicated that it was unable to compile modules against the installed kernel version because it was too new / it was too old / etc. What we have here is a detection problem, not a kernel mismatch problem. I can always compile an older kernel, but I first need to be certain that LabVIEW installer is capable of finding it.

    So, asking again, what do I need to do to make the LabVIEW installer detect the kernel source tree (or some of its components etc.) ?

Thanks,

[Elizabeth_S]

Hello,

Fedora Core 7 does meet LabVIEW requirements and you should be able to install the software.  According to your installation dialog, you were able to install LabVIEW successfully:

“LabVIEW installation complete”

The problem seems to be when you are installing hardware drivers.  Do you need to use hardware drivers?  You may have better luck installing the most current drivers from ni.com, but they are not supported with your particular distribution. 

What Linux Distributions do National Instruments' Drivers and Software Support?

http://digital.ni.com/public.nsf/websearch/35D2B5E483A001A18625716B005BE464?OpenDocument

Regards,

Elizabeth S.

Applications Engineer

National Instruments

[m-s]

Thanks for your response.

Yes, I do need to use hardware drivers - this is a deployment for a lab - and it needs to be able to control the NI USB or PCI cards that we will plug into it.

I will look up the more current versions of the hardware drivers, but is there a particular order in which they need to be installed ? Like NI-KAL before everything else, etc. ? This could be helpful for me to finish the deployment.

As regards that matrix of supported distributions, it is no doubt helpful as a starting point for those that know nothing about Linux, but what would be more helpful (given that none of the really big linux distros is supported by NI) is if NI could post the kernel versions (at the very least) and kernel configuration files that could help people deploy Labview on the more important distros. This would help both your users and NI ultimately.

Shawn has previously mentioned the instability of the API from version to version as the cause for NI's insistence on older Linux distros. I would submit that these issues could be resolved far more effectively if NI just targeted a particular kernel version (along with a .config file) of its choice for a release and left it to the users to deploy that kernel. NI already does a part of that job by specifying what versions of glibc etc. you need. This would just be a logical completion of that task.

[Shawn B.]

---

I will look up the more current versions of the hardware drivers, but is there a particular order in which they need to be installed ? Like NI-KAL before everything else, etc. ? This could be helpful for me to finish the deployment.

---

Well, I would recommend installing the latest version of NI-KAL first, then the latest version of the driver you require.  If you don't do it in this order it will still probably work, but you may need to run "updateNIDrivers".

Since you are using Fedora Core 7 I would recommend reading the some of the other posts in these forums for Fedora Core 5, 6 and 7.  This one might make things smooth and easy:

Fedora 7 NIDAQmx installer

If you are not using NI-DAQmx, then it will be slightly more complicated.  However since the problems are likely going to be in shared driver components it may work to simply install NI-DAQmx first following the instructions in that post, then the driver you need.  At that point you could uninstall NI-DAQmx.

Shawn B.
National Instruments

[m-s]

Hello Shawn,

Thanks for your suggestion. I downloaded the latest version of NI-KAL

$ ./INSTALL

*****************************************************************************
  NI-KAL Installer Distribution
     version 1.5.0f0 for Linux/x86 32-bit
*****************************************************************************

National Instruments products support the following Linux distributions:
   Mandriva Linux Official
   openSUSE
   Red Hat Enterprise Linux WS
Refer to README.txt for the latest information at the time of release.
Refer to www.ni.com/linux for the most recent information about Linux
support at National Instruments.

Continue? [Yn] y

Checking required install tools...
Checking installer tool versions...
rpm        4.4.2 can be used with a default installation path
tar        1.15.1
Checking dependencies...
glibc      2.6
Unpacking install files to /tmp/nikal-1.5.0f0.install...

NATIONAL INSTRUMENTS SOFTWARE LICENSE AGREEMENT (LINUX DRIVER SOFTWARE)


<mega snip>


By installing this software, you are acknowledging acceptance of the terms
of the included license file (LICENSE.txt).

Do you accept the license? [ynq] y



NI-KAL version 1.5.0f0
is about to be installed using rpm at /usr/local/natinst

Would you like to continue? [Yn] y

Installing NI-KAL version 1.5.0f0...
Pre Installation ..
Preparing...                ########################################### [100%]
   1:nikali                 ########################################### [100%]
Post Installation .
Warning: nikali post installation failed! /tmp/nikaliPostInstall.log follows:
 
Configuring for linux kernel version 2.6.22.
 
********************************* NOTE *********************************
Using kernel headers found in /lib/modules/2.6.22/source.
If this does not correspond to the location of the 2.6.22 headers,
then define KERNELHEADERS in your environment to point to the location
of the kernel headers, define KERNELTARGET as the version of the
kernel for which to compile, and then rerun ./configure.
********************************* NOTE *********************************
 
Kernel has reparent_to_init(): no
Number of arguments for do_munmap(): 3
pte_offset function: pte_offset_kernel()
Levels in page table: 4
Kernel has remap_pfn_range: yes
USB altsetting name: cur_altsetting
Kernel has usb_get_intf(): yes
Kernel has intf_cache member in usb_host_config: yes
Kernel has ep[] members in usb_device: yes
Kernel exports usb_set_configuration(): no
Units of USB_CTRL_GET_TIMEOUT: msec
Kernel has owner member in usb_driver: no
Kernel has put_page_testzero(): yes
Kernel has mutex method: yes
Kernel has kthread: yes
 
Storing configuration in Makefile.in
If the values stored are incorrect they can be changed before running make.
 
Uninstalling NI-KAL (nikal): done
/bin/rm -rf objects
Updating NI-KAL:
 NI-KAL update failed.
 
/bin/cp nikal.c objects/nikal.c
/bin/cp nikal.h objects/nikal.h
make -C /lib/modules/2.6.22/source SUBDIRS=/usr/local/natinst/nikal/src/objects modules
make[1]: Entering directory `/usr/src/linux-2.6.22'
  CC [M]  /usr/local/natinst/nikal/src/objects/nikal.o
/usr/local/natinst/nikal/src/objects/nikal.c:34:26: error: linux/config.h: No such file or directory
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_registerPCIDriver’:
/usr/local/natinst/nikal/src/objects/nikal.c:2667: warning: ignoring return value of ‘pci_register_driver’, declared with attribute warn_unused_result
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_buildControlURB’:
/usr/local/natinst/nikal/src/objects/nikal.c:3422: warning: passing argument 7 of ‘usb_fill_control_urb’ from incompatible pointer type
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_buildBulkURB’:
/usr/local/natinst/nikal/src/objects/nikal.c:3447: warning: passing argument 6 of ‘usb_fill_bulk_urb’ from incompatible pointer type
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_buildInterruptURB’:
/usr/local/natinst/nikal/src/objects/nikal.c:3498: warning: assignment from incompatible pointer type
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_buildIsochronousURB’:
/usr/local/natinst/nikal/src/objects/nikal.c:3539: warning: assignment from incompatible pointer type
/usr/local/natinst/nikal/src/objects/nikal.c:3644:48: error: macro "INIT_WORK" passed 3 arguments, but takes just 2
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_usbClearHaltAsync’:
/usr/local/natinst/nikal/src/objects/nikal.c:3643: error: ‘INIT_WORK’ undeclared (first use in this function)
/usr/local/natinst/nikal/src/objects/nikal.c:3643: error: (Each undeclared identifier is reported only once
/usr/local/natinst/nikal/src/objects/nikal.c:3643: error: for each function it appears in.)
/usr/local/natinst/nikal/src/objects/nikal.c: In function ‘nNIKAL100_reserveInterrupt’:
/usr/local/natinst/nikal/src/objects/nikal.c:3946: warning: ‘deprecated_irq_flag’ is deprecated (declared at include/linux/interrupt.h:66)
/usr/local/natinst/nikal/src/objects/nikal.c:3946: warning: ‘deprecated_irq_flag’ is deprecated (declared at include/linux/interrupt.h:66)
/usr/local/natinst/nikal/src/objects/nikal.c:3946: warning: passing argument 2 of ‘request_irq’ from incompatible pointer type
make[2]: *** [/usr/local/natinst/nikal/src/objects/nikal.o] Error 1
make[1]: *** [_module_/usr/local/natinst/nikal/src/objects] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.22'
make: *** [objects/nikal.ko] Error 2
 
ERROR: make of nikal kernel module failed, not installing kernel module.
   updateNIDrivers should be called again after fixing the problem.
   Logging failure...
   Include the file /tmp/niSystemReport.out.gz when contacting
   National Instruments for support.
 
.

FOR PATENTS COVERING NATIONAL INSTRUMENTS PRODUCTS, REFER TO
THE PATENTS.txt FILE ON /media/iso2 AND/OR
www.ni.com/patents

NI-KAL Installation completed with errors.

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

It does appear that the kernel version has some changes that NI-KAL did not expect. Could you suggest an older kernel for which you know that NI-KAL definitely does compile ? I might have better luck with that.

Thanks.

[Shawn B.]

Yep, that is why I pointed you to the other Fedora Core forum posts. 

NI-KAL 1.5 will only compile on kernels 2.6.18 and older.  There are patches that users have created on the other fedora core forum posts that will make it compile on newer kernels, but I can't vouch for their sanity.  Your other option of course is to keep you eyes peeled for a new version of NI-KAL that will likely support newer kernels.

Shawn B.
National Instruments

[m-s]

I took your advice, looked over the NI-DAQmx / FC7 page, decided that it might or might not apply to me (I am going to be using only IEEE 488.2 / serial ports / VISA), so pulled down kernel 2.6.18, and compiled it. Ran the labview installer program - again the older KAL version (1.4) refused to see thekernel sources. Then I installed 1.5.0f0.

NI-KAL :
*****************************************************************************
  NI-KAL Installer Distribution
     version 1.5.0f0 for Linux/x86 32-bit
*****************************************************************************
<snip>
Continue? [Yn] y
Checking required install tools...
Checking installer tool versions...
rpm        4.4.2 can be used with a default installation path
tar        1.15.1
Checking dependencies...
glibc      2.6
Unpacking install files to /tmp/nikal-1.5.0f0.install...
<mega snip>

NI-KAL version 1.5.0f0
is about to be installed using rpm at /usr/local/natinst

Would you like to continue? [Yn] y

Installing NI-KAL version 1.5.0f0...
Pre Installation ..
Preparing...                ########################################### [100%]
   1:nikali                 ########################################### [100%]
Post Installation ..

FOR PATENTS COVERING NATIONAL INSTRUMENTS PRODUCTS, REFER TO
THE PATENTS.txt FILE ON /media/iso2 AND/OR
www.ni.com/patents

NI-KAL Installation completed successfully.

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

Then I tried the labview installer again, hoping that at least VISA could get installed. It asked me to reboot at the end of the same set of questions posted earlier in the thread.

sort: open failed: +0: No such file or directory
Installing selected components ...
Preparing...               ####################################################################### [100%]
        package nikali-1.5.0-f0 (which is newer than nikali-1.4.0-f0) is already installed
Running NI-KAL Post Installation Script ...
***********************************************************************
* A reboot is required before attempting to use the NI-VISA software. *
***********************************************************************
Would you like to reboot now? [yes|no]                                      
-------------------
While rebooting for new software is a novel experience, I rebooted without demur. Ran through the procedure - and it asked me to reboot yet again ! Changed tack, decided to install the latest VISA driver manually.
  **********************************
  * NI-VISA 4.1.0 for Linux/x86
  **********************************
rpm 4.4.2 will be used with a default installation path
<mega snip>
Searching for installed components ...

find: /tmp/nivisa.install/nivisa: No such file or directory
Do you wish to install NI-VISA Runtime ? [Ynq] y
expr: syntax error
find: /tmp/nivisa.install/nivisa: No such file or directory
Do you wish to install NI-VISA Development ? [Ynq] y
expr: syntax error
find: /tmp/nivisa.install/nivisa: No such file or directory
Do you wish to install NI-VISA Configuration ? [Ynq] y
expr: syntax error
find: /tmp/nivisa.install/nivisa: No such file or directory
Do you wish to install NI-VISA Server ? [Ynq] y
expr: syntax error
Do you wish to install PXI Services 1.6.0? [Ynq] y
Do you wish to install NI Spy 2.5.0? [Ynq] y
<snip>
NI-PAL 2.0.0 requires NI-KAL 1.5.0.
NI-KAL 1.5.0 (f0) already installed.
NI-VISA Development  requires LabVIEW Runtime 8.2.1.
NI Spy 2.5.0 requires LabVIEW Runtime 8.2.1.
sort: open failed: +0: No such file or directory
LabVIEW Runtime 8.2.1 (1) is newer than installed version 8.2 (1).
LabVIEW Runtime 8.2.1 will be installed over the existing version.
The following components will be installed using rpm:
  NI-VISA Runtime                       1 KB  (in /usr/local/vxipnp)
  NI-VISA Development                   1 KB  (in /usr/local/vxipnp)
  NI-VISA Configuration                 1 KB  (in /usr/local/vxipnp)
  NI-VISA Server                        1 KB  (in /usr/local/vxipnp)
  PXI Services 1.6.0                  791 KB  (in /usr/local/natinst/nipxi)
  NI Spy 2.5.0                       2280 KB  (in /usr/local/natinst/nispy)
  CVI Runtime 8.0                    8554 KB  (in /usr/local/natinst/cvirte)
  LabVIEW Runtime 8.2.1             38472 KB  (in /usr/local/lib/LabVIEW-8.2)
  NI-ORB 1.6.0                        463 KB  (in /usr/local/natinst/.nicore)
  NI-DIM 1.6.0                        584 KB  (in /usr/local/natinst/.nicore)
  NI-RPC 3.3.1                        112 KB  (in /usr/local/natinst/.nicore)
  NI-PAL 2.0.0                       1840 KB  (in /usr/local/natinst/nipal)
Total space required:               53100 KB
Space available:                 12130268 KB

Installing selected components ...

Preparing...                ########################################### [100%]
   1:nipali                 ########################################### [ 13%]
   2:labview82-rte          ########################################### [ 25%]
sort: open failed: +2: No such file or directory
sort: open failed: +2: No such file or directory
ln: creating symbolic link `liblvrt.so' -> `': No such file or directory
ln: creating symbolic link `liblvrtdark.so' -> `': No such file or directory
   3:nirpci                 ########################################### [ 38%]
   4:niorbi                 ########################################### [ 50%]
   5:nidimi                 ########################################### [ 63%]
   6:nipxirmi               ########################################### [ 75%]
   7:nicvirte               ########################################### [ 88%]
   8:nispyi                 ########################################### [100%]
error: unpacking of archive failed on file /usr/local/natinst/nispy/nispy;46a7ed1d: cpio: read
Running NI-PAL Post Installation Script ...
Running NI-RPC Post Installation Script ...
Running NI-ORB Post Installation Script ...
Running NI-DIM Post Installation Script ...
Running PXI Services Post Installation Script ...
Installation completed successfully.

While I am an optimist, all these error messages make me nervous. How do I confirm that the process of installation did actually work ?