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

[Andalu]

@Mov AX, 0xDEAD

the A5 bsod (0x03, ***, 0xC0140008, 0x494E495F) was solved with one of the first acpiv2 releases. It had worked for all my boards except the GA-H470 for which I still got the a5 bsod with code (0x11, 0x08, ***, 0x20160527), as already reported here:
https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-x32-only/?do=findComment&comment=1216248

Now, also this bsod is solved with the acpi.sys V4.

So far, following your guide I was able to get only acpi.sys but modifying its code is still out of my reach, at least until now it is so .... never say never

Thanks

Edited April 24, 2022 by Andalu

[reboot12]

4 hours ago, genieautravail said:

With Intel HD graphics 3000 disable or not, I can't start the AMD graphics card (code 10 error).

You need to disable Intel 3000 card in bios instead in WinXP.

[genieautravail]

5 hours ago, daniel_k said:

If Kernel-Mode Driver Framework (KMDF) version 1.11 was installed, try to install Intel USB3 driver:
https://downloadmirror.intel.com/22824/eng/intel(r)_usb_3.0_extensible_host_controller_driver_5.0.4.43_v2.zip

I have installed  7 again from 0 and resolved the previous issues.

Before, I have installed some updates and drivers (video, network and chipset) and made a disk image.

By installing the chipset driver, I can see in the devices manager the famous 1E31 device and install and start the Modded USB3 from MDL

With the Modded USB3 from MDL and the Intel USB3 HCSwitch driver, each time I plug an USB device in one of the USB3 port, I get a BSOD and laptop restart.

After that I have restored the disk image and installed the official Intel USB 3.0 driver for 7.

With the official driver, no more BSOD and I can plug and use at full USB3 speed all my USB devices, even the problematic USB flash drives.

Regards

 

.

 

 

[Mov AX, 0xDEAD]

1 hour ago, Andalu said:

The only yellow mark that resists every version is this:

https://anonfiles.com/7ds2R2Z2x0/Yellow_mark_resource_png

Not a problem, it is there since I have the GA-H470 but it never bothered me

@Andalu

Please take screenshot of Resource tab too

Seems it is again IOTRAP device, we already have workaround for it, but probably H470 has another definition

[George King]

 

@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?

Edited April 24, 2022 by George King

[Mov AX, 0xDEAD]

16 minutes ago, George King said:

Now my laptop (Asus K53SV) can detect and install secondary GPU without any issues. Thanks for v4!

true v4 is just zero length buffer workaround, apparently it's about upgraded _OSI by Daniel, so be carefull, your DSDT hides secondary GPU for XP/2003

[daniel_k]

1 hour ago, genieautravail said:

With the Modded USB3 from MDL and the Intel USB3 HCSwitch driver, each time I plug an USB device in one of the USB3 port, I get a BSOD and laptop restart.

Please do one last test.

Install Win7 and the Modded USB3 from MDL.

Do not install the Intel USB3 HCSwitch driver.

Can you dump the DSDT from ACPI tables using RWEverything?
http://rweverything.com/download/

[George King]

10 minutes ago, Mov AX, 0xDEAD said:

true v4 is just zero length buffer workaround, apparently it's about upgraded _OSI by Daniel, so be carefull, your DSDT hides secondary GPU for XP/2003

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

[daniel_k]

14 minutes ago, Mov AX, 0xDEAD said:

true v4 is just zero length buffer workaround, apparently it's about upgraded _OSI by Daniel, so be carefull, your DSDT hides secondary GPU for XP/2003

With enough testing, do you think we can add the new _OSI to our "official" source?

Edited April 24, 2022 by daniel_k

[Andalu]

@Mov AX, 0xDEAD

here the shot for the resource tab:

https://anonfiles.com/9aI0TaZ1x0/ResourceTab_png

[Mov AX, 0xDEAD]

5 minutes ago, daniel_k said:

With enough testing, do you think we can add the new _OSI to our "official" source?

I think better to split 1) Windows 7/8/8.1/10 EMULATION and 2) LEGACY XP

Question is which variant is preferrable...

When i see code like this, i want to use only Legacy XP

Quote

    Scope (_SB.PCI0.GFX0)
    {
        Method (_DEP, 0, NotSerialized)  // _DEP: Dependencies
        {
            If ((S0ID == One) || (OSYS >= 0x07DF))
            {
                Return (Package (0x01)
                {
                    PEPD
                })
            }
            Else
            {
                Return (Package (0x00) {})
            }
        }
    }

for XP _DEP() returns empty package (if S0ID != One)

for Windows10 _DEP() return depended package PEPD

PEPD is big device with a lot of sub-packages inside

Quote

  Scope (_SB)
    {
        Device (PEPD)
        {
            Name (_HID, "INT33A1" /* Intel Power Engine */)  // _HID: Hardware ID
            Name (_CID, EisaId ("PNP0D80") // _CID: Compatible

            Name (_UID, One)  // _UID: Unique ID
            Name (PPD0, Package (0x03)
            {
                "\\_SB.PCI0.SAT0",
             ....

with EMULATION version, XP must handle this garbage and nobody know how correctly

[Mov AX, 0xDEAD]

21 minutes ago, Andalu said:

@Mov AX, 0xDEAD

here the shot for the resource tab:

https://anonfiles.com/9aI0TaZ1x0/ResourceTab_png

Thanks, this is not IOTRAP device, it is LDRC and have conflict with some else

Quote

 Scope (_SB.PCI0)
    {
        Device (LDR2)
        {
            Name (_HID, EisaId ("PNP0C02") )  // _HID: Hardware ID
            Name (_UID, 0x02)  // _UID: Unique ID

Quote

Scope (_SB.PCI0.LPCB)

    Device (LDRC)
        {
            Name (_HID, EisaId ("PNP0C02") )  // _HID: Hardware ID
            Name (_UID, 0x02)  // _UID: Unique ID
 

probalby this is problem, but parents are different....

Edited April 24, 2022 by Mov AX, 0xDEAD

[Dietmar]

@daniel_k

Can you remember, for the acpi.sys version 6666 you make different kind of Win versions hack (1, 2, 3, 4).

Do you know, which was the best acpi.sys 6666 from those tests

Dietmar

[Dietmar]

There is another interesting thing,

what can be tested with the new acpi.sys V4.

I remember, that on newer DSDT table,

before with acpi.sys version 6666 I got Bsod when I load this acpi table via

asl /loadtable dsdt.aml

Before, the  asl Tool vers 4 or vers 5 fails with BSOD 0x000000A5 (0x00000003, xxx, C0140001, yyy) after uploading a working DSDT table for Acpi.

Always when you load a DSDT table via asl /loadtable from Skylake above

you get this Bsod with acpi.sys 6666.

When this Bsod can be solved, it will be much more easy to upload any DSDT table to XP,

because XP SP3 listens to registry entry for DSDT (or FACP etc.). Winserver 2003 listens only to Bios DSDT.

Dietmar

Edited April 24, 2022 by Dietmar

[Dietmar]

I just make the test for the new acpi.sys V4 and asl.exe version 5.

I change the DSDT table on the Asrock z370 gaming k6 board against its own(!) one.

But on next reboot I got this Bsod which looks very similar to the famous

0x7E(c0000005, ...) error in AcpiArbCrackPRT()

Dietmar

 

Edited April 24, 2022 by Dietmar