multi boot or virtual machine?

[_Bryan]

Which is the best way to go?

I find myself supporting from 7.1 - 2011 and I only have 1 development machine.  I thought about virtual machines, but all the posts have said there is no support for PCI cards.  So then I was thinking about multi boot systems so I would have full access to hardware.  I have only "played" with a virtual machine at home on my win 7 machine.  And I have not had the chance to play with any multi boot systems.

I just about have my boss talked into a new machine to handle a handful of virtual machines with the different versions of LabVIEW.  I am thinking the same machine could handle multiple boot options as well with a big enough hard drive.

I know that win 7 pro and ultimate have free downloads for virtual machines with XP included.  With a multi boot system I imagine you are supposed to buy an OS for each boot?  So I guess I have to decide how bad I need to access hardware (multi boot) vs just having the programming environment (virtual).

Any suggestions?

[Ben]

Multi-boot is the path I used.

Only draw backs;

every version will try to install new hardware the first time you bring it up with a new widget installed.

Switching version takes some time.

Ben

[ErnieH]

I recently had a case where I needed to update a real time program in 8.5. Having 2009 and 2011 on my main machine, I did not want to mess up my settings for these programs, since most of our programs that could be updated were updated to one of these versions( a long and painful process, trust me). I was able to set up a win xp virtual machine on windows 7. I loaded the 8.5 software and registered it. I was able to update the real time program, hook up to the controller on our Ethernet, and apply the update. Worked surprisingly well. I also added a 7.1 version for the few I have to support of those. I loaded the daq drivers, but I do not have the hardware installed on this machine. For most projects, I typically open the project, make a change, connect to the target PC (through PC anywhere), and replace the exe to test the mods. Then I can easily go back if more changes are needed. It is a great advantage not having to worry about updating the runtimes to support manufacturing.

[SteveChandler]

ErnieH, kudos for the post but also for the signature! I never noticed it before.

[ErnieH]

Thanks. Just added it a couple of weeks ago.

[_Bryan]

Thanks for everyones insight on this.  I am thinking of trying the virtual machines 1st and see how that works out for me.  I think it might be a bit easier with win 7 and the virtual machine that includes XP ready to go.  If not off to a multi boot system down the road.

Thanks again

[Todd_Lesher]

I've been meaning to try it (meaning I haven't, yet), but you can boot from a VHD file.

http://technet.microsoft.com/en-us/video/native-boot-to-vhd-part-i-of-iv-overview.aspx

[_Bryan]

Wow, that sounds cool, I will have to look into that.  I guess the advantage would be using less resources?  Since you are only running the virtual machine versus running the OS and the virtual machine?

[Todd_Lesher]

The vhd can run on bare metal, and it can run in Virtual PC. And they can be copied. I just don't know about licensing issues.

[SteveChandler]

---

@Todd Lesher wrote:
The vhd can run on bare metal, and it can run in Virtual PC. And they can be copied. I just don't know about licensing issues.

---

The licensing issues in LabVIEW terms are something like buying a commercial VI that is reentrant and being charged for each instance.

From Windows Explorer click on Help/About Windows. Click on the Microsoft Software License Terms. There is a section specific to installation on virtual machines.

3-d Use with Virtualization Technologies. Instead of using the software directly on the licensed computer, you may install and use the software within only one virtual (or otherwise emulated) hardware system on the licensed computer. When used in a virtualized environment, content protected by digital rights management technology, BitLocker or any full volume disk drive encryption technology may not be as secure as protected content not in a virtualized environment. You should comply with all domestic and international laws that apply to such protected content.

The way I interpret it is that Microsoft makes no distinction between a physical computer and a virtual computer. So you can install your copy of Windows as the host OS and run virtualization software but you must buy an additional copy for each virtual machine. Or you can install Linux or something as the host and install your copy of Windows on one virtual machine.

But then there is section 2.

2-b Licensed Computer. You may use the software on up to two processors on the licensed computer at one time. Unless otherwise provided in these license terms, you may not use the software on any other computer.

If Microsoft considers a core to be a processor then most of us are in violation of the licensing terms. However I can find no mention of the word "core" anywhere in the agreement.