@Baldiman TV No patching needed to Disable Driver Signature Enforcement (tested with standard image based on Windows 7 + 10 setup engine) Of course there are 32 bit and 64bit winload.efi files. 32 bit have also newer version in 5384 which I have in collection. There is reason why XP2ESD use boot files directly from setup media. In my tests it works without problem EDIT: Also If there is problem with digital signature, needed file can be resigned
@George King However, all versions of bootmgr/bootmgfw.efi (including 5048 one) requires ACPI to boot, and as a result, non-ACPI HAL will be probably irrelevant
I don't expected usage of different hals in modern boot methods. These methods should be always halmacpi + ntkrnlmp. How it looks in XP2ESD v1.6 In first part of build process is created needed boot structure. During XP2ESD setup are these files used to boot. I tested it with 7 / 8.0 / 8.1 / 10 as sources and it works fine. BOOTMGR + BCD BCD have enabled Legacy NTLDR boot option to see boot.ini settings. 1) NTLDR from Longhorn 6.0.5001.0 (winmain.040927-1610) for x86 Legacy boot - Last one that support detect HAL feature for every XP HALs and kernel Code: [hal] acpipic_up = halacpi.dll e_isa_up = hal.dll mps_up = halapic.dll mps_mp = halmps.dll acpiapic_up = halaacpi.dll acpiapic_mp = halmacpi.dll 2) NTLDR from Longhorn 6.0.5048.0 (winmain_idx02.050401-0536) for x64 Legacy boot is same HAL for two different kernels Code: [hal] acpiapic_mp = hal.dll acpiapic_up = hal.dll 3) winload.exe + mui for x86 / x64 from 6.0.6001.16497 (longhorn_beta3.070330-1720) for Modern boot. Currently works as second boot option after NLTDR loading. Pagefile size error needs to be solved 4) PC is scanned for other bootable partitions with \Windows\system32\winload.exe and add them into BCD UEFI (UNTESTED) BOOTMGR.EFI + BCD BCD is created as copy of standard one and have enabled Legacy NTLDR boot option too - untested if it can really boot 1) winload.efi from Longhorn 6.0.5384.4 (winmain_beta2.060518-1455) for x86 Modern boot option 2) winload.efi + mui from Longhorn 6.0.6001.16497 (longhorn_beta3.070330-1720) for x64 Modern boot option 3) Quibble 20210111 + WinBtrfs v1.7.7 (last one that works under XP) for x86 / x64 as opensource replacement to winload.efi as quibble.efi 4) PC is scanned for other bootable partitions with \Windows\system32\winload.efi and add them into BCD
@George King Can you add support for Microsoft official MUI Language packs for languages like Romanian?
Did you mean integrate MUI to ISOs or install MUI after installation? If you meant integrating MUI to ISOs, then I think it should be either completely impossible or extremely hard. I tried to make Windows Server 2003, Web Edition in German language. But it's not possible as it's still English. If you meant installing MUI after installation, then there's a chance to XP2ESD detect as in en-US or whatever the base language is. Anyways, it's a cool idea.
As an early adopter of XP64 since the beta days, I agree. XP64 is way better. But don't make the false assumption I did at the time... I thought what looked obvious: 64bit is better than 32bit. It was obvious and (mostly) wrong. The truth is that xp64 was faster and most robust not because the 64 v.s. 32 bit but because, the kernel 5.2 v.s. 5.1 Not convinced? Install Server 2003 x86 or, even better, windows home server 2007 (which is 32bit only and comes with all codecs that server 2003 lacks), turn it in to client using ntswitch or tweaknt, and you'll get what I call XP52, which is as fast (faster actually) and as good as XP64.
But sadly Server 2003 lost support in 2015 so you can only get updates up to 2015 and not 2019 as you would get on NT 5.1
and how about uploading or sharing the update pack for XP x86 and x64? It would be at least a preview while we wait for XP2ESD v1.6 (I think)
Okay so I had more time to set this up, got through the Snappy Driver installer and rebooted but didn't get the OOBE XP installer like in the video, has that changed now? Because its on the desktop and seems fine. All the applications are installed. That said it doesn't seem to be able to use either my 520UHD graphics (intel 6th gen) or my Nvidia 940M, which I tried installing by editing the nv4_dispi file. However didn't know what "Section###" the 940M has, checking newer drivers its not listed. 930MX is supported by XP so this should work? I tried Section001 and it did install however trying to open the NVidia control panel it says "You are not currently using a display attached to an NVIDIA GPU". Cannot launch any games.