Win10XPE Project General Discussions

Code: [Select]

[Variables]
%SetupFile%=PDFXCViewer.7z
%SetupFilex64%=PDFXCViewer64.7z

[Update_Container]
FileCopy,"%ProvideFiles%\{app}\PDF Viewer\PDFXCview,1.exe",%ProvideFiles%\%ProgramFolder%\x86\PDFXCview.exe
FileCopy,"%ProvideFiles%\{app}\PDF Viewer\PDFXCview,2.exe",%ProvideFiles%\%ProgramFolder%\x64\PDFXCview.exe
FileCopy,"%ProvideFiles%\{app}\PDF Viewer\PDFXCviewAx,1.dll",%ProvideFiles%\%ProgramFolder%\x86\PDFXCviewAx.dll
FileCopy,"%ProvideFiles%\{app}\PDF Viewer\PDFXCviewAx,2.dll",%ProvideFiles%\%ProgramFolder%\x64\PDFXCviewAx.dll
FileCopy,"%ProvideFiles%\{app}\PDF Viewer\resource.dat",%ProvideFiles%\%ProgramFolder%\x86
FileCopy,"%ProvideFiles%\{app}\PDF Viewer\resource.dat",%ProvideFiles%\%ProgramFolder%\x64
//--
ShellExecute,Hide,"%GTools%\7z.exe","a -y -m0=lzma2 -mx=9 -aoa -t7z #$q%ProvideFiles%\%SetupFile%#$q #$q%ProvideFiles%\%ProgramFolder%\x86\*#$q"
ShellExecute,Hide,"%GTools%\7z.exe","a -y -m0=lzma2 -mx=9 -aoa -t7z #$q%ProvideFiles%\%SetupFilex64%#$q #$q%ProvideFiles%\%ProgramFolder%\x64\*#$q"

It is a bit faster (for decompressing) if we split setup-x86 and x64 separately as you suggested. However, the structure of PDFXCviewer is too simple so I combined both (x86 and x64) in one zip file.

I did not Test Apps with Base Build (No Features or other Apps Selected)
To determine Require System Files or other Dependencies
Although noticed that process was also removed

Some unnecessary files were removed, but still make sure the program can work without these removed files.
Regarding the dependencies, are you using 'Dependency Walker', 'CFF Explorer', 'EXE_Explorer', or something else to get the list of these files?
This is a hardest part that I cannot figure it out.

Although you do exclude additional language support and a plugin for firefox..

EaseUS MobiMover requires the interface and drivers of iTunes when transferring contents, thus it is not able to work when running on a Windows or Mac computer without the latest iTunes installed.

I use 3 programs consistently when creating Apps..
Process Monitor
Regshot2
What Changed

1) Download the App Installer
2) see if Installer is compressed by using 7zip to open archive
3) Create a Base Build of XPE To Ram (No Feature Options and only those 3 Apps)
3a) if Installer or Installer Archive has .msi extension - add MSI support
3b) if x64 Build - Add WOW64 Basic Support
4) Boot XPE
4a) Run What Changed > X: > Take first snapshot
4b) Run RegShot2 - Take First Shot > Whole Registry
5) Run App Installer but do not allow launch of App - If No Error continue - else - may need to add NetFX4 or other support to build
5a) Take second snapshot with What Changed - report in program folder what changed - snapshot2.txt
5b) Take second shot with Regshot2 - desktop folder - reg-redo.txt
5c) Save Both txt Files for later use....

6) Run Process Monitor > there are 4 selected (blue) Icons in top pane - deselect all but File Cabinet


6a) Under the "Result" Header - find a "Name Not Found"


6b) Right click on 'Name Not Found" - then Include "Name Not Found"


Now Process monitor is filtered to look only for files that are not found

7) Launch the App and navigate around in the App - leave App Minimized or open...

8) Go into Process monitor - Under "Process Name" Header find the program.exe - right click Include "Program.exe"


Now Procmon filtered to find only files not found by program exe...

You can create other filters as well (not going to get into that now)
But you are generally looking for System32 and Syswow64 files
right click file name > Copy > Paste to New Txt Document, then save..

With those 3 saved txt files and a compare of the extracted files - you should be able to create a reliable App...

I have spent from a few minutes to a few DAYS creating and testing an App...

It takes time to learn, test, edit, re-test and test again with a different Arch build...

That is the challenge and the enjoyment for me..
Hope This helps...
Enjoy!

Thanks James.
This is a huge work and I could not imagine how much time it takes for you guys to finish every single project.

I will try to exploit Procmon to learn something from there.

By the way, I attach a PDF file of James' hints.

 James-Hints-Procmon.pdf (2671.98 kB - downloaded 37 times.)

Hi James

In your Plugin creators (and I guess subsequent plugins)

shouldn't

Code: [Select]

If,%Architecture%%WoW64Support%,Equal,x64False,EchoExtended

be

Code: [Select]

If,%Architecture%%WoW64Support%,Equal,x64,False,EchoExtended

and minor cosmetic with

Code: [Select]

[ProvideFiles_OpenDir_P_B]
If,Not,ExistDir,%ProvideFiles%,DirMake,%ProvideFiles%
OpenDir,%ProvideFiles%

Is the first line required as the 'OpenDir' macro creates dir, if not existing, by default?

regards and thanks for your endless forum support
APT

your BE is not correct - the shouldn't is correct...
as the variables are stacked against each other..

as far as the other it is a double positive, but ...

Thanks James.
This is a huge work and I could not imagine how much time it takes for you guys to finish every single project.

I will try to exploit Procmon to learn something from there.

By the way, I attach a PDF file of James' hints.

Very Good.. And looks very readable...

now with that in mind - can you recreate the HOW TO
with the first 8 posts of this > http://theoven.org/index.php?topic=2569.0
then merge the Procmon post at end...

Reason being current HOW TO included in project is blurry
Also, can the forum info be edited out (ie screenname etc, upper left corner)

Hi

your BE is not correct - the shouldn't is correct...
as the variables are stacked against each other..

  I bow to your superior wisdom!

Thanks James.
This is a huge work and I could not imagine how much time it takes for you guys to finish every single project.

I will try to exploit Procmon to learn something from there.

By the way, I attach a PDF file of James' hints.

Very Good.. And looks very readable...

now with that in mind - can you recreate the HOW TO
with the first 8 posts of this > http://theoven.org/index.php?topic=2569.0
then merge the Procmon post at end...

Reason being current HOW TO included in project is blurry
Also, can the forum info be edited out (ie screenname etc, upper left corner)

I GOT It....

The Win10XPE project requires a local Win10 ISO source file and from this forum I learned of the https://tb.rg-adguard.net/public.php website as one place to download the required Win10 ISO.  I was wondering and thus ask the forum members if that website is the only source that will work the Win10XPE project or are other there other sites that can be used as ISO source?  Also, could I just use the ISO produced by the Windows 10 media creation tool?  Thank you to all.

Also, could I just use the ISO produced by the Windows 10 media creation tool?

The media creation tool downloads the ISO with an Install.ESD
We Need the Install.wim thus the link provided

We Need the Install.wim thus the link provided

Thank you, James.  As always, a concise, understandable answer.  Having read about ESD file a while back, I should have remembered.

18945 w/ Admin - Just for Fun & Games

@james

Can you share the wallpaper.cant seem to find it.

here is the wallpaper > http://theoven.org/index.php?topic=2722.msg33725#msg33725

here is the wallpaper > http://theoven.org/index.php?topic=2722.msg33725#msg33725

Thanks

I GOT It....

Thanks James for updating the XPE HOW TO.

I followed your instruction and practiced with DiskFrag App.
I could get the list of dependent dll files after 3 tests.
Here is the whole process that I was trying to do: https://www.youtube.com/watch?v=SAS_KsU6EGM

Is there any other way that we can get this list of dll in one test?

You did that fast.... And made it look easy...
But as you see there are times that after loading some dependencies' - that there are now others....
always better to recheck again anywaylll

Gotta give you an A+ for that...

now I see a few things.. you added all stated name not found files - OK
then your ran extract to get required files - OK
then you copied into system folder - ok

Now that you have all the files listed in App

Use > Utilities/ Check Target Sys Files
point to your app and hit launch

target directory will show all available system files , mui and mum files..

as you may have included file locations not found in wim
that target directory will give you an accurate assessment of the Add_Files

Needless to say - You Seem To Have Mastered Process Monitor - (a lot better then I)...

Notes From a Distribution Stand point...
1) With the Base Project x86 Apps will have more SysWOW64 file requirements.
As the Base System32 files are different then the Base SysWOW64 File
So test for files in both x86 and x64 Builds - as your [AddFiles] and [AddFiles6432] lists may be different depending on Build Arch..

2) in your video I see several Apps included in Build - these Additional Apps MAY have already included a file that is required by your new App
so to minimize the chase of that - do not include any additional Apps or Features...
This will insure that no matter the App selection - your New App will run without any dependencies found in other Apps..

3) when you have a language code > \Windows\System32\en-us\glu32.dll.mui
change the language code to ??-?? > \Windows\System32\??-??\glu32.dll.mui
so as to support other languages...