Does VISA still work after building an application for multiple OS's

[daimyo505]

I am building a VISA application for Windows 2000 but program with labview installed on a Windows NT 4.0 machine. When I test the application with the NT machine everything works fine, I can use the COM1 port. Yet after building the application, my program as the top-level VI, VISA configure serial port as a dynamic VI, and _visa.llb as a support file. The application, once installed, will not let me choose a communication port from the VISA drop down box. The run-time engine is installed. Is there a problem with crossing operating systems or do I need to include something else in my build? Help is kindly appreciated.
Thanks
Brett

[shoneill]

You need to make sure VISA is installed and properly configured on the new computer. This is NOT a default part of the run-time as far as I know. Just copying the VISA.llb will not configure the VISA communication protocoll on the new computer.

Hope this helps

Shane.

[Dennis_Knutson]

If all that you are using is serial, then when you create the installer, click the Advanced button and check the Serial Support Box. This will include a much smaller version of VISA that can only be used for serial ports.

[daimyo505]

Thanks for the suggestions, yet I am still having trouble. My version of labview, 6.1, doesn't have a 'serial support box' check box.
I have installed VISA 2.6 on the computer I am trying to run the executable on. I am able to communicate with the instrument with the 'open session'. Yet when I trying to run my program now I get 'instruction at [ x ] reference memory at [ x ] and could not be read.' The program crashes the minute I start it. I have found that the 'VISA resource name' control is what is causing that problem. I believe I have VISA configured properly because I can communicate with the instrument through the comm port I want to use.
If you have more suggestions I would be ever so greatful again for them.
Thanks,
Brett

[waldemar.hersacher]

Dear Brett,

there is an issue with VISA 2.6 and the resource name to take into consideration when you only have installed the VISA runtime.
In the development system COM1 will be translated to the native resource name ASRL1::INSTR. This is not done in the runtime. You must use the native resource name if you have only the LV and VISA runtime installed.

Waldemar

[JohnM 64]

Hi Brett,

One thing to keep in mind is to be sure that the VISA Resource Name that is used in the program matches with the name of the COM port on the new computer. If you have given it an alias on the original computer, you will have to either give the port on the computer with the executable that same name, or change the input to be the default name (COM1). Is VISA 2.6 the driver version used to create the program? You do not actually need all of NI-VISA installed on that machine, just the VISA Run Time Engine for the same version that the executable was built with, but it is wise to use the same versions of the driver on both computers. Hope this helps!

John M
Applications Engineer