the only method I have found and tried in the past is with panther xp, but personally it sucks !!! I tried to simply start install.wim with Vista or Seven boot but it doesn't work.
Installed Windows XP SP Professional, added need files and changed boot.ini. Reboot and it seems work. Then I captured image to test setup with Windows 7 setup engine. Instalation failed on Installing features with this error 0xC0000005 Code: 2021-01-05 21:47:13, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x7423F848 in X:\Sources\WinSetup.dll (+000DF848). Minidump attached (65310 bytes). EDIT: With Vista RTM setup cannot read install.wim, so this needs research with Windows 7 Setup Engine EDIT2: If I tried to boot applied image with Windows 7 Setup, after click on error and reboot I got bootmgr is missing error - thats weird as bootmgr is present on C:\ I tried to boot to PE and execute these commands to fix it, but nothing works Code: bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd EDIT3: boot.ini file was missing on deploeyd Windows, I added them, but bootmgr is still missing and I don't know how to fix it Any ideas? Maybe @abbodi1406 will be interested?
Windows FLP is based on XP embedded SP2 and it uses an install.wim based installer instead of the legacy installer from DOS era. Maybe you can try to play with it.
I tried Windows 10 setup engine form Windows 7 PE to see if same 0xC0000005 error appers. Yes same unexcpected crash appears. This also means it can be installed from ESD if error 0xC0000005 in winsetup.dll can be patched to terminate directly, it can be done
sorry but why the hell you want port winxp setup iso to a wim based setup (this in absolutely nonsense in my eyes)
Just remember that windows xp does the hardware configuration part during the initial setup. If you use install.wim, that initial setup is skipped so it's most likely that you will have BSOD 0x7B every time you deploy a image because you are lacking the correct storage drivers. Vista and windows FLP are the first ones that are designed to work with install.wim in different systems. With XP you can only do that if you capture an image and deploy it on the same machine. Unless you can find a way to port the windows FLP initial setup process to windows xp
@ma.prezentalok Thanks for info. 1) XP2ESD have working solution for detecting correct HALs and Kernels during first boot. So already solved using modded Longhorn NTLDR. And we don't use real XP sysprep, but customized MyFactory project turned into "auto-sysprep" 2) Images created by XP2ESD are booted trough bootmgr + BCD + NTLDR. To boot using winload.exe are needed some steps to be finished, but it's doable using winload.exe v6.0.6001.16497 (longhorn_beta3.070330-1720). This new option will be part of XP2ESD v1.6