Damnation

@Dietmar In source code we just comment out entire function and return all OK?

@Andalu I have this same problem on my AMD Threadripper System, I even get this A5 0x11 0x08 BSOD on Windows 8.0 as of right now the best we can do for this case is to tell acpi.sys to ignore failed DDB Load.

@Dietmar I recall the problem was somewhere near PciInterfacesInstantiated I think the problem in ACPIArbCrackPRT might be this if (((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI) { // // It's a PCI PDO, which means a root PCI bus, // which means that we should just handle this // as an ISA device. // return STATUS_NOT_FOUND; } try commenting this out and see if that works?

@Mov AX, 0xDEAD I would like to try and see if I can implement 64bit integer support. what functions should I be focusing on to properly implement this? which acpi.sys version has a proper 64bit integer support?

I bought my first AMD Ryzen 5000 series desktop system today (previous desktop was older 2000 series with 300 chipset) I'll compile and test this when the system is ready. I went with an ASRock motherboard, for whatever reason they use an iASL compiler from 2012 for their AMD boards and they seem to be the only vendor doing this. I wonder if this might be more ACPI friendly for XP because of it?

@Dietmar But isn't that hack just skipping over the error rather than actually resolving the issue?

@Dietmar there is an ACPIDebugResourceRequirementsList function, maybe that can help?

@Dietmar you may as well try my earlier suggestion -

@TrevMUN That would be @Dietmar he's on this forum actually, he can help you get NVMe working on XP if you're still interested.

@George King As far as I know there isn't an easy way to convert assembly back into C code, at best you can get some psuedo code with a dissassembler. Everything would be so much easier if there was a reliable way to convert to C code.

We'll have to convert those functions implemented with _asm into C code if we ever want to produce an x64 version of this.

@Mov AX, 0xDEAD Concerning the CreateQwordfield implementation, would doing something like this work better? pbf->FieldDesc.dwNumBits = 8*sizeof(ULONGLONG); pbf->FieldDesc.dwFieldFlags = ACCTYPE_QWORD;

@Mov AX, 0xDEAD Nice Work! much appreciated! thanks!

@Mov AX, 0xDEAD If not 2000 then ME? I think Windows 2000 and Windows ME are on par to each other in terms of WDM driver model support. As in Windows ME's NTKERN.VXD has the same functionality implemented as 2000, unless I'm mistaken. I think it'd be cool to have storport/ahci/nvme and usb3 support in ME. But then I doubt you're that interested in supporting any of Windows 9x/ME

I recall needing AHCILDR at least for the 1st part of setup, I also tried PATCHMEM to see if that would get past the error but it didn't help.

you'll likely need an AHCI driver for your hardware.

@Adamwo Try KernelXE https://msfn.org/board/topic/182051-kernelxe-my-unofficial-windows-2000-kernel/

@we3fan I'm certain that installing an AHCI driver whilst your controller is still in IDE mode will either do nothing at best, brick your install at worst. Installing the driver will not magically switch your IDE controller into AHCI mode - that's done in BIOS. Unfortunately, since it seems your laptop model never got an AHCI option update for your BIOS, You're going to need to get into BIOS modding if you want that controller to go into AHCI mode.

@blackwingcat I've tried to PM you but you aren't accepting messages.

@we3fan What laptop model do you have? there might be an updated BIOS that enables AHCI/IDE switching.

@windows2 Out of curiosity, why 2000 and not XP?

I ran into this problem on my AMD Threadripper 3960x system, gave up after running into the VCACHE error despite rloew's patches. It runs just fine on my AB350 2700x system with rloew's patches.

@windows2 Damn! Unfortunately it seems the only viable solution for this at the moment would be to install XP. Sorry.

@Birkin_Pl My suggestion - Start from a fresh 2000 install, then install this - http://ximonite.com/kernelxe/Windows2000-KernelXE-v0.2.4.2-x86-ENU.exe then install unmodded XP 368 driver. Kernelxe covers missing dependencies for the driver so I think it should work.

@windows2 actually try this one - dl.driverpack.io/driverpacks/repack/Video_Intel-XP/Intel/FORCED/5x86/Haswell_6.14.10.5445/Intel-FORCED-5x86-Haswell_6.14.10.5445-drp.ziphttps://dl.driverpack.io/driverpacks/repack/Video_Intel-XP/Intel/FORCED/5x86/Haswell_6.14.10.5445/Intel-FORCED-5x86-Haswell_6.14.10.5445-drp.ziphttps://dl.driverpack.io/driverpacks/repack/Video_Intel-XP/Intel/FORCED/5x86/Haswell_6.14.10.5445/Intel-FORCED-5x86-Haswell_6.14.10.5445-drp.ziphttps://driverpack.io/en/hwids/PCI\VEN_8086%26DEV_041E?os=windows-xp-x86 I think for windows 2000 also install KernelXE too, to resolve missing videoprt.sys dependencies/