on screen keyboard not working with labview

[shruthiganapathy]

I have added this in my UI where when i run the program on screen keyboard pops up. this is working in my laptop but it is not working in my another touch panel pc. what could be the possible issue ? Kindly guide me. 
labview configurations : NI Labview 2024 Q3 (64 bit)

[billko]

---

@shruthiganapathy wrote:

I have added this in my UI where when i run the program on screen keyboard pops up. this is working in my laptop but it is not working in my another touch panel pc. what could be the possible issue ? Kindly guide me. 
labview configurations : NI Labview 2024 Q3 (64 bit)

---

Describe "not working".  Does the keyboard pop up but you can't press the keys on the touch screen?  Does the keyboard NOT pop up?

[shruthiganapathy]

This is the error i am getting regardless of what command line i am using. 
Thanks

 

[dkfire]

What OS is your panel running ? 

What is the difference between the 2 setups ? 

You need to give a lot more details about your setup before we can help. 

Could it be that OSK is not installed ?

[pincpanter]

You forgot to type a space between cmd and /c.

[rolfk]

---

@pincpanter wrote:

You forgot to type a space between cmd and /c.

---

Well don’t see any cmd /c in that pic but it sure may be related to the problem, System Exec dosn’t try to giess where Windows might keep its executables. If exe file you try to call isn’t located in a few very specific locations the underlaying Windows API will not find it and report error 2, file not found, which the System Exec translates without shame into the LabVIEW error 2, which has a different meaning.

Adding cmd /c in front will first invoke cmd.exe which has an extensive search to find the exe file that is passed as parameter.

Or the osk.exe is not installed as already suggested. Can be easily tested by opening the command like window and typing osk. If it starts up it is installed and adding cmd /c in front should let System Exe find it too. If it doesn’t start up you have to make sure to install it first!

[rolfk]

Sorry for any typos and errors in my previous post. The “always” helpful Cloudflare site protection that NI uses refuses to let me correct anything.

[UliB]

---

@rolfk wrote:

---

@pincpanter wrote:

You forgot to type a space between cmd and /c.

---

Well don’t see any cmd /c in that pic

---

It's in the error message dialog: Command was "cmd/c osk.exe".

I'm not OP, but I can't get OSK to open with System Exec.vi either. When I enter "C:\Windows\System32\osk.exe" in Windows file explorer or in a cmd window the OSK pops up.

With System Exec and [ cmd /c "C:\Windows\System32\osk.exe" ] as command line I get "C:\Windows\System32\osk.exe was not found" as standard error output.

On the other hand System Exec with [ cmd /c "C:\Windows\System32\calc.exe" ] opens the windows calculator.

[pincpanter]

---

@rolfk  ha scritto:

---

@pincpanter wrote:

You forgot to type a space between cmd and /c.

---

Well don’t see any cmd /c in that pic

---

Try again. Time to upgrade your glasses? 😊

Anyway: suppressing the space, I get error 2. With the space, I get in the standard error output: "osk.exe not recognized as a command ...".

The problem is that osk.exe is in the \Windows\System32 directory.

However, the content of \Windows\System32 exposed to a 32 bit process is different from that exposed to a 64 bit process.

To show the difference, compare the output of "cmd /c dir C:\Windows\System32" in a console window and in the standard output of SystemExec.vi

Being my LabVIEW 32 bit, osk.exe is not found in that directory.

[rolfk]

Weird, I have used that in the past in several applications, although admittingly compiled in LabVIEW 2013 and 2017. And that application has been installed on many computers. Maybe it is in SysWOW64?