NIPALK message

[Yuliya Vladimirov]

Hi,
I am having a very similar problem as I found that somebody else had on the discussion forum. But, no one answered, so I am posting my own question, in hopes that somebody who knows about this stuff will help. I am also using Labview6i, Windows 98, and a variety of hardware. We have a PCI-MIO-16E-1, DIO, GPIB, and a few serial port devices.
I added a new version of code onto the test station, basically made a few non-hardware related changes, and all of a sudden my new code doesn't work. Although the old code does. But the two versions are almost the same. I even tried it on a different computer using the same set how hardware and OS, but I am still getting a blue screen and an error message.
The message I get looks like this:"An exception
00 has occured at 0028:C29A440 in VxD NIPALK(01)+ 00000360. This was called from 0028:C29C7740 in VxD NIPALK+00023660. It may be possible to continue normally". It happens right after a reboot of the PC. Sometimes it goes away after the first run, but most of the time it doesn't. I've also noticed that it start to hick up at places that Aquire Data, specifically the tests that use AI Aquire Waveform.
Any help or suggestions would be greatly appreciated.

Thanks,
Julia

[JustinBritten]

Julia,

You say that you have made "a few changes" to the software and that now it doesn't work, but the old program does. You also state that the two versions are "almost the same." I suppose my first question would be what has changed? It seems to me that you added some code which is causing this crash.

What did you add?

Regards,
Justin Britten

[Yuliya Vladimirov]

I changed the user interface, changed a few global vis, but I didn't change anything that talks to the hardware in any way. At one point of time I added a call to a NI dll called lvwutil32.dll, then the code stopped working and was giving me the above error. Later, I removed this dll and all the calls made to it, but I am still getting the same errors.

Julia

[Yuliya Vladimirov]

"EURIKA! I solved the problem! It turned out that I had to upgrade NIDAQ, and it started working again. It works without errors so far, so I hope it will stay this way."