Run LabVIEW 2012 SP1 user-created VI on Windows 2000 machine

[Quevvy]

The VI on which I am working (on Windows XP) will need to be implemented onto 4 different computers: 3 with Windows XP SP3 and 1 with Windows 2000 SP4. This is new software for us, so we purchased LabVIEW 2012 SP1. This version of labview works on Windows XP, Vista, 7, & 8. The corresponding Runtime Engine works on Windows XP, Vista, & 7. As you'll notice, Windows 2000 is not listed here. I tried building it into an .exe file, but it still needed the corresponding RTE. Is there any way for me to be able to run my VI on the Windows 2000 computer? (Obviously, upgrading the OS would be a solution, but I would like to avoid that, if possible.)

[I was messing around with Runtime Engines and the newest version that could install was LabVIEW RTE 2009 (not SP1) on the Windows 2000 computer, if that helps at all.]

[JÞB]

I do not  actually recommend this work-around you should upgrade the OS.

You could take your source code and back-save it to 2009 and build a second "downgrade" exe to deploy to the old target.  Be kind to yourself and note the difference in the about.vi so you never forget why you did this silly workaround

[RavensFan]

You could try to install the latest run-time engine on the Win2000 PC, but it is not supported, and is pure luck for you if it works.  That version of Windows is ancient at over 13 years old.  Microsoft doesn't support it anymore, so why should NI?  Even XP is soon not going to be supported by Microsoft.

I'd highly recommend that you upgrade the OS.

(You said that you could install LV2009 run-time.  That seems to agree with Windows Version Compatibility with LabVIEW.  So you could downgrade your LV12 VI's to LV9 and work in that enviroment.  But I'd still suggest you upgrade the OS rather than working with Win 2000.)

[Dennis_Knutson]

Building an exe for 2009 would require you to have a copy of LabVIEW 2009, of close. I don't know if your 2012 license would even permit that and if you are using some features, you might not be able to do the down conversion.

[JÞB · Accepted solution]

---

@Dennis_Knutson wrote:
Building an exe for 2009 would require you to have a copy of LabVIEW 2009, of close. I don't know if your 2012 license would even permit that and if you are using some features, you might not be able to do the down conversion.

---

If you have a license for a version of LabVIEW you can have every (Older) version installed as well.  You need an active SSP to upgrade though!

All the new features migrate back to at least 8.0 (You'll get a bunch of warnings and maybe some very ugly code).

I would try to avoid backing any queues (or config file functions) over the 8.6 - 2009 boundry.  you might see some unexpected changes and prefomace hits. 

[Quevvy]

---

@JÞB wrote:

I do not  actually recommend this work-around you should upgrade the OS.

You could take your source code and back-save it to 2009 and build a second "downgrade" exe to deploy to the old target.  Be kind to yourself and note the difference in the about.vi so you never forget why you did this silly workaround

---

I tried this, but I couldn't find how to build it in LV 2009. What is this "downgrade" exe that you speak of? It might be a hassle to reinstall drivers (not sure if we can still find the CDs) for the different instruments, so I would rather use a work-around.

---

@RavensFan wrote:

You could try to install the latest run-time engine on the Win2000 PC, but it is not supported, and is pure luck for you if it works.  That version of Windows is ancient at over 13 years old.  Microsoft doesn't support it anymore, so why should NI?  Even XP is soon not going to be supported by Microsoft.

I'd highly recommend that you upgrade the OS.

(You said that you could install LV2009 run-time.  That seems to agree with Windows Version Compatibility with LabVIEW.  So you could downgrade your LV12 VI's to LV9 and work in that enviroment.  But I'd still suggest you upgrade the OS rather than working with Win 2000.)

---

Even with RTE 2009 SP1, it said it required XP SP2 or higher, so installing RTE 2012 SP1 is a no-go. (I also have explicity tried it.)

I tried saving the .lvproj for LV9.0, but when it built, it still required RTE 2012 SP1.

---

@Dennis_Knutson wrote:
Building an exe for 2009 would require you to have a copy of LabVIEW 2009, of close. I don't know if your 2012 license would even permit that and if you are using some features, you might not be able to do the down conversion.

---

My program is not that complex (as far as I know), it doesn't use any DAQ, but it does use VISA. How would I find out if my license would permit that?

---

Thanks everybody!

[Quevvy]

Actually, the simplest [non-sustainable] solution would just be to use the 30-day evaluation version of LabVIEW...

---

@JÞB wrote:

---

@Dennis_Knutson wrote:
Building an exe for 2009 would require you to have a copy of LabVIEW 2009, of close. I don't know if your 2012 license would even permit that and if you are using some features, you might not be able to do the down conversion.

---

If you have a license for a version of LabVIEW you can have every (Older) version installed as well.  You need an active SSP to upgrade though!

All the new features migrate back to at least 8.0 (You'll get a bunch of warnings and maybe some very ugly code).

I would try to avoid backing any queues (or config file functions) over the 8.6 - 2009 boundry.  you might see some unexpected changes and prefomace hits. 

---

I would be able to activate a version of 2009 with my current serial number...

http://digital.ni.com/public.nsf/allkb/5635EA3F315B391A86256F480049E933

It took a while to find the downloads though… (http://search.ni.com/nisearch/app/main/p/ap/tech/lang/en/pg/1/ps/30/sn/n8:28,ssnav:pdl/) [There's a smiley in my link! :)]

[I'll update when I try to activate it.]

[JÞB]

---

@JÞB wrote:

---

All the new features migrate back to at least 8.0 (You'll get a bunch of warnings and maybe some very ugly code).

---

I am going to correct myself.  The fun new features like error rings, IPE structures, native recursion, File operations, do back migrate well (if sometimes hashing a BD to near unreadability)

On the other hand, I shudder to think of was a "DVR containing an array of dynamically dispatched inherited class obects with methods marked private by the PPL they belong to (and seperated from source) using a Peer to Peer stream on a paralleized for loop and dependant on the memory management pallate" would look like in LabVIEW 8.0.  No, I think the 8.0 RTE would feel like Moses listening to a burning bush  ("Oh Lord, you are going to do WHAT?")

Thanks for the nightmares Dennis!

[Quevvy]

---

@JÞB wrote:

---

@JÞB wrote:

---

All the new features migrate back to at least 8.0 (You'll get a bunch of warnings and maybe some very ugly code).

---

I am going to correct myself.  The fun new features like error rings, IPE structures, native recursion, File operations, do back migrate well (if sometimes hashing a BD to near unreadability)

On the other hand, I shudder to think of was a "DVR containing an array of dynamically dispatched inherited class obects with methods marked private by the PPL they belong to (and seperated from source) using a Peer to Peer stream on a paralleized for loop and dependant on the memory management pallate" would look like in LabVIEW 8.0.  No, I think the 8.0 RTE would feel like Moses listening to a burning bush  ("Oh Lord, you are going to do WHAT?")

Thanks for the nightmares Dennis!

---

I was able to get LV 2009 running on the Windows 2000 machine. Other than the VIs for the instruments that I haven't loaded yet (testing with simulated data), the only things that didn't transfer well were the "Formula" Express VIs. But come to think of it, those are very simple and could be replaced by the simple add/subtract/multiply/divide/etc. ones, making compatibility more likely if ever transferred to other OSes.

[RavensFan]

Congratulations in the progress you've made so far.

But I would still recommend dumping Win2000, (and possibly that PC itself which is probably old) and upgrading it to at least WinXP.

I thinking you are going to be delaying the inevitable.  In probably less than 1 or 2 years, something will occur with that PC and you'll be forced to upgrade it anyway.