on screen keyboard not working with labview

[UliB]

---

@rolfk wrote:

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?

---

In windows file explorer or in a command line window (dir os*) I see osk.exe and OskSupport.dll in C:\Windows\system32 but not in C:\Windwos\SysWOW64.

If I execute [ cmd /c "dir os*" ] with System Exec and set C:\Windows\system32 or C:\Windwos\SysWOW64 as working directory I do not get osk.exe or OskSupport.dll in the list (but osbaseln.dll and osuninst.dll). So the command is executing, but returning a different output.

I'm on Win10 22H2 using LabVIEW 2022 Q3 (32bit)

[UliB]

OK, I got it working. I simply copied osk.exe and OskSupport.dll from C:\Windows\system32 to C:\Windows\SysWoW64 as proposed here:

https://support.industry.siemens.com/cs/document/109780864/why-can't-you-open-the-on-screen-keyboard... 

And [ cmd /c osk.exe ] is enough as command line.

[GerdW]

Hi,

this is what works for us:

It's both times the same kernel function call…

(Win7 uses the simple SysExec call without Redirection.)

[rolfk]

Another option is to use %windir%\Sysnative as path instead. This is not a real path but tells Windows not to redirect System32 to SysWOW64 when used in a 32-bit application context.

[UliB]

---

@rolfk wrote:

Another option is to use %windir%\Sysnative as path instead. This is not a real path but tells Windows not to redirect System32 to SysWOW64 when used in a 32-bit application context.

---

For me %windir%\Sysnative\osk.exe translates to C:\WINDOWS\Sysnative\osk.exe, but using it I get a windows error dialog "Der angegebene Pfad ist nicht vorhanden." (The specified path does not exist.). Seems like Sysnative does not work on my system.

[UliB]

---

@GerdW wrote:

Hi,

this is what works for us:

It's both times the same kernel function call…

(Win7 uses the simple SysExec call without Redirection.)

---

Isn't it   Wow64DisableWow64FsRedirection   and   Wow64EnableWow64FsRedirection  ?

[GerdW]

Hi Uli,

---

@UliB wrote:
Isn't it   Wow64DisableWow64FsRedirection   and   Wow64EnableWow64FsRedirection  ?

---

You are (partly) correct!

The 2nd call is to Wow64RevertWow64FsRedirection