MacOS X v10.4.2 rejects nipalk.kext v1.91. Any upgrade available?

[BergmannH]

After installation of "NI-DAQmx_Base_1.5.0f2.mpkg" for MacOS X version 10.4.2 the OS rejects the system extension "nipalk.kext". Therefore starting any coinstalled National Instruments application becomes closed automatically.
Is there any update available?
Many thanks for your support!

Sorry for posting this question first to the "Solution Forum".

Although there was the answer given:

"Having said that, NI-DAQmx Base 1.5.0f2 should work with MacOS X ver. 10.4.2"

...the problem still persitst even after a reinstallation attempt. May be the problem occured because there was not yet any NI device really attached, because my new board was not yet delivered. But even in this case the software should not react this way. Some more friendly answer should display the cause of rejection.
I have still doubts whether the "NI-DAQmx Base 1.5.0f2" cooperates with "MacOS X ver. 10.4.2".
Many thanks for your support!

[Norbert_B]

BergmannH,

that's weird. the problem should not be connected to missing hardware since all drivers from NI should be installed before the hardware is inserted.
Could you provide some more infos on your system?

Norbert B.

Message Edited by Norbert B on 12-07-2005 03:17 AM

[BergmannH]

Many thanks for your care!
I attached the screen shot of the message (in German).
If you could provide me a direct eMail address, I could send you the XML collection prepared by the System Profiler. This I do not want to post to the public.
If you want more specific information, please tell.

Best regards,
Harald Bergmann

[Norbert_B]

Harald,

well, it seems that the MAC-world is a bit (a huge bit!) different than the world of windows. during my investigation, i found the following installation instruction:

INSTALLER NOTES

Install your hardware first before installing the driver software.

To install NI-DAQmx Base, run NI-DAQmx_Base_1.5.0f2.mpkg.

The installer performs the following:

  1.  Installs NI-VISA.

  2.  Installs all needed shared object files and documentation for supported PCI/PXI hardware.

  3.  Installs shared tools for device detection and configuration.

  4.  Installs LabVIEW 7.0, 7.1, and/or C API functionality.

  5.  Installs USB device support

So it also seems that your first suspicion, that the issue could be connected to missing hardware, could be very true.
Another point i am thinking of: Which version of LV do you have installed on the system?

Norbert B.

Message Edited by Norbert B on 12-08-2005 01:55 AM

[BergmannH]

Hello Norbert,

many thanks for your successful search. Although the message is not too friendly, your search results tells that there is not really a bad behaviour and I am full of hope that everything shall work fine.
Your shortcut LV means "LabView"? Sorry I shall not use LabView but the driver API via own software.


Best regards,
Harald Bergmann

[Norbert_B]

Harald,

since the DAQmx Base is a pure LabVIEW-program, you will need the LabVIEW-RunTime Engine (RTE) to use DAQmx Base. You can use the driver in your own software, but you will always need the LV RTE to run the application..... i suggest you should download the LV RTE for MacOS here.

Norbert B.

[Norbert_B]

Harald,

well, well, i am a bit hastily lately it seems....
the info about DAQmx Base is true, but you do not have to install the RTE manually. the driver installs all neccessary parts of the RTE (fitting version) on his own, so you do not have to download it..... so, in general, it should work if the hardware is in the PC.

Norbert B.

[BergmannH]

Hello Norbert,

now the board has arrived. Trying with installed hardware resulted to a correct operation only after complete deinstallation and reinstallation of the driver software. But at least everything is OK and as expected.
NI may want to think about a more intuitive and graceful method of hardware access.
Many thanks for your help!

Best regards,
Harald

[_Chris]

Here is the explanation and the fix.
MacOSX 10.3.x did not care much about the owner and group of startup extension such as nipalk.kext
MacOSX 10.4. enforce correct owner and group settings for "kext" which is good!

you have to fix this by changing the "nipalk.kext" owner and group using the unix command chown
I take absolutly no responsability if this fail of terminate your computer. You are typing the following
commands in the terminal thus you are responsible of your fingers typing.

cd /System/Library/Extensions
ls -all

you should see something like

...
drwxr-xr-x 3 admin wheel 102 Mar 23 2004 nipalk.kext
...

then change the owner by typing (you'll have to enter an admin password)
the -R if for recusive since a "kext" is a actually a "folder" and not a file

sudo chown -R root:wheel nipalk.kext

do a ls -all and check that the change as been made correctly

restart your machine