Using cmd with Labview app build

[Youssef Menjour]

Hi everybody,

 

I have a problem with cmd LabVIEW. I did a state machine and build an exe(So far, so good). 

I did a state machine with a 2000ms timeout. Everytime out i launch a cmd (So far, so good). This command consist to check if nvidia cuda is installed  (All is in the code and So far, so good).

 

 

In my state machine i have a state which launch an external installer which will be installed cuda (So far, so good). 

 

 

My problem start when cuda is installed during the execution of this state machine (build in exe) and my timeout state does no work (the cmd which check if cuda is installed does not work).

When i restart the exe this state work ! and detect cuda with no problem 🤔

Why do i have to restart my exe to make it work ? (i put the state machine in snip copy and work well in LV version - Not work well when build exe)

 

CMD inside the exe are blocked since cuda installer was launched, why ?

 

If you want to do the test, just run the exe in the project, install cuda and when cuda is installed just see that it is not detected.
Restart the exe and there are no worries cuda is detected. 😭

I searched and I still haven't found out why   😭  😭  😭

 

217806318_SourceInstaller.zip

Edited January 23, 2023 by Youssef Menjour

[Lipko]

I think you should show all cases, maybe you would get replies from people you are not able to try your code at the moment (like me). We don't see where/how you set states apart from "4 - Display".

[Youssef Menjour]

22 minutes ago, Lipko said:

I think you should show all cases, maybe you would get replies from people you are not able to try your code at the moment (like me). We don't see where/how you set states apart from "4 - Display".

To answers you only need the two states explain upper.

If you want to see all cases you just have drag and drop on your labview diagram the sniped.

 

[ShaunR]

37 minutes ago, Youssef Menjour said:

If you want to see all cases you just have drag and drop on your labview diagram the sniped.

Snippets don't work very well and the meta information is stripped by some websites and browsers. It is always better to post the code.

3 hours ago, Youssef Menjour said:

CMD inside the exe are blocked since cuda installer was launched, why ?

Probably the "cmd /c where nvcc" isn't finishing for some reason (waiting for input?) and as you have the cmd VI set to wait until completion, it just gets stuck there.

[Youssef Menjour]

i was 100 % sure you'll try ShaunR 😁

32 minutes ago, ShaunR said:

Snippets don't work very well and the meta information is stripped by some websites and browsers. It is always better to post the code.

 

code is posted upped (zip file with thewhole project), i put the code vi in attached.

Quote

Probably the "cmd /c where nvcc" isn't finishing for some reason (waiting for input?) and as you have the cmd VI set to wait until completion, it just gets stuck there.

This is not logical, this command works perfectly before installation and it works perfectly after installation and reboot of the exe

Nevertheless, I agree, there is an execution link. 
But then why in the .VI version it works and in the .exe version not at all? 🤔
 

Installer.vi

[ShaunR]

25 minutes ago, Youssef Menjour said:

But then why in the .VI version it works and in the .exe version not at all?

Maybe it requires privilege escalation because it's in an executable. Maybe it needs a confirmation to run the command. The only way you will know is to not hide the cmd window and run it with the "/k" switch so you can see what it's actually doing.

Edited January 23, 2023 by ShaunR

[LogMAN]

This might be an issue with environment variables. Your application runs with whatever environment variables exist at the time it was launched and cuda is only added to PATH during its installation.

Quote

By default, where searches the current directory and the paths that are specified in the PATH environment variable.

-- where | Microsoft Learn

It should work if you specify the path explicitly (or somehow reload environment variables).

[Youssef Menjour]

Thank you

16 hours ago, LogMAN said:

This might be an issue with environment variables. Your application runs with whatever environment variables exist at the time it was launched and cuda is only added to PATH during its installation.

It should work if you specify the path explicitly (or somehow reload environment variables).

 

How to  reload in CMD environment variable ?

Edited January 24, 2023 by Youssef Menjour

[cordm]

"where" without parameters searches in the PATH (https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/where). That environment variable will not update unless you restart your process. (or you jump through some hoops (https://stackoverflow.com/questions/171588/is-there-a-command-to-refresh-environment-variables-from-the-command-prompt-in-w))

Try querying the registry for environment variables that the installer will create (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment).