seriously, you are not (anymore) a newbie, you should by now have learned how your approaches of setting before you a goal (often a difficult or complex one, or however well beyond your current reach/possibilities) and then putting together randomly bits and pieces you get from here and there without taking the time to study and understand the basics of the involved tools or of a given method are deemed to either failure or take an endless amount of time, even after having been steered away from your initial mis-planning into the right direction?
You do not really believe that the good MS guys created a .script interpreter that can read and execute Windbuilder .scripts, do you?
maybe that will make more clear to you that cscript is related to the Windows Script Host (and that it "understands" ONLY scripts written in some LANGUAGES, .vbs for VBScript and .js for JScript).
- Visual Basic Script is one script LANGUAGE. (and it is interpreted by cscript.exe)
- Java Script is another script LANGUAGE.(and it is interpreted by cscript.exe)
- Batch is yet another script LANGUAGE (and it is interpreted by command.com or cmd.exe)
- Winbuilder is yet another script LANGUAGE (and it is interpreted by Winbuilder.exe)
If you want to "get" something out of a Winbuilder .script, you need to study and understand the Winbuilder .script syntax.
If you want to "translate" this something into a batch script, you need to study and understand also the batch script syntax.
The above is usually obtained (at least this is how all the other people learned the Winbuilder or the batch syntax) by studying it, and then trying writing small, simple scripts, and experimenting a lot, you simply cannot expect to get to the level of interpreting a complex script such as the Wow64 one for Winbuilder without having first got the basics, and as well you cannot expect to write a complex batch file if you cannot write on your own simple ones or - as it seems - you cannot even understand why a working, tested, already written batch suddenly fails to work when you try to run it.
Same applies for getting the info from the Make_PE3, in this case you won't need to study and learn Winbuilder syntax, but you will need anyway to study and learn the batch one.
And it still seems to me like you are missing a very basic concept, the Wow64 (32 bit sub-system) addition to a PE is made essentially of 2 (two) different parts:
- adding the needed files
- adding the needed Registry hives/keys
If you add the files only, it won't work.
If you add the Registry hives/keys only, it won't work.
BOTH parts are needed.
Of course, there is always the possibility that someone (doesn't matter if moved by pity, simply good disposition or to only stop you from re-asking always the same thing) will do what essentially is your homework, like it happened in the past, but does it gives you a sense of satisfaction to not learn anything, even after months of dealing on the same topics?