New
#1891
In post-build, you can use XPEStartup.cmd or/and XPEStartup.ini, at Y:\ root
They are called at startup, if if they exist, before explorer shell, via pecmd.ini
The script is in Apps\System Tools\XPE Startup
In post-build, you can use XPEStartup.cmd or/and XPEStartup.ini, at Y:\ root
They are called at startup, if if they exist, before explorer shell, via pecmd.ini
The script is in Apps\System Tools\XPE Startup
No no, I know about it, was asking about merging the registry though. Although the startup redirect script from pese works post shell, after startup or am I wrong? Kyhi did say about the Y:\Drivers too. Is there a similar method but for registry at pre-shell mode?
EXEC %WinDir%\System32\Regedit.exe /S Y:\Registry\Filename.reg
When importing a .reg file - be sure the File Paths are correct - as we build Apps to X or Y and not C
and we usually change the programs default program location
EXEC %WinDir%\System32\CMD.exe /C "FOR %%F in ("Y:\Registry\*.reg") DO regedit /s "%%F""
Does the job fine for multiple registry files. Might not work with some special characters in the name, although spaces and underscores work.
EDIT: EXEC %WinDir%\System32\CMD.exe /C "FOR /R Y:\Registry\ %%F in ("*.reg") DO regedit /s "%%F""
Added subfolder support.
Last edited by Raex-D; 03 Oct 2020 at 05:47.
Looks good, indeed. To be put in pecmd.ini or in XPEStartup.ini
You can also add it in XPEStartup.cmd, if you wish: For %%F in ("Y:\Registry\*.reg") Do Regedit /s "%%F"
Yeah it can go in either of those easily. I was only hesitant to use cmd since I had seen that you guys used powershell instead in the pese project to call forth multiple registry files. cmd has some bad habit sometimes to neglect spaces in variables. But it worked well on testing, so I was glad that I could use that instead.
Worst case scenario, I would have then attempted to use powershell and replicate the plugin from pese for xpe. But it worked well, had no problems at all.
Your pese does not come from me, I wouldn't have done it in Powershell, I don't know it well enough.
It is a Bob.omb PESE Plugin... Thus would also require Powershell to be added to PESE build.... But again it was used in his distribution of a Pre-Made ISO to allow user modifications...
Just like XPEStartup can be is external of build
Oh yeah, I did see that part (it being Bob's plugin) when browsing the list of plugins on the site. My apologies. Also, I might not be aware of it if PESE wasn't your project initially perhaps, Chris. Sorry, came to the game late indeed and I just assumed you created it or at least are maintaining it now.