04-12-2007 02:44 PM
Utopia wrote:LabVIEW needs to support features of modern processors.-- 64bit memory space-- number of threads in LabVIEW needs to scale with number of cores (4 threads is not enough)-- SSE support
07-31-2007 10:57 AM
07-31-2007 01:53 PM
I wouldn't say that LabVIEW was almost as bad as a virus, but I definitely agree that there are too many NI services running around. I can understand why NI went this way, but these services are annoying.
By the way, I'm not sure how much system resources these services actually take up.
07-31-2007 02:17 PM - edited 07-31-2007 02:17 PM
Message Edited by Jeff B on 07-31-2007 02:18 PM
07-31-2007 02:51 PM
08-01-2007 03:31 PM
Yeah, thanks Jeff. Is there any additional info out there to go through those services one-by-one and identify what a user will lose by stopping it? Even if it's disclaimed as a non-exhaustive non-authoritative list, a few specifics would really help.
Meanwhile, I've mostly given up on my educated-guess-based trial-and-error. I *think* I recall that one of them was necessary for finding examples, another (or maybe the same one?) was needed to have popup help, yet another 2 or more were needed for data acq device management via MAX, etc. I'm pretty sure I've suffered no ill effects from disabling the Lookout Citadel Server and maybe also the Time Synchronization service.
Still, I'd like to see something like the following get implemented:
- on boot, the service needed by "Find Examples..." is NOT started.
- when the user picks "Find Examples..." from the menu, the underlying code checks to see if the service is running. If not, the service is started. Either way, a flag is set meaning "ok to stop me when LabVIEW is shut down."
08-02-2007 04:29 PM - edited 08-02-2007 04:29 PM
This is just a bit of information that I have read in the past, but can't find reference to right now.
As far as I know or have read, none of the NI software tries to "Phone Home" every time it runs. NI uses "localhost IP connections" for communications between different components. This is similar to the way MS Activesync uses an IP connection to sync your PDA via USB. These types of connections can trigger a firewall alert even though the machine is talking to itself.
Now, this may have changed in 8.2. It was a couple years ago I read that and they may be doing something different now. But I doubt NI is up to anything sinister.
That being said, it would indeed be nice to have to the option during install to not turn certain processes on if you know you're not going to need them.
Message Edited by Ed Dickens on 08-02-2007 04:30 PM
08-02-2007 05:00 PM