Some things about WoW64 pluggin

hi,

Reference in
   http://win10se.cwcodes.net/Projects/Win10PESE/Build/5-Wow64.script
   http://re boot.pro/topic/21695-setwow64exe-and-loadwow64exe/?hl=misty#entry206134

What i saw :
   the two programs do the same thing but in different contexts ( The available APIs are different )
   "SetWOW64.exe" seems no more used
   "loadWoW64.exe" seems not useful after build 14393

note : in the pluggin, perhaps "-Replace2X" and not "-Relpace2X" in "ShellExecute,open,WOW64Patch.exe,-Relpace2X,%ProjectTemp%\WOW64Basic"  ? ( see below )

Knowledge is lost in the course of the versions.

[Main]
Title=5 - WoW64 Basic
Type=Plugin
Author=JFX
Description=WoW64 (Windows on Windows64) provides support for running 32bit programs in a 64bit environment.
Credits=All credits go to Microsoft for developing this Operative System and to everybody on the BootLand forums for helping on the debuggind and improvement of this plugin. yamingw setWow64 tool
Version=051
...
[Files_10_only]
//- SetWOW64 by yamingw. It works by creating the KnownDlls32 kernel object and linking it against X:\Windows\SysWow64 folder. It ~does what smss.exe should do. Note that it does not allow ThinApp packages to work.
//ExtractFile,%ScriptFile%,Files,SetWOW64.7z,%ProjectTemp%\WOW64Basic
//ShellExecute,Hide,%Tools%\7z.exe,"x #$q%ProjectTemp%\WOW64Basic\SetWOW64.7z#$q -y -o#$q%Target_Sys%#$q"
//TXTReplace,%Target_Sys%\winpeshl.ini,[LaunchApps],"hiderun.exe SetWOW64.exe"
//TXTAddLine,%Target_Sys%\winpeshl.ini,[LaunchApps],Prepend
ExtractFile,%ScriptFile%,Files,loadWoW64.exe,%Target_Sys%
RegHiveLoad,Tmp_System,%RegSystem%
Call,RegMultiSZ,Append,Tmp_System\ControlSet001\Control\Session Manager,BootExecute,loadWoW64.exe
RegHiveUnLoad,Tmp_System
....

[processWinNT6]
...
// Change driver Letter is useless with 14393 and Up. Already X:, also Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion,PathName no longer exist
If,%ver3%,Smaller,14393,Begin
Echo,"Set drive letter to X: ..."
ShellExecute,open,WOW64Patch.exe,-Relpace2X,%ProjectTemp%\WOW64Basic
End

My english is poor. I use a translator. So, I hope you can understand the following.

More generally :
   In Pluggin, are there still substantial changes to older OS versions (winpe for xp, vista, seven, 8, 8.1 ...)?
   Is there an advantage to changing logic by doing a repository of scripts per OS version?
        The non-regression tests would be less numerous. So the quality is improved
   I do not believe that a writer of a new Pluggin will test it on all the old versions of OS nor now on all the old builds of Winpe10 ( two by year ! )

What does the community think?

Knowledge is lost in the course of the versions.

You get wow64 working on project, than knowledge is not lost. 
Memo written inside plugin by authors can change, which is up to them.

More generally :
   In Pluggin, are there still substantial changes to older OS versions (winpe for xp, vista, seven, 8, 8.1 ...)?
   Is there an advantage to changing logic by doing a repository of scripts per OS version?
        The non-regression tests would be less numerous. So the quality is improved
   I do not believe that a writer of a new Pluggin will test it on all the old versions of OS nor now on all the old builds of Winpe10 ( two by year ! )

What does the community think?

2 Year 
Same Wow64 plugin since written for PE1 works fine with all projects: Gena (10 year I guess), Win7PESE, Win8PESE, Win8.1SE, Win10PESE.

When updated, It is updated at all projects.
This way the quality of the plugin on all projects keeps at the same level.
--> Result: No trouble with Wow64 plugin for years now. Self prove all fine.

Hi Lancelot,

You are right.
I wrote too hativement.
I sometimes look for a detail in a pluggin and sometimes I digress in philosophy. But not in criticism.
If the maintenance of the pluggin seems complicated, I do not have to give in my opinion.
Thank you for being nice to me despite my stupid remarks.

Hi Noel,

the SetWOW64.exe does create KnownDllPath symlink and also adds all the file mappings.
Someone create the loadWoW64 as a native exe (good if admin login is used and SetWOW64 alone may not works), but he "forgot" to add all the file mappings.

On wuyou forum there also showed up kmwow64.exe that combines both features to one native exe.
But Microsoft has fixed the bug in smss.exe and we don't need them anymore.

I sometimes look for a detail in a pluggin and sometimes I digress in philosophy. But not in criticism.
If the maintenance of the pluggin seems complicated, I do not have to give in my opinion.
Thank you for being nice to me despite my stupid remarks.

Hi Noel,

Feel free to give an opinion. 
Also, try to figure out why things design that way you see. 

There is wow64 topics time to time around the forum for years now.......



*
This may help you with your posts with English.

https://www.grammarly.com/

I use Add-On of Grammarly on FireFox which works fine so far.
Not perfect but works fine.

Here is the picture when writing the current post, Grammarly underline with red.

And I try to fix as much as I can.