For years I have been happily compiling my apps to a centralized
network destination. Users who have access to these servers
can run my apps without the LV runtime on each local machine-- I have
the minimum set of DLL's in the same subdirectory on the server.
Nobody's registry needs to be messed with. I know it aint kosher
but it is convenient.
Well, I got 7.1 installed and have become enamored of timed
loops. I especically like the power of my stop button, now
event-driving my exit state to shut down all the other loops by
name. No more notifier wires or occurences adding to the
spaghetti. (Yes, it aint dataflow, but..).
..I digress. My problem is that when I build the app it wants to
install LValarms.DLL up on the ntetwork.. This can be a problem
if another app is running which uses timed loops. And the problem
is the timed loop; I ran a small compile of a simple loop .EXE and it,
too, choked.
I have seen this behaviour with lvsound.DLL as well. But since my
app usage of that DLL is sporadic, I can usually rename the existing
one and upload it again with the compile. But this LValarms.DLL
is used continuously.... I guess I'm answering my own query by knowing
this, but I don't have the same problem with LVanalys.DLL, mesa.DLL, or
even LVrt.DLL. They allow me to copy apps up to their network
locus no problem. Any hints out there?
Thanks
