Jim Kring

Felix: Here's some good reading on the reasoning behind the choice to release the OpenG libraries under the BSD license.

Sign up for NIWeek 2011 and network with these guys I want to know what's so funny on that computer screen (PS - Ya, I'm just jealous)

Shaun, You're the man! I'm starting to play around with "Separate Compiled Code From Source" and was about to create a tool just like your (and now I don't have to). To me, it seems odd that the "Mark VIs" dialog does include this "folder on disk" functionality -- rarely do my LabVIEW project files include every VI from my project folder on disk. Thanks!

@dannyt FYI: you can subscribe an RSS feed of a twitter user's tweets without actually signing up for a twitter account yourself.

He there! Sorry for the trouble, but I have good news This bug (9665: VIPM shows errors when installing a package with read-only files inside) has been fixed in VIPM 2010.0.1. You can find out more info here: http://jki.net/vipm/release-notes Regards, -Jim

Mikael: LabVIEW 2010 introduced a variety of new compiler optimizations to take advantage of the new compiler architecture and DFIR. So, it doesn't surprise me too much that there are some issues in corner cases.

Update: This was assigned CAR#: 252210 by NI

[cross-posted to ni.com] [CAR#: 252210] [Update: I just tested this in LabVIEW 2010 SP1 and it seems to be fixed The CAR Number (252210) is also in the list of LabVIEW 2010 Service Pack 1 Bug Fixes. Thanks NI!] I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture LabVIEW 2010 CRASH.vi

Ya, just a little bit. I think my fingers were on autopilot

I got excited when I found VIPM VMWare ThinApp as a possible solution (it allows you to "record" an app installation and then package it up as a single file EXE), but then I looked at the price tag (~$6K). [update: VIPM ThinApp -- haha! ]

I've got a customer who can't install the run-time engine, due to this known issue and their IT dept is unable to resolve the problem. So, we have to find a solution that lets us run our application without having the run-time engine installed (for example, by including the run-time engine DLLs along with the built EXE). I recall that several years back there was an NIWeek presentation by Kennon Cotton that documented how one could distribute a LabVIEW app on a CDROM and include the run-time engine DLLs on the CDROM (in a subdirectory beneath the EXE). Does anyone know if this is still feasible in LabVIEW 2009 or 2010? Does anyone happen to have a link to (or copy of) the documentation or presentation about this? I'm going to keep digging for more info and will post whatever I find. I figured it would be useful to post here to see if anyone knows, off hand. Thanks! [update 2010-09-28: I just found the "Runtimeless Installer and LabVIEW applications" thread started by Jack Hamilton where he posted his presentation and example files, including Kennon's NIWeek presentation.] [update 2010-10-01: We were able to successfully install the LabVIEW 2010 Run-Time Engine (it's not affected by the known issue) and decided to just build our application in LabVIEW 2010.]