LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I get the current operaction system version by labview?

Dear All,
How can I get the operaction system version in the current station by labview?
 
Regards,
Jimmy
0 Kudos
Message 1 of 11
(4,150 Views)
Create a application property node and pick OS.Name and OS.Version. See attached (LabVIEW 7.0)

Message Edited by altenbach on 01-03-2006 08:46 PM

Download All
0 Kudos
Message 2 of 11
(4,151 Views)
I'm just wondering if this VI will work to make sure the OS of the target machine is compatable with the exe. built in a different OS. For example I build an app in XP. The target machine is win2000. Since (it's my understanding) the app will not be compatible with the targets OS can I use this VI to check and let the operator know that the app is not compatable with their OS? Hope this makes sense and thanks in advance.
Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 3 of 11
(4,110 Views)
Do you have some specifc code in your program that will run only on XP? If that's the case, then, yes, you can warn the operator that the application is not compatible. If you mean compatiblility in general, a LabVIEW 8 app will only install on a Windows 2000 or XP system. I'm not aware of any compatiblity issues between a Win2000 and WinXP LabVIEW program. I do all of my development in XP and deploy to mostly Win2000. A LabVIEW 7.1 will not install at all on Win98 and a 7.0 app will not install on Win95.
Message 4 of 11
(4,104 Views)
If you are on a windows system, you can read registry values to get the OS name. I could post a sample when I get back to my desk.
0 Kudos
Message 5 of 11
(4,090 Views)

Thanks for the quick replys. I don't think I have any code specific to XP vs. 2000 but have no OS 2000 systems to check my app on. Dennis thank you for clarifying what version works with what OSSmiley Happy. Maybe I'll develop in 7.1 (save as 7.0) and 8.0 with seperate executables. Not sure what OS this app might be used on. Have to think this through. Smiley Wink

 Should I build 2 seperate executables to realize this? One to check the OS for compatibility and one to install the app. Or is there a way to to impliment this in a single exe. that gives an abort install?

Unclebump, I'm not really familiar with using Windows registry. I would look at your example if you have time to post. If you can't find the time I would still like to say thanks.

The bugger is in the details.

Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 6 of 11
(4,069 Views)
If you use the installer that comes with the app builder, it will first check the OS. If it detects an incompatible OS, it pops up a message that says that and will not proceed.
Message 7 of 11
(4,061 Views)
duh meSmiley Sad As you probably can tell I haven't used the app builder before. I usually work in TestStand. Guess I need to review the manuals before asking questions that have been covered. I really appreciate your help Dennis. As always your anwers are right on the money.
Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 8 of 11
(4,054 Views)
Here is a 7.0 format vi to read the windows product name from the registry. I use this for windows 2000. Not sure what it will do on winXP.
Message 9 of 11
(4,041 Views)
I appears to run correctly on XP.  Returning: "Microsoft Windows XP"
0 Kudos
Message 10 of 11
(4,001 Views)