02-16-2010 11:01 PM
I'm a bit confounded on the library situations...I'm not using an RT target...
though when running the deployed executable/installer.... upon start it asks for these 2 dlls: lvuste.dll & lvalarms.dll. which seem to be related to RT ???? how do I get around this? How would I include these dlls within an executable or installer?
I'm using 8.5.
02-16-2010 11:03 PM
06-16-2010 07:35 AM
I'm hoping someone will have an answer to this question, as I was just going to post it myself. I haven't looked into how much I'm using these particular DLLs (the same exact ones as jonathanupr), but I'd really like to somehow bundle them into my application so it is self-sufficient, rather than requiring a data folder with these DLLs in it in the same folder as the executable. Any ideas? I'm using LabVIEW 8.5.1.
Joe
P.S. As far as usage, I don't do anything with real-time per say, but I do use timed while loops, which if I recall correctly might be the culprit. If that is true, I might be able to replace them with regular while loops and wait VIs to fix this issue. I do not use shared variables.
06-17-2010 04:17 PM
It looks like this was a problem with the way Timed loops link directly to those 2 DLLs. Does the error ask for those DLLs in a specific folder? If so you can copy them from their current location (which I believe should be <labview>\resource folder) to the folder that it wants them to be in. Alternately you can simply remove the timed loops, since timed loops on a Windows PC doesn't really have much benefit over a while loop with a timer.
Hope this helps...
06-21-2010 07:45 AM
Thanks, David! Hearing that timed loops probably are the cause, and re-confirming that they do not add value compared to a regular while loop with a timer, is exactly what I needed. I'll try to remove them in the next update of my application and hopefully that will remove the dependancy.
-Joe
06-22-2010 11:21 AM
Great, glad to help. Let us know if that doesn't solve it.