Why does LabVIEW think I'm running Windows NT v5.1? I'm on XP Pro!!!

I read from an application property. They show Windows NT v5.1

XP is really just a label Microsoft put on the newest release of Windows NT. Instead of just changing the version number, this makes it appear as an entirely new operating system instead of just a new version of the same old thing. That's marketing for you.
XP Pro should show as Windows NT 5.1 as you have seen.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Similar Messages

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

Why does LabVIEW think the Analyser is not connected?

Hi All,
        this almost works but not quite.
       I have a specialised analyser from LeCroy called a CATC Protocol Analyser System Model 10k. It is for observing and supplying traffic on a SATA disc interface. LeCroy supply an automation library of ActiveX components for controlling it called SataAutomation.tlb. After registering this with a utility I found called ccrpregutil.exe the automation library became visible in labVIEW.
        As an exercise to prove that this can work from LabVIEW I have written a small vi, called Code Interface.vi on file and uses two of the (simplest) methods from within it. They should return the Serial number and the firmware version. The analyser is connected (via usb) to the computer and is powered up. Running the attached vi results in the following message. "Error -2147220975. Exception occured in CATC.SataAnalyser.1: Analyser device is not connected Code Interface.vi.".
So it thinks the analyser is not connected when physically it is. Does anyone know if I have to do something extra to "Connect" it. There is not a method in the .tlb file to do this. All the methods seem to assume it is connected.
The chances that anyone has seen this exact problem with this exact instrument are small but perhaps someone has seen something similar.
thanks
George
ps this is LabVIEW2009
Attachments:
Code Interface.vi ‏12 KB

Hi George,
I have been looking into this problem for you. First of all, I must advise you that it is not possible for us to replicate this problem since we do not have the required hardware. As a result, the support I am going to be able to provide on this issue is limited. I had a look into the error that you are receiving and it seems that LabVIEW can offer no explanation as it is undefined, it may be that this is a custom error message/code that was created by LeCroy.
I found this link to a Knowledge Base (KB) article that may be of use for you, it relates to communicating with 3rd party hardware in LabVIEW. Do you know if LeCroy provide another methodology you can try for controlling the device such as LabVIEW VIs or a DLL? Otherwise, I can only advise that a high success rate is usually achieved when using ActiveX with LabVIEW and that this issue may be due to a problem in the ActiveX library that is provided by LeCroy. For more information on ActiveX in LabVIEW, see this link. I will continue looking into this for you but I must reiterate that there is only so much I can do without having the hardware to recreate the problem.
Best Regards,
Christian Hartshorne
Application Engineer
National Instrument
Andrew McLennan
Applications Engineer
National Instruments

Why does Labview allow a cursor in a indicator?

Hello,
Why does Labview allow the user to position the cursor with the mouse inside a numeric indicator? Users think that just because they can put a cursor they should be able to type something and enter data. Is there a way to disable/stop the user from putting the cursor in a numeric indicator?
Regards,
Kaspar
Solved!
Go to Solution.

Disabling the indicator satisfies your requirements, but this is funnier. It would be even better if I calculated the position of the indicator and the "entry point" and just kept the mouse from entering, but I have a project to finish...
Message Edited by jcarmody on 03-27-2009 11:58 AM
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
Attachments:
move.png ‏4 KB
test.vi ‏9 KB

Why does LabVIEW allow me to have 2 controls with same name

Here's a general LabVIEW question:
Why does LabVIEW allow me to have 2 controls with the same name in the same VI? It seems like this only increases the chances of confusion. Especially when someone is just looking at a block diagram (or documentation of a block diagram).
No other programming language that I know of allows this. I realize that uniqueness of name is not as critical in LabVIEW as it is in any text based language. For example, in a text based language, if I had 2 variables called abc and I wrote a statement
abc = 12;
the compiler would not know which abc was being referred to. In LabVIEW, if we had 2 controls called abc, the equivalent of doing an abc=12 is writing to a local variable (which is always linked to one of the controls) and there is no ambiguity. Still, someone looking at the code cannot figure out which abc is linked to unless he does a right click>>Find>>terminal (or a double click).
Even though I have never and never will name 2 controls the same, I think it would be a nice constraint to see enforced by LabVIEW.
Any input from NI engineers on this?
Message Edited by S G on 12-18-2007 03:38 PM
S G
Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor
Attachments:
Trial1.JPG ‏21 KB

I know when you copy and paste a control or indicator, LabVIEW automatically increments the label. But since you can hide the label, and show or hide the caption, there must be another mechanism that LabVIEW uses to keep track of all the controls. I thought I remember back in the "old days" (ver 6 or 6i) LabVIEW would give you an error if you tried to make two controls with the same name. Perhaps that was LabWindows/CVI.
I don't know where the index is actually stored, but if you look at a property node linked to the Pane, you will see an array of references to the controls and indicators. Since the references are stored in an array, I assume that any local variables are tied to the index of that array. Since the labels themselves are properties of the control, I guess there's no reason to limit what that label is. They all have a unique index number.
Interestingly, this array of references grows from the beginning. That is, any new control or indicator is put at index 0, not the end of the array.
B-)
Message Edited by LabViewGuruWannabe on 12-18-2007 08:45 PM
Attachments:
Labels.png ‏12 KB

Why does my iPhoto open and run slow since upgrading to OSX 10.8.5

Why does my iPhoto open and run slow since upgrading to OSX 10.8.5? I have an Imac - Intel 2.5 GHz quad core I5 - with 20 GB of memory. Before the upgrade it was much faster.

Why does my iPhoto open and run slow since upgrading to OSX 10.8.5? I have an Imac - Intel 2.5 GHz quad core I5 - with 20 GB of memory. Before the upgrade it was much faster.

Why does my MacBook come up with window saying "setting Up Mac" when I turn it on and enter my password and stays there and does not go any further

Why does my MacBook come up with window saying "setting Up Mac" when I turn it on and enter my password and stays there and does not go any further

You may want to put this question on the MacBook community forum to get a better response.
https://discussions.apple.com/community/notebooks/macbook

Why does it take 18 hours to install security update 2013-002 onto my macbook pro 10.6.8 safari?

why does it take 18 hours to install security update 2013-002 onto my macbook pro 10.6.8 safari?

Are you connected by ethernet, Magsafe or using wifi?

Can i run windows xp(no virtualization software) in my macbook pro retina 15 inch mid 2012 . all the bootcamp compatible to my laptop support only win 7 or 8.

can i run windows xp(no virtualization software) in my macbook pro retina 15 inch mid 2012 . all the bootcamp compatible to my laptop support only win 7 or 8.

Not without using a VM. XP is no longer supported in Boot Camp or on newer Apple computers.

Why does my iPhone 4 always say "sync will resume when "... MacBook Pro" is available??? i can't seem to sync over wifi

why does my iPhone 4 always say "sync will resume when "... MacBook Pro" is available??? i can't seem to sync over wifi

Try the following:
1. Connect the phone to your computer using the USB cable and let it sync.
2. Uncheck "Sync with this iPhone over Wi-Fi"
3. Click Apply
4. Check "Sync with this iPhone over Wi-Fi"
5. Click Apply
6. Quit iTunes
7. Disconnect the phone from the USB cable
8. Make sure your phone is connected to your Wi-Fi network
9. Open iTunes
iTunes should see your iPhone and connect to it. Go under Settings > General > iTunes Wi-Fi Sync and see if you can initiate a sync.

Why does Adobe force you to install a "cloud" program before they will activate Acrobat Pro?

Why does Adobe force you to install a "cloud" program before they will activate Acrobat Pro?

If you are referring to the Cloud desktop application, that replaced the Adobe Application Manager (AAM) which is what would previously have been installed instead.

Why does labview close whilst my program is running?

I am running a program doing data acquisition using the PCI-6602 cards. Everything works fine but somehow after I have been doing acqusition and saving the data for approximately 2 days, I find out that the program has been stopped by LabVIEW and find all the windows closed including labVIEW. In my program I did not use any of the exit functions provided with LabVIEW but somehow, labVIEW exits by itself without issuing any error messages. Why is this happening?

I experienced a problem with LabVIEW 7.0 shutting down unexpectedly. It may be completely unrelated, but I thought I'd mention it just in case. My problem was that I was calling a DLL that used a reference handle. At the end of my test (using TestStand), the test closed, and thus the DLL was unloaded from memory as well. Because there was still a handle open to this DLL, LabVIEW must not have known how to handle this and shut down (or it confused Windows and it shut down LabVIEW). In any case, the solution was to have a VI stay in memory which calls this DLL, and put the DLL in a the true case of a case statement wired with a constant false. Thus, the DLL is never actually called by this VI, but it keeps the DLL in memory.
So if you call any VIs dynamically, etc., where a VI could be unloaded from memory, check those VIs and make sure you aren't leaving any references open or something like that.
Hope this is in some way helpful.
Tom

Why does LabView dll not work in C Thread?

Hello Everybody,
I want to use a LAbView Application as Dll in a Console Application.
There is an Example Available (DLL_Example.zip)in (Displaying the Front Panel of a LabVIEW-Built DLL Function)
When I use this Example in a Windows Console Application, it Works fine (It is important for me, to see the LV Window!)
Code example:
/* Example Start *******************************************/
int main(int argc, char* argv[])
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
/* Example Stop *******************************************/
When I use the function "SimpleCalculator" in a Thread, the LabView Window never appear, what's wrong?
Code example:
/* Example Start *******************************************/
DWORD WINAPI LVThread(LPVOID lpParameter)
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
int main(int argc, char* argv[])
DWORD ThreadID;
CreateThread(NULL,0,LVThread, NULL, 0, &ThreadID);
getchar();
return 0;
/* Example Stop *******************************************/
I'm using Microsoft Visual Studio 6.0. and LabView 7.0
Thanks for every help.

bobby wrote:
Hello Everybody,
I want to use a LAbView Application as Dll in a Console Application.
There is an Example Available (DLL_Example.zip)in (Displaying the Front Panel of a LabVIEW-Built DLL Function)
When I use this Example in a Windows Console Application, it Works fine (It is important for me, to see the LV Window!)
Code example:
/* Example Start *******************************************/
int main(int argc, char* argv[])
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
/* Example Stop *******************************************/
When I use the function "SimpleCalculator" in a Thread, the LabView Window never appear, what's wrong?
Code example:
/* Example Start *******************************************/
DWORD WINAPI LVThread(LPVOID lpParameter)
double Y = 4;
double X = 5;
double Result = 0;
SimpleCalculator(1, Y, X, &Result);
printf("Result = %f", Result);
return 0;
int main(int argc, char* argv[])
DWORD ThreadID;
CreateThread(NULL,0,LVThread, NULL, 0, &ThreadID);
getchar();
return 0;
/* Example Stop *******************************************/
I'm using Microsoft Visual Studio 6.0. and LabView 7.0
Thanks for every help.
Check out luciangeeks's explanation elsewhere on this forum in several threads about the message loop needing to be pumped by the intial thread starting up the LabVIEW runtime system. In Windows console applications the hidden startup code linked in from the C runtime library to intialize the environment before passing control to the console applications main function also contains a message loop, polling the Windows message queue to among other things translate those messages into keychars so that the C runtime library function getchar() and friends can work as expected. It also makes the console application look responsive to the Windows system so that Windows doesn't think it would need to shutdown the application. LabVIEW DLLs really running as GUI components can't work without an active message loop making sure those system messages are retrieved and distributed to the according (usually hidden) VI windows. However the setup in Windows makes it such that a DLL sort of inherits the message loop of the thread which first entered that DLL. If that thread does not have a message loop, LabVIEW windows simply can't work properly and this means that the LabVIEW code is not managed properly and therefore won't run.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

For Experts: Why does LabView cause System reboot while accessing hardware with driver?

Hello NI Developers!
I use LabView 7.1 under Windows XP
I have a programm console application which accesses through Jungo Windriver PCI-E board.
This program works fine - and performs DMA data transfer between PC and Board's memory.
In order to implement this console application work together with LabView I did following:
1) Added this function inside the source:
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue);
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue)
    AllocConsole();                   //Open new console window
   SetConsoleTitle(L"Debug Window"); //Set a title for console window
    freopen("CONOUT$","a+",stdout); //redirec standard output stream to current window so
                                    // so we are able to see "printf" outputs
   freopen("CONIN$","a+",stdin);    //redirec standard input stream to current window so
                                    // so we are able pass inputs from keyboard
   main();                          //Call applications main function which does all the work
2) Compiled this new source as DLL library
3) Call LVMainFunction(...) function from LabView using Call Library Node
In the result: Executing VI - opens new console window, shows debug outputs and receives keyboard inputs.
It works fine till the last function, which perform DMA data transfer - and reboots PC.
1) Why does this happen?
2) I understand that opening console from Call Library Node, attaches together this console window and running VI. So If I close one of them - both windows closes.
   So does LabView have somekind of restrictions of accessing Hardware's functions?
I can read Board's resource information and view size of memory on board, interrupt functions and other information about device, but when I try to reach
DMA my system reboots. And I understand that this should be some kind of LabView problem, cause I tried different implementations, even without use of
console window - and the result is the same.
3) Should I split the program in to two separate processes and perform data exchange using Sockets or Pipes techology?
Thank you in advance!
ACiDUser
Message Edited by ACiDuser on 11-13-2008 09:37 AM

Hello!
At LAST!!!
I solved this problem!
From the beginning I was following National Instruments manual on how to build DLL with external IDE:
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/building_library_project/
Set the Struct member alignment control to 1 Byte.
Now this option caused my PC to reboot!
So could someone explain why this happened? and If it is a bad tip, so it's better to remove from manual. Then other people will not have such problems as I did
- wasting 2 monthes of time determining the problem.
I changed it to Set the Struct member alignment control to DEFAULT.
and now everything works fine.
Regards
Message Edited by ACiDuser on 11-13-2008 11:14 AM

Why does Labview crash when using DLL to retrieve desktop directory?

In Labview 7.0 I run this VI and it occasionally will crash labview upon closing it. The error is "Labview 7.0 Development System has encountered a problem and needs to close. We are sorry for the inconvenience."
The error signature is:
AppName: labview.exe AppVer: 7.0.0.4000 ModName: labview.exe
ModVer: 7.0.0.4000 Offset: 00801e0e
What do you think???
Attachments:
desktop_path.vi ‏14 KB
appcompat.txt ‏19 KB

AKlijn wrote:
> This was, indeed, the solution. Thanks so much for taking the time.
> I must say I could not find this preallocation concept in the labview
> documentation, but perhaps they assume a more experienced programmer
> would be reading it.
As far as I remember it is mentioned in the tutorial. However this is a
very basic C programming concept, that the caller has to allocate and
deallocate buffers passed to functions. This is because there are
basically a myriad of ways to allocate memory and if the allocation and
deallocation is not done by the same entity you have to exactly specify
which memory pool has to be used. Windows itself has about three or four
different memory management libraries and most C runtime libraries add
th
eir own again, although the Microsoft Visual C runtime library does
redirect its malloc() calls to one of the WinAPI memory management
calls. But Borland runtimes typically have their own meory management
library and if a DLL created in Borland C or Delphi would allocate
memory and you would try to deallocate it in a Visual C application you
would get very bad crashes.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Why does LabVIEW think I'm running Windows NT v5.1? I'm on XP Pro!!!

Similar Messages

Maybe you are looking for