exe doesn't work

[analog]

Hi,
I have a .exe file (that has been known to work for over a year now) that doesn't work on my laptop, Pentium III. The .exe works on two other Pentium IV PC's. The two desktops have GPIB cards, and the laptop has USB-to-GPIB cable. I have tested the USB-to-GPIB, and it works, I can communicate with all instruments. The .exe file works in the beginning, it opens a spreadsheet, then an error message will pop up "*.exe has encountered a problem and needs to be closed. Sorry for any inconvenience. Please don't get confused this post with the other post that I had, which is about the same error message except, the other one happens at the end, when everything is done; this one pops up when the program is about to start taking data.
Thanks.

[Brian_Powell]

You don't really provide a lot of information, so I think we all would like to ask a few followup questions...

* How is the .exe built? Is it an executable you made with LabVIEW?

* Is the USB-to-GPIB cable an NI product? If so, which model?

* What versions of NI software are you using?

* Assuming you are using LabVIEW, does it work in the development system, or just as an .exe?

* Have you done anything to try to debug the .exe? E.g., to try to narrow down exactly what operation causes the crash?

Brian

[analog]

Yes, it's an executable that I made with LabView. The USB-to-GPIB is not an NI product, but it works fine, I was able to communicate with instruments just fine. I am using LabView 7.0 and the Runtime engine is 7.0 also. The application works in the development system and as an exe on my desktop, and it works on the other desktop as an .exe file (the other desktop only has a runtime engine installed). I installed LabView evaluation this morning to my laptop just to see if it would run in the developement system. When I ran it, I get this message: "LabView 7.0 Evaluation has encountered a problem and needs to close. Sorry for any inconvenience." The two desktops are Pentium IV, the laptop is Pentium III, all of them use windows XP.

[Brian_Powell]

This error is a little troubling, but perhaps unrelated.

Perhaps you could add code to your VIs to log what it is doing, to try to narrow down where the crash is occurring.

How do you communicate with the GPIB? Are you using third party VIs? How are they implemented? Have you tested the USB-to-GPIB device on the laptop, or just on your desktop? Are there pieces that you need to deploy to the laptop to make it work?

Brian

[SVences]

Hello �

Do you have VISARC in the directory that has the executable? Do you have the VISA32.DLL or VISA.DLL in the Windows\system directory? Those would be the first two things to check.

S Vences
Applications Engineer
National Instruments

[Brian_Powell]

The "visarc" file is not needed with an executable; it is only needed when developing applications that use VISA.

Are you using VISA functions, or are you using a 3rd party interface to the GPIB controller?

Brian

[analog]

I am using VISA, and I have Visa32.dll in my system32 folder.

[analog]

where can I get visarc?

[Brian_Powell]

If you are using NI-VISA, then it gets installed into the LabVIEW "resource" directory by either the LabVIEW installer or the Driver CD installer--I'm not sure which.

If you are not using NI-VISA, I'm not sure what happens.

Brian

[analog]

Hi,
I just now installed the full LabView on the laptop, and the VI always work. But the exe still crashes for some reason. The application first communicates with a DG2040 data generator. When I ran the application exe, it crashes before even communicate with the instrument. I took part of the application out and made another exe (right after it communicates with the DG2040) and it works fine. So I can't tell what the problem is. Can it be possibly the exe is taken up more memory to run then the VI itself, and that causes the crash or something?
Thanks.