Multiple versions of LabVIEW

[ErnieH]

I need to support LabVIEW programs from 6.1 up. When I install a newer version, I must uninstall/re-install install some of the toolkits that I use (SQL, report generation). I also use FPGA, RT, Vision. I guess there is a way to reinstall them one at a time, move some files around, etc.. I am looking at pluggable drives, boot managers, dual booting etc.  I could install each version on a hard drive and then boot up on each one. Is there a better/ easier way?  My goal is to keep the version I have intact and make it easier to install a new version when it is available.

[Ben]

"boot managers," I had my IT person set-up a machine that way to allow for versions beyond LV 8.5 Since I was running out of space in my cube.

1-PC - LV 5.1 and prior

1-PC - LV 6.1, 7.0, 7.1 (I found out too late and the drivers are all goofed up but the toolkits are all there)

1-PC- LV 8.0 and 8.2 they seem to place nice together but the LV add-ons and toolkits install for LV 8.2 stepped on the LV 8.0 versions (I back-save if developing in 8.0)

1-PC - Multiple boots, one for LV 8.5 and standing by for more.

Ben

[smercurio_fc]

Having multiple boots is by far the safest approach, whether you do it with separate drives, separate partitions, or even separate virtual machines. In general, installing toolkits for multiple versions of LabVIEW is not generally recommended by NI, even though there's a KB article on it.

[DFGray]

Virtual machines are fast and useful.  However, you will probably have problems with direct access hardware drivers (e.g. DAQmx, NI-SCOPE, etc.).  The issues will depend on your virtual machine solution.  Networked drivers (e.g. cRIO) should not be an issue.

[Graziano]

Hi!
   Since I use compact Fieldpoint technology, which mainly involves ethernet, I find that Virtual machine is the best solution: I've a PC with a Developer Suite 7.1, and for evaluation purposes (and to read VIs from forum ) I've a VMware virtual machine on this PC, which hosts a windows XP SP2 with LabView 8.5.

   The strong pro to VM, is that you can pass a file from host System inside virtual machine easily (VMware tools), this can be useful to quickly open a VI from 2 different versions of LV.

   Of course, performance suffers a little bit, and this approach can be good only if you use one version most of the time! And if you have a good processor and RAM (2 GB is good for it).

   Of course, if you have to deal with DAQ devices, things change (I suppose, since on my PC I currently have no DAQ device)

graziano


Message Edited by Graziano on 04-16-2008 08:35 AM

[ErnieH]

I purchased (finally thorough our IS department) a new Dell quad core computer to use in development. It wiill have a bank of 3 plugable SATA drives. I purchased VMware's workstation software to try the virtual machine route first. If that does not work up to my expectations, then I will set it up as a multiboot system. I wll post my results in a few weeks. Thanks to all who responded.

[K1200LT_rider]

I'm really curious to know how the VMware solution worked out.  If it works well enough, we may have to go that route at my workplace.  We have app's written in 7.1, 8.5, and may go to 8.6.  7.1 and 8.5 on my machine work, but I couldn't install the device drivers when I installed 7.1 (so I wouldn't over-write my 8.5 device drivers).

- Brad 

[gosenbach]

We like to use virtual machines here.  Some of us use VMware Workstation and others (myself included) use Sun Virtual Box.  I just set up a virtual machine with XP Pro SP 2 and intall the approprate version on that.  I have had no problems.  You can also setup a virtual machine for testing releases.  After you have a bare bones windows setup, take a snap shot.  You can then run your installer and you can find out real quick if your release is going to work on a pc that does not already had a bunch of NI components floating around.  Then make any changes, roll back you VM back, and try again.

Cheers  🙂

Greg

[K1200LT_rider]

Greg,

Those are some great suggestions.  I may have to talk to our IT department very soon to get something set up.

- Brad