Adding the Windows 2003 Server files disk.inf + crcdisk.sys = BSOD after the last Installation reboot.
You cannot, because the addon includes the newest files that were integrated into it. If you just mean the registry changes, they are in opmwxpup.inf of the OnePiece Update Pack (at least for XP)
I had made an empty XP x64 GENA ISO, so I can add the software that exists in XP2ESD (especially the auto-Sysprep, backported drivers, BCD support, etc) The reason why I wanna do this is to see if I can get to boot Windows XP x64 PE from UEFI on modern hardware. An installed Windows Image requires more drivers resulting in 0x7B BSOD in real hardware, but in Windows XP PE, at least the OS theoretically should be able to load even tho the lack of Mass Storage drivers will prevent newer HDD/SSD from showing unless drivers are integrated. Grub4Dos for UEFI images can show the mapped driver on RAM or rely on SVBUS x64 (It works on VirtualBox legacy mode. But on real hardware UEFI Class 3, if SATA mode isn't set to AHCI, it doesn't work for Windows 7 PE but works on Windows 10 PE).
First of all: THX for all your work on this project! I`m trying to create a XP_x86_German.ISO and struggling at some points. First i was confused about paths with "VirtualBox", i changed paths in "config.ini", but had also change paths in "setup.cmd" (changed everyting to drive "Z"). Integration with nLite works, installation starts and continues until restart, then i run into bluescreen within the VM. When i manually stop the VM it is deleted and gone. EDIT: The script went on and an "install.wim" was created. After that everything was stopped/closed, no ISO was created. EDIT2: A try by building an ISO manually (copied the files manually) ran into fault not getting the right sourcepath. I change back the paths from Z to X and try again.
Dear @George King, welcome back in the game! I hope everything`s fine, you`re still healthy and motivated. Can`t await 1.6 release!
Now as i see development in the progress of the tool, i got to tell, what my goal was (and is), before i discovered this thread. I know some things about "install.wim", how to install it with a "boot.wim". I`m able to merge different "boot" and "install" into ISO, so i did with an updated "Win7" installed by a "Win10-Boot". I`m able to create a "WinXP_SP3_AllUpdates.iso" by myself, since i`m used to nLite since 2003. I can install this XP-Iso into VM, modify it to my dues and create a WIM from VHD - that`s what i`ve done. I`ve got a WIM with an installed XP_x86. I run a WDS-Server (2019) in my homenet, i put a "boot.wim" from "Win10_x86" into it and the "install.wim" from XP. Started "Hyper-V" (even tests with VirtualBox and VMWare) over network and the "install.wim" was deployed to disk in seconds. In some cases i had to change the boot-order in the VM, but XP started up with no issues. Great step, i was impressed! The real goal of mine is to put this into an ISO. So i put the same "boot.wim" and "Install.wim" into some folder, let NTLite take control. I made about 100 variations of this, but no effort. Sometimes it misses the "install.wim" (No Images were found) or it can`t find the licence file.