what versions of NI-VISA are compatible with CVI 7.1.1

[RobertoBozzolo]

Hi Martin, I understand why you want to maintain VISA structure.

A simple little suggestion can be to investigate in event registry in search of informations recorded on system crashes: you could possibly find some additional information that is not reported in the error message you have posted and may help you to narrow the range of possible causes.

[MJF]

Nick,

I just tried this on a brand new machine that I just got and the only thing I installed beyond what our IT group installs as standard software is CVI 7.1

I ran my program and got the following error:

 FATAL RUN-TIME ERROR:   Unknown source position, thread id 0x00000A78:   A non-debuggable thread caused a 'General Protection' fault at address 0007DFEE.

I've attached screen shots of the info from the Loaded Modules command.

I don't see anything in the address range in the error message.

Anna,

I have not yet had a chance to try any of the VISA examples, I have to go install them.

Will update when I do.

[nickb]

Hey Martin - 

Just to clarify - does the GPF happen before execution begins, or can break into the CVI debugger and find a particular line that will throw the GPF upon stepping over?

Also - you said the only thing beyond what IT installs was CVI 7.1.  Were you still doing VISA calls, or is VISA out of the picture at this point?

NickB

National Instruments

[MJF]

Nick,

The GPF occurs (I believe) before execution of the application begins (evidenced by no variable information in the variable window after I hit the Break button in the error window).

I installed CVI on a new machine, our IT group does not do that for us. I installed ONLY CVI 7.1.1 and attempted to compile and execute the program I was writing. I did not install VISA but it compiled and linked OK. I tried to execute it and got the GPF as noted in my last post.

I didn't think it would compile and link without installing VISA but it did. I then installed VISA afterword, regardless, I get the same result no matter what I do if I include even a single function out of the VISA library.

This is why this is so frustrating. I can't determine why this is happening or what is unique about our software environment here. Our IT group picks and chooses which bug fixes they deploy from Microsoft and they control a lot of software configuration and security things that I have no insight into. The fact that it occurs on multiple machines on our network and one off the network is very frustrating.

I'm going to try another approach and build a release DLL with the VISA stuff in it. What I need to do isn't particularly complicated or challenging so I can get away with doing that and using NI-Spy for snooping into what is going on. I just hope that third party VISA based drivers I need will behave.