Hi, after waiting for a week for a callback of NI germany, maybe I can get some help in here.
I'm develloping a System with VC 6 SP4 on a NT 4 SP6 System. There are 3 NI cards installed in the system.
PCI 6032E as device #1 PCI DIO 96 as device #2 PCI 6703 as device #3
I':m using NI-DAQ 6.9.1. I'd made an OCX with ODBC drivers and NI DAQ Driver linked. this OCX is used by an acoustic measurement system as the container when the DAQ driver is loaded and the other measurement system is the container NT crashes with a bluescreen displaying NIPALK.SYS in the first line. When I do a remote debugging session with WinDbg, the last trace lines before the bluescreen were.
When I reduce the OCX to ODBC and NIDAQ calls and run it in the VC Testcontainer. the following symptoms apear. The OCX is loaded and work correctly, but when I try to run NI MAX and try to access any device I got a MessagBox like ... initializing nipalu.dll failed.. the text is translated from german NT so the text may differ..
Hi Erin .... > > You can download the patch from: > > http://digital.ni.com/softlib.nsf/16a19f446db24ce5862568d2005b971c/960515e73 2471626862569d8006ee1d3?OpenDocument > > Hope this resolves your problem. .... I use NI DAQ 6.9.1 (the patch is related to 6.8.1 and 6.9.0) and I'd tried this before and it doesn't work.
Maybe I have to check the rebasing option. Bur I hope I get a solution from NI.
This patch also applies to 6.9.1. All it does is changed the preferred load address of the nipalu.dll. Do you actually get an error message that applying the patch fails? If it fails, I would suggest determing the load addresses of all .dlls used by your applications and rebasing nipalu.dll to load to an unoccupied location.
Erin B. schrieb in im Newsbeitrag: 506500000005000000783E0000email@example.com... > This patch also applies to 6.9.1. .... NI Germany told me it doesn't ! But I'd tried it before and get no error message but the bluescreen appears again. ... > All it does is changed the > preferred load address of the nipalu.dll. Do you actually get an > error message that applying the patch fails? If it fails, I would > suggest determing the load addresses of all .dlls used by your > applications and rebasing nipalu.dll to load to an unoccupied > location. .... maybe I have to try this.