Jump to content

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


Recommended Posts


Posted
30 minutes ago, Dietmar said:

@Mov AX, 0xDEAD

How big can the parts from a real DSDT be, that you can integrate in the DSDT from Qemu,

so that Qemu still works? Have you tested this?

And gives Qemu the same Bsod about failed to build DDB, when you run it with a zero size buffer in its given DSDT on a XP SP3 guest (Target)

1) I save current DSDT from any Windows under QEMU

2) This DSDT is base for modification, i dont change existing lines, only add new lines to any _INI method of any devices to check what i want

3) I didnt try to load DSDT from real hardware

4) Of couse QEMU shows same BSOD

Posted (edited)

@Mov AX, 0xDEAD

Was playing with Win7 SP1 WDK, compiling ACPI for both XP and 2003 environments.

Server 2003 as target OS seems to be a little more optimized and sections/data are packed tightly together.

Code is 99.999% the same, except for these:

Quote
XP as target OS (ugly unoptimized code):

cmp     dword ptr [edi+44h], 0
setnz   al
and     dword ptr [esi+1Ch], 0
test    al, al
jz      short loc_38DEC


Server 2003 as target OS (nice optimization):

and     dword ptr [esi+1Ch], 0
cmp     dword ptr [edi+44h], 0
jz      short loc_3A367

 

Quote
XP as target OS:

call    _ArbpGetRegistryValue@12
mov     esi, eax
cmp     esi, ebx
jl      cleanup_6
mov     esi, [ebp+info]
cmp     dword ptr [esi+4], 1
jnz     short loc_3904C

Server 2003 as target OS (another check for safety?!):

call    _ArbpGetRegistryValue@12
mov     esi, eax
cmp     esi, ebx
jl      cleanup_6
cmp     [ebp+info], ebx
jz      cleanup_6
mov     esi, [ebp+info]
cmp     dword ptr [esi+4], 1
jnz     short loc_3A5D1

 

Edited by daniel_k
Posted
3 minutes ago, daniel_k said:

@Mov AX, 0xDEAD

Was playing with Win7 SP1 WDK, compiling ACPI for both XP and 2003 environments.

Server 2003 as target OS seems to be a little more optimized and sections/data are packed tightly together.

Code is 99.999% the same, except for these:

ACPI.sys containts part from external arbiter.lib, this lib is little different when you switch target OS

I guess you shows code from this lib

Posted (edited)

@Damnation

Thanks for the tip ).

Here is answer from Intel about the Intel X540-T2 10Gigabit

Dietmar

The X540 uses an automatic MDI/MDI-X configuration. Intel recommends
using straight through cables. Where crossover cables are used, all four
pairs must be crossed. Using crossover cables where only some pairs are
crossed is not supported and might result in link failure or slow links.

Edited by Dietmar
Posted
18 minutes ago, Mov AX, 0xDEAD said:

ACPI.sys containts part from external arbiter.lib, this lib is little different when you switch target OS

I guess you shows code from this lib

Thanks for clarifying that.

By the way, with the latest fixes, I don't get any more crashes with Port 60/64 Emulation on my H310 board.
I've even added the all _OSI strings (up to "Windows 2020") to ACPI and no problems so far.

Posted
41 minutes ago, Mov AX, 0xDEAD said:

@Andalu

You reported about BSOD 0xA5 (0x03, ..., C0140008, ...) ValidateArgTypes(), do you still have this BSOD on your MBoards ?

is there another acpi.sys to try? The last acpi.sys working version is from @Dietmar with DBhack. Without the hack I got A5 bsod (0x11, 0x08, ..., 0x20160527)

Posted
41 minutes ago, Andalu said:

is there another acpi.sys to try? The last acpi.sys working version is from @Dietmar with DBhack. Without the hack I got A5 bsod (0x11, 0x08, ..., 0x20160527)

@Andalu

You can edit one source file (https://msfn.org/board/topic/183464-compiling-acpi-v20-driver-for-windows-xp-sp3-x32-only/?do=findComment&comment=1217375) and compile yourself to avoid BSOD (0x11, 0x08) or use compiled v4 by Dietmar (see post before)

i just remember you posted BSOD 0xA5 (0x03, ..., C0140008, ...) after we already found solution to this BSOD, so ask you to clarify current state

Posted

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

Posted (edited)

@daniel_k

With your modd about to fake the Win version, via acpi.sys V4

now on my Asrock z370 gaming k6 is a new acpi device found,

which I never saw before :P

Dietmar

PS: Its name is ACPI\INT33A1\1

which is first used in win8.1 as

Intel(R) Core(TM) 4xxxU and 4xxxY Processor Line Power Engine Plug-in

 

Edited by Dietmar
Posted
27 minutes ago, Damnation said:

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

@Damnation

With only one screen you need switch it from TARGET (selecting boot entry) to HOST (windbg), much better to use notebook as HOST with internal screen

See PM

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...