Showing results for 
Search instead for 
Did you mean: 
Reply

RUN Object will not start Windows On-Screen Keyboard

Solved!
Go to Solution

RUN Object will not start Windows On-Screen Keyboard

I am running Lookout 6.5 on Windows 7 Professional. I am using a pushbutton to fire a Sequencer whose A output starts a RUN object with a command line of "c:\Windows\system32\osk.exe". The RUN object executes, but I get a window that says "Could not start On-Screen Keyboard". The window only has "OK" as an option - click on OK and the window disappears. I have tried the same RUN object with notepad.exe and wordpad.exe, and these work fine.

Anyone see what I'm missing?

0 Kudos
Message 1 of 13 (7,486 Views)
Reply
0 Kudos

Re: RUN Object will not start Windows On-Screen Keyboard

I'm able to use the Run object to launch the osk on windows 7.

 

What if you run the command in window's Run? 

Ryan Shi
National Instruments
0 Kudos
Message 2 of 13 (7,467 Views)
Reply
0 Kudos
Solution
Accepted by topic author Traders
‎08-27-2015 06:09 PM

Re: RUN Object will not start Windows On-Screen Keyboard

Thanks for your reponse, Ryan.

I have now found a solution - but first a few puzzlers. I can successfully use the Lookout RUN object to start other executables in the Windows\system32 folder - but not the osk. I can start the osk by other means (shorcut, double-click on the .exe, starting from a bat file).

I copied the osk.exe to another folder on the hard drive and can now start it with the Lookout RUN object. I'm not sure why this works differently - but it does. Thanks.

Message 3 of 13 (7,455 Views)

Re: RUN Object will not start Windows On-Screen Keyboard

Maybe it's the security issue. The windows user that launches Lookout doesn't have enough privilege to execute the exe in system32 folder.
Ryan Shi
National Instruments
0 Kudos
Message 4 of 13 (7,445 Views)
Reply
0 Kudos
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.