Hello everyone,
I need to show On-Screen Keyboard on my application, but (run("c:\windows\system32\osk.exe")) it's not working for me. If someone could tell me how to show it I'll be so grateful.
Hello everyone,
I need to show On-Screen Keyboard on my application, but (run("c:\windows\system32\osk.exe")) it's not working for me. If someone could tell me how to show it I'll be so grateful.
Hello everyone,
To solve this issue, you can just add 2 files (OSKLauncher.exe & OSKLauncher64.exe) on your aplication folder, and run one of those files depeding on the architecture (64 or 32 bit) when you need to show the keyboard. Is this simple, this two files you can find it on your computer. I hope can help someone.
Regards.
The information contained within in the link that Govinda provided contains the answer, but you have to ferret it out.
In a quick test, I tried to execute the PowerScript command Run('C:\Windows\system32\osk.exe') and at runtime I get a "Could not start On-Screen Keyboard) message box. It fails because I'm running my test PB app from the IDE (therefore, it is a 32-bit process), and on my 64-bit Windows OS, the executables in the System32 folder are 64-bit.
When I change the command to 'C:\Windows\sysnative\osk.exe', the On-Screen Keyboard app opens and I can use it to send keystrokes to a DataWindow in my test app. The "sysnative" keyword is a virtual folder that signals windows to bypass file system redirection, so Windows looks (and executes) the osk.exe from the SysWOW64 folder, which is where the 32-bit version of system executables reside. Curiously, an attempt to run the osk.exe directly from the SysWOW64 folder fails. Oh, well. using "sysnative" appears to do the trick.
Please note that the "sysnative" alias should only be used from a 32-bit application. It should not be used from a 64-bit application.
HTH, John
Hi Pau,
I'm not certain but I think this may be a 32 bit versus 64 bit issue. Try running OSK from the windows side-by-side folder (WinSxS) versus System32.
On my machine the full path would be: C:\Windows\WinSxS\amd64_microsoft-windows-osk_31bf3856ad364e35_10.0.19041.1_none_60ade0eff94c37fc\osk.exe but the folder name after WinSxS on yours may be slightly different.
HTH.
Regards...Mark
Hi Pau,
Have you tried this: http://codeverge.com/embarcadero.delphi.nativeapi/osk.exe-on-a-w7-74bit-from-32-bi/2004568
It seems that this is a very common problem around software developers and that Microsoft tool. Try and see if that post provides a solution for you.
Regards,
Hi Pau;
Since this is another App from the "c:\windows\system32" folder ... does it work if you run your PB Calling App EXE "as Admin"?
Regards ... Chris