on a particular user's desktop.Ĭredits / past references / first effortsĮverybody's obvious first guess would be to run OSK.EXE using a shortcut from the "Startup" folder in the start menu, or from HKLM/Software/Microsoft/Windows/CurrentVersion/Run.
WINDOWS 10 OSK EXE PC
In embedded / industrial PC hardware, on machines with touch screen only (no keyboard), you often face a requirement to have the Windows standard "On Screen Keyboard" available all the time, both "at winlogon" (when no particular user is logged in) and after logon, i.e. If ( at winlogon (before logon) *and* on user desktop (after logon) OSK at winlogon (before logon) *and* on user desktop (after logon)īy: Frank Rysanek of FCC prumyslove systemy s.r.o. where the above call to Wow64DisableWow64FsRedirection would not would be used which handles process creation on a separate thread with psi.UseShellExecute = false the CreateProcessWithLogon API We must use ShellExecute to start osk from the current thread ProcessStartInfo psi = new ProcessStartInfo() WM_SYSCOMMAND, new IntPtr(SC_RESTORE), new IntPtr(0)) meanwhile -> proper exception handling should be added there might be a race condition if the process terminated Thread.SetApartmentState(ApartmentState.MTA) ThreadStart start = new ThreadStart(StartOsk) Path.GetFileNameWithoutExtension(OnScreenKeyboardExe)) Private const string OnScreenKeyboardExe = "osk.exe" Static extern IntPtr SendMessage(IntPtr hWnd,
WINDOWS 10 OSK EXE CODE
The code below checks the apartment state and then makes sure to start the On-Screen Keyboard from an MTA thread: using System when UseShellExecute is set to false and also when being called from an STA thread as it seems.
However, under certain conditions, Process.Start will create the new process from a separate thread, e.g. The reason seems to be that a call to Wow64DisableWow64FsRedirection only affects the current thread. Can anyone spot where I'm doing something wrong, or provide an alternative solution for this? It seems to work fine launching Notepad, it just won't play ball with the onscreen keyboard.Ĭertain things are going on under the hood that require you to start osk.exe from an MTA thread. I've tried putting long Thread.Sleep commands in around the osk.Start line, just to make sure it wasn't a race condition, but the same problem persists. The specified procedure could not be foundĪt (ProcessStartInfo startInfo) SendMessage(windowHandle, WM_SYSCOMMAND, new IntPtr(SC_RESTORE), new IntPtr(0)) īut this code, most of the time, throws the following exception on osk.Start(): Var windowHandle = keyboardProcess.MainWindowHandle Bring keyboard to the front if it's already running Re-enable directory virtualisation if it was disabled. SucessfullyDisabledWow64Redirect = Wow64DisableWow64FsRedirection(ref ptr) Disable 圆4 directory virtualization if we're on 圆4, Var keyboardProcess = query.FirstOrDefault() īool sucessfullyDisabledWow64Redirect = false Var query = from process in Process.GetProcesses() Check whether the application is not running String processName = System.IO.Path.GetFileNameWithoutExtension(OnScreenKeyboadApplication) Get the name of the On screen keyboard Private void KeyboardButton_Click(object sender, RoutedEventArgs e) Private string OnScreenKeyboadApplication = "osk.exe" Static extern IntPtr SendMessage(IntPtr hWnd, UInt32 Msg, IntPtr wParam, IntPtr lParam) Private const UInt32 SC_RESTORE = 0xf120 Private const UInt32 WM_SYSCOMMAND = 0x112 Public static extern bool Wow64RevertWow64FsRedirection(IntPtr ptr) Private static extern bool Wow64DisableWow64FsRedirection(ref IntPtr ptr)
/ Interaction logic for MainWindow.xaml I also added some code to bring the keyboard back up if it has been minimized (which works fine) - the code (in a sample WPF app) now looks as follows: using System Not a problem I thought, I'll just disable virtualization, launch the app, and enable it again, which I thought was the correct way to do things. Which won't work on 圆4 because of the directory virtualization. Originally the code was just using: Process.Launch("osk.exe") 90% of the time I am unable to launch osk.exe from a 32bit process on Win7 圆4.
0 kommentar(er)
