Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)

[Dietmar]

@Andalu

The last version of acpi.sys 6666 for the XP Integral Edition has a hack from me for >= z490 boards (or better chipset 1200)

which is yours,

about acpi must be fullfilled. So the problem with Bsod A5 (0x03, 0xA6672420, 0xC0140008, 0x494E495F) may be also there,

you only dont see it. I dont have a board with chipset 1200 because of no money in this time

Dietmar

Edited April 13, 2022 by Dietmar

[Damnation]

@Dietmar

I will test these acpi.sys on my Ryzen Threadripper system when I have time tomorrow.

[Andalu]

@Dietmar

I'll try to prepare and install a new XP ISO with your last acpiV22freeDDBhack. But always using an usb stick :)

[daniel_k]

@Andalu

Nice to see you here! 

What is the exact model of your Gigabyte H470 board?

[daniel_k]

@Mov AX, 0xDEAD

In the following A5 BSOD:

0x03, 0xA6672420, 0xC0140008, 0x494E495F (_INI)

Device name is always 4 characters/bytes.
Would be possible to replace 0xA6672420 parameter with the Device to which the _INI method belongs to?

Maybe this could help us to diagnose/fix these BSODs, even with no debugging.

[Andalu]

@daniel_k

Hi Daniel,

also for me it is a pleasure to see you

My board is a Gigabyte H470-HD3

 

About the A5 BSOD, I got a bit different code (0x03, 0xA6671420, 0xC0140008, 0x494E495F) when I used another SSD disk containing the same XP installation.

 

Edited April 13, 2022 by Andalu

[Andalu]

@Dietmar

Tried to install XP from scratch on the GA-H470 board using a thumb drive with the ISO containing the acpi.sys from acpiV22freeDDBhack.7z package.

I still got the A5 BSOD (0x03, 0x85B68420, 0xC0140008, 0x494E495F).

The same XP ISO installs correctly on the asus prime B250M.

[Dietmar]

@Andalu

In this case, only Windbg over Lan can help.

@Mov AX, 0xDEAD wants to send you all files.

A lot of instructions you need also, I can help as good as I can

Dietmar

PS: As far as I remember, this Bsod happens for the very first time on 1200 chipsets, never before.

Edited April 13, 2022 by Dietmar

[Andalu]

@Dietmar

I received the first package from @Mov AX, 0xDEAD but until now I was not able to obtain the connection. Surely, I missed something in the configuration

Does Windbg work on your XP system? I had to switch to Win8.1 even if without success.

Edited April 13, 2022 by Andalu

[Dietmar]

@Andalu

Yes, all works under XP SP3, ultrafast, not a single crash of Windbg.

Via Serial Windbg crashes are normal.

Very funny, today I can compare the size of 3 acpi.sys files, build from the same XP SP1 Source code.

Win10 gives the biggest, then Win7 SP1 and much smaller under XP SP3.

 

Write an exact list, which steps you have done already.

I have also the for XP edited files for Windbg, that all registers can be seen etc., Patch from Blackwingcat,

so be sure, that it will work

Dietmar

Edited April 13, 2022 by Dietmar

[Dietmar]

@Andalu

Windbg needs
Microsoft .NET Framework 4 (full)

You also need the Symbol package for XP SP3 debug. Unpack the Symbols and set the path on left corner above of Windbg to those Symbol folder.
WINDOWSXP-KB936929-SP3-X86-DEBUG-SYMBOLS-FULL-ENU-DEBUG.EXE

https://archive.org/download/somewinxpdownloads

Dietmar

PS: boot.ini with content similar to this (NOT on the compi where windbg runs)

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /KERNEL=ntos3.exe /HAL=hal3.dll
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP SP3 DEBUG" /KERNEL=ntos3.exe /HAL=hal3.dll /DEBUG /DEBUGPORT=NET /HOST_IP=192.168.2.101 /HOST_PORT=50000 /ENCRYPTION_KEY=1.2.3.4 /CPUFREQ=3000 /TARGET_IP=192.168.2.103 /BREAK

 

To fix empty Register window of WinDBG, patch dbgeng.dll 6.3.9600.17200 (size= 2865840):

  `000ECEA2:       0B 00`

ntos3.exe and hal3.dll

https://ufile.io/u6x7fync

Edited April 13, 2022 by Dietmar

[Mov AX, 0xDEAD]

5 hours ago, daniel_k said:

@Mov AX, 0xDEAD

In the following A5 BSOD:

0x03, 0xA6672420, 0xC0140008, 0x494E495F (_INI)

Device name is always 4 characters/bytes.
Would be possible to replace 0xA6672420 parameter with the Device to which the _INI method belongs to?

Maybe this could help us to diagnose/fix these BSODs, even with no debugging.

@daniel_k

ACPIBuildCompleteMustSucceed() :

Quote

    ULONG               nextWorkDone    = buildRequest->NextWorkDone;
    ULONG               ParentName;

        ...

        //
        // Death
        //

        ParentName = AcpiObject ? (AcpiObject->pnsParent ? AcpiObject->pnsParent->dwNameSeg : 0) : 0 ;
        KeBugCheckEx(
            ACPI_BIOS_ERROR,
            ACPI_FAILED_MUST_SUCCEED_METHOD,
            (ULONG_PTR) ParentName,
            Status,
            (AcpiObject ? AcpiObject->dwNameSeg : 0)
            );

 

[Mov AX, 0xDEAD]

Quote

Besides that unresolved unknown AMLILoadDDB BSOD have we resolved all known ACPI BSODs?

@Damnation

I made list of unresolved issues at first post

[Mov AX, 0xDEAD]

9 hours ago, Dietmar said:

Now I am going to test an old Oracle VM box, where I can use only the pure XP SP3 CD.

On Oracle 5.2.44-139111 box you need to prepare your xp.iso more than on real compi with massstorage driver, acpi.sys, hal.dll syssetup.dll etc.

It works but this is hard job to prepare such a XP CD only for to make a naked xp.vhd from it.

I remember much nicer Qemu in 2012. Does anybody know, if there is a Qemu for XP as host today?

May be somebody here in MSFN who knows, which Oracle VM box was the last, which works with a normal XP Setup CD

Any VBox works with original XP install CD, select IDE Controller at Storage setting

Qemu.exe -M "pc" : emulates ACPI1.0 hardware with IDE controller

Qemu.exe -M "q35" : emulates ACPI2.0 hardware with SATA controller

All Qemu versions after v0.15 are incredible slow without HAX acceleration, but q35 emulation started since v2.x

with HAX acceleration i never run XP succefull, it just hangs or crash

[Dietmar]

@Mov AX, 0xDEAD

There was a Qemu version 15.50 which was fastest of all (year about 2012).

I succeed to run win95 with it on Raspberry Pi with sound and Lan and Moohrhuhn ;)).

The same for XP SP1, but sloww.

On newer Raspis I never tested again  even pupils asks me for that

Dietmar