How do I build an application that will run without being installed?

[Obelix]

It was running under 98. I do still have the serpdrv but it doesn't fix the problem. I still got no errors, and serial wouldn't talk. I did go in and grab visa32.dll and add it. It then complained about not having and NiViSv32.dll. I thought this was good cause that would mean it was trying to use the visa32.dll, but when I added NiViSv32.dll it all went quiet again and still didn't work. There's got to be a file or 2 that I still don't have. Any suggestions on what to try?

Oh, the rest of the program works fine, btw.

Thanks for your help guys.

[AnalogKid2DigitalMan]

Does the program include proper use of Error clusters? That is, all code modules are strung together via error in/error out controls/indicators and errors are trapped and reported. Seems like some sort of error (either via internal code or LabView's error trapping) should be popping up in the serial routines to assist troubleshooting.

I believe there is a specific file to add in the build (for certain prior to VISA), but I never have used VISA yet.

Do you have the latest version VISA runtime engine driver installed? See:
http://digital.ni.com/softlib.nsf/websearch/C0CDC738994FCBC886256EEB004E9BB3?opendocument&node=132060_US
(you may wnat to look at the readme.txt file shown in the link)

[Dennis_Knutson]

Well, in order to use serpdrv, you would also have to replace all of your VISA Reads and Writes with the old functions. Did you do this?

[Obelix]

No I didn't convert any of them back. I brought forward some of the old code and it must have been updated to use the visa stuff. I think I read somewhere that upgrading from the older versions would update code to the current visa usage. It must have because I never had anyproblems getting the old code to run as I opened it in 7.1 (created in 5 I think)

I'm not handling all the errors, btu I do track the err numbers in the communications section. I'm getting an err # 42 which I think is a generic error. I am using the latest visa. Any idea where I could find out what it installs to my system? If I had that list, I could brute force all the files and pare out what didn't break the program.

Thanks

[LoganS]

I'm just going to make sure I understand the posts in this forum thus far. You've got an application that was built with LabVIEW 5.1 for a Windows 98 environment that you are trying to use in a newer Windows environment (NT/2000/XP. You're trying to rebuild the application in LabVIEW 7.1, and trying to install all necessary software for this device on a thumbdrive or other external device so that you don't have to install any software on the target system. Your basic application is you need to communicate with serial device that is attached to the target system. How much of this correct?

With that said, have you been able to get your application to work successfully in LabVIEW 7.1, just as a VI? You mention the error #42 below - is that running the actual application or is it in the development environment? Please let us know.

Logan S.

[Obelix]

Yes, you have the summary correct.

The app works fine running inside labview(as a vi).

It also works part of the time running as a standalone app with the labview runtime installed. Its failures are related to an embedded activeX component that doesn't always show up, and not this serial issue. The serial portion seems to wokr fine. The error occurs when trying to run it totally from the thumb drive on a virgin system.