The Win7 machines are 64bit, could this be an issue?

Hi Ray,

I changed the code to you recommendation. It said it couldn't find it in Sesame2. So, I copied OSK.exe from \System32 and placed it in \Sesame2 and it worked. But, it seems that it will only work in Add Data mode and not in Search or Update mode.

Also, I'm assuming that "not booting into Windows 7" means to simply run it as @AsynchShell("osk.exe"), and that running it as C:\Windows\System32\osk.exe boots it into Windows 7, is that correct?

On Element Entry

Hello Brandon,

Can you send me the test application that you have?

Also I just booted into Windows 7 and ran @AsynchShell("C:\Windows\System32\osk.exe") and the On Screen Keyboard appeared. It took 30 seconds but it did appear. So I'm wondering if Windows believes Sesame does not have rights to run programs in the C:\Windows\System32 directory on your system.

-Ray

Yes.

Ray

Hi Ray,

Yes, that was a careless mistake. After correcting it, it worked fine. However, it would not work in the application that I initially had trouble with. I really had no idea what to look for in the code because it has been working on XP and Vista machines for quite some time without issue. The only thing that stuck out was that I had used STOP in four places throughout the application. In one of your responses to another post you said to use a “Quitflag” instead of STOP. At that time I had completely forgotten that I had used STOP in any of my applications. So, I removed STOP and applied the Quitflag and all is working perfectly with @AsynchShell("osk.exe"). It will not work with @AsynchShell("C:\Windows\System32\osk.exe").

So, I believe, the moral of the story is, don’t use STOP.

Thank you for all of your time and help on this, my client is happy again!

Brandon

P.S. I'm using CreateAProcess("taskkill /im osk.exe /f /t") to close the keyboard. Do you know of a way to hide the command window when taskill is called?