How to correct installer resetting minimum restriction to windows XP SP3 or later

[Awhite144]

I am using Labview 2009 and building executables and installers that go onto systems that use windows 2000 and Windows XP SP2 and below.

Whenever I build my installer package, I get a warning:

*** WARNING ***
Cannot enforce the requested minimum operating system restriction because the deployment engine only supports Windows XP Service Pack 3 or later. Resetting minimum restriction to Windows XP Service Pack 3 or later.

I did not previously have this issue, until I recently got a new computer (windows XP => Windows 7) and had to reinstall all of my Labiew and NI systems.  Ever since this, I have not been able to run my installers and executables on anything below windows XP SP3.

How can I fix this?

[P@Anand]

Which version exactly do you have? LabVIEW 2009 or LabVIEW 2009 SP1. I see something about the compatibility between LV2009 and windows 7 here.

[mikeporter]

The message is correct. You have to have at least SP3 for XP -- and yes, the selection is mislabeled; and no, they are not going to fix it.

The fix to your problem is to update the XP target machine to SP3.

Mike...

[P@Anand]

Also you must be aware that microsoft stopped the support for XP and  XP is officially closed now.

[Awhite144]

Mike,

I have Labivew 2009 SP1.

On the installer properties, I can select minimum requirement system of Windows 2000 or better.

I had no issue using my executables on Windows 2000 and Windows XP machines below SP3.

But my development system recently updated to windows 7 and I had to reinstall my Labview.  NI also recomened me download and use some updates during my install (maybe some service pack or something.)

So the changes to my system are upgrading to Windows 7 and a fresh install of Labivew.  Now my executables won't work on the older target computers.  I use these executables in a lab that has MANY computers and I cannot simply upgrade 20+ computers so easily.

Especially when they were working fine previously. 

I would like to understand if the problem my upgrade to windows 7 on my development sestem or my fresh install of Labiew that caused the issue.

I need to get it back the previous condition.  Any clues would be helpful.

[mikeporter]

Actually, the real problem is a failure to keep 20+ computers in your lab up to date -- that is what caused the problem. BTW, this problem is going to get worse because now you are running an OS that isn't even supported now..

Mike...

[crossrulz]

I remember something about things built on Windows 7 can't work with anything before XP SP3.  So I would say it is coming from the fact that you are now using Window 7.

I know it is easier said than done, but you do need to update your test systems.  Computers are something that are (usually) very simple to update every 2-4 years.

[billko]

---

@crossrulz wrote:

I remember something about things built on Windows 7 can't work with anything before XP SP3.  So I would say it is coming from the fact that you are now using Window 7.

I know it is easier said than done, but you do need to update your test systems.  Computers are something that are (usually) very simple to update every 2-4 years.

---

In all fairness, sometimes it's the customer who applies the OS upgrade restriction.  For instance, there may be some contracts that requre a recertification of a test station (and all of the software that is run on it) if anything is upgraded and they aren't willing to pay for it.

Of course, what happens then is that a piece of hardware finally breaks, that hardware has been obsolete for 20 years and any substitute hardware only has drivers for the last two operating system revisions, so you have to upgrade ANYway, but it's going to cost more money than if you did it in a controlled fashion because now you have a tester down and you are using it for your development instead of building a dev station to work all the bugs out.

[edit] Wow, was that all once sentence?  I'm not proud of that... [/edit]

[Awhite144]

I appreciate the comments from everyone.  I truly wish I could upgrade all of my systems, but it is just not feasible to do all at once.

All of the lab computers are off the network and only used for specific test equipment.  We are a global company where all the labs are like this, and many of them are using my software.

In a market with tough competition and low profit margins, it is very difficult to gain global agreement that lower cost frequent upgrades and maintenence fees is more effecient in the long run than waiting for complete failure and replacement.

Based on one of the comments above, I will try to run my labivew system on XP mode and see if helps.

[mikeporter]

---

billko wrote: 

Of course, what happens then is that a piece of hardware finally breaks, that hardware has been obsolete for 20 years and any substitute hardware only has drivers for the last two operating system revisions, so you have to upgrade ANYway, but it's going to cost more money than if you did it in a controlled fashion because now you have a tester down and you are using it for your development instead of building a dev station to work all the bugs out.

[edit] Wow, was that all once sentence?  I'm not proud of that... [/edit]

---

Wow indeed Bill!

Maybe we need to be thinking about promoting you to "Upper-mid-level Minion"

MIke...