Tryind to add osk.exe

Hi,

I would like to use in winpe a on screen keyboard, and tried to use osk.exe from C:\Windows\system32\ but only copy the osk.exe to mounted BOOT.wim into Windows\System32\ is not working.
If I try to run osk.exe, nothing happens :(

Tried a other virtual keyboard like freevk

But is not working, I think because as described in someones blog (cannot post external links), not working on 64 bit systems.

Anyone have an idea?

Thanks!

I think from testing I did in past you need more than just the osk.exe for it to work

From my notes I just dug out:-

osk.exe
osksupport.dll
mmdevapi.dll

and possibly coremessaging.dll

You are genius!
I spent one hour on searching in web, tried with process monitoring tools on osk.exe but did not find any required dll files!

It is working with the required dlls you listed!

Thank you!

Sorry for double post, but I cannot edit my own posts :(

Do you have a solution to run osk.exe on startup?, I'm new in this section, I read that startnet.cmd will be ignored if there is an existing Winpeshl.ini.
According to the documentation, it is not possible to run 2 Apps together:
"The apps listed in [LaunchApp] and [LaunchApps] run in order of appearance, and don’t start until the previous app has terminated."

I need a solution for osk.exe start on startup, and should always be on top.

for the file list, you can found from the WIN10XPE project.


WIN10XPE\01-Components\za-Accessories\Accessibility\main.bat

Code: [Select]

goto :main
Title=Accessibility
Type=XPEPlugin
Description=Ease of Access, Magnify, OnScreenKeybord in addition to narrator
Author=ChriSR
Date=2018.05.30

:main
rem ==========update filesystem==========
call AddFiles %0 :end_files
goto :end_files
@windows\system32\

; In Common Osk Paint Wordpad
IconCodecService.dll,UIRibbonRes.dll
;WindowsCodecs.dll already in winre.wim
WindowsCodecsExt.dll

+mui
; mfc42u.dll already in winre.wim
UIRibbon.dll

; Osk
osk.exe,utilman.exe,OskSupport.dll

; Ease of Access
accessibilitycpl.dll,Magnification.dll,Magnify.exe,PlaySndSrv.dll,sethc.exe
;Windows.Media.Speech.dll
Windows.Internal.Shell.Broker.dll,Windows.Perception.Stub.dll,Windows.UI.dll

:end_files

for the startup, normally, they use pecmd.exe pecmd.ini for the startup process.
in the pecmd.ini, you can EXEC !osk.exe.

copy wpeint.exe line to startnet.cmd, and delete the winpeshl.ini, maybe work, but the cmd.exe window shows.
if you want hide the window, you can use the Winpeshl.ini with hide.run.exe, cmd /c yourstartup.cmd.

WIN10XPE\01-Components\za-Accessories\Accessibility\main.bat

That is a PESE File which now shares XPE Project Name
Thus Not a XPEPlugin, Nor was the Author ChrisR

Acturally, The file is a patch of WimBuilderUI(use simple batch syntax to modify the wim file with HTML UI settings).
http://theoven.org/index.php?topic=2390.0

Thus Not a PESE File, Nor a XPEPlugin.

The content is porting from:

D:\dev\Win10XPE_2018-10-12\Win10XPE\Projects\Win10XPE\Features\Accessibility.Script

Code: [Select]

[Main]
Title=Accessibility
Type=XPEPlugin
Description=Ease of Access, Magnify, OnScreenKeybord in addition to narrator
Author=ChriSR
Date=2018.05.30
Version=001
Selected=None
Mandatory=None
NoWarning=False
Level=0
Download_Level=0
Credits=
Contact=

so I just keep the description on the header.

WIN10XPE\01-Components\za-Accessories\Accessibility\main.bat

That is a PESE File which now shares XPE Project Name
Thus Not a XPEPlugin, Nor was the Author ChrisR

Hi James,

It is good people keep header information when porting to other projects with other builders that .script do not run.
slore use .bat
Kare use .srt

Good People show their respect the original source which is common by open source authors.
Edit:
When Keeping same header information not possible (using same builder),
Good People provide info to original authors and a copy of essential parts of original header. (Author= Date= Description= History......  etc.)
You can find info on many plugins pointing to the original.

Keeping header info shows the personality of the author.

ps: Type= not important for projects that do not use .script 

***

so I just keep the description on the header.

Thanks slore.
I do the same thing when porting.

If I can find some free time, I will be around wimbuilder and winxshell soon (maybe after 2 week with this busy life)

*
Forgot to mention,

Just for the record:
"On Screen Keyboard" plugin available since ~2011
( since XP (Gena) to Win10 (Win10PESE/Win10XPE) )
http://yomi.cwcodes.net/index.html


*
Back to subject.

Do you have a solution to run osk.exe on startup?

I may guess James will provide you information to edit X.ini or X.cmd or ? file to add osk to startup.

I leave X decision to James, I do not know the decision priorities of startup at Win10XPE

Following this Topic

http://theoven.org/index.php?topic=2624.0

OSK - Tablet Mode is launched via pecmd.ini _PostShell

Places OSK Launch Shortcut in system tray

Currently for XPE > OSK-Tablet Mode < was added as a "Desktop Personalization" Option

http://theoven.org/index.php?topic=2607.msg28735#msg28735

Hi, thank you for your answers. The first one helped me already :)

I remove WinpeIn.sh and used startnet.cmd, with commands:
@echo off
wpeinit
cmd /c %systemdrive/Winodws/system32 osk.exe
start MYAPPLICATION

Thanks!