Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

The ghost of Labview

I am running a C based appplication on a Mac that uses DAQmxbase. I am suddenly getting a message when the application starts that

 

"Labview could not determine the available disk space on volume "blank." To avoid this message in the future, you can disable this checking in the Preferences dialog under Performance and Disk."

 

This is pretty weird message given that Labview isn't installed. And why does ghost Labview care about how much disk space I have? For the record, it's multiple gigabytes.

0 Kudos
Message 1 of 6
(3,447 Views)

Hey Mauricev,

 

That is definitely odd. Could you please tell me more about your application? Which version of MAC OS and DAQmx Base are you using? What exactly do you do before the message comes up?

 

Thanks!

Regards,
Efrain G.
National Instruments
Visit http://www.ni.com/gettingstarted/ for step-by-step help in setting up your system.
0 Kudos
Message 2 of 6
(3,425 Views)

It will also be useful if you tell me which programming environment are you using.

 

Regards,

Regards,
Efrain G.
National Instruments
Visit http://www.ni.com/gettingstarted/ for step-by-step help in setting up your system.
0 Kudos
Message 3 of 6
(3,421 Views)

Hey mauricev,

 

Does this also happen when you run one of our shipping examples?

Regards,
Efrain G.
National Instruments
Visit http://www.ni.com/gettingstarted/ for step-by-step help in setting up your system.
0 Kudos
Message 4 of 6
(3,352 Views)

One thing to note, NI-DAQmx Base is built in LabVIEW, so it requires the LabVIEW Runtime Engine in order to function, much in the way that .NET executables require the .NET Runtime Engine.  Thus, when you install NI-DAQmx Base, you install the LabVIEW runtime engine as well.

 

As to why you are getting these messages from the LabVIEW RTE however, that is outside my expertise.

 

Regards,

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
Message 5 of 6
(3,350 Views)

The problem turned out to be system wide. The user could not type in the Finder, so I ran a program called Onyx, which cleans up cruft that builds up over time. This apparently left a little cruft behind such that it made the OS think the boot drive had no space left. I ran a newer build of Onyx and this problem disappeared. The system is now working, including being able to type in the Finder.

 

Anyway, you may want to change the dialog message to be more sensible. The programmers probably didn't expect the runtime engine would run outside of the Labview environment.

0 Kudos
Message 6 of 6
(3,276 Views)