From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
01-13-2011 02:25 PM
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?
Solved! Go to Solution.
01-16-2011 07:35 PM
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?
01-17-2011 12:51 PM
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.
01-17-2011 11:31 PM
03-18-2011 06:35 AM
Hi,
I have very similar problem but proposed solution is not working for me!
I tried to copy osk.exe in different folders but just doesn't work, I am all the time getting an error:
"Could not start On-Screen Keyboard"
I can launch osk without any problems from windows explorer and from command prompt!
I am using Labview 2009 SP1 and Windows 7 Professional!
Any new ideas how to solve the problem?!
Regards
Franjo Tonković
07-07-2011 12:56 AM
Hi franjo,
same problem here.
Did you find a solution ?
Regards,
Wim
07-07-2011 01:33 AM
Hi,
I managed to solve the issue. Since changing the folder didnt help, I additionaly tried with renaming "osk.exe" and it did help!
Regards
Franjo
08-09-2011 11:42 AM
Franjo
My guess is that this worked because, somehow, the Copy operation modified the permissions. It might be good to verify that because otherwise it might not work correctly in a deployed, built app.
val
Hi,
I managed to solve the issue. Since changing the folder didnt help, I additionaly tried with renaming "osk.exe" and it did help!
Regards
08-16-2011 01:52 AM
01-04-2012 01:00 AM
Hi All,
The likely reason why it's not working is that you're probably using 32-bit LabVIEW, but running on a 64-bit OS. Windows is not allowing you to call the osk.exe that it comes with since it's 64-bit. When you copied the osk.exe from Windows XP you copied the 32-bit version, and that's why it worked. If you were running LabVIEW 64-bit you wouldn't have an issue.
plz provide comments if this was the issue