G-Man

Hi Matt, Some time ago (when using LV6.1) I was faced with a similar situation. Now with LV8.0/1/2 I am faced with the same problem once again. Back in 6.1, I was able to build installers without including the runtime engine at all. As long as the necessary support libraries (dlls) are included in the installation and located in the same folder as the resultant executable or in the windows path things seemed to work alright. For example, a simple application that uses serial communication, serpdrv.dll would have to be included in the path. To support basic functionality there were a couple of object libraries (don't remember the names sorry) that also had to be included. If you're building a more complex application that uses vision, motion, or other types of added labview functionality, then I'm not sure if you'll be able to get away with 'cheating' like this. Today I am focussing my efforts on finding a 'reverse engineered' approach to building custom distribution packages as I too do not want to build a 130+MB installer to support a 3MB application In my case, I have to include support for VISA (runtime enging is 130MB I think). I beleive this can be avoided by simply including the visa32.dll as a support file. I'll keep you posted as I find anything out. I suppose I should also check in with the good folks at NI to find out if these methods breech the EULA (license). Regards, Doug.