Feb 09, 2017  OSK.exe is the on screen keyboard on Windows 7. When I run 'osk.exe' from the command line it opens fine but when I create a script with any of the following (listed below). OSK.exe is the on screen keyboard on Windows 7. When I run 'osk.exe' from the command line it opens fine but when I create a script with any of the following (listed below): run osk.exe.

Hi experts, I have a problem of not being able to execute osk.exe in the Windows System32 folder (from my VB6 app). If I copy osk.exe to my App folder and execute it (programmatically using CreateProcess or Shell) then all's good but I'd rather not do that because that means I'll either need to copy it from the target Windows folder to my App folder at install time (which I may have problems anyway) or I'd need to supply it as part of install but I should really be using the app that is appropriate for the target environment rather than one that I supply. Any help would be appreciated. Thanks, Mike. Hi Qlemo, I tried both of those and there's no problems running the (osk.exe) App. I then (programmatically) copied the App to various folders and run it from there but again the same problem. It appears that an app from System32 and SysWOW64 (on my Win7) can't be executed programmatically unless a security/privilege setting is adjusted however my colleague can execute the App on his Win8.

As soon as I get a chance I’ll try the same on another Win7 and see how I go. Thanks for all your suggestions.

The Portable App - On-Screen Keyboard and the KeePass On-Screen Keyboard plugin both suffer the same issue when run from any 64 bit Windows 7 PC I have tried them on. Both programs work fine in 32 bit XP and 32 bit win 7. This is what I found. (Visual Basic Development Center) This is an issue with 64-bit OS, it affects any 64-bit version of Windows.

Nextstep os. NeXTSTEP is an innovative OS made in the 1990s. Most of its features are present in Mac OS X today. This is a demo of NeXTSTEP running in a Virtual Machine. Does anyone have this install CD? I have my black hardware, its serial #, and a full, licensed set of manuals and media for NeXTSTEP v3.2 for Intel, NeXTSEP v3.3 for all platforms, and OpenStep v4.2 for Intel and Mach. So I don't think there's licensing issues with my asking after this CD. NeXTSTEP, from NeXT Computers headed by Steve Jobs, is a Unix based operating system designed to run on m68K NeXT workstations. Installation instructions. Note: The 3.x CDs are in BSD Unix format rather than standard ISO. Many CD utilities will not directly open these images, requiring you to.

Basically you are calling osk.exe, but your program you are calling it from is a 32-bit app. Windows won't allow you to call a 64-bit OSK.exe from your program. The comments appear to miss your point here, anyone can start osk.exe from Run, but call it from within a 32-bit application won't work in 64-bit Windows. I am developing software that uses the on-screen keyboard, the only work around is Wow64DisableWow64FsRedirection.

Ideally Microsoft should include a 32-bit version of OSK.exe in the system folder and allow us to use it, if being called from a 32-bit application. Another work around is to get your hands on 32-bit Windows XP and pull osk.exe from it, bundle this with you app. When you call the on-screen keyboard, check if OS is 64-bit, if it is call the Windows XP osk.exe, works OK. Although not ideal.

I hope this finds it's way to someone who can use it to make the On Screen keyboard app work again in 64 bit Windows. [Quote changed to a - mod Chris].