From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with How Do I Run an Executable in the Background ?

Solved!
Go to solution

Hi,

I am trying to run a LabVIEw executable in the background, but none of the methods described in the discussion forum and on ni.com seems to be working. I am using LV 2011 on a Win 7 64-bit machine in case this matters.

I tried the method described in "How Do I Run an Executable in the Background as a Start-Up Application?" (http://digital.ni.com/public.nsf/websearch/4A8B626B55B96C248625796000569FA9?opendocument&Submitted&&... but I still see a fragment of a window at the bottom near the start-button (Exhibit 1). Exhibit 2 shows that it only consists of the title bar. (I have customized the window appearance as described, and added the two items

HideRootWindow=True

UseTaskBar=FALSE

to the *.ini file.)

 

I also tried disabling all the other items in the Customize Window Appearance menu with the same result.

 

Then I tried the method described in "Running a LabVIEW Executable as a Background Process" (http://digital.ni.com/public.nsf/allkb/EFEAE56A94A007D586256EF3006E258B) adding the FP.Open method to the VI and setting the state to hidden. I got the same result (Exhibit 1).

 

Is there anything I need to do in addition or different for my windows version? I appreciate your help. Thank you.

 

 

0 Kudos
Message 1 of 5
(3,206 Views)

(I have customized the window appearance as described, and added the two items

HideRootWindow=True

UseTaskBar=FALSE

to the *.ini file.)

 


 

No you did not

Capture.PNG

They need to go in the exe's ini so the exe sees themSmiley Wink


"Should be" isn't "Is" -Jay
0 Kudos
Message 2 of 5
(3,193 Views)

Actually I did when I tried out the first method. Then for the second method I tried both with and without these two items in the ini file with the same result( Exhibit 1)

0 Kudos
Message 3 of 5
(3,182 Views)
Solution
Accepted by topic author pbuerki

I found the issue. It was an incorrect directory name for the build. I kept running an older version of the executable with the default window settings. The method described in How Do I Run an Executable in the Background as a Start-Up Application?" (http://digital.ni.com/public.nsf/websearch/4A8B626B55B96C248625796000569FA9?opendocument&Submitted&&... works.

Sorry, all for wasting your time. Mea culpa.

Peter

Message 4 of 5
(3,172 Views)

That is great!

 

First- I'm happy you found the trouble

Second- more details for the next guy?

 

Kudos!


"Should be" isn't "Is" -Jay
0 Kudos
Message 5 of 5
(3,156 Views)