Including plugin with soem 16 bit code

I have a old application that contains some 16 bit code that runs fine in Windows 10 32 bit on my hard drive.  However, it does not run on my WinPE installation on the thumb. Apparently, something necessary  for running 16 bit code  is not incorporated into the Windows 10 code on the WinPE that is present on my normal full install on the HD I have. I am using the Winbuilder Win10PE SE as the builder that I have successfully used for a number of plugins  on a thumb drive.
bruceb   

Try
Downloads\Components\Core\1 System\16 Bit support (WOW)
for x86 builds

but better use
Downloads\AppYGS\Virtualization\DosBox
Downloads\AppYGS\Virtualization\vDos

See tutorial:
Adding 3rd party plugins: \Downloads\ - MyPlugins_Direct - Yomi
http://theoven.org/index.php?topic=1208.0

Thanks Lancelot for the suggestions. Unfortunately, none of the suggestions worked. Perhaps some background on what I am trying to achieve. The program I am  incorporate into   32 bit Win10PE  is a windows 3.1 program called Stanford graphics, which does not currently have any exact counterpart for technical graphics. This program works fine in a full install on a HD, without even the need for compatibily mode. However, using Win10PE  SE  I get the following message “ SG.exe is a 16-bit application. You do not have permission to exceute  a 16-bit application in windows” Below summarizes what I get what I get using your suggestions.

1. Downloaded 16-bit support (WOW)  and installed in WinPE.  SG still did not work with the same message as above..
2. .Tried both Vdos and Dosbox and got the message “ SG.exe is a windows application and must be run in windows’
It seems that the original  windows  application is a mixture of windows 32 bit and 16 bit. Additionally since the application works perfectly in the fully installed Windows 10,it appears that some options to accomplish  running SG.exe are not being incorporated into the stripped  Win10builder SE version of windows .

Any ideas?
Bbersted

16-bit application support in Win10 is a feature that can be turned on/off.  In a normal installation of Windows 10 one would...

===> Go to Programs and Features>Turn features on or off>Legacy Components>NTVDM (Checked)

Then CMD prompt and type...

===> Fondue.exe /enable-feature:NTVDM 

I will try manually enabling in PE later this week, but until then these are the breadcrumbs I'm following...

BTW this is only for 32bit systems it will not be possible in 64bit

Thanks for your input bob
Have tried some things on my own in this regard. First some observations.
1. The message I get trying to run Windows 3.1 pgm is " you do not have permissions to execute 16-bit applications.check your
permissions with your system administrator.". I have administrator rights. Even trying "Run as Administrator
2. None of the components that seem to be necessary are present in the Win10PE SE bootable thumb drive (X:)
3. Copied files NTVDM.exe ( and corresponding DLL's), Fondue.exe, optionalfeatures.exe into System32directory on X: of booted thumb drive.
Trying optionalfeatures.ext and got a blank box. Tried fondue.exe/enable-feature:NTVDM to no avail. Same with using the recommended DISM enable feature.
 It seems that there must be a way to enable this , since the same version of Windows 10 32 bit and ISO on HD installed works fine. Apparently the subset of the HD installation that Win10PE SE installs on  the thumb does not contain enough to allow optionalfeatures.

Any luck on your end?

Unfortunately i havent had any time yet to apply to a fix, sorry for the delay

1.) The permission issue is because the feature is not activated

2.) It wont be present because we havent made it yet

3.) You are on the right track here.  You will need to copy all the files for the feature manually.  I would use regshot2 to take a snapshot of the registry before enabling the feature and another shot after enabling the feature.  Then I would add the files and reg keys so they are present before boot.  And start testing away...

I don't know when I will be able to look but will as soon as I can..

You wont be able to just activate the feature normally as you have seen...

Hi,

i am looking for the same.

Previous, I added net fx and NTVDM to an offline image.
After that, i used this image for WIN 10 PE SE.

I "controlled" it, with searching for NTVDM in the build  Win 10 PE SE - and found the NTVDM.exe and a few entries.

But it is NOT working!  still got the same message, as the thread starter got......

And about Win PE: adding this features....  seams to be impossible

Hi Ftmmsch,

As you may notice, it is not popular to "run 16 bit Windows applications with UI" inside PE
reminding, WOW (Windows 16 bit on Windows) is only possible with Windows 32 bit (and PE 32bit - PEx86), and relevant plugin not updated for years now (I still follow feedbacks, there is request but there is no feedback with improvement  )
https://en.wikipedia.org/wiki/Windows_on_Windows

ps: WOW and WOW64 are different.

ps: for Dos applications, there is DOSBox, vBox as mentioned before

one way is :
use qEmu to run old "Windows 16 bit applications with UI"
up to the application search internet :
install Windows 3.1 to qEmu
install Windows 98 to qEmu
install Windows XP to qEmu
install Windows 2003 to qEmu
...

after you get familiar with qEmu, you will notice qEmu is real portable and you can run qEmu inside ALL PE with the old application you use.

Memo: vmware and virtualbox are not portable and qEmu is fast enough to run old windows

Tip: There is also Virtualization\qEmu X plugin that use latest qEmu

ps: Latest qEmu here https://qemu.weilnetz.de/

Hi,

I have the same problem.

The offline image, which i used for Win10 PESE x86, i added offline  Netfx 3 +  NTVDM.
I load the second image to a virtual CD / DVD drive -  in my case, it was the drive number: "H".

Than, i used the commandline from Windows Kits 10 - with admin rights.
! - I used the enterprise versison - which is:  "index1"

Dism /Mount-Wim /WimFile:C:\ISO_FilesX86\Sources\install.wim /index:1 /MountDir:C:\test\offline
DISM /Image:C:\test\offline /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:H:\sources\sxs
DISM /Image:C:\test\offline /Enable-Feature /FeatureName:NTVDM /All /LimitAccess /Source:H:\sources\sxs

Controlled the installed features with:
DISM /Image:c:\test\offline /Get-Features /Format:Table
Dism /Unmount-Image /MountDir:C:\test\offline /Commit

Done

I allso tried to add net fx - with some "courios" commands :-)  which i didn't understand.....
Because DISM returned me failures - but the feature control told, that there IS net fx 4....

Anyway:
When i run the builder, he tild me, that net fx 3.5 is allready installed - but NOTHING about net fx 4......

I could not find out about NTVDM - It did NOT work in the created ISO.

Maybe, there is something going wrong, because i had to extract the ISO agin !
Because of Microsoft Serial Ballpoint driver ! - which causes problems - at least on toughbooks with internal GPS !

I changed the driver successfully, but in the created build - i had the problem again!

Previuos - in the original image, i did:
Dism /Mount-Wim /WimFile:C:\ISO_FilesX86\Sources\install.wim /index:1 /MountDir:C:\Mount
reg load HKLM\OFFLINE C:\Mount\Windows\System32\Config\SYSTEM
Then, go to start --> Regedit --> HKLM Offline --> Services --> Sermouse  and change the start value from 3 to 4 !
reg unload HKLM\OFFLINE
Dism /Unmount-Image /MountDir:C:\mount /Commit



Dism /Mount-Wim /WimFile:C:\ISO_FilesX86\Sources\BOOT.WIM /index:1 /MountDir:C:\Mount
reg load HKLM\OFFLINE C:\Mount\Windows\System32\Config\SYSTEM
Then, go to start --> Regedit --> HKLM Offline --> Services --> Sermouse  and change the start value from 3 to 4 !
reg unload HKLM\OFFLINE
Dism /Unmount-Image /MountDir:C:\mount /Commit



So, i extracted the build ISO and had again to do:
Dism /Mount-Wim /WimFile:C:\ISO_FilesX86\Sources\BOOT.WIM /index:1 /MountDir:C:\Mount
reg load HKLM\OFFLINE C:\Mount\Windows\System32\Config\SYSTEM
Then, go to start --> Regedit --> HKLM Offline --> Services --> Sermouse  and change the start value from 3 to 4 !
reg unload HKLM\OFFLINE
Dism /Unmount-Image /MountDir:C:\mount /Commit


Maybe, there is something going wrong.....  because, i had to make it bootable again - which i did with IMGBurn...


But today!   I found a very interesting video !
Run 16 Bit Programs on 64 Bit Windows! - WineVDM Tutorial & Demo
https://www.youtube.com/watch?v=uYU15CQcA-s 


The video is - at least in my view - not that stupid!
Because: try to run the Visual Studio, the app and the required - own 116bit software in a normal WinPE environment!

Ok - that, with the command line you can partly work around - if you e.g. "Q-dir" to the other tools in X: \ tools ...

I let the video go through my head ....

:-)

Because then I could stay with my beloved Win PE SE for the first time :-)

Thanks Ftmmsch,

It is fun watching WineVDM Tutorial & Demo
https://www.youtube.com/watch?v=uYU15CQcA-s 

winevdm page I found: http://www.columbia.edu/~em36/otvdm.html
and also https://github.com/otya128/winevdm
and this may also take your interest http://www.columbia.edu/~em36/win31dosbox.html
this is also interesting NTVDMx64 by Leecher1337 http://www.columbia.edu/~em36/ntvdmx64.html

+
yes enable NTVDM and Framework3 on your source wim
and later enable Framework plugin with v3 and "16 Bit support (WOW)" Plugin ( http://theoven.org/index.php?topic=2425.msg26099#msg26099 ) using the same source with the same index

see if it helps.

Memo: keep in mind, ms starting with NT5 (2000/xp/2003) never wanted to get 16 bit apps fully working with NTVDM (WOW)

*
Also check this :
https://reactos.org/forum/viewtopic.php?t=18510


****
As written before, wow is not popular on pe (it is the only topic since 10 years), and Bob.Omb knows better about the related subject.
 Shortly progress only with feedback by end-users like you. 

Have a nice summer