Hi dear friend, you think we can add this also : https://forums.mydigitallife.net/threads/create-your-own-multi-oem-windows-xp-dvd….21525/
"community/topics/windows-xp-setup-shutdowns-10-20-seconds-after-drivers-done-loading.57399/" at techspot.com reports a similar issue. Tried to build another XP2ESD image, the code at the end of this post is what showed up at command line with administrator privilegies. I don´t know if its relevant but, surprisinly, I got a crash dialog box stating "Boot Updater For Windows 7 Stopped Working" after step "[4] Patching Setup Design". Best regards. Code: Started on 02-Aug-2022 at 13:40:12.14 Auto-Sysprep progress: 1 / 1 [1] Extracting Windows XP Home x64 With SP2 Vl English.iso Windows XP Professional Volume License (en-US) SP2 v5.2.3790.3959 [2] Integrating UpdatePack [3] Adding Auto-Sysprep [4] Building ISO [5] Installing into VirtualBox [6] Extracting VHD Windows XP Professional Volume License (en-US) SP2 v5.2.3790.3959 [7] Capturing image [8] Exporting image Started on 02-Aug-2022 at 14:58:36.27 Windows XP Modern Installer [1] Extracting GRMCPRFRER_EN_DVD.iso Win8.1_English_x32.iso [2] Building setup structure Invalid path Building bootloader Adding DriverPacks support Adding Setup folder [3] Upgrading setup engine ERROR: The system cannot find the path specified. C:\Users\head\AppData\Local\Temp\boot\Windows\Boot\DVD\PCAT\bcd.log*: The system cannot find the path specified. The system cannot find the path specified. ERROR: The system cannot find the file specified. C:\Users\head\AppData\Local\Temp\boot\sources\*.*: The system cannot find the pa th specified. ERROR: The system cannot find the path specified. C:\Users\head\AppData\Local\Temp\boot\sources\recovery\*.*: The system cannot fi nd the path specified. The system cannot find the file specified. The system cannot find the file specified. The system cannot find the file specified. The system cannot find the file specified. The system cannot find the file specified. ERROR: The system cannot find the file specified. C:\Users\head\AppData\Local\Temp\boot\setup.exe: The system cannot find the file specified. [4] Patching setup design ERROR: The system cannot find the file specified. C:\Users\head\AppData\Local\Temp\boot\Windows\System32\setup.bmp: The system can not find the file specified. ERROR: The system cannot find the path specified. C:\Users\head\AppData\Local\Temp\boot\Windows\system32\drivers\acpi.sys: The sys tem cannot find the path specified. The system cannot find the file specified. [5] Modifying setup launch ERROR: The system was unable to find the specified registry key or value. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The system was unable to find the specified registry key or value. ERROR: The system was unable to find the specified registry key or value. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. ERROR: The parameter is incorrect. C:\Users\head\AppData\Local\Temp\boot\Windows\WinSxS - Access is denied. [7] Compressing boot.wim "G:\XP2ESD_v1.6\_output\sources\boot.wim" original size: 132644 KiB Using LZX compression with 4 threads Archiving file data: 369 MiB of 369 MiB (100%) done "G:\XP2ESD_v1.6\_output\sources\boot.wim" optimized size: 130727 KiB Space saved: 1916 KiB [8] Updating install.wim The system cannot find the file specified. 1. Windows XP Professional Volume License x64 Integrating drivers Applying RunOnceEx icon patch Applying RunOnceEx dialog patch Adding patched ACPI.sys Repacking sp2.cab Could Not Find G:\XP2ESD_v1.6\_output\sources\lang.ini [9] Compressing install.wim "G:\XP2ESD_v1.6\_output\sources\install.wim" original size: 1220668 KiB Using LZX compression with 4 threads Archiving file data: 3039 MiB of 3039 MiB (100%) done "G:\XP2ESD_v1.6\_output\sources\install.wim" optimized size: 1203727 KiB Space saved: 16940 KiB [10] Final customization [11] Building bootable ISO Finished on 02-Aug-2022 at 15:53:08.79 Process finished, press any key to exit...
@pracante Your host missing .NETs. Thats cause of all your issues Just install .NETs and repeat building process.
I already got factory installed .NET 4.8 ¿Do I really need to install 2.0 and 3.5 versions? I already tried and, somehow, it's somewhat difficult installing earlier versions on top of 4.8.
@George King As a suggestion regarding hardware support, I think you guys sometimes should do tests to ensure that the XP installation image created by XP2ESD works to boot from modern UEFI Class 3 computers. On older UEFI computers with CSM disabled, XP may boot more easily because of better backward compatibility with drivers (specifically referring to system-type drivers from the device manager). I don't understand how Windows 7 works on my UEFI class 3 laptop with Int10h emulator, so I was wondering if we can try to backport over time windows 7 and windows 8's Microsoft generic system devices from the device manager that XP lacks (like UEFI-compliant system, Acpi wake alarm, ACPI power button, etc) so XP can depend less on CSM like Windows 7, basically adding some UEFI support so we can get XP to boot more easily on Intel 8th and higher processors. Tbh I am not concerned about Int10h very much because the VGA requirement can be fixed by using an Int10h emulator like FlashBoot or UefiSeven (perhaps videoprt.sys from windows 7 should be backported in order to boot from winload.exe on bios because on UEFI it works with VmWare/VirtualBox using FlashBoot). Below, these are the drivers used by Windows 11 on my laptop but maybe we can backport from windows 7 and windows 8 system-device type drivers with versions up to 6.2 so they can be modified using CFF explorer to point to ntoskrn8.sys instead of ntoskrnl.exe (and then fixing the checksum by re-opening the file in CFF explorer and activating the checksum checkbox on the rebuild tab OR using any checksum exe program to refresh the checksum). If dependency services (listed in services.msc, but 3rd party serviwin.exe gives more details) for the driver are missing or refuse to start due to incomplete driver dependencies, 0x7E BSODs can appear especially when driver signature enforcement is disabled (if driver signature enforcement is enabled, windows will load but the OS will automatically block the driver from loading due to it causing problems, I experienced this on Windows 7).
No it’s not. XP2ESD ISO is designed to be used as fully expanded to USB / DVD as installer touch it's file system in various setup phases.
But I successfully installed XP2ESD ISO with ventoy. No error reported. OK, I'll use rufus next time and see what the difference is.
Hi George, finally i reached to complete, two times, the building of SP2EXD, one with ESD and another with WIM, both of them worked perfectly in Virtualbox, however, both of them, in my laptop, showed an error dialog box with the following text "Windows could not collect information for [OSImage] since the specified image file [X:\sources "\noreboot] does not exist". I guess I saw a field in "config.ini" regarding drive letter X ¿Could this be the issue?. PD. I used only Rufus 3.14 to lay the iso image in a usb pendrive.
Likely. I never used Grub4dos for UEFI in my life nor I own a UEFI only system. So I can't confirm or deny on the field. That would be awesome, likely that would make SVbus (or firadisk, or WinVblock) superfluous, while making possible to boot not just from fixed size VHDs but also dynamic expanding ones. Also if the driver would come from win8 VHDX could be usable as well, something that would be beneficial not just for XP and Vista but also Win7 (given the latter understands VHDs but not VHDXs)
Hi dear friend, I have "fr_it_es_windows_multilingual_user_interface_x64_cd.iso" is possible to integrate ?
@George King On setup.cmd, when building winload bcds, make sure add there the option to disable GUI boot ("quietboot on") on winload otherwise XP from install.wim will not boot from winload.