Multifunction DAQ: NIDAQmx 7.4 with Borland 6 C++ Builder. While the NI-DAQmx drivers are officially supported in the Borland C++ compiler, some customers have had success using the DAQmx import libraries that get installed with CVI support. NI-DAQmx 8.3 and Traditional NI-DAQ (Legacy) version 7.4.1 support Windows 2000/XP. NI-DAQmx 8.3 supports PharLap only with the LabVIEW Real-Time Module 7.1 and later. Measurement Studio requires Visual Studio.NET 2003, which requires Windows 2000/XP.
Hi @ allwe have a problem during the installation of NI-DAQmx 7.4 on our Windows XP system, showing the following error message: K: NIInstallers trunk 1.2.1 src UberInstaller UberInstaller.cpp(1118): IInstallerError 10009Fatal Error. Unable to create temporary file.Unable to copy original D: suppfiles niresdeu.dll to C: DOCUME1 de9adm01 LOCALS1 Temp nii53.tmp.Windows Error Windows Error 999: Fehler beim Einlagern einer Speicherseite. There is a chance that you have received a bad driver CD.
Please download NI-DAQmx 7.5 or 8.0 and run this installer. I would recommend using NI-DAQmx 8.0 but as it doesn't support some older devices anymore 7.5 might be a better option for you, depending which hardware you use. Please refer to the corresponding readme files. Best regards, Jochen Klier National Instruments Germany.
Hello, I am using the NI PCI 6225 M series DAQ board with NIDAQmx 7.4 driver. Hi Olyvia, While the NI-DAQmx drivers are officially supported in the Borland C compiler, some customers have had success using the DAQmx import libraries that get installed with CVI support. I'm not sure if you have seen the KnowledgeBase article (which I think you may have since you are able to get thigns working in), but that is a good starting point.
Also, a couple of other customers have had success and posted their tips in discussion forum thread. This is all with DAQmx 7.5 and 8.0 though, there may be some differences. Hello wuducookie, It sounds like the error might be caused because of the calling convention used by your compiler. The two different calling conventions are stdcall and cdecl.
The difference between the two is that in the cdecl calling convention, the called function is responsible for cleaning up the stack, while in the stdcall calling convention, the calling function is responsible for cleaning up the stack. Try changing this setting in your compiler to see if it fixes the errors. Just a thought.
Applications Engineering. Wuducookie, DAQmx 8.0 does not officially support, nor has been tested with Borland C. So though it may be possible to use some of the techniques mentioned in previous posts to get it to work, it is not something that DAQmx 8.0 was designed to do. Is there any particular reason that you need to use Borland C?
There may be some other options that would suit your needs. Let us know what your end goal is, and what you need from your programming environment and we may be able to offer some other options for you. Regards, -GDE.