I've just noticed that Windows XP Professional Reduced Media Edition was shared on Internet. You may add support for this edition to XP2ESD v1.6. This edition is only available in English and German languages for now. But beware that both of the ISOs are SP2 and if you update them to SP3 manually, then the OS will be renamed to Windows XP Professional N. If you want the ISOs, I can share the link privately since I'm not sure about if this is against the rules. @George King
A pre-release version of Windows XP N, essentially. It also becomes the latter if you update to sp3. furthermore, the (volume license) keys listed on the internet archive page are just plain old off the shelf xp pro vl keys whats next? bundling every single service pack beta build into one wim? lmao @example12345678912345678 @case-sensitive
Dont quote me . I posted a link to info . Nothing more . I wouldnt look at that edition if i had eyes in my arse and see no reason why it should be added to the project .
sorry i was just filled with rage when i saw these posts that i did not even bothered to read them properly p.s.: @George King read the dms
Reduced Media Edition = N Edition. It was only rebranded before release. XP2ESD will detect in as N I have added needed code to get UEFI support using beta EFI files for both x86 and x64 from Longhorn. But it's currently untested. I will add option to use Quibble as alternative too. GPT should work in same way as 2003. I will try it on real machine soon Got it, will answer you soon
@ExtremeGrief, @case-sensitive Please stop overreacting. You may dislike it, I can't do anything for that. But it was just an idea and I didn't say that it must be added to XP2ESD. So, getting mad is completely pointless. Also if you dislike the idea, there're way better ways to say that you disliked it. You don't have to post very mad comments.
It might be misunderstanding. Sorry for that. But I don't think this is the best way to tell your POV.
Please get back on topic . STOP QUOTING ME : I posted a link to try to avoid this moronic chit chat .
@Baldiman TV Only winload.exe / winload.efi are really needed from specific Longhorn versions. XP2ESD use boot files from used input Windows Setup (7 / 8.x / 10). And you also don’t need to press F8 to disable driver signature enforcement. You can play with them after v1.6 release
And also for booting XP/2003 32-bit in UEFI you need 32-bit UEFI, and for booting XP/2003 64-bit in UEFI, you need 64-bit UEFI. And about disable driver signature enforcement... Yes, you don't need it if you patch winload.exe/winload.efi. And... I don't think that Vista RTM/7/8/8.1/10/11 bootmgr/bootmgfw.efi can chainload Vista 5219 winload.exe/winload.efi. But Longhorn Server 6001.16497 winload.exe/winload.efi for booting XP/2003 x64... maybe newer bootmgr can chainload... But I recommend using 5219 bootmgr/bootmgfw.efi to chainload 5219 winload.exe/winload.efi, but about 6001.16497 winload.exe/winload.efi... You can play with bootmgr/bootmgfw.efi. Spoiler Offtopic: You can try to boot Vista/2008 x86 and 7 x86 on UEFI (32-bit of course) by using the Vista 5477 bootmgfw.efi and winload.efi for Vista x86, and 8 7850 bootmgfw.efi and winload.efi for 7 x86, and maybe it will be a part for your further projects like Vista2ESD and 72ESD But yes, I am waiting for XP2ESD v1.6 (and for Vista2ESD of course, because Vista and Server 2008 is my favorite OS).