Executables Crash under Windows 2000

[D. Brett Richardson]

Hello:

I have a program that is frequently used at my Lab. A problem with
this program developed when we "upgraded" from Windows NT to Windows
2000. When I start an executable form of the program under Windows
2000, it generates an error log. This application runs well in the
development environment under Windows 2000, but fails when run as an
executable. Under Windows NT (the old system), this program would run
in both the executable form and the VI form.

This program was compiled using Labview 6.0.2 amd Labview 6.1.

Does anyone have any clue as to why this might be. Thanks in advance
for your help!

David

[mikeporter]

What does the error log say?

Something that is sometimes helpful is if you can easily extract portions of the code to identify exactly what in the application is causing the trouble.

When exactly does the code crash? As it's loading? When it starts executing? After it has been running a bit? Can you tell from external indications (instruments changing states, indicators updating, etc) whether the program is doing anything prior to the crash?

Mike...

[D. Brett Richardson]

Thank you, Mike, for this set of questions. They may help us diagnose
the problem. I will try the program again and answer as many of them
as I can.

See you in a bit . . .

mikeporter wrote in message news:<50650000000500000011740000-1019262487000@exchange.ni.com>...
> What does the error log say?
>
> Something that is sometimes helpful is if you can easily extract
> portions of the code to identify exactly what in the application is
> causing the trouble.
>
> When exactly does the code crash? As it's loading? When it starts
> executing? After it has been running a bit? Can you tell from external
> indications (instruments changing states, indicators updating, etc)
> whether the program is doing anything prior to the crash?
>
>
Mike...

[Leigh@csiro]

Mike, the resolution to Brett Richardson's problem is of interest to me. My problem is different to Brett's in that it did not arise with migration to Windows 2000 from another operating system. I have been creating successful executables from the 5.0, then the 6.0 LV development environments since 2001. The executable resulting from a recent edit of one program causes Windows 2000 to close it down. The executable opens successfully, but every time I click on a front panel control button, Windows crashes the executable. The DR Watson error log entry describes the fault as: "The application, GTL Noise Fig v5.07, generated an application error. The error occurred on 07/25/2003 @ 09:39:18.039 The exception generated was c0000005 (access violation
) at address 30164426 (IsValidTag)" SEE ATTACHMENT. When in the 6.0 development environment, the same control button causes no problem, and the vis linked to the button open normally.