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

[reboot12]

Of course, if you patch the Windows file, you need to fix the checksum.

[K4sum1]

You should probably mention that in the post then.

[TheFighterJetDude]

9 hours ago, K4sum1 said:

For intelppm.sys, wouldn't you need to update checksum for Windows to accept the driver? Or is this a only a post-Vista behavior?

Might only be Vista+, I just hex edited the driver replaced it and it works great !

[K4sum1]

On Mon Nov 13 2023 (GMT+0000) at 4:01 PM, K4sum1 said:

Same issue with another Dell Broadwell laptop, this time the E7250.

Anyway to fix pls

[Jakob99]

2 hours ago, K4sum1 said:

Anyway to fix pls

I got this error on a Dell Inspiron 15 3542 laptop with Haswell, even with modded ACPI. The ACPI.sys I tried was given to me by K4sum1, and I know it works properly, as I've used this successfully on my Acer Aspire A315-21 (long gone). The BIOS is American MegaTrends APTIO Setup Utility. UEFI is disabled, Fastboot is disabled, USB is plugged into USB2 port... I know XP works perfectly on Haswell as I've gotten it to install with no ACPI mods needed on my long-gone Inspiron 3847 desktop tower (I'm wondering if a few of those were originally made with Ivy Bridge before they stuck Haswell in them. I know they have a few with AMD inside).

[Dietmar]

@K4sum1

I think, that the original acpi.sys has been copied back.

This acpi Bsod is now impossible with the last acpi.sys from Ramsey

Dietmar

[K4sum1]

17 hours ago, Dietmar said:

@K4sum1

I think, that the original acpi.sys has been copied back.

This acpi Bsod is now impossible with the last acpi.sys from Ramsey

Dietmar

I don't think so. Can you give me that acpi.sys pls? (for 5.2 x64)

[Dietmar]

@K4sum1

Here it is. This was the latest one,

that I build from Sources

Dietmar

https://ufile.io/zkdrmcs7

[K4sum1]

3 hours ago, Dietmar said:

@K4sum1

Here it is. This was the latest one,

that I build from Sources

Dietmar

https://ufile.io/zkdrmcs7

I just tried it and I got the same BSOD. I'm booting an installer and I replaced ACPI.SY_

[Dietmar]

@K4sum1

This kind of Bsod is not possible with this acpi.sys

Dietmar

[user57]

im maybe the wrong person to ask for a bug in this .sys file

there used to be something in the background services that backup files if they dont have the same checksum, it then used the backup file

if not windows make use of the backup file

 

drivers have 2 checksums that crc32 (pe header) check and a other driver signature checksum 

from what i remember but in xp the second driver signature wasnt important, but if that crc32 checks fail it wont load the driver

 

 

for replacing system files mircosoft use a "rename after boot" 

("SYSTEM\\CurrentControlSet\\Control\\Session Manager")

you have to create a REG_DWORD = 1 to that is called AllowProtectedRenames

there is a key(string) that is named "PendingFileRenameOperations"

here you can set your system file renames

 

that useally what the installer do (if you use a KBXXXXXX upgrade you can see what entrys it made at this place)

microsoft use the MoveFileEx function (what do exactly this) with parameter MOVEFILE_DELAY_UNTIL_REBOOT

 

i do not know if that helps

[K4sum1]

3 hours ago, Dietmar said:

@K4sum1

This kind of Bsod is not possible with this acpi.sys

Dietmar

 

In case it was funny setup bug, I did the first part of install on T430, swapped SSD, and did the ACPI mod afterwards.

 

https://files.catbox.moe/av6dtu.mp4

 

 

Edited July 18 by K4sum1

[D.Draker]

4 hours ago, user57 said:

in xp the second driver signature wasnt important, but if that crc32 checks fail it wont load the driver

You're right, I always rebuild the checksum when I mod the drivers. It could be done with CFF Explorer.

Look on how at my nVidia modding tutorials Part 1.

[user57]

looking the first page it says it has that 0xA5 error maybe not the exact code

do you maybe got the test for 32 bit ? to me it seems the list of error codes seem to be less for 32 bits

[Dietmar]

@K4sum1

I just see, that the acpi BSOD 03 is in acpi.sys bit64 other handled as in acpi.sys bit 32.

Here comes now the crazy hacked XP SP2 bit 64 version, where to 100% THIS BSOD never will happen again

Dietmar

PS: I find also the reason for this Bsod: C0140008 but I cant locate the exact place, where it happens:

ValidateArgTypes or CreateField or ObjTypeSizeOf.

This is a really evil Bsod. Maybe idea for hack from Skull is better

- 0xA5(0x03, ..., C0140008, ...) DSDT code have operation with unexpected type of arguments, partially solved
    This BSOD probably means some argument has datatype, allowed only in ACPI 2.0
        Patch:
        - _ValidateArgTypes must always return "OK", even on realy wrong types
          (mov edi, 0xC0140008=>mov edi, 0x00000000 at head of _ValidateArgTypes)

https://ufile.io/sepw9iul

and the much more nice solution from Skull

https://ufile.io/u42mdknr

or this one, only modded for ValidateArgTypes

https://ufile.io/463tiqvh

Edited July 18 by Dietmar