Damnation

@George King I'll make a new ACPI x64 once @Mov AX, 0xDEAD has a fix for object already existing.

@Mov AX, 0xDEAD I get these AE_ALREADY_EXISTS errors when I boot into Linux and check the boot logs too. Linux at least, although it notes the error, seems to not care.

@Mov AX, 0xDEAD I followed example set by @Andalu and got this output. too large to attach uncompressed, sorry. TRX40_DESIGNARE_ACPI_DEBUG_1.zip

@Mov AX, 0xDEAD OK, I got it started - Microsoft (R) Windows Debugger Version 10.0.19041.685 X86 Copyright (c) Microsoft Corporation. All rights reserved. Using NET for debugging Opened WinSock 2.0 Waiting to reconnect... Connected to target 192.168.88.22 on port 50000 on local IP 192.168.88.33. You can get the target MAC address by running .kdtargetmac command. Connected to Windows XP 2600 x86 compatible target at (Mon Apr 25 15:29:39.685 2022 (UTC + 8:00)), ptr64 FALSE Kernel Debugger connection established. ************* Path validation summary ************** Response Time (ms) Location OK C:\Symbols Symbol search path is: C:\Symbols Executable search path is: Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp3_qfe.180912-0606 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 System Uptime: not available Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 8052b718 cc int 3 ************* Path validation summary ************** Response Time (ms) Location OK C:\Symbols Symbol search path is: C:\Symbols Executable search path is: Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp3_qfe.180912-0606 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 System Uptime: not available Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 8052b718 cc int 3 kd> g ACPIInitializeDDB: AMLILoadDDB failed 0xc0000035 *** Assertion failed: ACPIInitializeDDB: AMLILoadDDB failed to load DDB 0 *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\shared\acpiinit.c, line 509 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? I recall you saying I need to enter !amli set spewon verboseon logon traceon after ed KD_ACPI_Mask 0xFFFFFFF at some point but I haven't reached that point yet. so what do I type in next?

@Mov AX, 0xDEAD Tomorrow, I'm also gonna try and get KDNET debugging up and running for my AMD Threadripper system, can you send me all the files I'll need to get started? P.S - I only have 1 PC screen, will that be an issue?

@pappyN4 @Dietmar you might need a crossover cat6 for direct PC-to-PC link, at least if MDIX is not supported. I would imagine these cards would support MDIX though.

b9a129fe: Name(SLIC,Buffer(Zero){}AMLI_ERROR(c0000206): Invalid buffer size Buffer: invalid buffer size (size=0) [/code] why would buffer size be 0?

@WinWord2000 Use XP Integral Edition with Optional Patch Integrator Script. In the script use options 1,3,4,5 and 7. put customized ISO onto USB with Wintoflash, install XP.

@daniel_k Oh, that's much simpler than I thought it was going to be, thanks! Some systems might need the OS version lie however, it seems @George King has a system where the GPU is hidden behind ACPI OS version code. Although it seems for this specific case "Windows 2006" should be sufficient given that ACPI 5048 worked.

@George King What was the modification to 5048 ACPI for GPU to work? we should implement this in C code if we can.

@Andalu Here, I made a checked build x86 acpi.sys for you. https://anonfiles.com/hfHcw4Z1x4/checked_acpi_xp_forandalu_7z

@pappyN4 Do you get this behavior with the default XP x64 acpi.sys too?

@reboot12 welp, I stand corrected then.

@George King @Dietmar I think using my x64 acpi.sys for your XP2ESD project should be a safe choice then I think.

@Dietmar Prior to using my x64 acpi.sys did this board have any BSODs with the original x64 acpi.sys?

@Dibya Yeah, we know about those already. We've gotten XP to boot in UEFI already, XP x64 on real hardware only though, and it's unstable.

@Dibya I believe ArcaOS is closed source? I could be wrong though.

@Andalu Symbols for halmacpi.dll halmacpi_symbols_forandalu.7z

@Andalu I've compiled a matching acpi.sys\acpi.pdb for you. https://anonfiles.com/T2x2h7Z7xe/acpi_xp_forandalu_7z

@Andalu Place the 4 ntoskrnl PDB files I sent you into W:\Symbols1\exe - see if that works. acpi PDB would go in W:\Symbols1\sys

@Andalu can you share a directory listing of W:\Symbols1 ?

@Andalu looking at your log file symbols should go here Symbol search path is: C:\WINDOWS\Symbols this path should be on your HOST machine (the one running windbg) not your TARGET machine (the one with the BSOD)

@Welder Welcome! This would be an extremely difficult task - Vista and later use WDDM driver model whereas XP and earlier use XDDM driver model. I'm not saying it'll never happen, but it's not likely. Best use XP compatible Maxwell and earlier GPUs for nvidia on XP.

@George King@Mov AX, 0xDEAD We could also try the ACPI OS version lie trick in the driver instead of editing the DSDT. I don't remember how to do the trick though. but I'm sure ACPI OS version is defined somewhere in the code.

@Andalu I got you PDB symbols for all 4 ntoskrnl's hope this helps. https://anonfiles.com/vbK9Z1Y7xa/andalu_ntkrpamp_symbols_7z for acpi.sys PDB symbols, build from source.