George King

Try to look into advapi32.dll from One-Core-Api, it have mentioned function Here is needed file set https://www.mediafire.com/file/3qkzns2rw4ds5z9/advapi32_One-Core-API-x86.7z/file https://github.com/Skulltrail192/One-Core-Api

Nice, I just included it so now more users can report possible problems

Here are compiled ACPI2.0 v4 from latest sources 1) x86 Windows XP x86 SP3 (5.1.2600.7777.4) + Windows Server 2003 SP2 (5.2.3790.7777.4) debug and free 2) x64 Windows Server 2003 / XP SP2 (5.2.3790.7777.4) debug and free https://www.mediafire.com/file/wsqgptapdrxhidf/ACPI2.0_v4_x86+x64_5.1+5.2.7z/file Extras included: a) _OSI extra OS list to unlock hidden devices b) modded acpiosnt.rc to overwrite PruductVersion attribute in file info, replaced "," with "." so it's now in same logic as other standard files, added .4 to easily detect which patch was used as build base

I have fixed it. I tried /Degbw and noticed tools\amd64\mofcomp.exe doesn't work properly on Windows 10 x64 host (same as build.exe). I grabbed these two from tools\x86 and now it's builded without errors!

It still complains about missing wmilog.bmf and WMI line must be commented in acpiosnt.rc, otherwise acpi.sys is not created

Seems better, but still needs some touch in acpisym.c, acpiosnt.rc - WMI line is problematic, commenting line can produce acpi.sys (It boots XP x64 on Asus K53SV laptop), but compile errors are still there

Thanks, patiently waiting for fixed v4 for 2K3

@Mov AX, 0xDEAD I compiled 5.1 acpi without any issues. When I try do same with Win2K3 source tree it fails on missing arblib.h (doesn't exist in both source trees)

@Mov AX, 0xDEAD I think you can edit acpiosnt.rc like this to easily distribute current patch version For XP (5.1) For Server 2003 / XP (5.2)

@Dietmar Have you tried it without _OSI modification too?

Yes, this laptop comes with Windows 7 and in it's days it was not possible to install XP in that machine. I will see how it goes in some daily usage

@Mov AX, 0xDEAD @daniel_k @Dietmar Now my laptop (Asus K53SV) can detect and install secondary GPU without any issues. Thanks for v4! @Damnation Can you please try to build x64 with these new fixes please?

I will try to detect If its PCI or ACPI device as @Mov AX, 0xDEAD told in few posts back. I can investigate it tomorrow. I can do things only remotely on my desktop now. I would like to see support as we have source.

I have modded by BIOS on Asus K53SV to unlock all available settings. After disabling integrated GPU I got no output at all. I must reset disassemble it and remove batery to reset CMOS. Current solution is latest patched 5048 ACPI by @pappyN4 to be able to detect and install secondary GPU.

Have you tried patched Windows 7 bootmgr too? This can work without GPU driver under pure UEFI. https://forums.mydigitallife.net/threads/tool-xp2esd-create-modern-windows-xp-installer-v1-5-6.82935/page-55#post-1731053

Yes I have added it as default option now (even in stucks in bootloop on my testing machine). Interesting is I can boot on same machine 32bit with latest v3 compiled. And 64bit stucks - I think it must be related to way how it is done now. Looking forward into this development ( and secondary GPU detection will be great too In future)

What should I do to get these informations? I can investigate it when new week starts.

@Mov AX, 0xDEAD Is there any chance to get secondary GPU available? My testing laptop Asus K53SV have integrated Intel HD GPU + NVIDIA GPU. With currently compiled (1106 or 5512 or 6666) can detect only Intel GPU. I was able to successfully install NVIDIA GPU drivers with only new and fresh modded ACPI 5048 by @pappyN4 for both x86 & x64 systems. It would be great if this new ACPI can detect it too.

Thanks, this one can actually boot XP x64 in VirtualBox! EDIT: On real HW it stucks on infinite loading bar

Thanks, but it doesn't work, 7B BSOD. I have proper drivers, it's caused by this ACPI.

@Mov AX, 0xDEAD In was wondering about x64 UEFI based PC to boot 32 bit XP - Do you think is possible to compile current NTLDR as NTLDR.efi x86_x64 target? Here I found out some source code https://github.com/ljvblfz/ntldr

Great, I can confirm, current one work on 5.2 x86 in my VM tests. I'm looking forward for possibility of compiling x64 one.

Why not use actively developed NTLite?

So now is needed solution for AMILoadDDB BSOD (only)? Seems like really good progress

I think we need to add support for mentioned H argument, but I have no idea what object type it is.