I have a large vision based (IMAQ) application that I developed as an executable for one of my customers using LV v6.1. The software uses the serial port to communicate with a microscope stage and has a PCI1409 frame grabber card. We are using Windows XP computers. The customer has a CD with all the necessary software to create a working system, their "Golden Master". They have used the Golden Master many times to create new systems. Last week, they installed the software on a new PC (it ran fine) then gave the PC to me to use in converting the development version of their software to LV v7.0. I installed LV, IMAQ, NI-IMAQ, etc. and did the conversion to v7.0. The only code changes required involved the different IMAQ image format. The software ran fine under the development version, and I was quite pleased.
Then, I started up the LV v6.1 executable that was originally installed by my customer. The executable opened OK and put up a few images, but then crashed and requested to send an error report to Microsoft. My customer's LV v6.1 program is now inoperable on the new computer. Something was changed when LV 7.0 was installed. I tried installing an earlier version of NI-IMAQ with no success. Hoping to solve the problem, I created an executable in LV v7.0. It also crashed (i.e. LVRT.dll crashed) after behaving in the same manner as the LV v6.1 executable. However, the LV v7.0 development version of the program runs fine with no problems. My customer then reclaimed their computer and uninstalled all of the NI software that I had installed. Next, they reinstalled the software from their Golden Master CD and started up the LV v6.1 executable. It crashed as described above. Now, that computer will not run their software successfully. It probably would if the hard disk was reformatted and Windows was reinstalled, but we have not done that yet. We did try some of the special tools NI has for purging NI software from a system, etc. I tried running the LV v6.1 executable on my development computer (contains LV v7.0). It crashed as described above. Next, I created a LV v7.0 executable on my development computer and it crashed as described above. So, I'm now in the position where I can not upgrade their software to LV v7.0 and create an executable. NI tech support has no clue what the problem is, nor do I. This software contains hundreds of VIs so troubleshooting will be extremely difficult and time consuming. For now I'm forced to use LV v6.1 to make any software enhancements to my customer's code. Any ideas why this happened. I sure would like to see some debugging tools made available for troubleshooting a LV executable. If I could tell which VI, or even which part of the LV code (e.g. IMAQ or VISA), was causing the crash it would be very useful. Lewis Drake Process Automation Corporation Belle Mead, NJ 908 359-1011 www.processauto.com
